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 572026 - crash in Panel: Leaving the computer on ...
crash in Panel: Leaving the computer on ...
Status: RESOLVED DUPLICATE of bug 452428
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-16 16:04 UTC by jeremybubs
Modified: 2009-02-16 18:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jeremybubs 2009-02-16 16:04:39 UTC 
Version: 2.20.3

What were you doing when the application crashed?
Leaving the computer on overnight.


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-486 #1 Sat Jan 10 17:46:23 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 367480832 vsize: 367480832 resident: 316157952 share: 9994240 rss: 316157952 rss_rlim: 4294967295
CPU usage: start_time: 1234284542 rtime: 221450 utime: 190366 stime: 31084 cutime:9 cstime: 2562 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6d68700 (LWP 24576)]
0xb7f4a430 in __kernel_vsyscall ()

+ Trace 212604

Thread 1 (Thread 0xb6d68700 (LWP 24576))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 __kernel_vsyscall
  • #8 raise
    from /lib/i686/cmov/libc.so.6
  • #9 abort
    from /lib/i686/cmov/libc.so.6
  • #10 IA__g_assertion_message
  • #11 IA__g_assertion_message_expr
    at /tmp/buildd/glib2.0-2.16.6/glib/gtestutils.c line 1229
  • #12 ??
    from /usr/lib/libORBit-2.so.0
  • #13 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (487674 sec old) ---------------------
GCJ PLUGIN: thread 0x88e3d78: NP_GetValue return
GCJ PLUGIN: thread 0x88e3d78: NP_GetValue
GCJ PLUGIN: thread 0x88e3d78: NP_GetValue: returning plugin description.
GCJ PLUGIN: thread 0x88e3d78: NP_GetValue return
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
DEBUG::Tue Feb 10 15:54:15 EST 2009::com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager::addNewOutboundRequests::242:
  ConnectDisconnectManager::address exception: full=/2001:0:cf2e:3096:1cef:f4c:68cd:3d2d:57457, hostname=2001:0:cf2e:3096:1cef:f4c:68cd:3d2d, port=57457, unresolved=false, full_sub=2001:0:cf2e:3096:1c
 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=-1, remote_address=<null>, remote_port=0
    TCPConnectionManager::mainLoop::212,TCPConne
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2009-02-16 18:02:55 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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