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 533766 - background pattern not working properly
background pattern not working properly
Status: RESOLVED DUPLICATE of bug 492529
Product: nautilus
Classification: Core
Component: [obsolete] Backgrounds Emblems and Themes
2.2.x
Other All
: Normal trivial
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-18 22:40 UTC by Mark
Modified: 2008-10-27 10:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Mark 2008-05-18 22:40:58 UTC 
Please describe the problem:
when I set a background pattern using Edit -> Backgrounds and Emblems and drag and drop a pattern onto the nautilus viewer pane it looks fine. But when I browse to another folder and come back to the folder in which I set the background pattern, the pattern is not showing properly.

Steps to reproduce:
1. Drag and drop and pattern onto the nautilus view pane using Edit -> Backgrounds and Emblems
2. Browse to another folder in the nautilus file browser
3. Come back to the previous folder using the back button or the up button in the file browser.


Actual results:
When you first select the pattern, it looks fine. When you navigate away from that folder and come back again the pattern looks messed up.

Expected results:
I want the background pattern I selected to be there when I come back to that folder.

Does this happen every time?
Yes.

Other information:
Comment 1 emerg.reanimator 2008-10-26 14:25:04 UTC 
GNOME Version: 2.22.3
Nautilus 2.22.5.1

The similar happens to me with only difference that I am changing the view mode icons/list.
Comment 2 Cosimo Cecchi 2008-10-27 10:05:17 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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