You are not logged in.
Pages: 1
Just updated to KDE 4.10. The multi-media player, Juk, takes about 20 seconds from launching to appearing in the system tray. Previously it would be there right away.
Console output while loading:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Object::connect: Attempt to bind non-signal LyricsWidget::setShown(bool)
Once the time is up the command prompt reappears and Juk is in the system tray as normal.
Juk still functions normally as before, it just takes quite the while to start up now. Perhaps something needs to "time out"?
Offline
Well, no confirmations or solutions. I did an extra step of deleting ".kde4" in my home folder. So, starting with a fresh configuration the issue still persists. If no one has any further suggestions then this issue, for myself, is tolerable - Juk still works albeit just takes a bit longer to load - and we'll just have to leave it at that.
Offline
I can confirm that bug. Even starting with a clean user reproduces the problem.
Offline
I have exactly the same bug, Juk startup take very long time, sometime Amarok also have this problem waiting for a solution.
Offline
when I startup Juk in console, I got this info:
session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Object::connect: Attempt to bind non-signal LyricsWidget::setShown(bool)
[0x1c180e8] main services discovery error: no suitable services discovery module
Last edited by silenceleaf (2013-03-16 00:53:16)
Offline
Pages: 1