[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-07 Thread Sebastien Bacher
let's close the bug then you can reopen if you still get the issue after upgrade ** Changed in: nautilus (Ubuntu) Status: Incomplete = Fix Released -- Desktop boarder problem caused by theme changes https://bugs.launchpad.net/bugs/553803 You received this bug notification because you are

[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-06 Thread Sebastien Bacher
thank you for your bug report, what version of nautilus do you use? ** Changed in: nautilus (Ubuntu) Importance: Undecided = Low ** Changed in: nautilus (Ubuntu) Status: New = Incomplete -- Desktop boarder problem caused by theme changes https://bugs.launchpad.net/bugs/553803 You

[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-06 Thread Ryan Vickers
It's the one that came with the Ubuntu 10.04 beta 1 a few days ago - I think it's 2.29.something Through further investigation with themes (as I always like to do) I realized something else. The boarder that was appearing around the desktop appeared to be the same boarder that appears (is used)

[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-06 Thread Ryan Vickers
To clarify, I believe it is 2.29.92.1, as this is the latest release not marked 2.30... PS, I don't think I ever gave any system details... here are some: - Ubuntu 32 bit beta 1 live CD running on USB stick (made with the USB stick maker program in 9.10) - no video drivers (it was a live CD -

[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-06 Thread Sebastien Bacher
Could you give details on the version you use or upgrade? it could be the issue fixed in this update: nautilus (1:2.29.92.1-0ubuntu2) lucid; urgency=low * debian/patches/92_git_change_no_desktop_frame.patch: - git change to not display a border around the desktop background (lp:

[Bug 553803] Re: Desktop boarder problem caused by theme changes

2010-04-06 Thread Ryan Vickers
That does sound like what I've been seeing, and the screenshot confirms that yes - that is what I'm talking about. So, if that has been fixed, then I guess we can consider this closed. If not, then I guess these reports are serving the same purpose... I'll do an update ASAP* and see if the