[Bug 1958242] Re: mesa update freeze/crash screen before login
I was reticent to install some random ppa. But since compiling it myself would be some adventure. I removed my personal stuff and other data, changed passwords and then installed the kisak ppa. And it seems to work without issue. Just as well as in 20.04.5. The current version in the ppa is 21.3.6. I have no idea what was broken in 21.2.6. Was there really a need for messing with r300 drivers? dmesg shows neither errors or weird warnings about mesa. Everything seems ok. Only thing I don't know what else might have been installed from that ppa. Yes I'm a little paranoid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958242 Title: mesa update freeze/crash screen before login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1958242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958242] [NEW] mesa update freeze/crash screen before login
Public bug reported: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. I went to Ctrl+Alt-F2, logged in and: ** sudo apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 sudo apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 *** Now everything works fine. Other than the mentioned mesa packages everything else is fully updated. === In short something got broken again in mesa 21.2.6, downgrading to 21.0.3 fixes the issue. === Running Lubuntu 20.04 Kernel: 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 GPU: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. + I went to Ctrl+Alt-F2, logged in and: ** apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 *** Now everything works fine. Other than the mentioned mesa packages everything else is fully updated. - === In short something got broken again in mesa 21.2.6, downgrading to 21.0.3 fixes the issue. === - Running Lubuntu 20.04 Kernel: 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 GPU: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon ** Description changed: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. I went to Ctrl+Alt-F2, logged in and: ** - apt
[Bug 1909171] Re: sddm-greeter segfault
Remy (remyzerems) solution seems better if the PPA author can be trusted. Part of the security in Linux, comes from not installing random stuff on the Internet. PPAs are individual repos that anyone can set up without Ubuntu responsability or oversight. I know nothing about the PPA author, maybe the greatest guy ever. I just want to remind people of performing due diligence on adding repos from unknown/un-trusted sources. I will stay with the downgraded mesa, since the platform I use is a laptop where everything I need works right now. Is older hardware, so there is no need for the newest and the greatest video card drivers. I'll wait for the official mesa from ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909171 Title: sddm-greeter segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909171] Re: sddm-greeter segfault
I have another workaround, which actually makes sddm-greeter work again. I had my doubts so I went to confirm my assumptions. You can skip my detective work and rambling by going under the asterisk line. And it is true that both programs which JohnDoe_71Rus (johndoe99) mentions have similar issues. I haven't looked at glxinfo till now and just now found that pages at unix.stackexchange.com cause tabs crashes with the RIP CODE message in dmesg. But only if I reach to the end of the web page. Strange behavior. Disabling hardware acceleration does not solve the problem. I mentioned previously that viewing video files was no problem and I tried 'mpv' from the terminal and it uses the gpu driver and works fine, except that it crashes when the video ends with a seg fault. Which is probably why I did not notice the problem when using SMPlayer as the GUI. Using the vo=xv driver causes no error when finishing the I suppose that I was just lucky that most webs I visits don't require the magic 3d that makes certain pages crash firefox tabs. Still sddm-greeter should not fail so catastrophically when it does nothing so complex that requires the gpu's shadow magic. Without terminal-fu level skills most users wont be able to maneuver through the issue. And blindly will blame it on Linux being "unusable". Some level of fault tolerance is needed but hardware issues are difficult to plan around. But again: Why sddm-greeter uses gpu's magic? Dependencies perhaps? Is it Qt5 indirect fault? Running gdb on sddm on runlevel 2 with no X and the segfault appeared in : QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 There is no RIP Code message in dmesg. So I was not convinced. strace was not helpfull either. So I gave up on finding the exact culprit. Short of recompiling sddm, qt5 and mesa and debugging them in tandem. Unfortunately I don't have the time. * First: I'm using Lubuntu 20.04, newer *buntu versions I have no idea of their status/compatibility/versioning/etc. This only applies to 20.04. So I tracked down the main mesa libraries and downgraded them all to the previous version. #apt install libglapi-mesa=20.0.4-2ubuntu1 libglx-mesa0=20.0.4-2ubuntu1 libgl1-mesa-dri=20.0.4-2ubuntu1 libegl-mesa0=20.0.4-2ubuntu1 libgbm1=20.0.4-2ubuntu1 So then with dpkg-reconfigure sddm-greeter I selected it again as the display manager. Went to runlevel 5 and presto IT WORKS. Firefox tabs do not crash anymore on unix.stackexchange.com and mpv on the command line using the gpu driver does not segfaults anymore on exit. So I can confirm without doubt that the main culprit as JohnDoe_71Rus said, is in the mesa libraries upgrade. But I can't confirm the exact code/library where the problem is located. Surprisingly i did not have any dependencies issues when downgrading this libraries. Other people experience might differ due to the uniqueness of their systems. To prevent apt from upgrading this packages again; #apt-mark hold libglapi-mesa=20.0.4-2ubuntu1 libglx- mesa0=20.0.4-2ubuntu1 libgl1-mesa-dri=20.0.4-2ubuntu1 libegl- mesa0=20.0.4-2ubuntu1 libgbm1=20.0.4-2ubuntu1 When the patched update to the mesa bug comes just use "apt-mark unhold" with the same list. This workaround/solution by downgrading might break some stuff and might not be future proof. So far on my own testing everything works. The changelog for mesa: https://launchpad.net/ubuntu/focal/+source/mesa/+changelog does not seem that impressive, so unless there is a change in your hardware there should be no impact on your system. But I can't give any guaranties. Most of the changelog is ppc64 fixes and the big upgrade: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699 I hope this helps others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909171 Title: sddm-greeter segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909171] Re: sddm-greeter segfault
I'm also affected by this bug. There is always a "RIP Code" warning available through dmesg, after crashing of sddm-greeter. Same graphics: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon Acer 5100 with Turion TL-60 CPU I use Lubuntu. My work around for anyone wanting something usable is Ctrl-Alt-f2 to the terminal, logging in and installing xdm or wdm, at the end of the installation it lets you choose a new display manager, choose xdm if it is what you installed. And it works, you can log in and use it normally. I have not tested other Desktops Environments. Everything works under LXqt: 3D Screensaver, Firefox, video playing, etc. So, If this is a mesa bug, why everything else works? And only sddm-greeter dies? It stands to reason that sddm-greeter does not do anything more complicated or graphics intensive than Firefox, Mplayer or the 3D screensaver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909171 Title: sddm-greeter segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1200117] Re: package linux-headers-3.2.0-49 (not installed) failed to install/upgrade: ErrorMessage: unable to create `/usr/src/linux-headers-3.2.0-49/include/asm-generic/cmpxchg-local.h.dpkg-new
I found this problem and the most common cause. The filesystem runs out of inodes even if it has many gigabytes of spaces left. Check your systems with df -i. If you have plenty of i-nodes left then is a apt database corruption. My recent experience with several systems running 12.04 is this case of running out of inodes. Previous versions of the linux-headers-generic package as well as the linux-images packages never got removed. If it was the last two or three no problem, but there were almost 20 versions of the kernel and kernel headers. the linux-headers package has a huge number of files, which eats up all your i-nodes. With removing all but the last tree kernels headers (previous linux-headers-generic-3.2.0-?) I went down from 100% i-nodes used to 45% used. For example on one PC I checked my i-nodes count and was a 100% full, well in practice like 200 free inodes from almost 700.000. Just removing the previous linux-headers packages does the trick. Synaptic makes it easier with the GUI + search feature and order feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1200117 Title: package linux-headers-3.2.0-49 (not installed) failed to install/upgrade: ErrorMessage: unable to create `/usr/src/linux- headers-3.2.0-49/include/asm-generic/cmpxchg-local.h.dpkg-new' (while processing `./usr/src/linux-headers-3.2.0-49/include/asm-generic /cmpxchg-local.h'): No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1200117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
