Bug 1110552 - [abrt] bluedevil: isSignalConnected(): bluedevil-requestpin killed by SIGSEGV
Summary: [abrt] bluedevil: isSignalConnected(): bluedevil-requestpin killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bluedevil
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7ef0190c34398d6498fed279f82...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-18 00:08 UTC by Brad
Modified: 2015-06-29 21:11 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:11:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (79.40 KB, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: cgroup (172 bytes, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: core_backtrace (2.11 KB, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: dso_list (10.96 KB, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: environ (1.45 KB, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: exploitable (82 bytes, text/plain)
2014-06-18 00:08 UTC, Brad
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-18 00:09 UTC, Brad
no flags Details
File: maps (58.84 KB, text/plain)
2014-06-18 00:09 UTC, Brad
no flags Details
File: open_fds (378 bytes, text/plain)
2014-06-18 00:09 UTC, Brad
no flags Details
File: proc_pid_status (937 bytes, text/plain)
2014-06-18 00:09 UTC, Brad
no flags Details
File: var_log_messages (215 bytes, text/plain)
2014-06-18 00:09 UTC, Brad
no flags Details

Description Brad 2014-06-18 00:08:48 UTC
Version-Release number of selected component:
bluedevil-2.0.0-0.11.rc1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/kde4/bluedevil-requestpin 'Brad\'s Handy.'
crash_function: isSignalConnected
executable:     /usr/libexec/kde4/bluedevil-requestpin
kernel:         3.14.7-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 isSignalConnected at kernel/qobject_p.h:237
 #1 QMetaObject::activate at kernel/qobject.cpp:3472
 #2 KNotification::activated at /usr/src/debug/kdelibs-4.12.5/x86_64-redhat-linux-gnu/kdeui/knotification.moc:143
 #3 KNotification::activate at /usr/src/debug/kdelibs-4.12.5/kdeui/notifications/knotification.cpp:239
 #4 KNotificationManager::notificationActivated at /usr/src/debug/kdelibs-4.12.5/kdeui/notifications/knotificationmanager.cpp:84
 #5 QMetaObject::activate at kernel/qobject.cpp:3567
 #6 OrgKdeKNotifyInterface::notificationActivated at /usr/src/debug/kdelibs-4.12.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:126
 #7 OrgKdeKNotifyInterface::qt_static_metacall at /usr/src/debug/kdelibs-4.12.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:66
 #8 qt_static_metacall at /usr/src/debug/kdelibs-4.12.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:115
 #9 OrgKdeKNotifyInterface::qt_metacall at /usr/src/debug/kdelibs-4.12.5/x86_64-redhat-linux-gnu/kdeui/knotify_interface.moc:116

Potential duplicate: bug 707025

Comment 1 Brad 2014-06-18 00:08:52 UTC
Created attachment 909802 [details]
File: backtrace

Comment 2 Brad 2014-06-18 00:08:53 UTC
Created attachment 909803 [details]
File: cgroup

Comment 3 Brad 2014-06-18 00:08:54 UTC
Created attachment 909804 [details]
File: core_backtrace

Comment 4 Brad 2014-06-18 00:08:56 UTC
Created attachment 909805 [details]
File: dso_list

Comment 5 Brad 2014-06-18 00:08:58 UTC
Created attachment 909806 [details]
File: environ

Comment 6 Brad 2014-06-18 00:08:59 UTC
Created attachment 909807 [details]
File: exploitable

Comment 7 Brad 2014-06-18 00:09:01 UTC
Created attachment 909808 [details]
File: limits

Comment 8 Brad 2014-06-18 00:09:02 UTC
Created attachment 909809 [details]
File: maps

Comment 9 Brad 2014-06-18 00:09:05 UTC
Created attachment 909810 [details]
File: open_fds

Comment 10 Brad 2014-06-18 00:09:06 UTC
Created attachment 909811 [details]
File: proc_pid_status

Comment 11 Brad 2014-06-18 00:09:08 UTC
Created attachment 909812 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 12:08:53 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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-06-29 21:11:08 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.