Bug 665927

Summary: [abrt] setroubleshoot-server-3.0.15-1.fc14: _dbus_warn_check_failed detects a fatal error
Product: [Fedora] Fedora Reporter: Bill Gradwohl <bill>
Component: dbus-pythonAssignee: David Zeuthen <davidz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: davidz, dmalcolm, dwalsh, ivazqueznet, james.antill, jonathansteffan, mclasen, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d96808de2d30ff5522e2f5337c1f07571915b263
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 17:52:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Bill Gradwohl 2010-12-28 00:01:02 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
component: setroubleshoot
crash_function: _dbus_abort
executable: /usr/bin/python
kernel: 2.6.35.10-74.fc14.x86_64
package: setroubleshoot-server-3.0.15-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1293492396
uid: 0

How to reproduce
-----
1. No idea
2.
3.

Comment 1 Bill Gradwohl 2010-12-28 00:01:22 UTC
Created attachment 470894 [details]
File: backtrace

Comment 2 Dave Malcolm 2010-12-28 20:38:35 UTC
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running the following command?
  rpm -q setroubleshoot-server dbus-python dbus dbus-libs

Looking at the backtrace, it looks like the problem occurred in thread #1 in message_queue_dispatch: "_dbus_warn_check_failed" detects this error:
> The last reference on a connection was dropped without closing the connection.
> This is a bug in an application.
> See dbus_connection_unref() documentation for details.

and terminates the process with SIGABRT.

Reassigning component from "python" to "dbus-python";  hopefully the dbus-python maintainer will be able to figure this out further or reassign as necessary (it may yet be an SETroubleshoot bug...)

Comment 3 Fedora End Of Life 2012-08-16 17:52:31 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping