Siduction Forum
Siduction Forum => Software - Support => Topic started by: mdmarmer on 2024/02/16, 01:27:25
-
sddm login screen flashes and disappears before i can enter anything
AMD graphics older dell desktop
lxqt siduction system
after i did the d-u, both firefox and chrome abended as soon as i tried to start them
then after reboot i was unable to login to gui
-
Uh, what does startx telling you? Any log files? Intel, AMD, Nvidia?
Xorg broken or using Wayland (ok not really because of lxqt).
Ah. there where a bunch of qt packages in the last d-u.
Questions over questions.
-
I decided a reinstall would be easier. I installed from the latest siduction testbuild of lxqt, added a few packages (streamtuner2, vlc, mpv, opera, chrome,hexchat, kpat, and meteo-qt). I did d-u in init 3 before restoring my data. Unfortunately the same thing happened. I probably should have kept the system and looked at startx log. However, I installed mxlinux. I still have not restored the data. This is an older Dell desktop with intel i5 and AMD graphics. Yesterday there were about 22 upgrades including sddm if I remember. On the original system I had done the xorg and i think also the qt upgrades days ago with no problem.
-
Hello,
I have the same problem. After the update on 16.02. Firefox could no longer be started. After restarting, the login screen popped up briefly and then went black. Logging in via xrdp and console is still possible.
I suspect that it has to do with the graphics card driver from AMD, because there were no problems on my laptop with an Intel graphics card.
Graphics card: AMD FirePro W5000
The following packages have been updated (excerpt from /var/log/apt/history.log) :
Start-Date: 2024-02-16 17:50:23
Commandline: apt full-upgrade
Upgrade: libglib2.0-dev-bin:amd64 (2.78.3-2, 2.78.4-1), ovmf:amd64 (2023.11-6, 2023.11-7), bind9-host:amd64 (1:9.19.19-1, 1:9.19.21-1), libglx-mesa0:amd64 (23.3.5-1, 24.0.1-1), libglx-mesa0:i386 (23.3.5-1, 24.0.1-1), libatkmm-1.6-1v5:amd64 (2.28.3-2+b1, 2.28.4-1), libgl
ib2.0-bin:amd64 (2.78.3-2, 2.78.4-1), libglib2.0-dev:amd64 (2.78.3-2, 2.78.4-1), libgbm1:amd64 (23.3.5-1, 24.0.1-1), libgbm1:i386 (23.3.5-1, 24.0.1-1), cockpit-networkmanager:amd64 (310.1-1, 311-1), libgbm-dev:amd64 (23.3.5-1, 24.0.1-1), libcbor0.10:amd64 (0.10.2-1.1, 0
.10.2-1.2), cockpit-bridge:amd64 (310.1-1, 311-1), qemu-efi-aarch64:amd64 (2023.11-6, 2023.11-7), liblua5.4-0:amd64 (5.4.6-2, 5.4.6-3), adwaita-icon-theme:amd64 (46~beta-1, 46~beta-2), libgegl-common:amd64 (1:0.4.46-4, 1:0.4.48-1), gvfs-fuse:amd64 (1.52.2-1, 1.53.90-1),
gvfs-common:amd64 (1.52.2-1, 1.53.90-1), libgegl-0.4-0:amd64 (1:0.4.46-4+b1, 1:0.4.48-1), gvfs-libs:amd64 (1.52.2-1, 1.53.90-1), libglib2.0-data:amd64 (2.78.3-2, 2.78.4-1), python3-scipy:amd64 (1.10.1-10, 1.11.4-1), qemu-efi-arm:amd64 (2023.11-6, 2023.11-7), libopenh26
4-7:amd64 (2.4.0+dfsg-1, 2.4.1+dfsg-1), mesa-va-drivers:amd64 (23.3.5-1, 24.0.1-1), mesa-va-drivers:i386 (23.3.5-1, 24.0.1-1), libgl1-mesa-dev:amd64 (23.3.5-1, 24.0.1-1), libxi-dev:amd64 (2:1.8-1+b1, 2:1.8.1-1), libgl1-mesa-dri:amd64 (23.3.5-1, 24.0.1-1), libgl1-mesa-dr
i:i386 (23.3.5-1, 24.0.1-1), libosmesa6:amd64 (23.3.5-1, 24.0.1-1), libosmesa6:i386 (23.3.5-1, 24.0.1-1), libegl1-mesa-dev:amd64 (23.3.5-1, 24.0.1-1), libpangomm-1.4-1v5:amd64 (2.46.3-1, 2.46.4-1), liburi-perl:amd64 (5.26-1, 5.27-1), python3-pexpect:amd64 (4.9-1, 4.9-2)
, dnsmasq-base:amd64 (2.90-1, 2.90-2), texlive-latex-base:amd64 (2023.20231207-1, 2023.20240207-1), gvfs:amd64 (1.52.2-1, 1.53.90-1), gvfs-daemons:amd64 (1.52.2-1, 1.53.90-1), bind9-dnsutils:amd64 (1:9.19.19-1, 1:9.19.21-1), mesa-vulkan-drivers:amd64 (23.3.5-1, 24.0.1-1
), mesa-vulkan-drivers:i386 (23.3.5-1, 24.0.1-1), libjansi-java:amd64 (2.4.0-2, 2.4.1-2), libbudgie-plugin0:amd64 (10.8.2-2, 10.8.2-3), libavif16:amd64 (1.0.3-1, 1.0.4-1), libavif16:i386 (1.0.3-1, 1.0.4-1), r-cran-survival:amd64 (3.5-7-1, 3.5-8-1), libglapi-mesa:amd64 (
23.3.5-1, 24.0.1-1), libglapi-mesa:i386 (23.3.5-1, 24.0.1-1), libglib2.0-0:amd64 (2.78.3-2, 2.78.4-1), libglib2.0-0:i386 (2.78.3-2, 2.78.4-1), libbabl-0.1-0:amd64 (1:0.1.106-3+b2, 1:0.1.108-1), bind9-libs:amd64 (1:9.19.19-1, 1:9.19.21-1), code:amd64 (1.86.1-1707298119,
1.86.2-1707854558), texlive-base:amd64 (2023.20231207-1, 2023.20240207-1), libegl-mesa0:amd64 (23.3.5-1, 24.0.1-1), gstreamer1.0-libav:amd64 (1.22.9-1, 1.22.10-1), mesa-vdpau-drivers:amd64 (23.3.5-1, 24.0.1-1), mesa-vdpau-drivers:i386 (23.3.5-1, 24.0.1-1), nss-plugin-pe
m:amd64 (1.1.0-1, 1.1.0+1-1), dnsutils:amd64 (1:9.19.19-1, 1:9.19.21-1), libxi6:amd64 (2:1.8-1+b1, 2:1.8.1-1), libxi6:i386 (2:1.8-1+b1, 2:1.8.1-1), texlive-latex-recommended:amd64 (2023.20231207-1, 2023.20240207-1)
End-Date: 2024-02-16 17:51:10
Many thanks for your help
RanSong
PS Sorry about this English, it's not my language. I would prefer German.
Edit, sorry made it readable, hendrikL
-
mh, xorg.log and maybe grep for errors in journalctl or dmesg.
-
Unfortunately I couldn't do anything with mh.
I have attached the xorg.log and the syslog for the last start.
-
Mh or mh is only a phrase 8)
-
The only thing I can find is a segfault that has to do something with radeon....., so yes I believe it is a problem with the AMD chip and not sddm!
2024-02-17T17:20:05.091308+01:00 PC100 kernel: QSGRenderThread[7495]: segfault at 40 ip 00007fe8ecdc586d sp 00007fe8c7dfe160 error 4 in radeonsi_dri.so[7fe8ec697000+13a2000] likely on CPU 4 (core 4, socket 0)
2024-02-17T17:20:05.091318+01:00 PC100 kernel: Code: 8b 6f 30 85 ed 0f 84 e5 00 00 00 31 db 49 89 e5 eb 34 0f 1f 00 4d 03 77 38 49 8b 36 48 85 f6 74 0e f0 83 2e 01 75 08 4c 89 e7 <41> ff 54 24 40 49 c7 06 00 00 00 00 41 8b 57 30 48 83 c3 01 39 d3
2024-02-17T17:20:05.101050+01:00 PC100 sddm-helper[7417]: [PAM] Closing session
Did you try an older kernel?
-
The problem happens without a kernel upgrade.
-
Only the logon screen really disappears, the mouse pointer is still visible.
When I end this process, the login screen is briefly displayed again.
/usr/lib/xorg/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_lWtzvf -noreset -displayfd 16
Then I logged on to the console as a user and started KDE via startX. KDE starts background image is displayed and hangs up immediately. I have attached the xorg.log of this process.
-
I installed siduction from latest lxqt test build in virtualbox. I did a full-upgrade in virtualbox and there is no problem logging in and out, whether or not I reboot with latest towo kernel.
-
Only the logon screen really disappears, the mouse pointer is still visible.
When I end this process, the login screen is briefly displayed again.
/usr/lib/xorg/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_lWtzvf -noreset -displayfd 16
Then I logged on to the console as a user and started KDE via startX. KDE starts background image is displayed and hangs up immediately. I have attached the xorg.log of this process.
What is journalctl telling you, maybe grep for error or amd/xorg, I don't know.
If it were an Intel-CPU I would say try the kernelparamet intel_iommu=igfx_off, but it isn't.
I am clueless, there was a "mesa" update if I read it correctly, perhaps that is the reason?
One last chance?
Did you try kwin-wayland, also for sddm --> this is my /etc/sddm.conf
:~$ cat /etc/sddm.conf
[Autologin]
Relogin=false
Session=
User=
[General]
DisplayServer=wayland
EnableHiDPI=true
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
HaltCommand=/bin/systemctl poweroff
InputMethod=
Numlock=none
RebootCommand=/bin/systemctl reboot
[Theme]
Current=<your prefered theme>
CursorSze=12
DisableAvatarsThreshold=7
EnableAvatars=
FacesDir=/usr/share/sddm/faces
ThemeDir=/usr/share/sddm/themes
[Users]
DefaultPath=/bin:/usr/bin
HideShells=
HideUsers=
MaximumUid=60000
MinimumUid=1000
RememberLastSession=true
RememberLastUser=true
[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
SessionCommand=/etc/sddm/wayland-session
On my system it didn't work with /etc/sddm.conf.d/<foo>.conf, so I tried /etc/sddm.conf and it worked.
PS.: you can use "startplasma-wayland" instead of startx if kwin-wayland is installed to test it.
-
the sddm.conf did not work for me.
Then I tried a little and installed the following packages:
Start-Date: 2024-02-21 15:05:05
Commandline: /usr/sbin/synaptic
Requested-By:
Install: mesa-amdgpu-va-drivers:amd64 (1:22.1.0.50205-1511377~20.04), mesa-va-drivers:amd64 (24.0.1-1), libosmesa6:amd64 (24.0.1-1), mesa-vulkan-drivers:amd64 (24.0.1-1), libdrm-amdgpu-amdgpu1:amd64 (1:2.4.110.50205-1511377~20.04, automatic), libdrm-amdgpu-radeon1:amd64
(1:2.4.110.50205-1511377~20.04, automatic), libllvm14.0.50205-amdgpu:amd64 (1:14.0.50205-1511377~20.04, automatic), mesa-amdgpu-vdpau-drivers:amd64 (1:22.1.0.50205-1511377~20.04), libdrm2-amdgpu:amd64 (1:2.4.110.50205-1511377~20.04, automatic), libdrm-amdgpu-common:amd
64 (1.0.0.50205-1511377~20.04, automatic), mesa-vdpau-drivers:amd64 (24.0.1-1), amdgpu-core:amd64 (22.20.50205-1511377~20.04, automatic)
End-Date: 2024-02-21 15:05:09
I was then able to log on to the computer via startx. Not all monitors could be addressed, and some other things were not as they should be, but it worked for the time being. Then I uninstalled the packages again and, as expected, the same problem occurred.
Next I reinstalled Siduction on an empty SSD. I left everything standard, all screens were there, the resolution was ok. But after the full upgrade, the screen was black here too.
It really seems to be an AMD driver problem.
I'm going to try out the new installation a bit, because if something breaks, it's no big deal.
-
Seems that mesa is a little bit disturbed these days. Maybe your problem is related or similar to this one? (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123)
-
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123#10
This looks like a workaround for it, or downgrade it.
-
The workaround fixes the problem on my system. I did a fresh install from the latest lxqt testbuild, and did d-u right after installation. My graphics card is AMD R7-200 (HD8670 RS340X). This is an older Dell desktop with i5-4590 processor.
-
The note from the bugreport has solved the problem for the time being.
I create a file /etc/X11/xorg.conf.d/10-radeonenvrac.conf
with in it:
Section "Device"
Identifier "radeaonenvrac"
Driver "radeon"
Option "Accel" "no"
EndSection
It really only seems to be a temporary solution, let's hope that the bug will be solved for good.
I would like to thank everyone who sacrificed their free time to fix this bug.
RanSong
-
It would be interesting if this bug hits also a Wayland Session!
-
Even when I start "Plama Wayland", the start screen animation appears briefly. An error message is displayed very briefly and then it is black.
Error message: 'ksplashqml was terminated unexpectedly'
-
According to the package maintainer, the bug is fixed in mesa (libgl1-mesa-dri and others) version 24.0.3-1 which is in sid as of 15 Mar 2024. I have not tested it yet. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123#59
Nach Angaben des Paketbetreuers ist der Fehler in der Mesa-Version (libgl1-mesa-dri und andere) 24.0.3-1 behoben, die sich seit dem 15. März 2024 in Sid befindet. Ich habe ihn noch nicht getestet. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123#59
-
I can confirm that.
-
I have the newer version of libgl1-mesa-dri and libglx-mesa0 and am still getting a blank login screen except for the boxes used to enter the username and password. I can enter the username and password carefully into the boxes, but, cannot see what I am typing. If I type them both correctly lxQT comes up and the OS runs fine. This is on my old Asus EEEpc that's been running siduction lxQT for many years.