[DO NOT REOPEN!] jockey-gtk times out on startup on hardware detection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Jockey |
Fix Released
|
High
|
Martin Pitt | ||
jockey (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
it is the 5th time it happens at boot up time
what else should i add ?
valgrinid or traceback is needed ?
how should i do that at boot time ?
ProblemType: Crash
Architecture: i386
Date: Wed Jul 30 14:14:08 2008
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.5
Package: jockey-gtk 0.4+r345-0ubuntu1
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.26-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner vboxusers video
Changed in jockey: | |
importance: | Undecided → High |
Changed in jockey: | |
assignee: | nobody → pitti |
status: | Confirmed → In Progress |
Changed in jockey: | |
status: | In Progress → Fix Committed |
status: | In Progress → Fix Committed |
Changed in jockey: | |
status: | In Progress → Fix Released |
Changed in jockey: | |
assignee: | pitti → cyklisten |
Changed in jockey (Ubuntu): | |
status: | Fix Released → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in jockey (Ubuntu): | |
status: | Fix Released → Fix Committed |
Changed in jockey (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in jockey: | |
status: | Fix Released → In Progress |
status: | In Progress → New |
Changed in jockey (Ubuntu): | |
status: | Fix Released → Confirmed |
status: | Confirmed → Fix Committed |
Changed in jockey: | |
status: | New → Fix Released |
Changed in jockey (Ubuntu): | |
status: | Fix Committed → Fix Released |
assignee: | cyklisten (cyklisten) → Martin Pitt (pitti) |
This crash has the same stack trace characteristics as bug #251347. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.