GNOME Bugzilla – Bug 446094
crash in Main Menu: for #430074
Last modified: 2007-07-02 03:47:24 UTC
Version: 0.11.3 What were you doing when the application crashed? for #430074 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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 47292416 vsize: 47292416 resident: 28073984 share: 19054592 rss: 28073984 rss_rlim: 4294967295 CPU usage: start_time: 1181498886 rtime: 184 utime: 167 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/alacarte' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208564032 (LWP 18734)] 0x00afa402 in __kernel_vsyscall ()
+ Trace 139834
Thread 1 (Thread -1208564032 (LWP 18734))
----------- .xsession-errors --------------------- Initializing gnome-mount extension Initializing nautilus-setup-background extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory 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' "/usr/bin/alacarte": not in executable format: File format not recognized Cannot access memory at address 0x0 Cannot access memory at address 0x0 --------------------------------------------------
Thanks Andras, good stacktrace! :-) *** This bug has been marked as a duplicate of 430074 ***