Bug 197111 - desktop icons don't re-appear after hidden
Summary: desktop icons don't re-appear after hidden
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
Keywords: Desktop
Depends On:
TreeView+ depends on / blocked
Reported: 2006-06-28 16:12 UTC by Zack Cerza
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-09-04 16:49:02 UTC

Attachments (Terms of Use)

Description Zack Cerza 2006-06-28 16:12:16 UTC
Description of problem:
If I disable the desktop icons via the /apps/nautilus/preferences/show_desktop
gconf key, they disappear. If I re-enable them, they don't re-appear. I noticed
that nautilus was not running, so I opened a folder to see if the icons would
re-appear then. They didn't.

Version-Release number of selected component (if applicable):

Comment 1 Alexander Larsson 2006-08-22 13:00:52 UTC
Exactly what do you mean. How could the icons show up when nautilus isn't even

However, if show_desktop is true and you launch nautilus (and it wasn't running
before) you should get a desktop with icons. Unless ---no-desktop was passed to
nautilus. How did you "open a folder"?

Comment 2 Zack Cerza 2006-08-22 15:49:57 UTC
Just try this:

gconftool-2 --type bool --set /apps/nautilus/preferences/show_desktop false
sleep 1
gconftool-2 --type bool --set /apps/nautilus/preferences/show_desktop true

After I do this, my desktop icons are still hidden.

How did I open a folder? The Places menu.

As far as the question "How could the icons show up when nautilus isn't even
running?", I don't know the answer. But I'd expect that re-enabling show_desktop
would, you know, show the desktop. It doesn't.

Comment 3 Alexander Larsson 2006-09-04 16:49:02 UTC
Nautilus is the thing listening to the changes to the setting, but if
show_desktop is false and there are no other nautilus windows open then nautilus
will not be running, so it can't detect the change.

We could either keep nautilus running anyway just to solve this issue, or create
a daemon specifically to listen to this change and keep that in the session.

The problem doesn't seem important enought for either of the solutions to be
worth it.

Note You need to log in before you can comment on or make changes to this bug.