I just upgraded nautilus and various other packages to the newest bits from unstable. I then restarted gdm3 to make sure that nothing went horribly wrong with my now-partially-GNOME3 desktop. As soon as my session started, nautilus popped up, showing my home directory. This bug reliably reproduces every time my session starts. - Josh Triplett
Le vendredi 14 octobre 2011 à 23:55 -0700, Josh Triplett a écrit : You probably have a nautilus instance in your saved session.
Sure enough, I just checked the "Startup Applications" preferences, and I have an entry named "Files", with no description, which runs the command "nautilus -n". Note, though, that I didn't get a window popping up at the start of my session until after I upgraded. What changed? How did nautilus end up in my session, or did my session always contain nautilus and it only started opening a window after I upgraded? Either way, it seems likely that this could happen to other users, who shouldn't have to dig around in their preferences to fix it. - Josh Triplett
Le samedi 15 octobre 2011 à 11:25 -0700, Josh Triplett a écrit : If you want the whole explanation, nautilus used to be started to draw icons on the desktop and it is not anymore, and the options of the nautilus binary have changed. So it used to be in a session you saved, and now when the session starts it, it starts in a different way. We should probably use a different place for saved sessions now, but… upstream decision.
didn't draw my desktop before, either. Any way to handle this issue automatically, and fix the user's session somehow? Problems with saved sessions seem to happen rather often when upgrading to new versions of GNOME. I don't mind hitting such issues as a user of unstable, but I'd like to help prevent users of testing and stable from having to deal with them. As for how I should fix this issue myself, should I just delete nautilus from my session, or change the entry somehow, or wait for some automatic migration to fix the problem so I can help test it? - Josh Triplett
Hey Josh, Should we close this bug ? it seems obsolete nowadays. thanks regards Pedro