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 338201 - Nautilus doesn't note the arrangement of the Network-Icons
Nautilus doesn't note the arrangement of the Network-Icons
Status: RESOLVED DUPLICATE of bug 330298
Product: nautilus
Classification: Core
Component: Desktop
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-12 10:53 UTC by eselfreak
Modified: 2009-11-07 17:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description eselfreak 2006-04-12 10:53:02 UTC
Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Nautilus doesn't note the arrangement of the Network-Icons
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: unspecified
Description:
Description of Problem:

i added some icons on my Desktop für "Network-Servers", for example
some Samba-Quicklinks, some SSH-Quicklinks etc. All works finde, but
after i reboot my system, the arrangement of the Icons is like that, as
it was before the reboot.

Steps to reproduce the problem:
1. Install Ubuntu Dapper ;)
2. Connect to some networks, so that there are some network icons
3. move them to an corner or somethink, and remember where they are
4. reboot
5. look at the corner and see, that the icon are not there, where they
are before the reboot

Expected Results: shoud just work :)

How often does this happen?

every reboot




------- Bug created by bug-buddy at 2006-04-12 10:53 -------

Comment 1 Christian Kirbach 2006-04-13 23:34:48 UTC
cannot reproduce (I am not using Dapper)
Comment 2 Nelson Benitez 2006-12-08 13:01:07 UTC
This seems a duplicate of bug 330298
Comment 3 André Klapper 2009-11-07 17:18:54 UTC

*** This bug has been marked as a duplicate of bug 330298 ***