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 443369 - crash in Main Menu: Moving items up and down...
crash in Main Menu: Moving items up and down...
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-06-02 23:26 UTC by cbyates3
Modified: 2007-06-03 10:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cbyates3 2007-06-02 23:26:01 UTC
Version: 0.11.3

What were you doing when the application crashed?
Moving items up and down in Accessories under Applications


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 47898624 vsize: 47898624 resident: 23740416 share: 13275136 rss: 23740416 rss_rlim: 4294967295
CPU usage: start_time: 1180826505 rtime: 1029 utime: 942 stime: 87 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)
[Thread debugging using libthread_db enabled]
[New Thread -1208891712 (LWP 3070)]
(no debugging symbols found)
0x00163402 in __kernel_vsyscall ()

Thread 1 (Thread -1208891712 (LWP 3070))

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


----------- .xsession-errors (10 sec old) ---------------------
(xsane:2946): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(xsane:2946): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(xsane:2946): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(xsane:2946): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(xsane:2946): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
CalDAV Eplugin starting up ...
(evolution:2971): e-data-server-DEBUG: Loaded default categories
(evolution:2971): e-data-server-DEBUG: Saving categories to "/home/cbyates3/.evolution/categories.xml"
Loading "installonlyn" plugin
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------
Comment 1 palfrey 2007-06-03 10:55:50 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 ***