Incorrect sidebar status with start-with-sidebar false config

Thank you for your bug report. What version of Ubuntu do you use? could you describe what you do exactly?

I use 13.10.

1. Open Nautilus (any folder)
2. Press F9 (nothing happens)
3. Press F9 (sidebar opens)

Debug:
1. Open Nautilus
2. Click the arrow pointing down and "Show sidebar" is ticked
3. Press F9
4. Click the arrow pointing down and "Show sidebar" is now unticked
5. Press F9
6. Click the arrow pointing down and "Show sidebar" is now ticked AND the sidebar is shown.

It seems like the state of "Show sidebar" is persisted in the UI (as it should be) but not in the options menu.

"I use 13.10.

1. Open Nautilus (any folder)
2. Press F9 (nothing happens)
3. Press F9 (sidebar opens)"

That doesn't really make sense, the sidebar is displayed by default ... how did you get off to start? can you try in a guest session?

Okay, that's weird..

I logged in as guest, and it works as you described (the sidebar is restored on each close/open).

I like though that mine stays hidden, apart from the anoying fact that I have to press F9 twice. There must be some inconsistency somewhere?

I might have changed some flags in dconf to make it stay hidden. I've attached a screenshot from "org -> gnome -> nautilus -> window state".

thanks, I can confirm that the behaviour is buggy when setting start-with-sidebar=false in the configuration, that seems like an upstream issue and should be reported to https://bugzilla.gnome.org/enter_bug.cgi?product=nautilus

The issue has been fixed upstream with this commit, https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-10&id=7a76c2dad619494ac04a0713d56882a3b141384c

This bug was fixed in the package nautilus - 1:3.8.2-0ubuntu10

---------------
nautilus (1:3.8.2-0ubuntu10) trusty; urgency=medium

  * debian/patches/git_sidebar_state_on_start.patch:
    - correctly set the sidebar status on start (lp: #1265401)
 -- Sebastien Bacher <email address hidden> Fri, 17 Jan 2014 13:46:26 +0100

Just out of pure curiosity; what's the process from now on - when would we expect to have a Ubuntu update with the fix?

The update is in Ubuntu (trusty), I'm not sure it's an issue important enough to justify a stable update to saucy though.

If you think it's really worth a stavle update, feel free to read https://wiki.ubuntu.com/StableReleaseUpdates and update the bugs with the rational, etc informations required for those updates

Ah, I see. Thanks!