Thanks for your comments! They are appreciated, I'm just very surprised
that you have so many failures that nobody else has.
Some of the tests whose hardware you don't have are shown because said
hardware is not detectable (either that or we haven't gotten around to
autodetecting it; I think it'd be possible with firewire). So checkbox
shows you the test but if you don't have the hardware you are expected
to just skip the test. This is normal behavior.
So your system lacks udisks, it also lacks alsa-base, and x-www-browser
doesn't point to a usable browser. This is not normal for a default
Ubuntu installation. You also mention "I'm not running a desktop that
does notifications", which further points to the fact that your
environment is somewhat idiosyncratic.
Developing checkbox scripts that work under every imaginable user
configuration and combination would be extremely time-consuming, so it's
probably not something we would be able to do (patches welcome,
though!). Perhaps a reasonable solution would be being clearer in test
requirements so they don't run if you don't have, say, udisks or alsa-
base (hey, not running beats running and crashing!).
I'll set this as Triaged since we know what to do (both this comment and
#2 are a good indication of that: making sure that package requirements
are as explicit as possible so that behavior doesn't seem too erratic on
systems not running unity and/or gnome).
** Changed in: checkbox (Ubuntu)
Status: New => Triaged
** Changed in: checkbox (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029113
Title:
checkbox-qt issues running on nonstandard desktops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1029113/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
