Version: 1.4.7-1+b1 (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages OS: Linux If I connect to a Rio Karma, exit Amarok without disconnecting it, unmount the Rio, and start Amarok again, then it won't start. Error messages on the tty: Amarok: [Loader] Starting amarokapp.. Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. kbuildsycoca running... kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x9b36b0 ): KAccel object already contains an action name "play_pause" QLayout "unnamed" added to QVBox "unnamed", which already has a layout kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x9b36b0 ): KAccel object already contains an action name "play_pause" QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow QObject::connect: Incompatible sender/receiver arguments StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&) * Libkarma warning: no device-settings file ** Libkarma error: utime() failed kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) This is pretty annoying, if you forget your Rio at work. Is there some failsafe mode to disable all connected devices? Regards Harri
This might be a libkarma issue...if it's not properly disconnected it may fail to initialize. The only reason this would be an Amarok issue is if the rio karma device is storing its state in ~/.kde/share/config/amarokrc and thinking it's already mounted. I'd watch that file as you test and see if there are entries in there for the karma that seem to indicate its connection state.
Here is the amarokrc.diff before and after configuring the Karma as a Media device: --- /export/harri/.kde/share/config/amarokrc.bak 2007-09-01 21:20:39.000000000 +0200 +++ /export/harri/.kde/share/config/amarokrc 2007-09-01 23:19:57.000000000 +0200 @@ -1,5 +1,5 @@ [BrowserBar] -CurrentPane=CollectionBrowser +CurrentPane=MediaBrowser Width=295 [Collection] @@ -55,6 +55,9 @@ [HTML Settings] AutomaticDetectionLanguage=0 +[MediaBrowser] +manual|Karma|/rio=riokarma-mediadevice + [OSD] New Playlist Items Color=255,208,0 (Sorry for the line breaks.) Of course both snapshots were made when Amarok was not running. The "after" version doesn't work if the Karma is not mounted. Is this expected?
So if the Karma isn't mounted, and Amarok isn't starting, and you replace the "after" version with the "before" version (changing nothing else on your system) and start Amarok, the problem goes away?
Yes.
What happens if you are in the "after" scenario (where Amarok isn't starting) and you change the line CurrentPane=MediaBrowser to CurrentPane=CollectionBrowser Does it work then? I'm trying to figure out if the issue is caused by the MediaBrowser being shown at startup, or from simply having that entry.
When I tried to register my Rio as an external device Amarok died at 99% of the scan. It said QComboBox::setCurrentItem: (speakerComboBox) Index 1 out of range Amarok restarted fine (/rio still mounted). Then I left Amarok, unmounted /rio, and set CurrentPane=CollectionBrowser in amarokrc. This did not work. Amarok did not start, as before. Regards Harri
Amarok died at 99% of what scan?
closing due to lack of feedback