After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331862 - "gnome-system-monitor" has quit unexpectedly on startup
"gnome-system-monitor" has quit unexpectedly on startup
Status: RESOLVED DUPLICATE of bug 160560
Product: system-monitor
Classification: Core
Component: general
2.8.x
Other other
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-20 05:01 UTC by cicada
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description cicada 2006-02-20 05:01:54 UTC 
Distribution: Debian 3.1
Package: system-monitor
Severity: normal
Version: GNOME2.8.3 2.8.1
Gnome-Distributor: Debian
Synopsis: "gnome-system-monitor" has quit unexpectedly on startup
Bugzilla-Product: system-monitor
Bugzilla-Component: general
Bugzilla-Version: 2.8.1
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
When I envoke gnome-system-monitor from either the system monitor panel
applet, or from the command-line, I get an error window stating "The
Application "gnome-system-monitor" has quit unexpectedly."  

Steps to reproduce the crash:
1.  Open Command Line
2.  run 'gnome-system-monitor' without arguments
3.  recieve a bunch of friendly but useless error messages

Expected Results:
?

How often does this happen?
Every time the command is envoked.

Additional Information:
When run from the command-line, I get the following GTK errors:
(gnome-system-monitor:25967): Gtk-CRITICAL **:
gtk_tree_view_column_set_visible: assertion `GTK_IS_TREE_VIEW_COLUMN
(tree_column)' failed

(gnome-system-monitor:25967): Gtk-CRITICAL **:
gtk_tree_view_column_set_fixed_width: assertion `GTK_IS_TREE_VIEW_COLUMN
(tree_column)' failed



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-system-monitor'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223485760 (LWP 25971)]
[New Thread -1223763024 (LWP 25972)]
(no debugging symbols found)
0xb7d20231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 66342

Thread 2 (Thread -1223763024 (LWP 25972))

  • #0 poll
    from /lib/tls/libc.so.6
  • #1 g_main_context_iterate
    at gmain.c line 2867 




------- Bug created by bug-buddy at 2006-02-20 05:01 -------


Unknown version 2.8.1 in product system-monitor.  Setting version to "2.8.x".
Comment 1 Karsten Bräckelmann 2006-02-20 05:14:20 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Stacktraces matches bug 324310 and other duplicates of bug 160560, same description.

*** This bug has been marked as a duplicate of 160560 ***