Bug 488547 – crash in Main Menu: In 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 488547 - crash in Main Menu: In Main Menu


Summary:	crash in Main Menu: In 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-10-20 09:52 UTC by jarvi
Modified:	2007-11-03 15:26 UTC

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

Description jarvi 2007-10-20 09:52:49 UTC

Version: 0.11.3

What were you doing when the application crashed?
In 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 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 60802000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 410689536 vsize: 410689536 resident: 31387648 share: 16015360 rss: 31387648 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192873835 rtime: 151 utime: 127 stime: 24 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496353104 (LWP 29298)]
(no debugging symbols found)
0x0000003f1fa0d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 171640

Thread 1 (Thread 46912496353104 (LWP 29298))

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

Comment 1 Rob Bradford 2007-11-03 15:26:14 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.

Please update your Fedora installation.

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