Version: 3.3 (using KDE 4.3.2) OS: Linux Installed from: Debian testing/unstable Packages Running juk from a terminal window, it forks and reports as it rescans my music directories (apparently successfully.) A popup is displayed saying "Phonon: KDE's Multimedia Library/The audio playback device VIA 82C686A/B rev50 with CS4299 (VIA 82C686A/B rev50) does not work./Falling back to default." This goes away and the 'scanning' messages finish scrolling. But no Juk window shows up. If at this point I strace -p to the juk process, I find it waiting in poll() on some event or other. I can move the mouse around, changing focus to unrelated windows (they're all unrelated since Juk never presents its own window here) but the Juk process receives some notification each time, runs a little, and then goes back to sleep ... but where's the Juk window? If it matters, I'm not at this moment running KDE as my desktop as I find plasma to be a rather pointless abuse of system resources. But it's all properly installed and up-to-date. I also tried running 'juk foo.mp3' while in this state and Juk crashes, but for the time being let's call this probably unrelated.
Mh, the crash sounds like an already reported issue about "crash when second instance is started". Juk could be on the SystemTray, and on KDE4.3 it should be using the old/standard FDO systemtray protocol. So the fact that Plasma is not running should not affect that (in fact, it should never affect it). Just in order to test, could you bring up Plasma and then start Juk ? (Note that I'm not a Juk developer and I don't know its code, I'm just guessing) Regards
It happens to me too, and I'm using kde4 with plasma and all. I've also experienced some random crashes when closing the app. I'm using mandriva 2010.0 kde 4.3.2 which has some backports from 4.3.3 to fix juk crash, but it still crashes somtimes :)
i have no window with juk when i have the current song plasmoid enabled in the plasma Without launch juk , it has juk in the backend allready.
@Dave: any news about this ?
Created attachment 38837 [details] Config files which, when in place, cause juk to not start properly
Thinking about this last night, I wondered if maybe there were too many mp3s in my collection. So just now I moved aside ~/.kde/share/config/jukrc and ~/.kde/share/apps/juk/playlists and started juk, which came right up. Then I added back my music directories, quit and restarted. This also worked. I'm not sure if the priority should change, though, since what happens to one person can happen to many others. Thus attached find a tarfile of the conf files which did _not_ work. Perhaps some of you could try installing them and see whether juk will fail to initialize.
for me this solves the problem i have only a crash at exit (i will reply with full debbug)
In my case, when StartDocked=true in the configuration file, the gui won't show, not even the icon in the systray, which is the expected behaviour. If the variable stays false, no problem, that's why at the moment when I fully exit juk I do it without juk being docked. And of course, that random crash on close, which I guess it is a separated bug, but it is annoying too.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
I remember this bug and fixed it a few years back. Though I don't seem to have made it easy to find the commit that did it.