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 431448 - crash in Main Menu: selecting menu items (sy...
crash in Main Menu: selecting menu items (sy...
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-04-19 19:38 UTC by allofmyjunkemails
Modified: 2007-04-20 00:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description allofmyjunkemails 2007-04-19 19:38:28 UTC
Version: 0.11.3

What were you doing when the application crashed?
selecting menu items (system > Admin > User and Groups)


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3088.fc7 #1 SMP Wed Apr 18 15:12:44 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 69693440 vsize: 69693440 resident: 30998528 share: 15560704 rss: 30998528 rss_rlim: 4294967295
CPU usage: start_time: 1177011002 rtime: 5129 utime: 4631 stime: 498 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 -1208092992 (LWP 2922)]
(no debugging symbols found)
0x00238402 in __kernel_vsyscall ()

Thread 1 (Thread -1208092992 (LWP 2922))

  • #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 ---------------------
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
error getting update info:  Cannot find a valid baseurl for repo: extras-development
** (gnome-panel:2785): WARNING **: Error loading menu layout from "/home/user/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
** (gnome-panel:2785): WARNING **: Error loading menu layout from "/home/user/.config/menus/applications.menu": Error on line 1 char 1: Document was empty or contained only whitespace
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3400003 (Main Menu); these messages lack timestamps and therefore suck.
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-04-20 00:53:22 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 ***