GNOME Bugzilla – Bug 413872
crash in Gimmie: launching gimmie (i.e. `...
Last modified: 2007-08-29 22:39:02 UTC
What were you doing when the application crashed? launching gimmie (i.e. `/usr/bin/gimmie`) (Note the same thing happens with 2.3 if it matters) Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.17.92 2007-02-27 (Ubuntu) BugBuddy Version: 2.17.4 System: Linux 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-gperfection2 Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (154 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 -------------------------------------------------- Traceback (most recent call last):
+ Trace 115210
trashdir = TrashDirectory(trash_uri)
self._trash_dir_changed()
for file in gnomevfs.open_directory(self.trash_uri):
This was due to a .Trash directory on an nfs mounted drive that either has invalid permissions itself, or contained files with invalid permissions. Don't know which I just deleted the dir after adding some debug to gimmie_trash.py. Seems fine without that. Also, no idea where the .Trash directory came from. Nautilus? gnome-vfs? I'm not familiar with any of the gnome libraries. It's all magic to me.
Fixed in SVN change #337. Thanks!
*** Bug 433353 has been marked as a duplicate of this bug. ***
*** Bug 434158 has been marked as a duplicate of this bug. ***
*** Bug 451663 has been marked as a duplicate of this bug. ***
*** Bug 456917 has been marked as a duplicate of this bug. ***
*** Bug 459742 has been marked as a duplicate of this bug. ***
*** Bug 460752 has been marked as a duplicate of this bug. ***