Bug 563096 - Daemon crashes need to be reported more nicely than "org.freedesktop.DBus.Error.NoReply: Message did not receive a reply"
Summary: Daemon crashes need to be reported more nicely than "org.freedesktop.DBus.Err...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 570395 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-09 08:10 UTC by Cătălin George Feștilă
Modified: 2015-02-01 22:51 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:05:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Cătălin George Feștilă 2010-02-09 08:10:25 UTC
Description of problem:
abrt-gui crash when start it.
Message system (gnome) error is :
"Error while loading the dumplist.
org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)"
Version-Release number of selected component (if applicable):
2.6.31.12-174.2.3.fc12.i686
Fedora 12
How reproducible:
I shotdown when abrt-gui try connect ( i suppose this is problem).

Steps to Reproduce:
1. Set abrt to connect 
2. Shutdown system when you have see icon of abrt
3.
  
Actual results:
Not crash

Expected results:


Additional info:
Before abrt have this problem i receive many crashes from my softwares. For example from soft like blender.This happen when i close it. Blender working fine.

Comment 1 Cătălin George Feștilă 2010-02-09 08:11:41 UTC
Sorry , my mistake :

Actual results:
Crash

Expected results:
Not crash

Comment 2 Jiri Moskovcak 2010-02-09 10:26:27 UTC
When you kill the abrt daemon when gui is trying to talk to it, it will die on timeout. The only thing I can do here is to catch this exception and make the gui die gracefully.

J.

Comment 3 Denys Vlasenko 2010-04-02 16:44:03 UTC
*** Bug 570395 has been marked as a duplicate of this bug. ***

Comment 4 Bug Zapper 2010-11-03 22:37:33 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 5 Bug Zapper 2010-12-03 23:05:03 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

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.