Bug 447767 – crash in Main Menu: Editing the Main Menu

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 447767 - crash in Main Menu: Editing the Main Menu


Summary:	crash in Main Menu: Editing the Main Menu


Status:	RESOLVED DUPLICATE of bug 430074

Product:	alacarte
Classification:	Applications
Component:	general
Version:	0.11.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Alacarte Maintainer(s)
QA Contact:	Alacarte Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-15 04:36 UTC by John Chendra
Modified:	2007-06-18 12:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description John Chendra 2007-06-15 04:36:00 UTC

Version: 0.11.3

What were you doing when the application crashed?
Editing the Main Menu


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 53207040 vsize: 53207040 resident: 23666688 share: 14082048 rss: 23666688 rss_rlim: 4294967295
CPU usage: start_time: 1181882092 rtime: 170 utime: 150 stime: 20 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208191296 (LWP 3839)]
(no debugging symbols found)
0x0064a402 in __kernel_vsyscall ()

+ Trace 141114

Thread 1 (Thread -1208191296 (LWP 3839))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gmenu_tree_ref
from /usr/lib/libgnome-menu.so.2
#5 gmenu_tree_directory_get_tree
from /usr/lib/libgnome-menu.so.2
#6 ??
from /usr/lib/python2.5/site-packages/gmenu.so
#7 PyObject_GetAttr
from /usr/lib/libpython2.5.so.1.0
#8 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#9 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#10 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#11 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#12 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#13 ??
from /usr/lib/libpython2.5.so.1.0
#14 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#15 ??
from /usr/lib/libpython2.5.so.1.0
#16 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#17 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#18 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#19 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#20 g_closure_invoke
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#23 g_signal_emit
from /lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_cell_renderer_activate
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-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 ??
from /lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /lib/libgobject-2.0.so.0
#32 ??
from /lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#34 g_signal_emit
from /lib/libgobject-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /usr/lib/libgdk-x11-2.0.so.0
#39 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#40 ??
from /lib/libglib-2.0.so.0
#41 g_main_loop_run
from /lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_gtk.so
#44 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#45 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#46 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#47 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#48 PyEval_EvalCode
from /usr/lib/libpython2.5.so.1.0
#49 ??
from /usr/lib/libpython2.5.so.1.0
#50 PyRun_FileExFlags
from /usr/lib/libpython2.5.so.1.0
#51 PyRun_SimpleFileExFlags
from /usr/lib/libpython2.5.so.1.0
#52 PyRun_AnyFileExFlags
from /usr/lib/libpython2.5.so.1.0
#53 Py_Main
from /usr/lib/libpython2.5.so.1.0
#54 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
ScimInputContextPlugin()
~ScimInputContextPlugin()
ScimInputContextPlugin()
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x69 specified for 0x3600039 (First-Run ).
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------

Comment 1 Diego Escalante Urrelo (not reading bugmail) 2007-06-18 12:54:39 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 430074 ***