checkbox does not notice if its backend does not start

Bug #334893 reported by Andy Whitcroft
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
High
Marc Tardif
checkbox (Ubuntu)
Fix Released
High
Marc Tardif

Bug Description

If the checkbox backend cannot start for any reason (here it had no dbus permissions) it will die with an error but the front end continues without noticing the backend is not there. No tests are found or run but the collection and reporting phases run. This is tremendously confusing.

The frontend should notice if the backend explodes and tell the user. It should also notice if its dbus messages are going nowhere.

Related branches

Revision history for this message
David Murphy (schwuk) wrote :

Confirmed.

Changed in checkbox:
assignee: nobody → cr3
status: New → Confirmed
Revision history for this message
David Murphy (schwuk) wrote :

Note that this behaviour is currently only seen when using a branch or tarball, not if the package (>= 0.6) has been installed or the setup procedure followed.

Revision history for this message
David Murphy (schwuk) wrote :

It seems that this bug is reproducible using the 0.7 package in Jaunty. arky reported the following when confirming that another bug had been fixed:

> When started it shows two screens only. One main system testing menu
> and when you click next it will build the report and ask to provide
> email address so that it can submit the report. I guess there is a
> pre-built report lying somewhere on the disk that's why it doesn't do
> the tests.
>
> Also if you close the window by clicking the close window icon it close
> with this warning.
>
> 2009-03-18 19:15:56,015 CRITICAL

Changed in checkbox (Ubuntu):
assignee: nobody → cr3
importance: Undecided → High
milestone: none → ubuntu-9.04-beta
status: New → Confirmed
Changed in checkbox:
importance: Undecided → High
milestone: none → 0.7.1
Revision history for this message
arky (arky) wrote :

Thanks Dave, one more thing while updating to 0.7 I get a warning.

dpkg: warning - unable to delete old directory `/var/lib/checkbox': Directory not empty

Does it make much difference if an old 'submission.xml' is present in this directory.

Revision history for this message
Marc Tardif (cr3) wrote :

No, /var/lib/checkbox should no longer be used with the introduction of policykit support. The difference is that the CHECKBOX_DATA which was previous set to that path should now be set to ~/.checkbox. So, the xml report will be generated under a subdirectory of the home.

David Murphy (schwuk)
Changed in checkbox (Ubuntu):
milestone: ubuntu-9.04-beta → none
Changed in checkbox:
milestone: 0.7.1 → 0.8
Marc Tardif (cr3)
Changed in checkbox:
milestone: 0.8-alpha2 → 0.8-alpha4
Revision history for this message
Рустам Second_Fry Губайдуллин (secondfry) wrote :

Getting this error in 10.04 Lucid Lynx.

krypt@krypt-laptop:~$ checkbox-gtk --version
0.8.6

But in synaptic I can see that 0.9 version is installed.

File /home/krypt/.cache/checkbox/submission.xml contains "untested" in all fields. (unsupported in 2 fields)

Revision history for this message
Daniel Manrique (roadmr) wrote :

Checkbox has been using a backend communicating through named pipes for a while now, thus the dbus problems should be gone altogether. Also, the development version now tries a few times to start the backend via sudo (in truth, gksudo should handle reprompting the user, but we work around bug 773284 while being a bit more forgiving) and tries to check for a working backend before asking it to run any tests.

If no working backend is found, the tests will be marked as failed indicating that the test couldn't be run with a short explanation.

See the attached branch for the relevant code.

I'll thus mark this bug as Fix Committed.

Thanks!

Changed in checkbox:
status: Confirmed → Fix Committed
Changed in checkbox (Ubuntu):
status: Confirmed → Fix Committed
Ara Pulido (ara)
Changed in checkbox:
status: Fix Committed → Fix Released
Changed in checkbox (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.