Summary: | amarok crashed when pressing play button [@ Phonon::PulseSupport::setOutputVolume] | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Phonon | Reporter: | dave <mckisick> |
Component: | Pulsesupport | Assignee: | Harald Sitter <sitter> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | albertspijkers, cheepeero, colin, jb, justin.zobel, kripton, lu.dolezal, mail, mail, martin.sandsmark, myriam, qianian, rbenech, vikvas |
Priority: | NOR | ||
Version: | 4.6.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
dave
2010-12-26 08:12:32 UTC
This appears to be a problem with libpulse I've not seen this problem before. Is it reliably reproducible? Does it happen after leaving more time for the system to "stabilise" after logging in? I'm wondering if it's because Amarok is setting the volume before the (necessary) round trip in PA to let the streams stabilise (this should all be hidden away in Phonon, but perhaps not). Ideally, Amarok would remove any initial volume setting anyway and let Phonon (and if PA is used underneath Phonon then offload further to PA) deal with the volume saving and restoration. Having individual apps try to outsmart the underlying sound system often leads to strange quirks (although this is clearly just a bug, not a quirk!) *** Bug 264903 has been marked as a duplicate of this bug. *** *** Bug 266455 has been marked as a duplicate of this bug. *** Confirmed by duplicates. *** Bug 276926 has been marked as a duplicate of this bug. *** *** Bug 283301 has been marked as a duplicate of this bug. *** *** Bug 293581 has been marked as a duplicate of this bug. *** Created attachment 72700 [details]
New crash information added by DrKonqi
knotify4 (4.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2
- What I was doing when the application crashed:
→ Started a 2nd KDE session
→ Suspended laptop after a while
→ Resumed laptop
→ Switched back to the 1st session
→ Was greeted by 2 dialogs:
#1 Phonon notification about a removed sounddevice (my internal soundcard)
#2 KNotify crash with a backtrace pointing to Phonon/PulseAudio
Using:
KDE 4.8.3
Qt 4.8.2
Phonon 4.6.0
Phonon GStreamer 4.5.1
PulseAudio 2.0
-- Backtrace (Reduced):
#8 0x00007f483a96f434 in pa_context_set_sink_input_volume (c=0x0, idx=38, volume=0x7fff775839a0, cb=0, userdata=0x0) at pulse/introspect.c:1469
#9 0x00007f483f1892b2 in Phonon::PulseSupport::setOutputVolume (this=<optimized out>, streamUuid=<optimized out>, volume=1) at /var/tmp/portage/media-libs/phonon-4.6.0-r1/work/phonon-4.6.0/phonon/pulsesupport.cpp:1259
#10 0x00007f483f1624a9 in Phonon::AudioOutput::setVolume (this=<optimized out>, volume=1) at /var/tmp/portage/media-libs/phonon-4.6.0-r1/work/phonon-4.6.0/phonon/audiooutput.cpp:183
#11 0x000000000040eab1 in setVolume (volume=<optimized out>, this=<optimized out>) at /var/tmp/portage/kde-base/knotify-4.8.3/work/knotify-4.8.3/knotify/notifybysound.cpp:65
#12 PlayerPool::getPlayer (this=0x79bd08) at /var/tmp/portage/kde-base/knotify-4.8.3/work/knotify-4.8.3/knotify/notifybysound.cpp:103
*** Bug 305929 has been marked as a duplicate of this bug. *** *** Bug 314291 has been marked as a duplicate of this bug. *** PulseAudio context here is NULL, hence crashing. The support rewritten... Thank you for the report, Dave. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |