Public bug reported:
I guess this is an amrok bug, though I'm not really sure. The symtoms are as
follows:
I have my music stored on a usb drive (WD MyBook) and use Amarok to manage my
music in Gnome. This all works fine until I quit Amarok, which causes my usb
drive to spin up for a second, then the icon for my harddrive disappears from
the desktop, though oddly any icons for CDs or other physical drives remain. If
I look in /media the external drive is no longer listed. If I restart hal (sudo
/etc/init.d/hal restart) the device shows up again. So far no data corruption
has occured, and the device appears to think that it is still connected, even
after its icon disappears (the lights stay on). My guess is that Amarok and the
kde support services it brings with it think that the computer is shutting down
and this causes one of the components to shut hal down. Either that or
something bad happens and hal crashes. dmesg gives me nothing. If I start
amarok from the command line I get the following:
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has
gone wrong?
[EMAIL PROTECTED]:~$ QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to
KHTMLPart::slotActiveFrameChanged( KParts::Part * )
DCOP aborting call from 'kded' to 'klauncher'
kded: ERROR: : couldn't create slave : Cannot talk to klauncher
** Affects: amarok (Ubuntu)
Importance: Undecided
Status: New
--
Amarok shuts down hal
https://bugs.launchpad.net/bugs/191370
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
