Bug 28152 - [NV36] corruption in FVWM window decorations
Summary: [NV36] corruption in FVWM window decorations
Status: REOPENED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 22:07 UTC by Nick Bowler
Modified: 2014-08-21 19:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Screenshot (incorrectly rendered) (8.11 KB, image/png)
2010-05-17 22:07 UTC, Nick Bowler
no flags Details
Screenshot (correctly rendered) (7.66 KB, image/png)
2010-05-17 22:08 UTC, Nick Bowler
no flags Details
Xorg.0.log (51.97 KB, text/plain)
2010-05-17 22:09 UTC, Nick Bowler
no flags Details
Kernel log (26.76 KB, text/plain)
2010-05-17 22:12 UTC, Nick Bowler
no flags Details
Xorg.0.log (64.60 KB, text/plain)
2013-08-18 18:33 UTC, Nick Bowler
no flags Details
Kernel log (39.77 KB, text/plain)
2013-08-21 05:39 UTC, Nick Bowler
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Bowler 2010-05-17 22:07:42 UTC
Created attachment 35718 [details]
Screenshot (incorrectly rendered)

On an AGP fx5700 (NV36) card, I'm experiencing rendering glitches in FVWM's
window decorations on nouveau.  The artifacts are completely consistent:
exactly the same glitches occur on every single window.

These glitches do not occur with other drivers, and I'm certain they didn't
occur in nouveau last time I tried it (but this was well over a year ago).

Attaching screenshots since pictures say 1000 words.
Comment 1 Nick Bowler 2010-05-17 22:08:48 UTC
Created attachment 35719 [details]
Screenshot (correctly rendered)
Comment 2 Nick Bowler 2010-05-17 22:09:20 UTC
Created attachment 35721 [details]
Xorg.0.log
Comment 3 Nick Bowler 2010-05-17 22:12:24 UTC
Created attachment 35722 [details]
Kernel log

The top part of the log unfortunately got cut off due to log buffer overflow before the boot process could save it, but all the nouveau stuff is there.

I've increased the log buffer size, so I can send the full log next time I reboot, if necessary.
Comment 4 Ilia Mirkin 2013-08-18 18:10:38 UTC
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team
Comment 5 Nick Bowler 2013-08-18 18:29:40 UTC
This bug did not magically fix itself.  The corruption persists exactly as in the screenshots posted over 3 years ago.
Comment 6 Nick Bowler 2013-08-18 18:33:06 UTC
Created attachment 84211 [details]
Xorg.0.log

Fresh Xorg log...

xf86-video-nouveau 1.0.9
mesa 9.1.6
server 1.4.2.901
Linux 3.9.4
Comment 7 Ilia Mirkin 2013-08-18 19:22:11 UTC
Thanks for re-checking!

Please also include a full kernel log (with a recent kernel).

And am I reading that right, xorg 1.4? Not 1.14? If so, it'd be nice to exclude some sort of API change issue with e.g. EXA in the interevning 6 years since 1.4's release.
Comment 8 Nick Bowler 2013-08-20 17:11:43 UTC
(In reply to comment #7)
> Thanks for re-checking!

Not hard to do, all I need to do is look at the top of any window :P

> Please also include a full kernel log (with a recent kernel).

I built 3.10.8, I will try it tonight to get the log...

> And am I reading that right, xorg 1.4? Not 1.14? If so, it'd be nice to
> exclude some sort of API change issue with e.g. EXA in the interevning 6
> years since 1.4's release.

You are reading it right, but it was written wrong!  Server version is 1.14.2.901.
Comment 9 Nick Bowler 2013-08-21 05:39:50 UTC
Created attachment 84368 [details]
Kernel log

Here's the log from the freshly minted 3.10.8 (of course the graphical problems are still present)
Comment 10 Ilia Mirkin 2013-08-21 06:06:17 UTC
Naturally I just popped the NV34 out of my system and forgot to test this out. For next time that it goes in... all I have to run is fvwm? Or is it fvmw2? fvwm95? Do I need to set up some sort of theme? Do you have some sort of compositor situation going on?
Comment 11 Ilia Mirkin 2013-09-02 07:09:26 UTC
I loaded up fvwm (2.6.5) on my NV34, and it all seemed fine. However it was a much more twm-y experience than I remember fvwm being. Perhaps you can share the requisite theme/where I can find it, so that I'm able to repro the issue?
Comment 12 Nick Bowler 2013-09-04 15:29:57 UTC
Right, the default window decorations for FVWM are not much to write
home about.  I'll try to bundle up my specific theme configuration into
something you can (hopefully) use.

I don't know if any of them exhibit the same problem that I have but in
the meantime you could perhaps try fvwm-themes which has a bunch of
different window styles (http://fvwm-themes.sourceforge.net/)
Comment 13 Ilia Mirkin 2014-08-21 19:58:28 UTC
Potentially of interest to you, here's something that helped a lot in tracking down some rendering issues on NV1x:

rendercheck -f a8r8g8b8 -t blend,composite,cacomposite

In the nv1x case, some of the cacomposite stuff was broken. If this all works out, try other formats, or other tests. The gradient test fails for me on all hw I've tried it on, so don't worry about that one.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.