Application: kalarm (2.8.1-ak) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-14-generic-pae i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I just click on the close button, but the alarm didn't make tha sound I set (I was listening music on Amarok). -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault [Current thread is 1 (Thread 0xb3ef3730 (LWP 2573))] Thread 3 (Thread 0xb1037b70 (LWP 10538)): #0 0xb4afe6c7 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb4aff637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb4affc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb56651c7 in QEventDispatcherGlib::processEvents (this=0x8c3e6d0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0xb5630d1d in QEventLoop::processEvents (this=0xb1037280, flags=...) at kernel/qeventloop.cpp:149 #5 0xb5630fb9 in QEventLoop::exec (this=0xb1037280, flags=...) at kernel/qeventloop.cpp:204 #6 0xb551a9dc in QThread::exec (this=0x8bdc7a0) at thread/qthread.cpp:501 #7 0xb560e2dd in QInotifyFileSystemWatcherEngine::run (this=0x8bdc7a0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0xb551de70 in QThreadPrivate::start (arg=0x8bdc7a0) at thread/qthread_unix.cpp:298 #9 0xb5044d31 in start_thread (arg=0xb1037b70) at pthread_create.c:304 #10 0xb530146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xa9c4ab70 (LWP 4796)): #0 0xb7719424 in __kernel_vsyscall () #1 0xb52f27ae in __GI___poll (fds=0x9239638, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb4e8d246 in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0 #3 0xb4e7b4ea in pa_mainloop_poll () from /usr/lib/i386-linux-gnu/libpulse.so.0 #4 0xb4e7bd47 in pa_mainloop_iterate () from /usr/lib/i386-linux-gnu/libpulse.so.0 #5 0xb4e7be24 in pa_mainloop_run () from /usr/lib/i386-linux-gnu/libpulse.so.0 #6 0xb4e8d1ce in ?? () from /usr/lib/i386-linux-gnu/libpulse.so.0 #7 0xb46d8216 in ?? () from /usr/lib/i386-linux-gnu/libpulsecommon-1.0.so #8 0xb5044d31 in start_thread (arg=0xa9c4ab70) at pthread_create.c:304 #9 0xb530146e 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 0xb3ef3730 (LWP 2573)): [KCrash Handler] #7 0x00000084 in ?? () #8 0xb5647521 in QObjectPrivate::deleteChildren (this=0x8db04b0) at kernel/qobject.cpp:1908 #9 0xb564cc91 in QObject::~QObject (this=0x90e7578, __in_chrg=<optimized out>) at kernel/qobject.cpp:927 #10 0xb6f40ec8 in Phonon::MediaObject::~MediaObject (this=0x90e7578, __in_chrg=<optimized out>) at ../../phonon/mediaobject.cpp:60 #11 0xb6f40f22 in Phonon::MediaObject::~MediaObject (this=0x90e7578, __in_chrg=<optimized out>) at ../../phonon/mediaobject.cpp:76 #12 0x080f481a in ?? () #13 0x080f4920 in ?? () #14 0xb5647521 in QObjectPrivate::deleteChildren (this=0x910c088) at kernel/qobject.cpp:1908 #15 0xb5db79bc in QWidget::~QWidget (this=0x910bf28, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1675 #16 0xb61f2d1f in QMainWindow::~QMainWindow (this=0x910bf28, __in_chrg=<optimized out>) at widgets/qmainwindow.cpp:388 #17 0xb69bbcd9 in KMainWindow::~KMainWindow (this=0x910bf28, __in_chrg=<optimized out>) at ../../kdeui/widgets/kmainwindow.cpp:467 #18 0xb6a0571c in KXmlGuiWindow::~KXmlGuiWindow (this=0x910bf28, __vtt_parm=0x81cb7f0, __in_chrg=<optimized out>) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:118 #19 0x080fd3a3 in ?? () #20 0x080fd690 in ?? () #21 0xb5646513 in qDeleteInEventHandler (o=0x910bf28) at kernel/qobject.cpp:4277 #22 0xb564d4b8 in QObject::event (this=0x910bf28, e=0x9182448) at kernel/qobject.cpp:1176 #23 0xb5dbd6a2 in QWidget::event (this=0x910bf28, event=0x9182448) at kernel/qwidget.cpp:8820 #24 0xb61f505c in QMainWindow::event (this=0x910bf28, event=0x9182448) at widgets/qmainwindow.cpp:1478 #25 0xb69bc7c4 in KMainWindow::event (this=0x910bf28, ev=0x9182448) at ../../kdeui/widgets/kmainwindow.cpp:1084 #26 0xb6a05272 in KXmlGuiWindow::event (this=0x910bf28, ev=0x9182448) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126 #27 0xb5d63844 in notify_helper (e=0x9182448, receiver=0x910bf28, this=0x89b5050) at kernel/qapplication.cpp:4555 #28 QApplicationPrivate::notify_helper (this=0x89b5050, receiver=0x910bf28, e=0x9182448) at kernel/qapplication.cpp:4527 #29 0xb5d68d12 in QApplication::notify (this=0x89b5050, receiver=0x910bf28, e=0x9182448) at kernel/qapplication.cpp:4520 #30 0xb68e1051 in KApplication::notify (this=0x898e5c8, receiver=0x910bf28, event=0x9182448) at ../../kdeui/kernel/kapplication.cpp:311 #31 0xb563218e in QCoreApplication::notifyInternal (this=0x898e5c8, receiver=0x910bf28, event=0x9182448) at kernel/qcoreapplication.cpp:876 #32 0xb56362e8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8961be0) at kernel/qcoreapplication.cpp:1500 #34 0xb563661c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393 #35 0xb5664d74 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #36 postEventSourceDispatch (s=0x8962fd8) at kernel/qeventdispatcher_glib.cpp:279 #37 0xb4aff25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #38 0xb4aff990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #39 0xb4affc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #40 0xb5665167 in QEventDispatcherGlib::processEvents (this=0x899da38, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #41 0xb5e18fda in QGuiEventDispatcherGlib::processEvents (this=0x899da38, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #42 0xb5630d1d in QEventLoop::processEvents (this=0xbfdf0e14, flags=...) at kernel/qeventloop.cpp:149 #43 0xb5630fb9 in QEventLoop::exec (this=0xbfdf0e14, flags=...) at kernel/qeventloop.cpp:204 #44 0xb56366ca in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #45 0xb5d616a4 in QApplication::exec () at kernel/qapplication.cpp:3816 #46 0x08083f40 in ?? () #47 0xb5247113 in __libc_start_main (main=0x8081e00, argc=3, ubp_av=0xbfdf12d4, init=0x81ba6e0 <__libc_csu_init>, fini=0x81ba750 <__libc_csu_fini>, rtld_fini=0xb7728ba0, stack_end=0xbfdf12cc) at libc-start.c:226 #48 0x080857d9 in _start () This bug may be a duplicate of or related to bug 246448. Possible duplicates by query: bug 295156, bug 295155, bug 292395, bug 290776, bug 287867. Reported using DrKonqi
If I understand you correctly, an alarm window appeared while you were listening to music using Amarok, but the alarm sound did not play. You then clicked Close in the alarm window, and KAlarm crashed. Can you confirm whether this is correct?
Hello David, You're right, sometimes a windows pops up, saying that one of the phonon components is not working... so it switch to another (that is exactly the one in use...) I've checked Kmix configuration, it seems to be OK. Thank you, Luis Alberto Arriola >________________________________ > De: David Jarvie <djarvie@kde.org> >Para: laarriola@yahoo.com >Enviado: Miércoles, 28 de marzo, 2012 5:42 P.M. >Asunto: [Bug 296089] Kalarm crashed when close alarm window > >https://bugs.kde.org/show_bug.cgi?id=296089 > >--- Comment #1 from David Jarvie <djarvie@kde.org> --- >If I understand you correctly, an alarm window appeared while you were >listening to music using Amarok, but the alarm sound did not play. You then >clicked Close in the alarm window, and KAlarm crashed. > >Can you confirm whether this is correct? > >-- >You are receiving this mail because: >You reported the bug. > > >
I'm sorry, but I'm still confused about what happens. Is the window which pops up saying that a phonon component is not working, a KAlarm window, or some other window? (Look in its title bar to check.) My question (in comment 1) was about *KAlarm* alarm windows - not error messages from other applications. Can you confirm whether what I said in comment 1 is correct?
comment 1 is correct, the other window is from system I'll check title... Luis Alberto Arriola >________________________________ > De: David Jarvie <djarvie@kde.org> >Para: laarriola@yahoo.com >Enviado: Jueves, 29 de marzo, 2012 10:57 A.M. >Asunto: [Bug 296089] Kalarm crashed when close alarm window > >https://bugs.kde.org/show_bug.cgi?id=296089 > >--- Comment #3 from David Jarvie <djarvie@kde.org> --- >I'm sorry, but I'm still confused about what happens. Is the window which pops >up saying that a phonon component is not working, a KAlarm window, or some >other window? (Look in its title bar to check.) > >My question (in comment 1) was about *KAlarm* alarm windows - not error >messages from other applications. Can you confirm whether what I said in >comment 1 is correct? > >-- >You are receiving this mail because: >You reported the bug. > > >
Could you please say which phonon backend you were using. To find this out, go to multimedia settings in System Settings, then select the Backend tab, and report which backends are listed (in order).
(In reply to comment #5) > Could you please say which phonon backend you were using. To find this out, > go to multimedia settings in System Settings, then select the Backend tab, > and report which backends are listed (in order). I have installed: GStreamer 4.6.0 VLC 0.5.0 another problem is that the OS eventually deletes some devices without any reason, then I get a pop up warning asking to forget the listed devices...
Reassigning this bug to phonon, since the crash is in a phonon destructor.
Is this still reproducible? Then please make sure you really have all debugging symbols installed, as the backtrace has many holes in the Thread where the crash happens. Please also have a look here: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Also please clearify which Phonon backend is actually used. Or is it happening with both? Also did you happen to uninstall PulseAudio perhaps?
(In reply to comment #8) > Is this still reproducible? Then please make sure you really have all > debugging symbols installed, as the backtrace has many holes in the Thread > where the crash happens. Please also have a look here: > http://techbase.kde.org/Development/Tutorials/Debugging/ > How_to_create_useful_crash_reports To summarise how to get a good backtrace, you should install the kdepim-dbg package.
Closing for lack of feedback. Please feel free to reopen if you can reproduce this with KDE 4.10.2 or later and specify the exact Phonon backend you are using.