Robert Munteanu wrote:

IceWM might not use hardware acceleration for rendering. You might want to try disabling hardware acceleration for rendering in KDE.

First thought: Um, where would I disable that? *shrug* The only reference I possibly found was Compositor in Hardware->Display and Monitor. But it is not enabled. Changed the Rendering backend nevertheless to 'XRender' and that seems to remove the issue. Playing around with the available options (XRender, OpenGL 2.0 and 3.1, initial setting been 2.0) I suddenly could not reproduce the issue anymore with any of the backends, until I noticed it only shows up if the compositor is DISabled! But then with any backend. This is weird....

Also try Gnome-Shell, this one surely uses hardware acceleration.

Don't really feel like pulling in all that gnome stuff just for a test :( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov wrote:

02.06.2017 13:13, Peter Suetterlin пишет:

...

Hi

is anyone else experiencing graphics glitches in Tumbleweed since a few snapshots back?

They show up as horizontal (short) bars on fast-changing features. E.g., I can see them when resizing an xterm horizontally forth and back. On the window border that I'm extending I see jaggy features. Another way to see them is switching desktop (I use slide), often the window title bar of one or more windows on the screen I slide to shows the artifacts.

Are you using intel or modesetting Xorg driver?

No idea :o I'm running on default settings and never checked what 'default' is(*).... Checking the log I see [ 6.371] (==) Matched modesetting as autoconfigured driver 0 [ 6.371] (==) Matched intel as autoconfigured driver 1 ... [ 6.371] (II) LoadModule: "modesetting" ... [ 6.372] (II) LoadModule: "intel" ... [ 6.537] (II) UnloadModule: "intel" So it's the modesetting one. (*)googling a bit it seems this is a recently ongoing issue, switching to modesetting. Any word if for TW such a change happened recently? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Felix Miata wrote:

Peter Suetterlin composed on 2017-06-05 12:39 (UTC+0100):

...

So it's the modesetting one.

...

(*)googling a bit it seems this is a recently ongoing issue, switching to modesetting. Any word if for TW such a change happened recently?

Check if the pci ID of your gfxchip matches any listed in /etc/X11/xorg_pci_ids/modesetting.ids.

Obviously it is (8086191B), else it wouldn't use the modesetting one :) The question rather was has that always been the case or/and has the ranking of modesetting vs. intel changed lately? Probably not, rpm -q --changelog xorg-x11-server lists * Sun May 08 2016 eich@suse.com - modesetting.ids: Add file for PCI IDs of ASICs which the modesetting rather than the native driver should be used for. This includes all Intel Gen9+ hardware (boo#978954). as last relevant change... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Felix Miata wrote:

Peter Suetterlin composed on 2017-06-05 14:20 (UTC+0100):

...

rpm -q --changelog xorg-x11-server lists

...

* Sun May 08 2016 eich@suse.com - modesetting.ids: Add file for PCI IDs of ASICs which the modesetting rather than the native driver should be used for. This includes all Intel Gen9+ hardware (boo#978954).

...

as last relevant change...

That same changelog has a March 17 entry pointing to https://bugzilla.opensuse.org/show_bug.cgi?id=1021803 that looks suspiciously like a possible cause of which your OP complained:

"graphics glitches...show up as horizontal (short) bars on fast-changing features".

Whee, I wouldn't have spotted that from the changelog itself :o But reading through the quite extended thread I'm not sure if it is the same thing - there it really was rather single pixels missing, if I read this correct (but TBH I did not understand too much of that discussion at all...) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov wrote:

Personally I have rather negative experience with modesetting driver on Intel HD 5500; I switched back to intel. You may try whether it makes any difference.

So far I couldn't complain TBH. Nevertheless, I commented out the entry for my HD530 in modesetting.ids and now it uses the intel one. No artifacts with that driver. Guess I'll stay with it, too. :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov wrote:

On Tue, Jun 6, 2017 at 12:57 PM, Peter Suetterlin wrote:

...

Andrei Borzenkov wrote:

...

Personally I have rather negative experience with modesetting driver on Intel HD 5500; I switched back to intel. You may try whether it makes any difference.

So far I couldn't complain TBH. Nevertheless, I commented out the entry for my HD530 in modesetting.ids and now it uses the intel one.

No artifacts with that driver. Guess I'll stay with it, too. :)

This really calls for bug report.

Sorry, yes, should have posted the link immediately: https://bugzilla.opensuse.org/show_bug.cgi?id=1042873 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org