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 531632 - crash in System Monitor: Double clicked on the ap...
crash in System Monitor: Double clicked on the ap...
Status: RESOLVED DUPLICATE of bug 516325
Product: system-monitor
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-05 22:54 UTC by Gilles Dartiguelongue
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Gilles Dartiguelongue 2008-05-05 22:54:37 UTC 
Version: 2.22.1

What were you doing when the application crashed?
Double clicked on the applet.

I double clicked on the applet to check our downstream bug report https://bugs.gentoo.org/show_bug.cgi?id=217633


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.1 2008-04-19 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r4-mactel #1 SMP Tue Apr 8 12:25:57 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Unity
Icon Theme: gnome-alternative

Memory status: size: 205279232 vsize: 205279232 resident: 12242944 share: 9965568 rss: 12242944 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210035195 rtime: 2 utime: 2 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x2aed630f7e90 (LWP 25144)]
0x00002aed5b101f25 in __libc_waitpid (pid=25147, stat_loc=0x7fff531ded20, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c
Current language:  auto; currently c

+ Trace 196978

Thread 1 (Thread 0x2aed630f7e90 (LWP 25144))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 IA__g_spawn_sync
    at gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 213
  • #4 <signal handler called>
  • #5 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 *__GI_abort
    at abort.c line 88
  • #7 IA__g_logv
    at gmessages.c line 497
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 main
    at procman.cpp line 651 


----------- .xsession-errors (198 sec old) ---------------------
alarm-queue.c:607 (load_alarms_for_today) - From Tue May  6 02:00:01 2008
 to Tue May  6 02:00:01 2008
alarm-queue.c:544 (load_alarms) 
alarm-queue.c:563 (loevolution-alarm-notify-Message: alarm.c:246: Requested removal of nonexistent alarm!
evolution-alarm-notify-Message: Setting timeout for 86400 1210118400 1210032000
evolution-alarm-notify-Message:  Wed May  7 02:00:00 2008
evolution-alarm-notify-Message:  Tue May  6 02:00:00 2008
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
--------------------------------------------------
Comment 1 Gilles Dartiguelongue 2008-05-05 22:55:21 UTC 

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