Bug 481417 – crash in Main Menu: i change the name of an ...

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 481417 - crash in Main Menu: i change the name of an ...


Summary:	crash in Main Menu: i change the name of an ...


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-09-28 20:24 UTC by franck.wiatrowski
Modified:	2007-10-07 17:56 UTC

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

Description franck.wiatrowski 2007-09-28 20:24:11 UTC

Version: 0.11.3

What were you doing when the application crashed?
i change the name of an entry  of menus


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 47443968 vsize: 47443968 resident: 24150016 share: 14602240 rss: 24150016 rss_rlim: 4294967295
CPU usage: start_time: 1191018096 rtime: 438 utime: 413 stime: 25 cutime:136 cstime: 19 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 -1208928576 (LWP 3082)]
(no debugging symbols found)
0x00b1c402 in __kernel_vsyscall ()

+ Trace 166269

Thread 1 (Thread -1208928576 (LWP 3082))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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 ---------------------
** (nautilus:2861): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS
** (nautilus:2861): WARNING **: Can not get _NET_WORKAREA
** (nautilus:2861): WARNING **: Can not determine workarea, guessing at layout
The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 621 error_code 4 request_code 55 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------

Comment 1 Rob Bradford 2007-10-07 17:56:01 UTC

This crash is because libgnome-menu is built with debugging turned off. Upgrading to the latest release avoids this.

This has been fixed in Fedora too.

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