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 598879 - crash in Panel: away from computer
crash in Panel: away from computer
Status: RESOLVED INCOMPLETE
Product: gnome-panel
Classification: Other
Component: general
2.26.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 599254 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-18 23:31 UTC by ben+debian
Modified: 2009-10-22 09:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description ben+debian 2009-10-18 23:31:47 UTC 
Version: 2.26.3

What were you doing when the application crashed?
away from computer


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-2-powerpc64 #1 SMP Sun Oct 4 09:29:28 UTC 2009 ppc64
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 89575424 vsize: 89575424 resident: 15974400 share: 8192000 rss: 15974400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255906372 rtime: 640 utime: 513 stime: 127 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xf652d430 (LWP 7781)]
0x0f291adc in __lll_lock_wait () from /lib/libpthread.so.0

+ Trace 218406

Thread 2 (Thread 0xf652d430 (LWP 7781))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.22.0-1-powerpc-CFSeO5/glib2.0-2.22.0/glib/gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.22.0-1-powerpc-CFSeO5/glib2.0-2.22.0/glib/gspawn.c line 700
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 js_NewGCThing
    at jsgc.c line 1869
  • #6 js_NewString
    at jsstr.c line 2472
  • #7 JS_NewString
    at jsapi.c line 5212 


----------- .xsession-errors ---------------------
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Invalid rate plugin version 10002
Cannot access memory at address 0x8
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-10-18 23:45:49 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Akhil Laddha 2009-10-22 09:07:22 UTC 
*** Bug 599254 has been marked as a duplicate of this bug. ***