Description of problem: Rebooted. It happens to me every time. Version-Release number of selected component: akonadi-1.10.3-1.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/akonadi_agent_launcher akonadi_kalarm_dir_resource akonadi_kalarm_dir_resource_0 crash_function: QString executable: /usr/bin/akonadi_agent_launcher kernel: 3.13.5-101.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QString at /usr/include/QtCore/qstring.h:725 #1 KCalCore::IncidenceBase::uid at /usr/src/debug/kdepimlibs-4.11.5/kcalcore/incidencebase.cpp:235 #2 KAlarmDirResource::loadFile at /usr/src/debug/kdepim-runtime-4.11.5/resources/kalarm/kalarmdir/kalarmdirresource.cpp:488 #3 KAlarmDirResource::loadFiles at /usr/src/debug/kdepim-runtime-4.11.5/resources/kalarm/kalarmdir/kalarmdirresource.cpp:437 #4 QObject::event at kernel/qobject.cpp:1194 #5 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562 #6 QApplication::notify at kernel/qapplication.cpp:4348 #7 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:949 #8 sendEvent at kernel/qcoreapplication.h:231 #9 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1573 Potential duplicate: bug 866065
Created attachment 884647 [details] File: backtrace
Created attachment 884648 [details] File: cgroup
Created attachment 884649 [details] File: core_backtrace
Created attachment 884650 [details] File: dso_list
Created attachment 884651 [details] File: environ
Created attachment 884652 [details] File: exploitable
Created attachment 884653 [details] File: limits
Created attachment 884654 [details] File: maps
Created attachment 884655 [details] File: open_fds
Created attachment 884656 [details] File: proc_pid_status
Created attachment 884657 [details] File: var_log_messages
Another user experienced a similar problem: Reboot. Happens every time. The abrt GUI is showing 35, dating back months. Hoping that if I keep reporting it, someone will fix this annoyance. Do not know if this might be related to my (unreported, by me, at least) "Can not get search result. Unable to create persistent search" errors in kmail. Granted this bug is about kalarm, but my experience with akonadi has been so poor, for so long, that I won't rule anything out. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/akonadi_agent_launcher akonadi_kalarm_dir_resource akonadi_kalarm_dir_resource_0 crash_function: QString executable: /usr/bin/akonadi_agent_launcher kernel: 3.14.7-100.fc19.x86_64 package: akonadi-1.10.3-1.fc19 reason: akonadi_agent_launcher killed by SIGSEGV runlevel: unknown type: CCpp uid: 1000
Moving to kdepim-runtime, where the code that crashes lives. It would be helpful if you could provide the calendar file that causes the application to crash, so that we can reproduce it and fix it. Feel free to send the file to me directly, if you don't want to upload it publicly.
Sent $HOME/.kde/share/apps/kalarm/calendar.ics privately.
Still crashes on every boot--constant annoyance. As it has for 6 months. Sent you the file you asked for four months ago. *Zero feedback* for four months. So, the usual Fedora approach of CLOSE WONTFIX as F19 reaches EOL? There is a long history of most Akonadi-related Web searches being about how disable this entire approach to PIM, over several Fedora versions. It has never been reliable. That is a Fedora project governance issue, like assigning bugs to a list, where there is no individual accountability for maintaining contact, demonstrating progress, etc. In this case, there *is* a specific person, and this does not reflect well on the professionalism of Dan Vrátil.
Sorry, I somehow missed the email and forgot about this issue completely. I was able to reproduce the crash and fixed it in upstream, so the fix will be available in next KDE update. Upstream commit: http://quickgit.kde.org/?p=kdepim-runtime.git&a=commit&h=0f270063ea8cca062321b93387392a923858f1b9
Greg, I appreciate your frustration, but calling out individuals and questioning their motivations is not constructive and goes against both the letter and spirit of the fedora code of conduct, http://fedoraproject.org/code-of-conduct Please be mindful of that in the future. In particular, the first 2 sentences of comment #15 are ok, but past that, not so much.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.