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 480199 - crash in Main Menu:
crash in Main Menu:
Status: RESOLVED DUPLICATE of bug 468635
Product: alacarte
Classification: Applications
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: Alacarte Maintainer(s)
Alacarte Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-09-25 12:43 UTC by kryptt
Modified: 2007-09-28 09:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kryptt 2007-09-25 12:43:21 UTC
Version: 0.11.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-11 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo-r8 #18 PREEMPT Thu Sep 6 21:27:28 AST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Milk 2.0
Icon Theme: Mist

Memory status: size: 191590400 vsize: 191590400 resident: 44269568 share: 24854528 rss: 44269568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190724158 rtime: 249 utime: 234 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/alacarte'

(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 47384649543904 (LWP 5772)]
0x00002b1898c9dad5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47384649543904 (LWP 5772))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gmenu_tree_ref
    from /usr/lib/libgnome-menu.so.2
  • #4 ??
    from /usr/lib64/python2.4/site-packages/gmenu.so
  • #5 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #6 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #7 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #8 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #9 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #10 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #13 ??
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #15 ??
    from /usr/lib/libpython2.4.so.1.0
  • #16 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #17 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #18 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #39 ??
    from /usr/lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #41 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gtk/_gtk.so
  • #43 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #44 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #45 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #46 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #47 PyEval_EvalCode
    from /usr/lib/libpython2.4.so.1.0
  • #48 PyRun_FileExFlags
    from /usr/lib/libpython2.4.so.1.0
  • #49 PyRun_SimpleFileExFlags
    from /usr/lib/libpython2.4.so.1.0
  • #50 Py_Main
    from /usr/lib/libpython2.4.so.1.0
  • #51 __libc_start_main
    from /lib/libc.so.6
  • #52 _start
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/applications.menu": Error on line 303 char 14: Document ended unexpectedly inside an element name
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/settings.menu": Error on line 1 char 1: Document was empty or contained only whitespace
EEEK useing shared already!!
** (gnome-panel:9573): WARNING **: Error loading menu layout from "/home/kryptt/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
EEEK useing shared already!!
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-09-28 09:10:18 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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