Application: kalarm (2.4.11) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 2.6.35.13-91.fc14.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I had just finished a security update as it happens and also changed my default language. Then when logging in the crash happened. It's happened more than once. Sometimes though it feels as if two KDE Alarms are starting at the same time though I don't know why. The crash can be reproduced some of the time. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f855b01b840 (LWP 4377))] Thread 2 (Thread 0x7f8554d22700 (LWP 4561)): #0 0x0000003d798d7283 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0000003d7b442374 in ?? () from /lib64/libglib-2.0.so.0 #2 0x0000003d7b442c82 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x0000003d818a5774 in ?? () from /lib64/libgio-2.0.so.0 #4 0x0000003d7b469446 in ?? () from /lib64/libglib-2.0.so.0 #5 0x0000003d7a406ccb in start_thread (arg=0x7f8554d22700) at pthread_create.c:301 #6 0x0000003d798e0c2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f855b01b840 (LWP 4377)): [KCrash Handler] #6 0x00000000004f632f in ref (this=0x1e842e0) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:536 #7 QList (this=0x1e842e0) at /usr/include/QtCore/qlist.h:117 #8 ResourceModel::refresh (this=0x1e842e0) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:216 #9 0x00000000004f64da in ResourceModel::ResourceModel (this=0x1e842e0, parent=<value optimized out>) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:52 #10 0x00000000004f658a in ResourceModel::instance (parent=0x0) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:45 #11 0x00000000004f7156 in ResourceSelector::ResourceSelector (this=0x1e64400, calendar=<value optimized out>, parent=<value optimized out>) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourceselector.cpp:85 #12 0x000000000049167f in MainWindow::MainWindow (this=0x1e62e00, restored=<value optimized out>, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/kdepim-4.4.11.1/kalarm/mainwindow.cpp:163 #13 0x0000000000491c57 in MainWindow::create (restored=false) at /usr/src/debug/kdepim-4.4.11.1/kalarm/mainwindow.cpp:126 #14 0x0000000000488ae7 in KAlarmApp::newInstance (this=0x1b8c130) at /usr/src/debug/kdepim-4.4.11.1/kalarm/kalarmapp.cpp:434 #15 0x0000003daaa460f2 in KUniqueApplicationAdaptor::newInstance (this=0x1d63e10, asn_id=<value optimized out>, args=...) at /usr/src/debug/kdelibs-4.6.2/kdeui/kernel/kuniqueapplication.cpp:436 #16 0x0000003daaa46192 in KUniqueApplicationAdaptor::qt_metacall (this=0x1d63e10, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff45cc1800) at /usr/src/debug/kdelibs-4.6.2/x86_64-redhat-linux-gnu/kdeui/kuniqueapplication_p.moc:81 #17 0x000000350d220c87 in QDBusConnectionPrivate::deliverCall (this=0x1b60960, object=0x1d63e10, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:941 #18 0x000000350d221e65 in QDBusConnectionPrivate::activateCall (this=0x1b60960, object=0x1d63e10, flags=337, msg=...) at qdbusintegrator.cpp:851 #19 0x000000350d2225ee in QDBusConnectionPrivate::activateObject (this=0x1b60960, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1409 #20 0x000000350d222828 in QDBusActivateObjectEvent::placeMetaCall (this=0x1e5c7f0) at qdbusintegrator.cpp:1523 #21 0x000000350c5715ca in QObject::event (this=0x1b8c130, e=<value optimized out>) at kernel/qobject.cpp:1217 #22 0x000000350ddba366 in QApplication::event (this=0x1b8c130, e=0x1e5c7f0) at kernel/qapplication.cpp:2503 #23 0x000000350ddb7cd4 in QApplicationPrivate::notify_helper (this=0x1b97890, receiver=0x1b8c130, e=0x1e5c7f0) at kernel/qapplication.cpp:4462 #24 0x000000350ddbc88a in QApplication::notify (this=<value optimized out>, receiver=0x1b8c130, e=0x1e5c7f0) at kernel/qapplication.cpp:4341 #25 0x0000003daaa3ff96 in KApplication::notify (this=0x1b8c130, receiver=0x1b8c130, event=0x1e5c7f0) at /usr/src/debug/kdelibs-4.6.2/kdeui/kernel/kapplication.cpp:311 #26 0x000000350c55d19c in QCoreApplication::notifyInternal (this=0x1b8c130, receiver=0x1b8c130, event=0x1e5c7f0) at kernel/qcoreapplication.cpp:731 #27 0x000000350c560985 in sendEvent (receiver=0x0, event_type=0, data=0x1b3e370) at kernel/qcoreapplication.h:215 #28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1b3e370) at kernel/qcoreapplication.cpp:1372 #29 0x000000350c5881b3 in sendPostedEvents (s=0x1b9c200) at kernel/qcoreapplication.h:220 #30 postEventSourceDispatch (s=0x1b9c200) at kernel/qeventdispatcher_glib.cpp:277 #31 0x0000003d7b441e33 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #32 0x0000003d7b442610 in ?? () from /lib64/libglib-2.0.so.0 #33 0x0000003d7b4428ad in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #34 0x000000350c58834f in QEventDispatcherGlib::processEvents (this=0x1b3df70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #35 0x000000350de5d35e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #36 0x000000350c55c532 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #37 0x000000350c55c77c in QEventLoop::exec (this=0x7fff45cc2570, flags=...) at kernel/qeventloop.cpp:201 #38 0x000000350c560c3b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #39 0x000000000045772f in main (argc=3, argv=0x7fff45cc34a8) at /usr/src/debug/kdepim-4.4.11.1/kalarm/main.cpp:127 Reported using DrKonqi
The crash is happening before KAlarm even looks at alarms, so it isn't related to starting alarms. On the face of it, the crash doesn't look possible (but obviously it is). I wonder whether it always crashes in exactly the same place - could you please try displaying the crash trace a couple of times more, and check whether the following lines are the same. If they are different, please post the complete traces here. Thread 1 (Thread 0x... (LWP ...)): [KCrash Handler] #6 0x... in ref (this=...) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:536 #7 QList (this=0x...) at /usr/include/QtCore/qlist.h:117 #8 ResourceModel::refresh (this=0x...) at /usr/src/debug/kdepim-4.4.11.1/kalarm/resourcemodelview.cpp:216 (Note that some numeric values will change every time, and should be ignored - I've replaced them with "...")
Can you please say where to download your kdepim package, so that I can check the exact source code in it. The Fedora repository doesn't seem to contain kdepim version 2.4.11 (as far as I can tell).
Hi David, It's not crashed again since I reported it. Here's the kdepim package info for you. Name : kdepim Relocations: (not relocatable) Version : 4.4.11.1 Vendor: Fedora Project Release : 2.fc14 Build Date: Tue 26 Apr 2011 15:31:49 BST Install Date: Sat 07 May 2011 11:40:12 BST Build Host: x86-16.phx2.fedoraproject.org Group : Applications/Productivity Source RPM: kdepim-4.4.11.1-2.fc14.src.rpm Size : 19211001 License: GPLv2 Signature : RSA/SHA256, Wed 27 Apr 2011 13:44:14 BST, Key ID 421caddb97a1071f Packager : Fedora Project URL : http://www.kde.org/ Summary : KDE PIM (Personal Information Manager) applications Description : KDE PIM (Personal Information Manager) applications, including: * akregator: feed aggregator * blogilo: blogging application, focused on simplicity and usability * kmail: email client * knode: newsreader * knotes: sticky notes for the desktop * kontact: integrated PIM management * korganizer: journal, appointments, events, todos /usr/bin/akonadiconsole /usr/bin/akregator /usr/bin/akregatorstorageexporter /usr/bin/blogilo /usr/bin/groupwarewizard /usr/bin/groupwisewizard /usr/bin/ical2vcal /usr/bin/kabc2mutt /usr/bin/kabcclient /usr/bin/kaddressbook /usr/bin/kalarm
As I said before, the crash happens in what looks like an impossible place. The most obvious explanation would be that some library (perhaps Qt) was out of sync with kdepim. I wonder if when the kdepim update was installed, another package which should also have been installed, wasn't due to some packaging/dependency fault. The fact that the crash no longer occurs lends some support to this theory. For that reason, I'm closing the bug as invalid. If it happens again, please reopen it, and provide a new crash backtrace if it differs at all from your original one.