Version: amarok-2.1.1-1.fc11.i586 (using KDE 4.2.4) OS: Linux Installed from: Fedora RPMs In Amarok 1.X, the splashscreen disappeared when I clicked it. In 2.X, in both Fedora 10 and Fedora 11, it does not, making my desktop nearly useless for the whole time Amarok spends starting up. I initially filed this in Red Hat's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=510356 but was told that it would be best reported here anyway. I was also told by at least one person that they aren't seeing this problem, and yet I've had it under two different versions of Fedora now, so I figure it's worth reporting.
In the unlikely event that this is relevant, I am using Amarok in a Gnome environment (as I had under previous versions where I did not have this problem)
Indeed, this has never been reported so far, so either this is a packaging issue of Fedora, or related to you using Gnome, but that has not been reported so far neither. If you say the "whole time Amarok takes to start up", how long is this? It should not take more than 2 or 3 seconds.
Just quit and re-started Amarok and timed it. Splash screen displayed for 39 seconds. =:( Have 9.768 tracks in the db, in case that explains it.
Most unlikely, 39 seconds definitely is too long. I have about the same amount of tracks in the database, and it doesn't take more than 4 seconds to be fully responsive, using 2.2-git it on KDE 4.2.96 though. But even with 2.1.1 there was never such a delay IIRC. And I was always able to click on the splash screen to make it disappear. I wonder if there is something else that could cause this delay. Could you please start amarok in a console with the --debug option and paste the console output here?
Well, that's just weird. After having had this problem for months, across two vesions of Fedora, I ran Amarok from the command line and it started in just a few seconds. Then I tried starting it from the GUI, and again it started in just a few seconds. I haven't been able to duplicate the delay yet. Will have to see if it comes back the next time I reboot, I guess.
Closing for now, feel free to reopen the bug if necessary.
Created attachment 35812 [details] amarok --debug output Finally got a capture of the --debug output during one of the times when Amarok took a long time to start. Maybe a DBUS issue? This is the output of me starting and then quitting the application.
Not sure what the appropriate thing to set it to now is, so I'm leaving it RESOLVED.
Pasting inline is easier to read: kdeinit4: preparing to launch /usr/libexec/kde4/klauncher kdeinit4: preparing to launch /usr/bin/kded4 kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kdeinit4: preparing to launch /usr/libexec/kde4/kconf_update Object::connect: No such signal KLineEdit::downPressed() QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified amarok(3545)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) amarok(3545)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0) HTTP GET "http://post.audioscrobbler.com/?hs=true&p=1.2.1&c=ark&v=2.1.1&u=usernamenumber&t=1249303720&a=b8a1a72ba08f3ecb4bac0efda7e7c735&api_key=402d3ca8e9bc9d3cf9b85e1202944ca5&sk=035caf58af6e291644587395e101dcc8" Couldn't resolve property: linearGradient5167 link XMLID_9_ hasn't been detected! Couldn't resolve property: linearGradient3563 link XMLID_9_ hasn't been detected! link XMLID_9_ hasn't been detected! link XMLID_9_ hasn't been detected! <unknown program name>(3542)/: Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " kdeinit4: preparing to launch kdeinit4: preparing to launch kdeinit4: preparing to launch kdeinit4: preparing to launch kdeinit4: preparing to launch kdeinit4: preparing to launch /usr/libexec/kde4/kio_http_cache_cleaner kdeinit4: preparing to launch /usr/libexec/kde4/kio_http_cache_cleaner kio_http_cache_cleaner: Already running! kdeinit4: preparing to launch "OK 96fbbc78ac69415f9f24f28602e5ddda http://post.audioscrobbler.com:80/np_1.2 http://post2.audioscrobbler.com:80/protocol_1.2" Caught an exception - perhaps the web service didn't reply? "Unexpected empty text node: age" amarok(3545): Couldn't start knotify from knotify4.desktop: "Could not find service 'knotify4.desktop'." amarok(3545)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "The name org.kde.knotify was not provided by any .service files" Object::disconnect: Unexpected null parameter Object::disconnect: Unexpected null parameter Object::disconnect: Unexpected null parameter QCoreApplication::postEvent: Unexpected null receiver
Hrmm.. hadn't noticed the scrobbler link when I initially posted this. Does it expose anything more sensitive than my username? If so, is there anything I can do about it?
Sorry, from your log it's not really clear why startup takes so long (resulting in blocked UI). There could be something wrong with your KDE installation. Do other KDE 4 applications show similar problems? At any rate, I'm closing the report for now, as there is nothing we could do from our side. The log does not indicate an Amarok bug per se.