Bug 149444 - amarok won't start if Rio isn't mounted
Summary: amarok won't start if Rio isn't mounted
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: Playlists/Saved Playlists (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-01 07:56 UTC by Harri
Modified: 2008-08-06 00:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harri 2007-09-01 07:56:52 UTC
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
Comment 1 Jeff Mitchell 2007-09-01 19:51:48 UTC
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.
Comment 2 Harri 2007-09-01 23:27:20 UTC
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?
Comment 3 Jeff Mitchell 2007-09-03 04:06:35 UTC
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?
Comment 4 Harri 2007-09-03 09:14:25 UTC
Yes.
Comment 5 Jeff Mitchell 2007-09-03 16:25:08 UTC
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.
Comment 6 Harri 2007-09-03 19:18:33 UTC
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
Comment 7 Jeff Mitchell 2007-09-04 13:16:04 UTC
Amarok died at 99% of what scan?
Comment 8 Lydia Pintscher 2008-08-06 00:48:05 UTC
closing due to lack of feedback