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 453863 - crash in Main Menu: clicking the button to m...
crash in Main Menu: clicking the button to m...
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-07-05 05:01 UTC by Tony
Modified: 2007-08-08 08:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Tony 2007-07-05 05:01:49 UTC
Version: 0.11.3

What were you doing when the application crashed?
clicking the button to make the shorcuts go up


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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 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: 376254464 vsize: 376254464 resident: 38109184 share: 21704704 rss: 38109184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183611353 rtime: 362 utime: 337 stime: 25 cutime:14 cstime: 3 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 46912496279376 (LWP 8936)]
(no debugging symbols found)
0x00000036ec80d865 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496279376 (LWP 8936))

  • #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_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #9 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #10 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #11 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #12 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #13 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #14 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #16 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #17 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #18 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #19 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #20 ??
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib64/libgobject-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 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #31 ??
    from /lib64/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #39 ??
    from /lib64/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #41 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gtk/_gtk.so
  • #43 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #44 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #45 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #46 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #47 PyEval_EvalCode
    from /usr/lib64/libpython2.5.so.1.0
  • #48 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #49 PyRun_FileExFlags
    from /usr/lib64/libpython2.5.so.1.0
  • #50 PyRun_SimpleFileExFlags
    from /usr/lib64/libpython2.5.so.1.0
  • #51 Py_Main
    from /usr/lib64/libpython2.5.so.1.0
  • #52 __libc_start_main
    from /lib64/libc.so.6
  • #53 _start
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
QTextImage: no mimesource for /home/Tony/.kde/share/apps/amarok/albumcovers/cache/150@9771e851159d12f8ef2eab5fd69436d2@shadow
QTextImage: no mimesource for /home/Tony/.kde/share/apps/amarok/albumcovers/cache/150@9771e851159d12f8ef2eab5fd69436d2@shadow
QTextImage: no mimesource for /home/Tony/.kde/share/apps/amarok/albumcovers/cache/150@9771e851159d12f8ef2eab5fd69436d2@shadow
mail-notification-Message: Mail Notification is already running
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
DCOP Cleaning up dead connections.
"/usr/bin/alacarte": not in executable format: File format not recognized
kbuildsycoca running...
Reusing existing ksycoca
DCOP Cleaning up dead connections.
--------------------------------------------------
Comment 1 Travis Watkins 2007-08-08 08:57:14 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 ***