https://bugzilla.suse.com/show_bug.cgi?id=1224342 https://bugzilla.suse.com/show_bug.cgi?id=1224342#c17 Stakanov Schufter <stakanov@disroot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(stakanov@disroot. | |org) | --- Comment #17 from Stakanov Schufter <stakanov@disroot.org> --- (In reply to Stefan Dirsch from comment #15)

I asked you to test if you could reproduce the original issue with regular TW Mesa.

Please be patient as I will be patient on this sentence too. Let us determine one thing: I have a problem described in this bug. I have it when the updates of PM were applied. I followed your request and installed the original Mesa Drivers from Tumbleweed. The issue was as described. So, I did NOT change the issue in a multi user from a multimonitor system but I did apply what you asked for. Not being sure that the I completely eliminated all PM related stuff, I did a complete deactivation of all Packman repos, and did a zypper dup --allow vendor change. Now with the system completely guaranteed in the new asset, while before it was already impossible to work with one user(with the Packman drivers), here we have that I write you from a "one user open" session, that allows me to use firefox. And it displays the background and the system is usable and can be shut down. Now if I open a second user, I will experience already a part of crashes. But still it seems usable. (I did not try for how long). Once I do open Firefox in this user, to e.g. post the output of the journal, then the firefox enters in a loop of crashes were the crash repreats constantly. Plasma crashes too, apparently for what I understood even akonadi crashes (I think I have seen the core dump) and the whole system becomes unresponsive to the request of closing this user or restarting / rebooting. But also the first original user now is haunted by the crash of firefox and proves to be unable to shutdown/reboot. So then you have to go Alt+CTRl+F1 and do a ctrl+alt+canc or login as root and reboot forcibly with shutdown -r now. Please note that I do not "change" anything but I do simply describe a reproducible behaviour, in a machine prepared according your indications and in the settings you have as of above. It comes now naturally to ask: is this user home maybe "compromised" by some crash or file error. Well no, I can exclude this, because if you choose user A, then logout then login user B, the new user will work. If you log out and then login in as A, even A will work. But if in any combination you work with two users open in X (I did not try in Wayland, can if you deem useful of course)) and perform actions like opening the browser in any of these users this will compromise the whole system behaviour like described. So: with Packman no show even with one user and right from login, with crashing monitors (in random order, that is monitor 1 goes dark, returns, monitor3 goes then returns etc. until finally all is gone and the usage can be done only via CLI and you cannot logout or shutdown. With pure TW (no codecs at all) we have the last attachment and the behaviour as explained. Please not that I do not change things here intentionally or try to raise attention or whatever. I have a problem, I follow your indications and tell you the outcome. Fair enough? -- You are receiving this mail because: You are on the CC list for the bug.