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 536458 - crash in Panel: I wasn't local to the ma...
crash in Panel: I wasn't local to the ma...
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-03 16:36 UTC by dann frazier
Modified: 2008-06-03 16:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description dann frazier 2008-06-03 16:36:16 UTC
Version: 2.20.3

What were you doing when the application crashed?
I wasn't local to the machine when it crashed, so I'm not totally sure. But, it looks like bug-buddy started at approximately the same time I started an vnc session. I typically run gnome locally and KDE in a vnc session in which I run evolution. So maybe evolution caused this crash?


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-1-itanium #2 SMP Mon Apr 28 15:57:16 UTC 2008 ia64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 91029504 vsize: 91029504 resident: 30097408 share: 13303808 rss: 30097408 rss_rlim: 18446744073709551615
CPU usage: start_time: 1215192021 rtime: 42582 utime: 39704 stime: 2878 cutime:3 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x20000000029c33e0 (LWP 22951)]
[New Thread 0x2000000004cb71c0 (LWP 26616)]
0xa000000000010721 in __kernel_syscall_via_break ()

Thread 2 (Thread 0x2000000004cb71c0 (LWP 26616))

  • #0 __kernel_syscall_via_break
  • #1 poll
    from /lib/libc.so.6.1
  • #2 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2951
  • #3 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #4 link_io_thread_fn
    from /usr/lib/libORBit-2.so.0
  • #5 g_thread_create_proxy
    at /build/buildd/glib2.0-2.16.3/glib/gthread.c line 635
  • #6 start_thread
    from /lib/libpthread.so.0
  • #7 __clone2
    from /lib/libc.so.6.1

Thread 1 (Thread 0x20000000029c33e0 (LWP 22951))

  • #0 __kernel_syscall_via_break
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374


----------- .xsession-errors ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Audacious)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Audacious)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-panel:22951): WARNING **: The calendar backend for file:///home/dannf/.evolution/tasks/local/system has crashed.
warning: .dynamic section for "/usr/lib/libgnome-desktop-2.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgnome-menu.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/gio/modules/libgvfsdbus.so" is not at the expected address (wrong library or version mismatch?)
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 Philip Withnall 2008-06-03 16:57:26 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 378854 ***