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 488069 - crash in Main Menu:
crash in Main Menu:
Status: RESOLVED DUPLICATE of bug 430074
Product: alacarte
Classification: Applications
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: Alacarte Maintainer(s)
Alacarte Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-18 22:11 UTC by Sam
Modified: 2007-10-19 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sam 2007-10-18 22:11:28 UTC
Version: 0.11.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-10-05 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r5 #1 SMP Sun Sep 9 09:51:25 PDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 178319360 vsize: 178319360 resident: 34107392 share: 21241856 rss: 34107392 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192745474 rtime: 45 utime: 41 stime: 4 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/libthread_db.so.1".
(no debugging symbols found)
0x00002af0031139e5 in waitpid () from /lib/libpthread.so.0
  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gmenu_tree_ref
    from /usr/lib/libgnome-menu.so.2
  • #4 ??
    from /usr/lib64/python2.4/site-packages/gmenu.so
  • #5 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #6 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #7 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #8 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #9 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #10 ??
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #12 ??
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #15 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 ??
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gtk/_gtk.so
  • #37 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #38 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #39 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #40 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #41 PyEval_EvalCode
    from /usr/lib/libpython2.4.so.1.0
  • #42 ??
    from /usr/lib/libpython2.4.so.1.0
  • #43 PyRun_SimpleFileExFlags
    from /usr/lib/libpython2.4.so.1.0
  • #44 Py_Main
    from /usr/lib/libpython2.4.so.1.0
  • #45 __libc_start_main
    from /lib/libc.so.6
  • #46 _start


----------- .xsession-errors (100061 sec old) ---------------------
ALSA lib pcm_hw.c:1357:(_snd_pcm_hw_open) Invalid value for card
ALSA lib confmisc.c:848:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:397:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device
ALSA lib confmisc.c:1248:(snd_func_refer) error evaluating name
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device
ALSA lib conf.c:3972:(snd_config_expand) Evaluate error: No such device
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib pcm_hw.c:1357:(_snd_pcm_hw_open) Invalid value for card
ALSA lib confmisc.c:848:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
ALSA lib confmisc.c:397:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_c
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Martin Möller 2007-10-19 18:00:34 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 ***