Summary: | Amarok crashed during KDE session restore after login (volumefadereffect) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Phonon | Reporter: | Thilo-Alexander Ginkel <thilo> |
Component: | Xine backend | Assignee: | Matthias Kretz <kretz> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, jagevi1, jmwagner, mail, martin.sandsmark, maximiliano, mirceasava, sam.khawse |
Priority: | NOR | ||
Version: | 4.3.0 (KDE 4.2.0) | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
phonon-xine log
ksystemsettings screenshot |
Description
Thilo-Alexander Ginkel
2009-11-11 04:54:39 UTC
My apologies if this is a duplicate of an existing bug. The crash is reproducible, so if you would like me to change anything and reproduce the issue, please let me know. Not much we can do about, since this is a crash in Xine. Martin? The backtrace is related to bug 188602, which states that reintalled xine "fixed" the issue.. Could you check this ? (you need to reinstall the "libxine1" and "phonon-xine" packages (I'm not really sure if this are the proper names)) Thanks Created attachment 38274 [details]
phonon-xine log
Unfortunately, re-installing libxine1, libxine1-bin and phonon-backend-xine did not help.
I had a look at the xine and Phonon source code, though.
Before hitting xine_interface.c:875
xine_post_input (this_gen=0x0, name=0x7f7371386db9 "parameters")
(which segfaults because this_gen is null) the code tried to create a new plugin instance by calling
xine_post_init(m_xine, "KVolumeFader", 1, &audioPort, 0);
So, apparently the instantiation of the KVolumeFader did not work.
I enabled xine's debug logging by setting PHONON_XINE_VERBOSITY=255. This resulted in the attached output.
So, apparently, Phonon tries to access an unnamed output device (probably my onboard audio, which mysteriously disappeared).
Is there any way to get rid of this spurious entry? I already deleted my phonondevicesrc and it was re-created without the spurious entry, but I can still see the unnamed entry in ksystemsettings (see second attachment).
Created attachment 38275 [details]
ksystemsettings screenshot
Just a brief update: The empty entry is not my onboard audio, which correctly came back as an additional entry after I re-enabled it in the BIOS. Unfortunately, the spurious output remained... *** Bug 214923 has been marked as a duplicate of this bug. *** Confirmed by duplicate. *** Bug 217749 has been marked as a duplicate of this bug. *** *** Bug 218720 has been marked as a duplicate of this bug. *** *** Bug 220487 has been marked as a duplicate of this bug. *** *** Bug 221312 has been marked as a duplicate of this bug. *** well, seems like i found a workaround AGAIN, which i had found some weeks ago: make sure to remove pulseaudio from your system, then rm the $HOME/.xine directory... after that, amarok will startup again quite fine. (In reply to comment #13) > well, seems like i found a workaround AGAIN, which i had found some weeks ago: > make sure to remove pulseaudio from your system, then rm the $HOME/.xine > directory... > > after that, amarok will startup again quite fine. Thank you very very much Johannes!!! i just removed ${HOME}/.xine directory, and amarok started to work again!!! thank you again, it's great be part of this community. Regards from Argentina. Can you all please remove $HOME/.xine and confirm this works for you? (In reply to comment #15) > Can you all please remove $HOME/.xine and confirm this works for you? Yes Myriam, it worked for me. I removed $HOME/.xine, and then amarok started to work fine. Regards. Thank you for the feedback. Closing, marking as duplicate of original bug 188602 *** This bug has been marked as a duplicate of bug 188602 *** |