| Summary: | gnome-base/nautilus-2.26.4: cannot mark a desktop icon as trusted | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Andersson <filigran> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 263083 | ||
Confirm this bug for me. Although the .destop file is executable, it can't be marked as trusted. A permission issue perhaps, because the root don't have this problem while any existing or new user does. (In reply to comment #1) > Confirm this bug for me. Although the .destop file is executable, it can't be > marked as trusted. > > A permission issue perhaps, because the root don't have this problem while any > existing or new user does. > Yeah, probably, but since chmodding the .desktop file doesn't work, I wonder what other files are involved? (In reply to comment #1) > Confirm this bug for me. Although the .destop file is executable, it can't be > marked as trusted. > > A permission issue perhaps, because the root don't have this problem while any > existing or new user does. > Are you also using the gnome-light ebuild btw? Reading the code, conditions to have the launcher marked as trusted are as follows: * if it is a launcher, file is should not be executable (the .desktop) * file is local, that is in ~/.gnome2 or in XDG_DATA_DIRS I created a launcher in $HOME with 2.26 nautilus yesterday and it was trusted out of the box. Is your home folder on a nfs or something ? In my case I have fixed this when I change the /home/ partition's options in /etc/fstab to auto (don't know what option could have done this, there were many, will try some later). @Thomas: Is your /home/ on separate partition? What mount options do you use? For me this bug is invalid. (In reply to comment #4) > Reading the code, conditions to have the launcher marked as trusted are as > follows: > * if it is a launcher, file is should not be executable (the .desktop) > * file is local, that is in ~/.gnome2 or in XDG_DATA_DIRS > > I created a launcher in $HOME with 2.26 nautilus yesterday and it was trusted > out of the box. Is your home folder on a nfs or something ? > Should NOT be executable? Right after creation it gets the following bits: htpc@mediasmurf ~/Desktop $ ls -l hejsan.desktop -rwxr-xr-x 1 htpc htpc 168 2009-10-30 17:48 hejsan.desktop Should I add my Desktop folder to this then? htpc@mediasmurf ~/Desktop $ echo $XDG_DATA_DIRS /usr/local/share:/usr/share:/usr/share/gdm I have linked my ~/Desktop to /storage/Desktop to save me from backing it up if I reinstall, and /storage is mounted with: htpc@mediasmurf ~/Desktop $ cat /etc/fstab |grep /storage /dev/sda3 /storage ext3 user,noatime 0 0 And, as said, the Desktop folder is really a symlink: htpc@mediasmurf ~ $ ls -l Desktop lrwxrwxrwx 1 htpc htpc 23 2009-10-19 05:14 Desktop -> /storage/gnome-desktop/ htpc@mediasmurf ~ $ ls -l /storage|grep gnome-desktop drwxr-xr-x 6 htpc ssmtp 4096 2009-10-30 17:48 gnome-desktop Should I use some other mount options? (In reply to comment #5) > In my case I have fixed this when I change the /home/ partition's options in > /etc/fstab to auto (don't know what option could have done this, there were > many, will try some later). > @Thomas: Is your /home/ on separate partition? What mount options do you use? > > For me this bug is invalid. > See above for the mount options. I assume auto for the file system? I played around with the mount options, and it seems that the 'user' option makes the icons not appear. It works just like it should without it. So, now my fstab looks like this: htpc@mediasmurf ~ $ cat /etc/fstab | grep /storage /dev/sda3 /storage ext3 noatime 0 0 and it works like a charm. Add the user option again, and it goes bonkers once again. In my eyes, this looks like a bug ... if not, why is it this way? Thanks for your help and tips, finally I have launchers that are trusted, with the correct icons! yeah, user options behind all kind of weird in other situation too, no idea where the problem comes from. Hum anyway closing upstream since it's not a gentoo issue. If you think this is buggy behavior of nautilus, I recommand going for upstream bugzilla, you can cc gnome@gentoo.org there if you want us to monitor the issue too. Thanks for reporting. |
--- Some information: Linux mediasmurf 2.6.30-gentoo-r7 #5 SMP Sun Oct 18 23:01:54 CEST 2009 i686 Pentium(R) Dual-Core CPU E5300 @ 2.60GHz GenuineIntel GNU/Linux * gnome-base/gnome-light installed: 2.26.3* {:2.0} Installed time: Mon Oct 19 00:30:32 2009 * gnome-base/nautilus installed: 2.26.4* {:0} Installed time: Mon Oct 19 00:03:20 2009 Use flags: (X) (-beagle) (-debug) (-doc) (gnome) (-tracker) (-xmp) --- The issue: Trying to create an application launcher on the desktop, it turns into a "appname.desktop" file (after doing some research, this is expected behavior?). Double-clicking it gives me "Untrusted application launcher" (also expected?). I click "Mark as trusted", the dialog box goes away, I try to execute it again, and same thing happens. The launcher never gets trusted. I can click "Launch anyway", and the app launches. I tried chmod 755 (even 777) on the desktop file, same thing. What else could I try? I'm using gentoo, emerged (actually, paludis .. ized?) gnome-light, could this have anything to do with it? Am I missing something vital, that is shipped with the regular meta package "gnome"? Do I need to set permissions on something else? Is there a log somewhere that could have some vital information? Tell me what else you might need to resolve the issue. Reproducible: Always Steps to Reproduce: 1. Right click on gnome desktop 2. Select "Create launcher" and enter information. 3. Double click new icon, a box pops up saying application is not trusted. 4. Click "Mark as trusted". Box goes away. 5. Double click icon again, same box pops up. Click "Launch anyway", app launches as normal, but clicking it again gives the same box. Actual Results: Everytime you click the icon, it asks you to mark as trusted, it's named "whatevernameyouentered.desktop", and gets a default file icon, instead of the icon you specify. Expected Results: The app should be marked as trusted, icon should appear, and name should be correct (without the .desktop extension).