Bug 657772

Summary: [abrt] evince-2.32.0-2.fc14: initable_init: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Saikat Guha <sg266>
Component: glib2Assignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: burhan.ali, gaul, lacombar, mclasen, mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2580e8202cf6064eefe2f5726fbef45dccf4c0f4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 19:19:53 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 Saikat Guha 2010-11-27 19:51:35 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evince main.pdf
comment: Note: "unset DBUS_SESSION_BUS_ADDRESS" allows evince to start. So DBUS_SESSION_BUS_ADDRESS isn't fundamentally necessary. If the address is incorrect, evince should simply fallback to not using it rather than crashing.
component: evince
crash_function: initable_init
executable: /usr/bin/evince
kernel: 2.6.35.6-48.fc14.x86_64
package: evince-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1290886069
uid: 500

How to reproduce
-----
1.Use stale bus address in DBUS_SESSION_BUS_ADDRESS
   (e.g. by starting GNU/screen under one X session, restarting the X session, and starting evince from inside screen)

Comment 1 Saikat Guha 2010-11-27 19:51:39 UTC
Created attachment 463268 [details]
File: backtrace

Comment 2 Marek Kašík 2010-11-29 16:15:32 UTC
Hi Saikat,

this has to be solved in glib2 because initable_init() doesn't return an error but calls assert which triggers SIGABRT.
=> reassigning

Marek

Comment 3 Marek Kašík 2010-12-13 09:55:13 UTC
*** Bug 662525 has been marked as a duplicate of this bug. ***

Comment 4 Arnaud Lacombe 2011-01-08 19:49:12 UTC
Package: evince-2.32.0-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. start a screen session, the environment will contain DBUS information
2. logout/login, previous information are now invalid
3. re-attache the screen session
4. try to read a pdf

Comment
-----
Failure to attach to a D-BUS session should not prevent to read a pdf. At worst,
it should only prevent access to functionnality using D-BUS.

Comment 5 Marek Kašík 2011-05-30 10:34:26 UTC
*** Bug 701526 has been marked as a duplicate of this bug. ***

Comment 6 Andrew Gaul 2011-05-30 15:07:20 UTC
Continues to occur with evince-3.0.0-1.fc15.

Comment 7 abrt-bot 2012-03-20 15:40:37 UTC
*** Bug 676830 has been marked as a duplicate of this bug. ***

Comment 8 Fedora End Of Life 2012-08-16 19:19:55 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