After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589156 - 'Keep Aligned' option always resets to 'true' after desktop reload
'Keep Aligned' option always resets to 'true' after desktop reload
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Desktop
2.28.x
Other Linux
: High normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 639665 648887 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-20 17:40 UTC by Matt Drake
Modified: 2011-09-23 17:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
Preserve 'Keep Aligned' option between reloads and sessions (#589156) (1.51 KB, patch)
2010-07-30 22:02 UTC, Marcus Carlson
none Details | Review

Description Matt Drake 2009-07-20 17:40:02 UTC
This bug was originally reported at https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/399974 and the description is from comment 3.

"I'm also using Karmic, with nautilus at version 1:2.27.4-0ubuntu1.

There are several files in my Desktop folder, which I prefer to have placed at specific locations on my desktop.
However, it is impossible to permanently disable the "Keep Aligned" option.

I've tried two methods: from the right click-menu on the desktop and also by changing /apps/nautilus/desktop-metadata/directory/icon_view_keep_aligned to "false" in gconf-editor.

These changes are not saved, though.

Logging out and back into a Gnome session resets "Keep Aligned" back to "true". The same happens when refreshing the desktop by pressing F5.

In short:
Expected behaviour: "Keep Aligned" can be turned off permanently.
Actual behaviour: The changes are not saved."
Comment 1 pablomme 2009-10-15 09:22:28 UTC
This continues to be an issue in 2.28.0 (in particular, in Ubuntu version 1:2.28.0-0ubuntu6). Since this used to work in 2.26 and earlier, I assume the fix must be really trivial.
Comment 2 Thomas M. 2009-11-17 09:56:23 UTC
I have the same issue, and many users also have this issue (see launchpad bug reports).
Comment 3 Tsu Jan 2009-12-04 02:16:17 UTC
I'm in debian squeeze/sid and can see the same problem. But I don't think it's necessarily related to Nautilus 2.28.X because I also had it with Nautilus 2.26 in Gnome 2.28. I think it may be related to gconf2 2.28.0.
Comment 4 Tsu Jan 2009-12-04 03:09:19 UTC
I'm sorry for the above comment (I was too tired). I downgraded to Nautilus 2.26.3 and the problem was fixed. So, the bug must be in Nautilus 2.28.1.
Comment 5 hdfssk 2009-12-29 00:08:42 UTC
I've also this problem, on Fedora 12, nautilus 2.28.2.
Comment 6 Luis Menina 2010-02-03 16:13:51 UTC
Confirming on Mandriva 2010.0, GNOME 2.28.
Comment 7 Luis Menina 2010-02-03 17:50:12 UTC
Nautilus 2.28 sets the 
/apps/nautilus/desktop-metadata/directory/nautilus-icon-view-keep-aligned key to "true" on startup.

The name of the key is different, this "desktop-metadata" stuff seems new. There must be a bug in the transition commit.
Comment 8 Luis Menina 2010-02-05 13:16:29 UTC
I investigated last night, and saw that the metadata system migrated to be gvfs-based during the 2.28 cycle. I tested the 2-28 branch.

The problem seems to lie in libnautilus-private/nautilus-file.c. I found that at startup, nautilus_file_get_metadata returns the default metadata for some keys that exist, just because at some moment file->details->metadata pointer associated to the x-nautilus-destop file is NULL. It's not with all the boolean keys, and some keys work with the x-nautilus-desktop uri, so I'm still unsure about what causes the metadata to disappear.
Comment 9 Luis Menina 2010-02-05 13:24:04 UTC
As I've seen people on launchpad wanting a patch for this, even if it requires to recompile from source, I think a simple workaround would be to make get_default_directory_keep_aligned in src/file-manager/fm-icon-view.c return FALSE instead of TRUE.
Comment 10 Luis Menina 2010-02-05 15:13:15 UTC
Note to self: examine nautilus_desktop_update_metadata_from_gconf in libnautilus-private/nautilus-desktop-directory-file.c.
Comment 11 Tsu Jan 2010-02-06 00:17:49 UTC
Luis, thanks for your workaround (changing TRUE to FALSE).
Comment 12 Tsu Jan 2010-05-03 21:38:36 UTC
This bug is still present in Nautilus 2.30.1. The above workaround is needed again.
Comment 13 asbesto 2010-07-09 09:08:59 UTC
Same problem here, on Ubuntu 10.04 fresh install, on two different computers. What are developers doing? This bug is from MONTHS ago!!! :(
Comment 14 Marcus Carlson 2010-07-30 22:02:04 UTC
Created attachment 166859 [details] [review]
Preserve 'Keep Aligned' option between reloads and sessions (#589156)

Really tricky one. The thing is that desktop metadata is saved in gconf instead of gvfs-metadata (for valid reasons of course) but the code does not handle this very well and resets the metadata read earlier. For instance query_info_callback() in nautilus-directory-async.c calls g_file_query_info_finish () with file 'x-nautilus-desktop' and fails. Might exists a better solution for this but then I need help ;)

Patch has the changes documented because of this.
Comment 15 Marcus Carlson 2010-07-31 00:00:22 UTC
Hmm. Or is it better to add desktop:// to gvfs and let it handle the metadata as the rest of the files and even trash:// ?
Comment 16 Cosimo Cecchi 2011-02-02 15:47:58 UTC
*** Bug 639665 has been marked as a duplicate of this bug. ***
Comment 17 Cosimo Cecchi 2011-05-03 13:17:11 UTC
*** Bug 648887 has been marked as a duplicate of this bug. ***
Comment 18 asbesto 2011-06-02 10:04:15 UTC
Jesus FXXXXXX CHRIST, since 2009 and this DAMNED BUG is already there!!!!!

O_O


A patch was available since 2010, WHY isn't this bug fixed???

WHY?

WAKE UP DEVELOPERS!!! :(
Comment 19 Luis Menina 2011-06-02 17:44:55 UTC
(In reply to comment #18)
> Jesus FXXXXXX CHRIST, since 2009 and this DAMNED BUG is already there!!!!!
> 
> O_O
> 
> 
> A patch was available since 2010, WHY isn't this bug fixed???
> 
> WHY?
> 
> WAKE UP DEVELOPERS!!! :(

This comment is of the kind that has no use except annoy people and add extra noise to the bug report. I hope you'll find out that you get more from people by asking kindly than by denigrating them.

@Cosimo:
This bug is a regression introduced in 2.28 that seems to annoy a good bunch of people. It would be a pity to let this patch rot... If I remember well, alarsson introduced the bug with the gvfs migration. Tha twould be gret if him or another nautilus developer could review the patch. I don't have enough nautilus knowledge to do that...
Comment 20 asbesto 2011-06-02 20:18:19 UTC
Sorry, I was very STRESSED when I wrote that... but hey, two years, with a patch ready to be used... this is really annoying! :(
Comment 21 Tsu Jan 2011-06-02 22:48:54 UTC
I think the developer's focus is on Gnome3. Gnome-Shell's desktop is totally different from that of Gnome2.
Comment 22 asbesto 2011-06-03 15:43:40 UTC
(In reply to comment #21)

> I think the developer's focus is on Gnome3. Gnome-Shell's desktop is totally
> different from that of Gnome2.

Yes, indeed this is also the MOST DANGEROUS BUG to be SOLVED. O_O
Comment 23 Stefan Bethge 2011-07-25 12:18:06 UTC
(In reply to comment #21)
> I think the developer's focus is on Gnome3. Gnome-Shell's desktop is totally
> different from that of Gnome2.

Actually, AFAIK Gnome3 still uses nautilus for the desktop (if you enable it) and nautilus 3 still has this exact bug. While the bug is not dangerous, existing features should at least be working before one starts to add new features, no?
Comment 24 Tsu Jan 2011-07-25 13:16:22 UTC
(In reply to comment #23)
> ... nautilus 3 still has this exact bug ...

Oh, you're right! I didn't know that as I've accepted the GNOME-Shell style of using the desktop.
Comment 25 pablomme 2011-09-19 22:47:31 UTC
This bug has just been fixed in nautilus 3.1.92 (as found in Ubuntu oneiric under version 1:3.1.92-0ubuntu1). This report should be marked as fixed.
Comment 26 Cosimo Cecchi 2011-09-23 17:02:07 UTC
This is fixed now indeed.