Bug ID 1208645
Summary Multiple screens stopped working with latest update
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Normal
Priority P5 - None
Component X11 3rd Party Driver
Assignee gfx-bugs@suse.de
Reporter rosuna@suse.com
QA Contact sndirsch@suse.com
Found By Customer
Blocker ---

Created attachment 865109 [details]
logs

I've found this issue several times, last one happened in late January or early
February.
I'm using G06 nvidia propietary drivers, having a Lenovo Thinkpad P15 gen2
laptop. The laptop is using 3 external screens connected through a Dell dock
station.
Latest working snapshot is dated from February 10th, I can roll back to this
one and everything will work well. First time I detected this problem was
around the upgrade released on February 13th or 14th, with new nvidia drivers.
I think there were newer ones released on 14th, but those have not helped
either.
I've just tried the upgrade again today, with the same symptoms:
I'm using sssd and X11 (Tumbleweed defaults anyway), and I've lost one of my
screens, and none of them is the main one any more (no menu bar).
Right click on the desktop to set up screen preferences from plasma menu
doesn't really make things better, it does detect the 3 screens + laptop screen
(which I usually turn off), but one of the screens will never turn on, and no
matter which one I select as primary, neither takes that setting (so as a
result I'm still with no menu-bar in Plasma). Alt-tab does work and fortunately
at least I have a console open to fetch some logs.
I've tried to set up the monitors with nvidia-settings, but that did not work
either.
Last time I had this issue (or similar), it was solved by forcing remove the
nvidia G06 driver, reinstalling it in a multi-user target and making sure
prime-select would use nvidia. This time that did not do the trick.
I'm attaching a few logs, but probably less than needed. Let me know if you
need any other file, or if any other information is needed (because I know the
bug description is not the best).


You are receiving this mail because: