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 455216 - crash in Main Menu: Clicked to add Contol ce...
crash in Main Menu: Clicked to add Contol ce...
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-09 16:43 UTC by Denis Belanger
Modified: 2007-07-09 21:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Denis Belanger 2007-07-09 16:43:09 UTC 
Version: 0.11.3

What were you doing when the application crashed?
Clicked to add Contol center to main menu


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 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 56086528 vsize: 56086528 resident: 31092736 share: 21540864 rss: 31092736 rss_rlim: 4294967295
CPU usage: start_time: 1183999113 rtime: 639 utime: 585 stime: 54 cutime:74 cstime: 14 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 -1208826176 (LWP 24156)]
(no debugging symbols found)
0x007e0402 in __kernel_vsyscall ()

+ Trace 146770

Thread 1 (Thread -1208826176 (LWP 24156))

  • #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) ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
kbuildsycoca running...
Reusing existing ksycoca
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/Alacarte/MainWindow.py", line 98, in loadUpdates
    item_id = os.path.split(items[iter][3].get_desktop_file_path())[1]
  File "/usr/lib/python2.5/posixpath.py", line 77, in split
    i = p.rfind('/') + 1
AttributeError: 'NoneType' object has no attribute 'rfind'
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
kbuildsycoca running...
Reusing existing ksycoca
"/usr/bin/alacarte": not in executable format: File format not recognized
kbuildsycoca running...
Reusing existing ksycoca
--------------------------------------------------
Comment 1 palfrey 2007-07-09 16:44:54 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 ***
Comment 2 Denis Belanger 2007-07-09 21:15:40 UTC 
I was able on reopening Alacarte to add it to System -->Preferences Menu the control center that is I put this down to Fedora release builds paranoia about menu changing fist distro was Fedora Core 3 and SELinux set to enforce,i do not use the power manger service probably why keycoca could not connect.
hope this is useful Denis