abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: /usr/bin/python -Es /usr/bin/sealert -s component: setroubleshoot crash_function: poll_for_event executable: /usr/bin/python kernel: 2.6.35.6-45.fc14.i686 package: setroubleshoot-server-2.2.102-1.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1288460162 uid: 500 How to reproduce ----- 1.yum groupinstall gnome-desktop from f14 RC1-live-soas sugar-terminal 2.yum install sugar-emulator liveusb-creator livecd-tools spin-kickstarts 3.log out of sugar and switch to gnome with gdm
Created attachment 456658 [details] File: backtrace
*** Bug 645545 has been marked as a duplicate of this bug. ***
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start f14 desktop live in Virtualbox 2. 3.
*** Bug 643094 has been marked as a duplicate of this bug. ***
*** Bug 646795 has been marked as a duplicate of this bug. ***
*** Bug 647314 has been marked as a duplicate of this bug. ***
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Logged into my desktop. An SELinux window popped up complaining about ntpd. I tried to report the bug, and crash.
Looks to me like a python crash.
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 -qa gtk2 libxcb pygtk2 Looking at the backtrace, it looks like this: assertion failed xcb_io.c:221: poll_for_event: Assertion `(((long) (event_sequence) - (long) (dpy->request)) <= 0) inside frame 3 of the program's single thread inside "poll_for_event", deep within GTK's main loop. Something's gone wrong in the communication between GTK and the X server. Reassigning component from "python" to "gtk2"; hopefully the gtk2 maintainer will be able to figure this out further or reassign as necessary.
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Click on report in the crash reporter for se linux
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Every time I click report in bug report 2. 3. Comment ----- No
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Click on "Update Policy" when the SELinux report appears. 2. 3.
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Started setroubleshoot, which reported several postifx errors (cannot perform "getattr" on postfix/drop) 2. clicked "Delete" 3.That's all folks.
*** Bug 474009 has been marked as a duplicate of this bug. ***
*** Bug 475304 has been marked as a duplicate of this bug. ***
Package: setroubleshoot-server-2.2.102-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Clicked on "Update Policy" 2. 3.
Jon please update your system yum -y update
What version is this supposed to be fixed in? I am still seeing it with gtk2-2.24-4-1.fc15 on an updated F15 Beta install when canceling ntp during firstboot (see bug 475304 and bug 702659)
*** Bug 702659 has been marked as a duplicate of this bug. ***
The reporter of bug #475304 has seen it happen again on F-15 and I could confirm it by running firstboot, configuring for NTP and cancelling the "Contacting NTP server" dialog: nils@gibraltar:~> sudo firstboot Loading /lib/kbd/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz python2: xcb_io.c:221: poll_for_event: Assertion `(((long) (event_sequence) - (long) (dpy->request)) <= 0)' failed. firstboot: Fatal IO error 4 (Interrupted system call) on X server :0.0. nils@gibraltar:~> Matthias, do you want this bug reopened or a new one?