I know this applies to some gnome-base/nautilus-2.10.0 installs. On one computer, I installed nautilus-2.10.0 when it was still masked, and it functions properly. On a new install, I installed nautilus-2.10.0 after it was marked 'stable', and the 'stable' emerge is the one that is acting improperly. After setting desktop_is_home_dir through gconf-editor and logging back in and out, root user is able to move all objects around on the desktop. For all other users, however, the objects appear locked down, and with the exception of objects like Computer, Audio Disk, *user*'s Home, and Trash, return to their original location on the desktop. If an object is dragged from another location and dropped onto the desktop, the object remains locked at that location on the desktop until it is moved to another directory, or until the user issues an organization command to line the objects on the desktop. I reformatted my linux install and reinstalled everything up to gnome, and have gotten the same results. I've added the user to all groups listed in /etc/group, but there was no noticable change, so I set the group memberships back to normal. Reproducible: Always Steps to Reproduce: 1.Mark desktop_is_home_dir in applications>nautilus>preferences under Gnome Configuration Editor 2.log out and log back into Gnome 3.attempt to drag object (other than Computer, Audio Disc, *user*'s home, etc) from one location on desktop to another Actual Results: Object returns to original location Expected Results: Object remains at location it was dragged to Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 i686) ================================================================= System uname: 2.6.11-gentoo-r11 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 15 2005, 21:12:42)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apm avi berkdb bitmap-fonts cdr crypt cups curl dbus dvd eds emboss encode esd fam flac foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal imlib ipv6 java jpeg libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl spell sse sse2 ssl svga tcpd threads tiff truetype truetype-fonts type1-fonts vorbis win32codecs xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Update: Objects can also be re-arranged through the File Browser. However, the desktop then has to be manually refreshed, such as control+R. Since this problem does not exist for root user, however, I'm still believing that this is a permissions problem.
I always run desktop_is_home and I've never seen this - could it be a fam/gamin/notify thing? (John/Dan - any ideas?)
Is this reproducable with gamin and GNOME 2.12?
No response from reporter, marking invalid due to comment #2
(In reply to comment #3) > Is this reproducable with gamin and GNOME 2.12? > I have removed fam and emerged gamin, but there's no change. Root is able to move all objects around, but normal users are not. I created a new user to see if the problem was existing settings, but my test user also was unable to move around objects like ~/Desktop around on the screen as it should have. If you need me to list anything (e.g. packages installed, configuration settings, etc.) just ask.
Please try the following. killall nautilus ; nautilus --debug and then try moving icons around and see if it provides any output from the terminal.
(In reply to comment #7) > Please try the following. killall nautilus ; nautilus --debug and then try > moving icons around and see if it provides any output from the terminal. > I've tried using nautilus --debug, and then re-emerged nautilus with the debug flag, but --debug made no difference and produced no output. I did nautilus --help and there were no notes for any --debug flag.
The main thing that is confusing me about this issue is that I've had this problem since I first installed Gnome on this computer, even when using the same make.conf from another computer that didn't have this issue. Perhaps this could just be a Dell Dimension 8400 issue? (In reply to comment #8) > (In reply to comment #7) > > Please try the following. killall nautilus ; nautilus --debug and then try > > moving icons around and see if it provides any output from the terminal. > > > > I've tried using nautilus --debug, and then re-emerged nautilus with the debug > flag, but --debug made no difference and produced no output. I did nautilus > --help and there were no notes for any --debug flag. >
If you dont mind, could you rm -rf the following directories, log out, log back in, and test again. (You probably should check through to make sure you wont loose anything important). ~/Desktop ~/.gconf ~/.gconfd ~/.icons ~/.gnome2 ~/.gnome2_private ~/.gstreamer* ~/.icons ~/.local ~/.metacity ~/.nautilus ~/.themes ~/.thumbnails
To me it simply sounds like the xml files in ~/.nautilus aren't updated, i guess this might be a permissions problem there. What are the permissions in ~/.nautilus/metafiles/ ? You say you rebuild your system, but did that include a complete removal of your home dirs as well ?
(In reply to comment #10) > If you dont mind, could you rm -rf the following directories, log out, log back > in, and test again. (You probably should check through to make sure you wont > loose anything important). > > ~/Desktop ~/.gconf ~/.gconfd ~/.icons ~/.gnome2 ~/.gnome2_private ~/.gstreamer* > ~/.icons ~/.local ~/.metacity ~/.nautilus ~/.themes ~/.thumbnails > I just removed all of these directories, but still have the same issues. I also created a test user and emptied the user's home directory completely (rm -rf ~/* and rm -r ~/.* -rf), but still cannot move files or directories around on the desktop. (In reply to comment #11) > To me it simply sounds like the xml files in ~/.nautilus aren't updated, i > guess this might be a permissions problem there. > > What are the permissions in ~/.nautilus/metafiles/ ? > > You say you rebuild your system, but did that include a complete removal of > your home dirs as well ? > Just to check for permissions issues, I chmodded everything in the test user's home directory 777, but could still not move files or directories around for the test user. I could move the computer shortcut, the trash icon, and any other virtual icon that you can enable or disable through the configuration editor, but I still could not move "physical" or non-virtual objects around on the desktop. There are two main things that are still confusing me about this issue: 1) The root user appears to have no issues with this, which means that if any program is being executed under another user, there should be no permissions issues since it can modify the most restrive account. 2) When I move objects around using a nautilus browser window, I do not have any problems. The problem appears to be with the desktop extension for nautilus. I've tried running nautilus with different flags, but nothing seems to make a difference. I also have not been able to view any errors from nautilus since I cannot even get it into a verbose mode (unless there's a log file somewhere that nobody's mentioned yet.) These two things are what is making this issue impossible for me. The problem doesn't appear to be nautilus as a whole, but just the part of nautilus that controlls the desktop.
Rob, Can you still reproduce this bug with newer version (2.14 or the soon to be stable 2.16) of gnome/nautilus? If the bug is still there, don't hesitate to reopen this bug. Did you also try looking at gnome's bugzilla for similar bugs? Thanks
