Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3238 - Changing Desktop background in gnome 2.12-1 produces weird results

Attached to Project: Arch Linux
Opened by Kevin Read (obsidian) - Tuesday, 27 September 2005, 19:46 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I use latest Gnome 2.12 from testing, upgraded from 2.10. On my first login my desktop background picture displayed correctly. When I try to select multiple icons on my desktop (by clicking and dragging) the drag box leaves afterimages on my background picture. Opening a context menu by right clicking leaves the menu open on the background pic even after I select a menu entry. If I select an icon the marker (the changed background color on the selected filename) doesn't disappear again. If I change to a solid color background everything is fine. If I change to another picture (jpg), the new background only shows after a redraw, for example if I drag a window across the screen. All background changing was done with standard gnome tools.

This looks like a missing refresh or something like that to me. I haven't yet deleted my home dir after the upgrade (shudder), but could do that for testing out things.

Hope this helps. Shoot any further questions at me.

Cheers,

Kevin
   Screenshot.png (601.7 KiB)
   Screenshot-1.png (580.3 KiB)
   Screenshot-2.png (607.5 KiB)
This task depends upon

Closed by  arjan timmerman (blaasvis)
Monday, 31 October 2005, 11:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  well seems it has been resolved
Comment by Jan de Groot (JGC) - Tuesday, 27 September 2005, 20:14 GMT
Did you also update xorg to the testing version (as in, didn't force installation of cairo without it :P), and after that, did you restart Xorg?

There's a bug in xorg from current which cairo has a workaround for. Since we fixed the version in testing, I also wrecked out the workaround to get some extra speed again.
Comment by Kevin Read (obsidian) - Tuesday, 27 September 2005, 21:58 GMT
Yes, I did update xorg and restarted it, but that was a few days ago. I'll do an update again and let you know if anything changes (can't change that now, working on a thesis for uni ATM :).

Cheers,

Kevin
Comment by Jan de Groot (JGC) - Wednesday, 28 September 2005, 06:24 GMT
Hmm, if you're running the new X, please make a screenshot and give information about what videocard and what drivers you use. This is important for the xorg guys, since this is another bug in XRender...
Comment by Kevin Read (obsidian) - Saturday, 01 October 2005, 06:42 GMT
Unfortunately I haven't been able to update the packages again, because I can't recompile the kernel just now (I'm on the move) and so can't get wireless to work...

But here are version numbers of the installed packages, and I attached some screenshots.

xorg-11R6.8.2-5
gnome-desktop-2.12.0-1
cairo-1.0.0-1

Anything relevant missing?

This is on a Compaq Evo N400c laptop sporting a P3-850 and an ATI Rage Mobility Chip, which is Mach64 based. Standard Mach64 (afaik "ati") driver. Here's some log blurb:

(--) ATI(0): ATI 3D Rage Mobility graphics controller detected.
(--) ATI(0): Chip type 4C4D "LM", version 4, foundry TSMC, class 0, revision 0x01.

I used to have the dri bleeding-edge mach64 drivers installed but the kernel module doesn't load anymore and I don't need it at the moment so it isn't active. RENDER, DAMAGE and COMPOSITE extensions are enabled.

I should be able to do an update or perform some bigger downloads on Monday. Please let me know if there is anything else that I should look up.

Cheers,

Kevin
Comment by Jan de Groot (JGC) - Saturday, 01 October 2005, 09:55 GMT
Try disabling composite extension, as it is known to cause trouble in the most cases. Maybe composite is better in Xorg 6.9/7.0, but with Xorg 6.8 I would certainly disable this extension.
Comment by Kevin Read (obsidian) - Saturday, 01 October 2005, 17:13 GMT
I tried disabling Composite (it wasn't explicitly enabled anyway), but this didn't seem to do the trick:

Section "Extensions"
Option "Composite" "Disable"
EndSection

in xorg.conf. Xorg.0.log still says

(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
Comment by Kevin Read (obsidian) - Thursday, 06 October 2005, 11:20 GMT
Guess I should have had a closer look at the logfile. Although it still spits out those "Initializing" lines as above, the X server also says "(**) Extension "Composite" is disabled", which sounds kind of good :)

But doesn't fix the issues though.
BTW, a checkout of testing from today doesn't fix things...
Comment by Kevin Read (obsidian) - Tuesday, 11 October 2005, 12:45 GMT
The latest pacman -Syu seems to have fixed these. I'll check with re-enabled extensions later.

Thanks to all for the help.

Loading...