Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages Similar to bug# 185633 but NOT resolved. On startup, during bootup or manual, kalarm displays list of active alarms and one overdue alarm. It then crashes and displays "KAlarm - The KDE Crash Handler" "The application KAlarm ... and caused the signal 11 (SIGSEGV). No details are available. I set up the kdebugdialog to send output for errors for 5900, 5950 and 5951. Rebooted but still no output. I am using a setup which is probably unusual. I am running VMPlayer 2.5.1 build-126130 on host WinXP SP3, fully updated, with guest Ubuntu 8.10 - also fully updated. Problem started after update last Thursday I think. I have reloaded the sources so whatever fixes you have implemented have either not reached Ubuntu Synaptic or have not worked for this setup.
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
The reporter sent me an email: ----------- Hi Darío. I can certainly reproduce it at will - all I have to do is run kalarm. After the crash notification appears, it states it is loading the backtrace and shortly after that a new popup informs me that "This backtrace appears to be of no use." I am pasting it in anyway - hope it helps but that's the reason I didn't bother to post it with my bug report. I deleted a bunch of (no debugging symbols found). As I mentioned in my bug report, the kde debug processor ( I can't recall the exact name) did not create log files for errors 5950 and 5951 and one other, I think 5900. I made sure that the /tmp directory was 777 and directed the error log there as /tmp/kalarm.log. I don't know what more I can do but I am willing to try anything you suggest (not rm -R). Ivan --------------------------------------------------------- This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb51e36c0 (LWP 913)] [New Thread 0xb327bb90 (LWP 919)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7fb3430 in __kernel_vsyscall () [Current thread is 0 (LWP 913)] Thread 2 (Thread 0xb327bb90 (LWP 919)): #0 0xb343894b in ?? () from /usr/lib/libpulse.so.0 #1 0xb3421989 in pa_mainloop_dispatch () from /usr/lib/libpulse.so.0 #2 0xb3421ce1 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #3 0xb3421da4 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #4 0xb342e2e3 in ?? () from /usr/lib/libpulse.so.0 #5 0xb344f8e2 in ?? () from /usr/lib/libpulse.so.0 #6 0xb627b50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb63d3a0e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb51e36c0 (LWP 913)): #0 0xb7fb3430 in __kernel_vsyscall () #1 0xb638ef36 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb638ed4e in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb76f5d72 in ?? () from /usr/lib/libkdeui.so.5 #4 0xb76f6734 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #5 <signal handler called> #6 0xb66d07f7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #7 0xb7cd4fc3 in ?? () from /usr/lib/libphonon.so.4 #8 0xb7cbe216 in ?? () from /usr/lib/libphonon.so.4 #9 0xb7cbf4aa in ?? () from /usr/lib/libphonon.so.4 #10 0xb7cbdb85 in ?? () from /usr/lib/libphonon.so.4 #11 0x080f7530 in ?? () #12 0x080fa7c0 in ?? () #13 0xb66cfa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0xb66d07e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb66d5db7 in ?? () from /usr/lib/libQtCore.so.4 #16 0xb66d5edc in ?? () from /usr/lib/libQtCore.so.4 #17 0xb66ca53f in QObject::event () from /usr/lib/libQtCore.so.4 #18 0xb6b6c8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #19 0xb6b7472e in QApplication::notify () from /usr/lib/libQtGui.so.4 #20 0xb7685fed in KApplication::notify () from /usr/lib/libkdeui.so.5 #21 0xb66bae61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #22 0xb66e8d81 in ?? () from /usr/lib/libQtCore.so.4 #23 0xb66e5520 in ?? () from /usr/lib/libQtCore.so.4 #24 0xb57ed6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb57f0da3 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0xb57f0f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb66e5478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb6c06ea5 in ?? () from /usr/lib/libQtGui.so.4 #29 0xb66b952a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #30 0xb66b96ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #31 0xb66bbda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #32 0xb6b6c767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #33 0x080963ee in _start () #0 0xb7fb3430 in __kernel_vsyscall ()
@Ivan: can you install the "phonon-dbg" Ubuntu package and recreate the backtrace ? Thanks
Could you try temporarily removing your calendar files so that KAlarm starts afresh, to see if that makes any difference. The easiest way to do that would be to rename your KAlarm data directory (probably ~/.kde/share/apps/kalarm). Then run KAlarm, and see if it still crashes.
Could you also try removing your KAlarm configuration file (~/.kde/share/config/kalarmrc or ~/.kde4/share/config/kalarmrc), again by renaming it so that you can restore it afterwards. Check if that makes a difference.
The reporter sent me an email: ----------- That looks a lot better. Let me know if you need anything else. Application: KAlarm (kalarm), signal SIGSEGV [Current thread is 0 (LWP 29856)] Thread 2 (Thread 0xb338fb90 (LWP 29894)): #0 0xb64f5d6a in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6 #1 0xb3562bf1 in ?? () from /usr/lib/libpulse.so.0 #2 0xb354253c in ?? () from /usr/lib/libpulse.so.0 #3 0xb3534509 in pa_mainloop_poll () from /usr/lib/libpulse.so.0 #4 0xb3535cd3 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #5 0xb3535da4 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #6 0xb35422e3 in ?? () from /usr/lib/libpulse.so.0 #7 0xb35638e2 in ?? () from /usr/lib/libpulse.so.0 #8 0xb638f50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #9 0xb64e7a0e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb52f76c0 (LWP 29856)): [KCrash Handler] #6 0xb67e47f7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #7 0xb7de8fc3 in Phonon::AudioOutputAdaptor::outputDeviceIndexChanged (this=0x0, _t1=0) at /build/buildd/phonon-4.3.0/obj-i486-linux-gnu/phonon/moc_audiooutputadaptor_p.cpp:185 #8 0xb7dd2216 in Phonon::AudioOutputPrivate::handleAutomaticDeviceChange (this=0xa550170, device2=@0xbf8c8634, type=Phonon::AudioOutputPrivate::FallbackChange) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:366 #9 0xb7dd34aa in Phonon::AudioOutputPrivate::setupBackendObject (this=0xa550170) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:269 #10 0xb7dd1b85 in Phonon::AudioOutputPrivate::init (this=0xa550170, c=Phonon::NotificationCategory) at /build/buildd/phonon-4.3.0/phonon/audiooutput.cpp:85 #11 0x080f7530 in ?? () #12 0x080fa7c0 in ?? () #13 0xb67e3a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0xb67e47e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb67e9db7 in ?? () from /usr/lib/libQtCore.so.4 #16 0xb67e9edc in ?? () from /usr/lib/libQtCore.so.4 #17 0xb67de53f in QObject::event () from /usr/lib/libQtCore.so.4 #18 0xb6c808ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #19 0xb6c8872e in QApplication::notify () from /usr/lib/libQtGui.so.4 #20 0xb7799fed in KApplication::notify () from /usr/lib/libkdeui.so.5 #21 0xb67cee61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #22 0xb67fcd81 in ?? () from /usr/lib/libQtCore.so.4 #23 0xb67f9520 in ?? () from /usr/lib/libQtCore.so.4 #24 0xb59016f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb5904da3 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0xb5904f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb67f9478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb6d1aea5 in ?? () from /usr/lib/libQtGui.so.4 #29 0xb67cd52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #30 0xb67cd6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #31 0xb67cfda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #32 0xb6c80767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #33 0x080963ee in _start ()
This is a Phonon bug already fixed : bug 180109 Look at bug 180109 comment 17 for a workaround to this crash. *** This bug has been marked as a duplicate of bug 180109 ***
The reporter sent me an email: ----------- This is the offending directory. Once I renamed it, the program runs without crashing. > --- Comment #4 from David Jarvie <djarvie kde org> 2009-03-06 14:20:12 --- > Could you try temporarily removing your calendar files so that KAlarm starts > afresh, to see if that makes any difference. The easiest way to do that would > be to rename your KAlarm data directory (probably ~/.kde/share/apps/kalarm). > Then run KAlarm, and see if it still crashes.