A screenshot of the error I'm encountering is here: http://www.u.arizona.edu/~ajgarcia/screenshot.png I removed xfce 4.0.6 and all config files, then installed 4.1.90. It seems like when the xfdesktop desktop menu is destroyed, all of the application windows are refreshed, but the root window isn't? I'm not quite sure what's causing this, I'm using gtk+-2.5.3, librsvg-2.8.0, and libart-2.3.16. I'm running XFree86 4.3.0.2. Reproducible: Always Steps to Reproduce:
do you have the compositor enabled in xfwm4? olivier: could composite be causing this?
Nope, it can't be the compositor, there is no compositing extention in XFree86 (at least not in 4.3.0 not in 4.4.0)
(In reply to comment #2) > Nope, it can't be the compositor, there is no compositing extention in XFree86 > (at least not in 4.3.0 not in 4.4.0) meh. go me, way to not pay attention. also way to not look at the screenshot. sorry, didn't get much sleep last night. i'm not sure what to say. i've never seen anything like it. xfdesktop sets the back pixmap of its virtual root window to your selected backdrop, so it doesn't need any manual repainting on expose events and whatnot. oh, my. gtk 2.5.3. that could be your problem. can you install the latest gtk in the 2.4.x series and see if the problem's still there? if it's not, i'm not interested in fixing this bug at this point, at least not until 2.6.0 comes out and it's shown that the bug is still present. the 2.5.x series is (possibly buggy) development code, and supporting it would not be the best use of my time.
Wala! I installed gtk+-2.4.13 and everything's fine. That was weird. :)
meh, beta code bites.
*** Bug 446 has been marked as a duplicate of this bug. ***
*** Bug 491 has been marked as a duplicate of this bug. ***
for reference: http://bugzilla.gnome.org/show_bug.cgi?id=161561
I don't see this with gtk+-2.6.0
Even I upgrade to gtk+ 2.6.0, the problem is still there. I think this is a bug about XFDesktop.
Yes and no. It's possible that I was doing something somewhat dodgy in xfdesktop, but the fact remains that the gtk devs went and changed a behavior between minor releases, which is (IMHO) a big no-no.
Actually Jasper pointed to the explanation from Owen here: http://bugzilla.gnome.org/show_bug.cgi?id=159012 As a side note, that bug doesn't show at all when using the compositor because windows are rendered off screen and there is no refresh problem as the compositor handle all this nicely. I think that bug should be reopened and fixed, I could eventually help, what do you think Brian?
(Just to clarify, about reopening the bug, I'm obviously talking about *our* bug #403, not the gtk bug.)
i'm still unable to fix this, even by allowing the widget to be double-buffered. hooking into expose-event and calling gtk_widget_queue_draw_area() makes the entire window not get drawn period. any ideas?
ok, this is fixed now. gdk_draw_drawable() appears to be the key. i still think this is a behavior change in gtk 2.6 that shouldn't have happened, but whatever. it works, and that's all i care about.