Bug 447236 – crash in Main Menu: i was deleting wine 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 447236 - crash in Main Menu: i was deleting wine menu...


Summary:	crash in Main Menu: i was deleting wine 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-13 17:41 UTC by phildar60
Modified:	2007-06-13 22:07 UTC

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

Description phildar60 2007-06-13 17:41:32 UTC

Version: 0.11.3

What were you doing when the application crashed?
i was deleting wine menus from my main menu


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 364445696 vsize: 364445696 resident: 35368960 share: 20840448 rss: 35368960 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181756350 rtime: 238 utime: 208 stime: 30 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 46912496213840 (LWP 5262)]
(no debugging symbols found)
0x000000366160d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 140714

Thread 1 (Thread 46912496213840 (LWP 5262))

#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 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_menu_shell_activate_item
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 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#25 ??
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit
from /lib64/libgobject-2.0.so.0
#28 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#33 ??
from /lib64/libglib-2.0.so.0
#34 g_main_loop_run
from /lib64/libglib-2.0.so.0
#35 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib64/python2.5/site-packages/gtk-2.0/gtk/_gtk.so
#37 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#38 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#39 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#40 PyEval_EvalCodeEx
from /usr/lib64/libpython2.5.so.1.0
#41 PyEval_EvalCode
from /usr/lib64/libpython2.5.so.1.0
#42 ??
from /usr/lib64/libpython2.5.so.1.0
#43 PyRun_FileExFlags
from /usr/lib64/libpython2.5.so.1.0
#44 PyRun_SimpleFileExFlags
from /usr/lib64/libpython2.5.so.1.0
#45 Py_Main
from /usr/lib64/libpython2.5.so.1.0
#46 __libc_start_main
from /lib64/libc.so.6
#47 _start
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (502 sec old) ---------------------
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:CMP_WaitNoPendingInstallEvents 0
fixme:setupapi:SetupDiGetClassDevsW returning empty list
fixme:setupapi:SetupDiEnumDeviceInterfaces 0x8541c0, (nil), {53f56307-b6bf-11d0-94f2-00a0c91efb8b}, 0x00000000, 0x7c8ed3ac
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Damien Durand 2007-06-13 22:07:27 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 430074 ***