Hide Forgot
Version-Release number of selected component: bluedevil-1.3-3.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/kde4/bluedevil-requestpin '' crash_function: KNotification::activate executable: /usr/libexec/kde4/bluedevil-requestpin kernel: 3.10.7-200.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Aug 23 09:43:33 paradise abrt[1992]: Saved core dump of pid 1989 (/usr/libexec/kde4/bluedevil-requestpin) to /var/tmp/abrt/ccpp-2013-08-23-09:43:29-1989 (8048640 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 KNotification::activate at /usr/src/debug/kdelibs-4.10.5/kdeui/notifications/knotification.cpp:240 #1 KNotificationManager::notificationActivated at /usr/src/debug/kdelibs-4.10.5/kdeui/notifications/knotificationmanager.cpp:84 #2 QMetaObject::activate at kernel/qobject.cpp:3547 #3 OrgKdeKNotifyInterface::notificationActivated at /usr/src/debug/kdelibs-4.10.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:126 #4 OrgKdeKNotifyInterface::qt_static_metacall at /usr/src/debug/kdelibs-4.10.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:66 #5 qt_static_metacall at /usr/src/debug/kdelibs-4.10.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:115 #6 OrgKdeKNotifyInterface::qt_metacall at /usr/src/debug/kdelibs-4.10.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:116 #7 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:951 #8 QObject::event at kernel/qobject.cpp:1194 #9 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562 Potential duplicate: bug 770617
Created attachment 789509 [details] File: backtrace
Created attachment 789510 [details] File: cgroup
Created attachment 789511 [details] File: core_backtrace
Created attachment 789512 [details] File: dso_list
Created attachment 789513 [details] File: environ
Created attachment 789514 [details] File: exploitable
Created attachment 789515 [details] File: limits
Created attachment 789516 [details] File: maps
Created attachment 789517 [details] File: open_fds
Created attachment 789518 [details] File: proc_pid_status
Another user experienced a similar problem: trying to configure bluetooth adapter reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/kde4/bluedevil-requestpin SGH-D900i crash_function: KNotification::activate executable: /usr/libexec/kde4/bluedevil-requestpin kernel: 3.12.7-200.fc19.i686 package: bluedevil-1.3.2-1.fc19 reason: bluedevil-requestpin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.