Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 42199 bytes cmdline: gnome-system-monitor comment: no help here also... component: gnome-system-monitor Attached file: coredump, 13103104 bytes crash_function: _XAllocID executable: /usr/bin/gnome-system-monitor kernel: 2.6.35.13-91.fc14.i686 package: gnome-system-monitor-2.28.2-1.fc14 rating: 4 reason: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1305603364 uid: 500 How to reproduce ----- 1.sorry happened long time ago... 2. 3.
Created attachment 502923 [details] File: backtrace
Package: gnome-system-monitor-3.0.0-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- from an upgrade of a toshiba Laptop from F13.
Package: gnome-system-monitor-2.28.2-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) Comment ----- I really don't know how this bug is created. Could be caused by the noip2, I recall only I've experience something crashed while I was debugging my noip2 init script.
Package: gnome-system-monitor-2.28.2-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.kann mich nicht mehr erinnern 2. 3.
Backtrace analysis found this bug to be similar to bug #699076, closing as duplicate. This bug seems to belong to component gtk2, glib2, cairo, libXrender or libX11. Bugs which were found to be similar to this bug: emacs: bug #743059 evolution: bug #710910 gnome-system-monitor: bug #651239, bug #699061 gnote: bug #699076 libX11: bug #708271 metacity: bug #677057 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 699076 ***