Description of problem: I was in the calendar window of Kontact, and right clicked on the Calendar there. I selected Add a new calendar, and specified a KAlarm Directory. I then selected the directory that my Fedora 17 entries were in, in an attempt to get them recognized. I checked all the Alarm types, and when I clicked OK, the crash happended. Version-Release number of selected component: akonadi-1.9.2-1.fc19 Additional info: reporter: libreport-2.1.6 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.10.4-300.fc19.x86_64 runlevel: N 3 uid: 14060 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.10.5/kcalcore/incidencebase.cpp:226 #2 KAlarmDirResource::loadFile at /usr/src/debug/kdepim-runtime-4.10.5/resources/kalarm/kalarmdir/kalarmdirresource.cpp:487 #3 KAlarmDirResource::loadFiles at /usr/src/debug/kdepim-runtime-4.10.5/resources/kalarm/kalarmdir/kalarmdirresource.cpp:436 #4 KAlarmDirResource::configure at /usr/src/debug/kdepim-runtime-4.10.5/resources/kalarm/kalarmdir/kalarmdirresource.cpp:203 #5 qt_static_metacall at /usr/src/debug/kdepimlibs-4.10.5/x86_64-redhat-linux-gnu/akonadi/controladaptor.moc:118 #6 Akonadi__ControlAdaptor::qt_metacall at /usr/src/debug/kdepimlibs-4.10.5/x86_64-redhat-linux-gnu/akonadi/controladaptor.moc:119 #7 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:951 #8 QDBusConnectionPrivate::activateCall at qdbusintegrator.cpp:856 #9 QDBusConnectionPrivate::activateObject at qdbusintegrator.cpp:1427 Potential duplicate: bug 866065
Created attachment 783959 [details] File: backtrace
Created attachment 783960 [details] File: cgroup
Created attachment 783961 [details] File: core_backtrace
Created attachment 783962 [details] File: dso_list
Created attachment 783963 [details] File: environ
Created attachment 783964 [details] File: exploitable
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.