Bug 1000347

Summary: [abrt] bluedevil-1.3-3.fc19: KNotification::activate: Process /usr/libexec/kde4/bluedevil-requestpin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: ajaytandon1502
Component: bluedevilAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: error, jgrulich, jreznik, kevin, ltinkl, rdieter, support, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5c66f938a6a02a6a9415614000ef36ec0c3caa65
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:53:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description ajaytandon1502 2013-08-23 09:07:56 UTC
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

Comment 1 ajaytandon1502 2013-08-23 09:08:02 UTC
Created attachment 789509 [details]
File: backtrace

Comment 2 ajaytandon1502 2013-08-23 09:08:07 UTC
Created attachment 789510 [details]
File: cgroup

Comment 3 ajaytandon1502 2013-08-23 09:08:12 UTC
Created attachment 789511 [details]
File: core_backtrace

Comment 4 ajaytandon1502 2013-08-23 09:08:17 UTC
Created attachment 789512 [details]
File: dso_list

Comment 5 ajaytandon1502 2013-08-23 09:08:23 UTC
Created attachment 789513 [details]
File: environ

Comment 6 ajaytandon1502 2013-08-23 09:08:27 UTC
Created attachment 789514 [details]
File: exploitable

Comment 7 ajaytandon1502 2013-08-23 09:08:32 UTC
Created attachment 789515 [details]
File: limits

Comment 8 ajaytandon1502 2013-08-23 09:08:38 UTC
Created attachment 789516 [details]
File: maps

Comment 9 ajaytandon1502 2013-08-23 09:08:44 UTC
Created attachment 789517 [details]
File: open_fds

Comment 10 ajaytandon1502 2013-08-23 09:08:49 UTC
Created attachment 789518 [details]
File: proc_pid_status

Comment 11 Leon 2014-01-15 20:05:24 UTC
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

Comment 12 Fedora End Of Life 2015-01-09 19:33:55 UTC
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.

Comment 13 Fedora End Of Life 2015-02-17 16:53:17 UTC
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.