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 435238 - crash in System Monitor: Hiding a process
crash in System Monitor: Hiding a process
Status: RESOLVED DUPLICATE of bug 361345
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-02 16:41 UTC by tc
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description tc 2007-05-02 16:41:08 UTC
Version: 2.16.1

What were you doing when the application crashed?
Hiding a process


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 56246272 vsize: 0 resident: 56246272 share: 0 rss: 16592896 rss_rlim: 0
CPU usage: start_time: 1178123981 rtime: 0 utime: 1067 stime: 0 cutime:874 cstime: 0 timeout: 193 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225229824 (LWP 12274)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225229824 (LWP 12274))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_store_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_tree_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 _IO_stdin_used
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-05-03 13:27:56 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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