Bug 296684 - KMix crashed when starting youtube in Chromium
Summary: KMix crashed when starting youtube in Chromium
Status: RESOLVED DUPLICATE of bug 288441
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: 4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-24 15:43 UTC by fedorastyle
Modified: 2012-03-24 16:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fedorastyle 2012-03-24 15:43:46 UTC
Application: kmix (4)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.0.0-16-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

Opened a youtube.com video in Google Chrome just after kde booted

The crash does not seem to be reproducible.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7753720 (LWP 1947))]

Thread 2 (Thread 0xacb97b70 (LWP 1957)):
#0  0x00248416 in __kernel_vsyscall ()
#1  0x00df27ae in __GI___poll (fds=0x8ce5ff8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x02d4d34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x02d3e896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x02d3ec2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x05e83217 in QEventDispatcherGlib::processEvents (this=0x8ce50b8, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x05e4ed6d in QEventLoop::processEvents (this=0xacb97290, flags=...) at kernel/qeventloop.cpp:149
#7  0x05e4f009 in QEventLoop::exec (this=0xacb97290, flags=...) at kernel/qeventloop.cpp:204
#8  0x05d389dc in QThread::exec (this=0x8cdfc00) at thread/qthread.cpp:501
#9  0x05e2c2dd in QInotifyFileSystemWatcherEngine::run (this=0x8cdfc00) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x05d3be70 in QThreadPrivate::start (arg=0x8cdfc00) at thread/qthread_unix.cpp:298
#11 0x076b3d31 in start_thread (arg=0xacb97b70) at pthread_create.c:304
#12 0x00e0146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb7753720 (LWP 1947)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0x00f6e978 in MDWSlider::update (this=0x8cd39d0) at ../../kmix/gui/mdwslider.cpp:1001
#9  0x00f696d3 in ViewDockAreaPopup::refreshVolumeLevels (this=0x8cca920) at ../../kmix/gui/viewdockareapopup.cpp:168
#10 0x00f6641f in ViewBase::qt_metacall (this=0x8cca920, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfa8b2d0) at ./viewbase.moc:87
#11 0x00f69082 in ViewDockAreaPopup::qt_metacall (this=0x8cca920, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfa8b2d0) at ./viewdockareapopup.moc:73
#12 0x05e574fd in metacall (argv=0xbfa8b2d0, idx=30, cl=QMetaObject::InvokeMetaMethod, object=0x8cca920) at kernel/qmetaobject.cpp:245
#13 QMetaObject::metacall (object=0x8cca920, cl=QMetaObject::InvokeMetaMethod, idx=30, argv=0xbfa8b2d0) at kernel/qmetaobject.cpp:240
#14 0x05e6721d in QMetaObject::activate (sender=0x8c65060, m=0xfa9d48, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3566
#15 0x00f894f5 in Mixer::controlChanged (this=0x8c65060) at ./mixer.moc:103
#16 0x00f8962c in Mixer::qt_metacall (this=0x8c65060, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfa8b400) at ./mixer.moc:82
#17 0x05e574fd in metacall (argv=0xbfa8b400, idx=5, cl=QMetaObject::InvokeMetaMethod, object=0x8c65060) at kernel/qmetaobject.cpp:245
#18 QMetaObject::metacall (object=0x8c65060, cl=QMetaObject::InvokeMetaMethod, idx=5, argv=0xbfa8b400) at kernel/qmetaobject.cpp:240
#19 0x05e6721d in QMetaObject::activate (sender=0x8d208b0, m=0xfa7ce4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3566
#20 0x00f3ea95 in Mixer_Backend::controlChanged (this=0x8d208b0) at ./mixer_backend.moc:93
#21 0x00f3ed58 in Mixer_Backend::readSetFromHW (this=0x8d208b0) at ../../kmix/backends/mixer_backend.cpp:155
#22 0x00f4bc8a in Mixer_PULSE::triggerUpdate (this=0x8d208b0) at ../../kmix/backends/mixer_pulse.cpp:1286
#23 0x00f4fff5 in sink_cb (c=0x8c5c438, i=0x0, eol=1) at ../../kmix/backends/mixer_pulse.cpp:191
#24 0x00873035 in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
#25 0x06025ebd in ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so
#26 0x060262c0 in pa_pdispatch_run () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so
#27 0x00866add in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
#28 0x0602b893 in ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so
#29 0x06015c18 in ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so
#30 0x0022eaaa in ?? () from /usr/lib/i386-linux-gnu/libpulse-mainloop-glib.so.0
#31 0x02d3e25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#32 0x02d3e990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0x02d3ec2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#34 0x05e831b7 in QEventDispatcherGlib::processEvents (this=0x8946eb8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#35 0x0119b06a in QGuiEventDispatcherGlib::processEvents (this=0x8946eb8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0x05e4ed6d in QEventLoop::processEvents (this=0xbfa8be74, flags=...) at kernel/qeventloop.cpp:149
#37 0x05e4f009 in QEventLoop::exec (this=0xbfa8be74, flags=...) at kernel/qeventloop.cpp:204
#38 0x05e5471a in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#39 0x010e36a4 in QApplication::exec () at kernel/qapplication.cpp:3816
#40 0x00f582ab in kdemain (argc=3, argv=0xbfa8c0d4) at ../../kmix/apps/main.cpp:76
#41 0x0804850b in main (argc=3, argv=0xbfa8c0d4) at kmix_dummy.cpp:3

This bug may be a duplicate of or related to bug 288441.

Possible duplicates by query: bug 296639, bug 296628, bug 296570, bug 296557, bug 296454.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-03-24 16:53:37 UTC

*** This bug has been marked as a duplicate of bug 288441 ***