abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: nautilus --sm-client-id 1070f84de646d2c750128882373990134800000053800040 --sm-client-state-file /home/nice/.config/session-state/nautilus-1288903070.state component: nautilus crash_function: *INT_cairo_set_source_surface executable: /usr/bin/nautilus kernel: 2.6.35.6-48.fc14.i686.PAE package: nautilus-2.32.0-1.fc14 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1288926963 uid: 500 comment ----- Since upgrading to Fedora 14, after running for a few hours I start to get messages on the console Maximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedxwininfo: unable to open display ':0.0' I am unable to open any new windows then and lots of programs crash. When things are still running correctly. $ xlsclients |wc -l 44 $ xwininfo -root -children | wc -l 208 A few mintues later $ xwininfo -root -children | wc -l Maximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedxwininfo: unable to open display ':0.0' 0 $ xlsclients |wc -l Maximum number of clients reachedxlsclients: unable to open display ":0.0" 0 $ xterm Maximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedMaximum number of clients reachedxterm Xt error: Can't open display: :0.0 $ I believe this crash was captured when about 6 file managers looked like they randomly started loading on the taskbar, pulsated for 30 seconds or so then started crashing and disappearing.
Created attachment 457995 [details] File: backtrace
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) Comment ----- Unable to run Gnome for more than a day without these crashes starting. (Switched to KDE for a day and didn't seem to get the same problem). This crash happened seconds after https://bugzilla.redhat.com/show_bug.cgi?id=651694
I think I have solved this. The first solution is just to switch to KDE, but that wasn't a good long term solution since I wanted to be on Gnome. The second solution is: rpm -e gnome-packagekit It seems as though gpk-update-icon has a resource leakage. As far as I could tell, that package didn't do anything I needed and my problems seem to have gone away since getting rid of it.
Backtrace analysis found this bug to be similar to bug #680606, closing as duplicate. Bugs which were found to be similar to this bug: bug #657120, bug #680606, bug #718702 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 680606 ***