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)
Created attachment 463268 [details] File: backtrace
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
*** Bug 662525 has been marked as a duplicate of this bug. ***
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.
*** Bug 701526 has been marked as a duplicate of this bug. ***
Continues to occur with evince-3.0.0-1.fc15.
*** Bug 676830 has been marked as a duplicate of this bug. ***
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