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 346405 - system monitor crashed when left unattended for a weekend
system monitor crashed when left unattended for a weekend
Status: RESOLVED NOTABUG
Product: system-monitor
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-02 16:49 UTC by timeless
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description timeless 2006-07-02 16:49:24 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: gnome-applets
Severity: Normal
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: system monitor crashed when left unattended for a weekend
Bugzilla-Product: gnome-applets
Bugzilla-Component: multiload
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. leave computer alone for a weekend
2. return to computer
3. receive crash notice

Expected Results:
no crash dialog

How often does this happen?
this is the first such crash that i can recall

Additional Information:



Debugging Information:

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 -1492269376 (LWP 11752)]
[New Thread -1503990864 (LWP 11756)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 69157

Thread 1 (Thread -1492269376 (LWP 11752))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 IA__g_object_remove_weak_pointer
    at gobject.c line 1517
  • #5 fetch_net_wm_check_window
    at gdkevents-x11.c line 2559
  • #6 IA__gdk_text_extents_wc
    at gdkfont-x11.c line 722
  • #7 _gdk_x11_convert_to_format
    at gdkdrawable-x11.c line 1198
  • #8 gdk_x11_draw_pixbuf
    at gdkdrawable-x11.c line 1260
  • #9 gdk_x11_draw_pixbuf
    at gdkdrawable-x11.c line 1272
  • #10 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #11 g_main_context_iterate
    at gmain.c line 2547
  • #12 IA__g_main_loop_run
    at gmain.c line 2751
  • #13 gtk_label_button_press
    at gtklabel.c line 2737
  • #14 ??
  • #15 ??
  • #16 _IO_stdin_used
  • #17 ??
  • #18 ??
  • #19 ??
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-07-02 16:49 -------


Bugreport moved from gnome-applets / multiload
  to system-monitor / general
Comment 1 Benoît Dejean 2006-07-02 18:49:57 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Karsten Bräckelmann 2006-09-18 02:11:50 UTC 
Ugh. Got a stacktrace. Even got debugging symbols. REOPENing.
Comment 3 Benoît Dejean 2006-09-18 11:09:34 UTC 
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 4 Karsten Bräckelmann 2006-09-18 13:52:54 UTC 
Benoît, the stacktrace is fine. Please explain, what you want. REOPENing.
Comment 5 Benoît Dejean 2006-09-18 16:29:56 UTC 
it's not, it has no debug info about multiload.
Comment 6 Elijah Newren 2006-09-18 17:57:12 UTC 
Benoit: um, multiload-applet-2 isn't what crashed.  gnome-system-monitor was.  Why would debug info about multiload be needed?
Comment 7 Karsten Bräckelmann 2006-09-18 19:12:20 UTC 
multiload...  Ah, now I understand. Benoit, as Elijah said, that's not what crashed. The report merely has been set falsely to that product initially, and has been corrected automatically.

So we do not need debugging symbols for multiload.


Anyway -- please be more verbose, when requesting specific information. Multiload isn't mentioned in the GettingTraces documentation at all. Thus, there is no way for the user to understand what you are about, by looking at the page you pointed him to.
Comment 8 Benoît Dejean 2006-09-18 19:40:59 UTC 
Sorry, i misread. system-monitor is the name of the applet and the application so i even fool myself. But this stacktrace doesn't have any debug symbol for system-monitor. it's has for gtk, but not system-monitor. So the stacktrace is bad.


and bugbuddy is screwed :

Synopsis: system monitor crashed when left unattended for a weekend
Bugzilla-Product: gnome-applets
Bugzilla-Component: multiload

that why i though it was about the applet, the bug header is always wrong ...
Comment 9 Chris Kühl 2011-02-23 21:46:23 UTC 
Is this still occurring? I've tried this a couple times without a crash.
Comment 10 Chris Kühl 2011-03-03 22:47:49 UTC 
Due to the lack of response, inability to reproduce, and age of this bug I'm closing.