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 446481 - crash in Panel: opening alacarte menu ed...
crash in Panel: opening alacarte menu ed...
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-11 19:43 UTC by napopa_2000
Modified: 2007-06-11 21:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description napopa_2000 2007-06-11 19:43:35 UTC 
Version: 2.18.2

What were you doing when the application crashed?
opening alacarte menu editor


Distribution: Unknown
Gnome Release: 2.18.2 2007-05-31 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-ARCH #1 SMP PREEMPT Fri Jun 8 20:10:32 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 29413376 vsize: 29413376 resident: 16498688 share: 11755520 rss: 16498688 rss_rlim: 4294967295
CPU usage: start_time: 1181590425 rtime: 116 utime: 104 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224759616 (LWP 15811)]
(no debugging symbols found)
0xb7f55410 in __kernel_vsyscall ()

+ Trace 140154

Thread 1 (Thread -1224759616 (LWP 15811))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #6 remove_watch
    from /usr/lib/libgnome-menu.so.2
  • #7 inotify_data_pending
    from /usr/lib/libgnome-menu.so.2
  • #8 g_io_unix_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (506 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Visualizza)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Visualizza)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Visualizza)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 André Klapper 2007-06-11 21:31:42 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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