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 136715 - Background gradient
Background gradient
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.5.x
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-10 05:14 UTC by Richard Blumel
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Richard Blumel 2004-03-10 05:14:02 UTC 
Distribution: Debian testing/unstable
Package: control-center
Severity: normal
Version: GNOME2.5.5 2.5.x
Gnome-Distributor: GARNOME
Synopsis: Background gradient
Bugzilla-Product: control-center
Bugzilla-Component: background
Bugzilla-Version: 2.5.x
Description:
Description of Problem:
When a screen resolution is enlarged from a smaller resolution the
gradient tiles instead of enlarging	

Steps to reproduce the problem:
1. Set resolution to 1024x768	
2. set back ground to vertical gradient	
3. set resolution to 1280x1024

Actual Results:
Background is now a messed up gradient that tiles 

Expected Results:
Background is still one large gradient.

How often does this happen?
Every time		

Additional Information:
gnome 2.5x built with garnome




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-10 00:14 -------

The original reporter (blumel@earthlink.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, dobey@free.fr.
Comment 1 Rodney Dawes 2004-03-12 04:00:44 UTC 
The settings daemon isn't re-drawing the background properly on
resolution changes. This seems to work fine with Nautilus running.
Comment 2 Chris Lahey 2004-03-12 20:54:16 UTC 
This bug is fixed by the patch to bug #105316.  The two fixes are
highly intertwined, hence the single patch.
Comment 3 Sebastien Bacher 2004-11-28 23:49:01 UTC 
this bug is fixed now