https://bugzilla.novell.com/show_bug.cgi?id=467862 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=467862#c1 Wolfgang Rosenauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org Component|Firefox |GNOME Version|RC 2 |Final AssignedTo|bnc-team-mozilla@forge.prov |bnc-team-gnome@forge.provo. |o.novell.com |novell.com --- Comment #1 from Wolfgang Rosenauer 2009-01-21 01:43:06 MST --- The Gnome components are creating that file/directory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=467862 User amanison@anselsystems.com added comment https://bugzilla.novell.com/show_bug.cgi?id=467862#c3 Andrew Manison changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amanison@anselsystems.com --- Comment #3 from Andrew Manison 2009-02-14 17:32:06 MST --- I have the same problem, which is rendering some programs unusable. The issue seems to be the permissions for the .gvfs directory. As su, ls -l in the home directory gives this (partial) result: drwx------ 5 andrew users 4096 2009-02-14 17:41 .gconf drwx------ 2 andrew users 4096 2009-02-14 18:11 .gconfd drwx------ 10 andrew users 4096 2009-02-14 18:05 .gnome2 drwx------ 2 andrew users 4096 2008-12-21 12:55 .gnome2_private -rw-r--r-- 1 andrew users 18251 2008-12-21 12:55 .gnu-emacs drwxr-xr-x 2 andrew users 4096 2008-12-22 01:23 .gstreamer-0.10 d????????? ? ? ? ? ? .gvfs drwxr----- 2 andrew users 4096 2008-12-21 12:56 .hplip -rw------- 1 andrew users 6016 2009-02-14 17:32 .ICEauthority drwxr-xr-x 2 andrew users 4096 2008-12-21 13:33 .icons -rw-r--r-- 1 andrew users 861 2008-12-21 12:55 .inputrc Also as su, both ls -l .gvfs and ls -ld .gvfs return the result: ls: cannot access .gvfs: Permission denied Note, this is as super-user! Some programs scan the user's home directory when they open, and because of this bug they lock up completely. Visual SlickEdit is an example of this. In my case, on my laptop, my Windows partitions are mounted. Running mount reports: /dev/sda6 on / type ext3 (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda2 on /boot type ext3 (rw,acl,user_xattr) /dev/sdb5 on /home type ext3 (rw) /dev/sda1 on /windows/C type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) /dev/sda3 on /windows/E type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) /dev/sdb1 on /windows/F type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) /dev/sdb3 on /windows/V type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) This seems to show that the Windows partitions are mounted using the FUSE daemon, although I'm not sufficiently familiar with this stuff to be sure. There is clearly some connection, since ps aux | grep fuse reports: andrew 3616 0.0 0.0 35032 1548 ? S 17:32 0:00 /usr/lib64/gvfs//gvfs-fuse-daemon /home/andrew/.gvfs root 3617 0.0 0.0 12236 796 ? S 17:32 0:00 fusermount -o rw,nosuid,nodev,subtype=gvfs-fuse-daemon -- /home/andrew/.gvfs root 3620 0.0 0.0 13732 920 ? S 17:32 0:00 /bin/mount -i -f -t fuse.gvfs-fuse-daemon -o rw,nosuid,nodev,user=andrew gvfs-fuse-daemon /home/andrew/.gvfs The offending .gvfs directory is mixed up in this to the hilt! One workaround that occurs to me is to move the .gvfs directory to a subdirectory of the home directory. In this way, programs that scan the home folder will not lock. But all my searching for the configuration file that starts the fuse daemon has come up empty. If anyone can point me to the right place I would be grateful. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=467862 User vkrevs@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=467862#c5 Vadim Krevs changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vkrevs@yahoo.com --- Comment #5 from Vadim Krevs 2009-02-19 15:38:11 MST --- Same here on openSUSE 11.1 for x86-64. Even kill -9 wouldn't kill the affected process. After half a day of system lockups, I solved the problem by uninstalling gvfs-fuse gvfs-backends packages and rebooting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=467862 User hpj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=467862#c7 --- Comment #7 from Hans Petter Jansson 2009-02-24 06:05:24 MST --- gvfsd does this on startup: #ifdef HAVE_FUSE if (!no_fuse) { char *fuse_path; char *argv2[3]; fuse_path = g_build_filename (g_get_home_dir (), ".gvfs", NULL); if (!g_file_test (fuse_path, G_FILE_TEST_EXISTS)) g_mkdir (fuse_path, 0700); argv2[0] = LIBEXEC_DIR "/gvfs-fuse-daemon"; argv2[1] = fuse_path; argv2[2] = NULL; g_spawn_async (NULL, argv2, NULL, G_SPAWN_STDOUT_TO_DEV_NULL | G_SPAWN_STDERR_TO_DEV_NULL, NULL, NULL, NULL, NULL); g_free (fuse_path); } #endif The directory can appear with no permission if the gvfs-fuse-daemon crashed or was killed, or if the process is not owned by the accessing user. Root can not access users' .gvfs mounts, for instance. Hangs can occur if the fuse daemon is hanging. I suggest installing debuginfo, attaching to gvfs-fuse-daemon with gdb, and issuing "t a a bt" in gdb. This will produce a backtrace of all running threads. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.