http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c1 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Severity|Critical |Normal --- Comment #1 from Egbert Eich --- Fixed -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c3 --- Comment #3 from Robby Engelmann --- it it this SR?: https://build.opensuse.org/request/show/396011 Perhaps you may consider to enroll it through the TW update channel and pass Stagings etc. It is hardly possible to make it worse than now for a normal intel user on TW. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c5 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Egbert Eich --- (In reply to Robby Engelmann from comment #3)

it it this SR?: https://build.opensuse.org/request/show/396011

Perhaps you may consider to enroll it through the TW update channel and pass Stagings etc. It is hardly possible to make it worse than now for a normal intel user on TW.

Unfortunately, you've missed to include - the list of packages that have changed between your last good and your first bad installation, - the Xserver log file from before and after you've updated from the user repo. in your original report. This way, I was not able to draw the correct conclusions. I've investigated this myself now: The problem occurred due to a switch from xf86-video-intel to the modesetting driver for anything g9+ to address that xf86-video-intel doesn't really have good support for this hardware: for other reasons we've disabled the hardware cursor on xf86-video-modesetting altogether. I've fixed this and submitted it to Factory now. The issue can be work-arounded by a simple edit to /etc/X11/xorg.conf.d/50-device.conf. It is not serious enough to justify an emergency updated for Tumbleweed. Tumbleweed is a rolling release, which means that things may break at times - however it will won't be too long until a fix shows up. the fix will show up there. Closing this issue now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c7 --- Comment #7 from Egbert Eich --- (In reply to Robby Engelmann from comment #6)

Sorry for the missing information, it seemed clear to me, that the transition from TW20160512 to TW20160514 was the bad guy here as there was in update in the x-server package.

Unfortunately, even this would not have helped much as there is no list of package that got updated between TW releases - if there is, I'm not aware of it :( Such a list would most likely contain more packages than which got updated on your system as there may have been updates to packages you don't have installed. Therefore, the best source for for finding the packages which have changed is /var/log/zypp/history.

Now, I added the X11 factory repo, where fixed intel and x-server packages are in. It works fine here again. I will remove that repo again, when both SR's hit TW. Thanks for your help.

Ok, great! Good to know! Thanks for testing :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c9 --- Comment #9 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (980124) was mentioned in https://build.opensuse.org/request/show/396135 Factory / xorg-x11-server -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c11 --- Comment #11 from Robby Engelmann --- For TW it does not matter a lot. Kernel 4.6 final was submitted to factory today. I am not a programmer, thus I do not know how to figure out that. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c16 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com --- Comment #16 from Jiri Slaby --- Oh yeah, the flickering was fixed for me by update to 4.6 too. Cool! I am on Ivy Bridge using modesetting_drv though (so maybe unrelated to this report). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=980124 http://bugzilla.novell.com/show_bug.cgi?id=980124#c18 --- Comment #18 from Jiri Slaby --- (In reply to Egbert Eich from comment #17)

On IvyBridge I'd still recommend xf86-video-intel. There is a problem with sw cursor at the moment. Most KMS drivers provide a working HW cursor today, though.

I am running patched Xorg by: https://patchwork.freedesktop.org/patch/75985/ I am using modesetting_drv for a month now and saw no problems with Xrender compositing. 4.6 fixed also OpenGL compositing. So I will stick with modesetting until is breaks if at all :). -- You are receiving this mail because: You are on the CC list for the bug.