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 456228 - 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)
: 458021 465820 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-12 13:25 UTC by Mike
Modified: 2007-08-12 01:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Mike 2007-07-12 13:25:22 UTC 
Version: 0.11.3

What were you doing when the application crashed?
опитах да изтрия ненужни менюта на wine


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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Xfce-curve
Icon Theme: Neu

Memory status: size: 59805696 vsize: 59805696 resident: 33349632 share: 22192128 rss: 33349632 rss_rlim: 4294967295
CPU usage: start_time: 1184246246 rtime: 444 utime: 385 stime: 59 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 -1208269120 (LWP 6579)]
(no debugging symbols found)
0x00622402 in __kernel_vsyscall ()

+ Trace 147515

Thread 1 (Thread -1208269120 (LWP 6579))

  • #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 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 (7 sec old) ---------------------
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x3350f4) stub!
fixme:process:IsWow64Process (0xffffffff 0x34e2b8) stub!
fixme:shell:DllCanUnloadNow stub
wine: Unhandled page fault on write access to 0x00000067 at address 0x603295f7 (thread 0029), starting debugger...
"/usr/bin/alacarte": not in executable format: File format not recognized
--------------------------------------------------
Comment 1 palfrey 2007-07-19 15:05:58 UTC 
*** Bug 458021 has been marked as a duplicate of this bug. ***
Comment 2 Iestyn Pryce 2007-08-07 10:12:49 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 ***
Comment 3 Pedro Villavicencio 2007-08-12 01:16:48 UTC 
*** Bug 465820 has been marked as a duplicate of this bug. ***