GNOME Bugzilla – Bug 512180
crash in Main Menu: problem
Last modified: 2008-01-30 20:04:31 UTC
Version: 0.11.3 What were you doing when the application crashed? problem 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: Clearlooks Icon Theme: Fedora Memory status: size: 53334016 vsize: 53334016 resident: 22167552 share: 14876672 rss: 22167552 rss_rlim: 4294967295 CPU usage: start_time: 1201354107 rtime: 404 utime: 350 stime: 54 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 -1209063744 (LWP 3690)] (no debugging symbols found) 0x00738402 in __kernel_vsyscall ()
+ Trace 186839
Thread 1 (Thread -1209063744 (LWP 3690))
----------- .xsession-errors (17 sec old) --------------------- i = p.rfind('/') + 1 AttributeError: 'NoneType' object has no attribute 'rfind' Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/Alacarte/MainWindow.py", line 419, in on_item_tree_show_toggled self.editor.setVisible(item, True) File "/usr/lib/python2.5/site-packages/Alacarte/MenuEditor.py", line 205, in setVisible self.__addUndo([self.__getMenu(item), item]) File "/usr/lib/python2.5/site-packages/Alacarte/MenuEditor.py", line 404, in __addUndo file_path = os.path.join(util.getUserDirectoryPath(), os.path.split(item.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' kbuildsycoca running... Reusing existing ksycoca "/usr/bin/alacarte": not in executable format: File format not recognized --------------------------------------------------
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. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 430074 ***