Hide Forgot
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: xscreensaver -no-splash component: xscreensaver crash_function: g_main_context_init_pipe executable: /usr/bin/xscreensaver kernel: 2.6.35.10-74.fc14.i686 package: xscreensaver-base-1:5.12-12.fc14 rating: 4 reason: Process /usr/bin/xscreensaver was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1297055544 uid: 500 How to reproduce ----- 1. I was AFK when this happened, as far as I know 2. 3.
Created attachment 477374 [details] File: backtrace
Does this segfault constantly hapen when you get away from your computer?
Not always, but happened at least twice over the last 2 days. Never seen it happen since installing F14 in October. Updated to xscreensaver*5.12-12.fc14.i686 on Jan 31st, that might've been the start
Once switching to fprintd
No idea why glib would fail to create a main loop context here. Konstantin, could you check in your ~/.xsession-errors what the full error message for "Cannot create pipe main loop wake-up" was? Also the actual version of fprintd would be useful.
Haven't noticed the problem since Using Fedora 16 now, recommend closing bug
Backtrace analysis found this bug to be similar to bug #670382 from component fprintd. You might want to check that bug for additional information. This comment is automatically generated.
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