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 490490 - crash in Main Menu: Moving application item ...
crash in Main Menu: Moving application item ...
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-26 12:09 UTC by vanbeek25
Modified: 2007-11-03 15:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vanbeek25 2007-10-26 12:09:41 UTC
Version: 0.11.3

What were you doing when the application crashed?
Moving application item up in the menu.


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

System: Linux 2.6.22-gentoo-r8 #1 SMP PREEMPT Thu Oct 4 08:34:52 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome-icon-theme-2.18.0

Memory status: size: 223498240 vsize: 223498240 resident: 39297024 share: 21659648 rss: 39297024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193400504 rtime: 307 utime: 277 stime: 30 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)
0x0000003fd740dd55 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_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #9 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #10 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #13 ??
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #15 ??
    from /usr/lib/libpython2.4.so.1.0
  • #16 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #17 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #18 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-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 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/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 /usr/lib/libglib-2.0.so.0
  • #39 ??
    from /usr/lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #41 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 ??
    from /usr/lib64/python2.4/site-packages/gtk-2.0/gtk/_gtk.so
  • #43 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #44 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #45 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #46 PyEval_EvalCodeEx
    from /usr/lib/libpython2.4.so.1.0
  • #47 PyEval_EvalCode
    from /usr/lib/libpython2.4.so.1.0
  • #48 ??
    from /usr/lib/libpython2.4.so.1.0
  • #49 PyRun_SimpleFileExFlags
    from /usr/lib/libpython2.4.so.1.0
  • #50 Py_Main
    from /usr/lib/libpython2.4.so.1.0
  • #51 __libc_start_main
    from /lib/libc.so.6
  • #52 _start


----------- .xsession-errors (29905 sec old) ---------------------
[00000001] main private debug: opening config file /home/michael//.vlc/vlcrc
[00000001] main private warning: config file /home/michael//.vlc/vlcrc does not exist yet
[00000001] main private debug: CPU has capabilities 486 586 MMX 3DNow! MMXEXT SSE SSE2 FPU 
[00000001] main private debug: looking for memcpy module: 4 candidates
[00000001] main private debug: using memcpy module "memcpymmxext"
[00000237] main playlist debug: waiting for thread completion
[00000237] main playlist debug: thread 1140889936 (playlist) created at priority 0 (playlist/playlist.c:184)
[00000238] main private debug: waiting for thread completion
[00000238] main private debug: thread 1174460752 (preparser) created at priority 0 (playlist/playlist.c:210)
[00000239] main interface debug: looking for interface module: 1 candidate
[00000239] main interface debug: using interface module "hotkeys"
[00000239] main interface debug: thread 1149282640 (interface) created at priority 0 (interface/interface.c:231)
[00000241] main interface debug: looking for interface module: 1 candidate
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Rob Bradford 2007-11-03 15:27:14 UTC
Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed.

Please do not build with debugging turned off.

*** This bug has been marked as a duplicate of 430074 ***