Bug 289792 - Kscd crash.
Summary: Kscd crash.
Status: RESOLVED DUPLICATE of bug 278022
Alias: None
Product: kscd
Classification: Miscellaneous
Component: general (show other bugs)
Version: 1.5
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-25 17:11 UTC by Ivan Ramos
Modified: 2011-12-26 12:39 UTC (History)
0 users

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 Ivan Ramos 2011-12-25 17:11:49 UTC
Application: kscd (1.5)
KDE Platform Version: 4.7.3 (4.7.3) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-14-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:I was playing a cd. But the program crash in the moment it should open his graphic. So, i couldn't hear my cd. First i try to ignore the bug because i though is a duplicate and i was in a hurry. But the next  time i try to use the program the crash handler open. So i report it.

-- Backtrace:
Application: KsCD (kscd), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77c9730 (LWP 2619))]

Thread 3 (Thread 0xb6920b70 (LWP 2620)):
#0  0x0032c46b in __i686.get_pc_thunk.bx () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x0033297f in pthread_getspecific () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x05d0ba00 in get_thread_data () at thread/qthread_unix.cpp:172
#3  QThreadData::current () at thread/qthread_unix.cpp:210
#4  0x05e352f7 in postEventSourcePrepare (s=0x8c83d80, timeout=0xb692010c) at kernel/qeventdispatcher_glib.cpp:254
#5  0x03f8e88c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x03f8f637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x03f8fc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x05e35b37 in QEventDispatcherGlib::processEvents (this=0x8a0f5a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#9  0x05e061dd in QEventLoop::processEvents (this=0xb6920290, flags=...) at kernel/qeventloop.cpp:149
#10 0x05e06421 in QEventLoop::exec (this=0xb6920290, flags=...) at kernel/qeventloop.cpp:201
#11 0x05d0990b in QThread::exec (this=0x8c6f488) at thread/qthread.cpp:498
#12 0x05de6e2d in QInotifyFileSystemWatcherEngine::run (this=0x8c6f488) at io/qfilesystemwatcher_inotify.cpp:248
#13 0x05d0c7b3 in QThreadPrivate::start (arg=0x8c6f488) at thread/qthread_unix.cpp:331
#14 0x0032dd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#15 0x03ab40ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xb1f6db70 (LWP 2622)):
#0  0x00348416 in __kernel_vsyscall ()
#1  0x03aa540e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x009f1246 in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
#3  0x009df4ea in pa_mainloop_poll () from /usr/lib/i386-linux-gnu/libpulse.so.0
#4  0x009dfd47 in pa_mainloop_iterate () from /usr/lib/i386-linux-gnu/libpulse.so.0
#5  0x009dfe24 in pa_mainloop_run () from /usr/lib/i386-linux-gnu/libpulse.so.0
#6  0x009f11ce in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0
#7  0x05344216 in ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so
#8  0x0032dd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#9  0x03ab40ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb77c9730 (LWP 2619)):
[KCrash Handler]
#7  Phonon::MediaObject::currentSource (this=0x0) at ../../phonon/mediaobject.cpp:235
#8  0x0805772b in KSCD::KSCD (this=0x825c6e8, parent=0x0) at ../../kscd/kscd.cpp:72
#9  0x08052278 in main (argc=2743216, argv=0xb77db848) at ../../kscd/kscd.cpp:872

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

Possible duplicates by query: bug 288774, bug 287587, bug 285703, bug 282161, bug 278022.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-12-26 12:39:05 UTC

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