Public bug reported:
I'm not sure if ubuntu-friendly cares about collecting information from
systems that aren't running the standard Unity/Gnome desktop, but in
case you do, I encountered some minor problems trying to run it on my
relatively lightweight Openbox setup:
- Missing package dependency on python-dateutils (that's a real bug, so
I reported it separately).
- The automatic SD card test didn't work, just sat there forever. I
guess it was waiting for some kind of automount service to do something
with the card. It didn't time out after 10 seconds as it said it would,
either. After a minute or two of waiting to see if it would do
something, I gave up and clicked Yes (since Ubuntu does handle the SD
card reader hardware, hooray).
- Same for the automatic USB stick test -- nothing happened after I
inserted the stick, so after a while I clicked Yes.
- The wireless test was greek to me since it's all based on wording that
presumably appears on the standard desktop. I wasn't sure exactly what
was being tested. I clicked Yes since wireless more or less works
(though it's flaky and seldom connects on the first try, and I have to
retry several times no matter what software package I use to make the
connection).
- When I reviewed the results before uploading, I discovered that a lot
of tests had failed because of missing packages like alsa-base. I would
have been happy to install these packages if I'd known they were needed,
and re-run the tests, but there's no way to know about the failures
until the whole suite of tests is finished. Maybe an optional status
window I could look at so I could see when things were failing due to
something I could fix?
- At the end, I guess (hope) it sent the information correctly, but
there wasn't any feedback, so I'm not sure and have no idea how to find
out. It would be very helpful if it printed "Uploading results ..." and
"Results uploaded successfully!" or something like that. In general,
there wasn't much status info about when it was busy vs. when I needed
to do something. (And the status bar, dark blue on dark grey, is almost
invisible even when it's present.)
- After a few minutes I gave up waiting and clicked the windowmanager 'x' to
close the window. At exit, it printed
/usr/bin/checkbox-qt: line 26: 6085 I/O possible python
$CHECKBOX_SHARE/run "$@" $CHECKBOX_SHARE/configs/$(basename $0).ini
[2] + exit 157 checkbox-qt
- General UI comment: I found it confusing trying to guess when I was
supposed to click Yes or No versus when I was supposed to click Next to
skip a test (e.g. firewire, which this laptop doesn't have), especially
since Next is in a completely different place from Yes and No. It would
be helpful if tests gave suggestions like "If you don't have firewire,
please click Next."
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: checkbox-qt 0.13.7
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic i686
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
CheckboxSubmission: 59f5c4278a96c566305a5aafb84ff28a
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Jul 25 13:17:53 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
ProcEnviron:
TERM=xterm
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/usr/bin/zsh
SourcePackage: checkbox
UpgradeStatus: Upgraded to precise on 2012-05-07 (79 days ago)
** Affects: checkbox (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
