Bug 458021 – crash in Main Menu: Deleting menu item

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 458021 - crash in Main Menu: Deleting menu item


Summary:	crash in Main Menu: Deleting menu item


Status:	RESOLVED DUPLICATE of bug 456228

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-07-18 16:17 UTC by carl_d_harris
Modified:	2007-07-19 15:05 UTC

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

Description carl_d_harris 2007-07-18 16:17:12 UTC

Version: 0.11.3

What were you doing when the application crashed?
Deleting menu item


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:21:08 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: 68747264 vsize: 68747264 resident: 32632832 share: 22716416 rss: 32632832 rss_rlim: 4294967295
CPU usage: start_time: 1184775394 rtime: 1438 utime: 1218 stime: 220 cutime:288 cstime: 101 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 -1208473392 (LWP 15742)]
(no debugging symbols found)
0x00b78402 in __kernel_vsyscall ()

+ Trace 148880

Thread 1 (Thread -1208473392 (LWP 15742))

#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 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_menu_shell_activate_item
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 /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /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 /lib/libglib-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_gtk.so
#43 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#44 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#45 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#46 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#47 PyEval_EvalCode
from /usr/lib/libpython2.5.so.1.0
#48 ??
from /usr/lib/libpython2.5.so.1.0
#49 PyRun_FileExFlags
from /usr/lib/libpython2.5.so.1.0
#50 PyRun_SimpleFileExFlags
from /usr/lib/libpython2.5.so.1.0
#51 PyRun_AnyFileExFlags
from /usr/lib/libpython2.5.so.1.0
#52 Py_Main
from /usr/lib/libpython2.5.so.1.0
#53 main
#0 __kernel_vsyscall



----------- .xsession-errors (44291 sec old) ---------------------
[PP] Using codec's postprocessing, max q = 4.
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 320x240 => 320x240 Planar YV12 
Selected video codec: [wmv8] vfm: dshow (Windows Media Video 8)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 32000 Hz, 2 ch, s16le, 48.0 kbit/4.69% (ratio: 6000->128000)
Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
A:   5.0 V:   5.0 A-V:  0.002 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   5.0 V:   5.0 A-V:  0.006 ct: -0.003   2/  2 ??% ??% ??,?% 0 0              
A:   5.1 V:   5.1 A-V: -0.040 ct: -0.0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-07-19 15:05:58 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 456228 ***