[Bug 66924] behaves poorly when a previous instance has frozen
Sam Morris
sam at robots.org.uk
Thu Oct 19 13:15:40 UTC 2006
Public bug reported:
Binary package hint: rhythmbox
My Dad asked me to take a look at his computer because he couldn't start
Rhythmbox. Launching it from the Applications menu resulted in the
'please wait' mouse cursor with no activity. Running it from a shell
with --debug revealed that it was trying to contact a previous instance
that had apparantly frozen.
The workaround was to kill all 9 or so rhythmbox processes in the system
monitor.
It would be better if rhythmbox would have a 5 second timeout for trying
to contact a previous instance; if the timeout is reached, put up a
dialog explaining the situation, along with a button that kills all
rhythmbox instances and launches a fresh one.
** Affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
behaves poorly when a previous instance has frozen
https://launchpad.net/bugs/66924
More information about the desktop-bugs
mailing list