Bugzilla – Bug 1079863
Mesa related packages in Tumbleweed-Update are lethal!
Last modified: 2018-02-08 07:55:10 UTC
Mesa related packages from http://download.opensuse.org/update/tumbleweed/ with the version number 18.0.0-187.1 made my notebook unusable! As soon as X.org started, the displays changed to empty and white. Please remove these packages ASAP! I could hardly revert to 18.0.0-185.1
I guess that's another duplicate of boo#1079465.
Please check https://bugzilla.opensuse.org/show_bug.cgi?id=1079465#c3
With 18.0.0-187.1 it should be already fixed, but you most likely have damaged shader in cache saved by 18.0.0-185.1. Delete ~/.cache and /var/lib/sddm/.cache directories.
(In reply to Stefan Dirsch from comment #1) > I guess that's another duplicate of boo#1079465. Probably not. The mentioned Mesa versions appeared just today in Tumbleweed-update. Anyway, Tumbleweed-update shouldn't contain "real" packages, only some test and meta packages, AFAIK! Putting these real packages into this repository was probably a mistake.
(In reply to Stefan Dirsch from comment #1) > I guess that's another duplicate of boo#1079465. I mean putting these real packages into this repository was probably an accident. BTW, see #c4
Not sure what you would like to tell me. I can only ask you to give the latest Mesa packages with the fix a try and remove the cache manually as suggested in comment #3. Michal and me are pretty sure it's just a duplicate.
OK, I'll try. One moment please...
(In reply to Stefan Dirsch from comment #6) > Not sure what you would like to tell me. I can only ask you to give the > latest Mesa packages with the fix a try and remove the cache manually as > suggested in comment #3. Michal and me are pretty sure it's just a duplicate. OK, deleting the cache files solved the problem. However, I think the new packages probably should include some post/pre-install scripts to delete the packages, because this way they will render so much computers practically unusable.
Seems this bug related: https://bugzilla.suse.com/show_bug.cgi?id=1079891
*** Bug 1079891 has been marked as a duplicate of this bug. ***
Closing as dup. (In reply to Tamás Németh from comment #8) > OK, deleting the cache files solved the problem. However, I think the new > packages probably should include some post/pre-install scripts to delete the > packages, because this way they will render so much computers practically > unusable. I guess you're talking about removing *cache* files. I expect more harm than benefit when trying this. Seriously. And you cannot remove files in $HOME of a network drive anyway. *** This bug has been marked as a duplicate of bug 1079465 ***
(In reply to Stefan Dirsch from comment #11) > Closing as dup. > > (In reply to Tamás Németh from comment #8) > > OK, deleting the cache files solved the problem. However, I think the new > > packages probably should include some post/pre-install scripts to delete the > > packages, because this way they will render so much computers practically > > unusable. > > I guess you're talking about removing *cache* files. I expect more harm than > benefit when trying this. Seriously. And you cannot remove files in $HOME of > a network drive anyway. > > *** This bug has been marked as a duplicate of bug 1079465 *** I think, you're right. Thank you for your effort.