Bug 309790 - Phonon setting crash
Summary: Phonon setting crash
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_phonon (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-11-09 03:28 UTC by Joerg Schnee
Modified: 2018-10-27 02:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schnee 2012-11-09 03:28:35 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-32-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:sound did not work, started system settings -> hardware -> Multimedia -> Phonon, settings to default, then testing left, and later right speaker, each time followed by a crash

-- Backtrace:
Application: System Settings (systemsettings), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2be568f780 (LWP 2916))]

Thread 3 (Thread 0x7f2bc77d6700 (LWP 2918)):
#0  QTimerInfoList::timerWait (this=0x7f2bc0002860, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#1  0x00007f2be32a097c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f2bc77d5c6c) at kernel/qeventdispatcher_glib.cpp:136
#2  0x00007f2be32a0a25 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#3  0x00007f2be0302846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2be0302f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f2be0303164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f2be32a1426 in QEventDispatcherGlib::processEvents (this=0x7f2bc00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x00007f2be3270c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f2be3270ed7 in QEventLoop::exec (this=0x7f2bc77d5dd0, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f2be316ffa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#10 0x00007f2be32509ff in QInotifyFileSystemWatcherEngine::run (this=0x1226250) at io/qfilesystemwatcher_inotify.cpp:248
#11 0x00007f2be3172fcb in QThreadPrivate::start (arg=0x1226250) at thread/qthread_unix.cpp:298
#12 0x00007f2be07cfe9a in start_thread (arg=0x7f2bc77d6700) at pthread_create.c:308
#13 0x00007f2be2b2bcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#14 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f2bbb0ef700 (LWP 2924)):
#0  0x00007f2bcb7c332a in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#1  0x00007f2bcb7b476c in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x00007f2bcb7b4dd9 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x00007f2bcb7b4e90 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x00007f2bcb7c330f in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x00007f2bcaf2cd18 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#6  0x00007f2be07cfe9a in start_thread (arg=0x7f2bbb0ef700) at pthread_create.c:308
#7  0x00007f2be2b2bcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2be568f780 (LWP 2916)):
[KCrash Handler]
#6  0x00007f2be2a6e425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f2be2a71b8b in __GI_abort () at abort.c:91
#8  0x00007f2be2a670ee in __assert_fail_base (fmt=<optimized out>, assertion=0x7f2be1ed9b78 "!xcb_xlib_threads_sequence_lost", file=0x7f2be1ed9e32 "../../src/xcb_io.c", line=<optimized out>, function=<optimized out>) at assert.c:94
#9  0x00007f2be2a67192 in __GI___assert_fail (assertion=0x7f2be1ed9b78 "!xcb_xlib_threads_sequence_lost", file=0x7f2be1ed9e32 "../../src/xcb_io.c", line=273, function=0x7f2be1ed9f58 "poll_for_event") at assert.c:103
#10 0x00007f2be1e67683 in poll_for_event (dpy=<optimized out>) at ../../src/xcb_io.c:270
#11 0x00007f2be1e676a1 in poll_for_response (dpy=0xb5c1a0) at ../../src/xcb_io.c:288
#12 0x00007f2be1e67dfd in _XEventsQueued (dpy=0xb5c1a0, mode=<optimized out>) at ../../src/xcb_io.c:362
#13 0x00007f2be1e5942f in XEventsQueued (dpy=0xb5c1a0, mode=2) at ../../src/Pending.c:43
#14 0x00007f2be3f90bf7 in x11EventSourcePrepare (s=0xb3ae00, timeout=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:77
#15 0x00007f2be0302846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f2be0302f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f2be0303164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f2be32a13bf in QEventDispatcherGlib::processEvents (this=0xb094b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#19 0x00007f2be3f90d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#20 0x00007f2be3270c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#21 0x00007f2be3270ed7 in QEventLoop::exec (this=0x7fffd30f18f0, flags=...) at kernel/qeventloop.cpp:204
#22 0x00007f2be3275f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#23 0x000000000040a7e5 in main (argc=5, argv=0x7fffd30f1c28) at ../../../systemsettings/app/main.cpp:49

Possible duplicates by query: bug 303176, bug 301141, bug 294897, bug 289949, bug 289248.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2015-09-26 13:40:40 UTC
systemsettings 4 is no longer supported, we do only support version 5

I can not reproduce this crash with the following combinations
  systemsettings 5.4.1 + Qt 5.5.0
  systemsettings 5.3.2 + Qt 5.4.1
Can you still reproduce this hang on version 5?

If you can still reproduce the crash could you please install valgrind and then run
   valgrind systemsettings5
in a terminal, try to reproduce the crash and add here the valgrind output?
Comment 2 Andrew Crouthamel 2018-09-25 21:41:39 UTC
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 set the bug status 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!
Comment 3 Andrew Crouthamel 2018-10-27 02:39:43 UTC
Dear Bug Submitter,

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!