Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: GoinEasy9 on 2022/12/03, 04:41:45
-
Hi
After my weekly update on my EEEpc running lxqt, boot will not complete. It stops in the middle of the boot process at
Finished Record Runlevel Change in UTMP,
My 2 siduction installs with KDE updated without a problem so I'm leaning on the link that was created after last weeks problem with libfm-qt11. Link was created with ln -s libfm-qt.so.12 libfm-qt.so.11.
I noticed libfm-qt11 was removed and libfm-qt12 came in during the update. I don't know if the created links have something to do with the incomplete boot.
Attachments show where boot stopped and the libfm-qt links.
Any help would be appreciated.
---------------------------------------------------------------------------------------------------------------------
Hallo
Nach meinem wöchentlichen Update auf meinem EEEpc mit lxqt wird der Bootvorgang nicht abgeschlossen. Er stoppt mitten im Bootvorgang bei
Finished Record Runlevel Change in UTMP,
Meine 2 siduction-Installationen mit KDE wurden ohne Probleme aktualisiert, so dass ich mich auf den Link stütze, der nach dem Problem der letzten Woche mit libfm-qt11 erstellt wurde. Der Link wurde mit ln -s libfm-qt.so.12 libfm-qt.so.11 erstellt.
Ich habe festgestellt, dass libfm-qt11 entfernt wurde und libfm-qt12 während des Updates hinzukam. Ich weiß nicht, ob die erstellten Links etwas mit dem unvollständigen Bootvorgang zu tun haben.
Die Anhänge zeigen, wo der Bootvorgang gestoppt wurde und die libfm-qt-Links.
Für jede Hilfe wäre ich dankbar.
-
I was experiencing the same problem, but maybe for different reasons.
It was related to the 22.3.0-1 version update of libgl1-mesa-dri.
In order to confirm that your problem is related do the following:
In the grub boot loader menu (edit the start option by typing "e")
search the line starting with
linux ...
Instruct systemd to go multi-user by appending
"systemd.unit=multi-user.target" to this very line and hit "ctrl-x"
to fire up the kernel.
The boot process should complete and present you with a terminal login
window. Login and start the X server (after su root) by:
Xorg -retro
If that results in a segfault (look at /var/log/Xorg.0.log) we are likely
to having the same issue. I rolled back to the
previous version 22.2.4-1 of libgl1-mesa-dri (with all other dependencies)
to resolve the problem. Beware that I am only guessing your problem could be
the same.
BR
-
actually the problem might be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025297
-
Thanks for the feedback Teriarch
Your linux foo is certainly better than mine, your guess hit the nail on the head. That, and the bug report were right on the money. Since seeing your post I've been trying to downgrade to 22.2.4-1 from testing. Unfortunately, I seem to be running into dependences that have unmet dependencies.
apt install -t testing libgl1-mesa-dri=22.2.4-1 libglapi-mesa=22.2.4-1 gives me a depends of libegl1 and libgl1 which have dependencies that have unmet dependencies.
I haven't downgraded an app in decades and I know I'm doing something wrong. Your instructions were right on and to the point. So much appreciated.
-
Here is what you can do (assuming you run the latest sid version):
Grab the following version 22.2.4-1 deb packages (e.g. from <https://snapshot.debian.org>):
libegl-mesa0
libegl1-mesa
libgbm1
libgl1-mesa-dri
libgl1-mesa-glx
libglapi-mesa
libglx-mesa0
libosmesa6
libxatracker2
mesa-vdpau-drivers
Put them into a separate folder, cd to that folder and execute
(as root, ignore the warnings about previous versions):
dpkg -i *.deb
Put them on hold (so they are not overwritten by the following upgrades):
apt-mark hold libegl-mesa0,
apt-mark hold libegl1-mesa, etc.
Wait until the dust settles and the graphic guys finally resolve the issue
with a later version. As soon as that happens, unhold the packages.
HTH
BR
-
After working all day to figure out the fix, you've given me precise instructions that helped me bring back my old EEEpc. I can't thank you enough. So much appreciate your effort.
Tom
-
glad I could be of service,
your gratitude more than repays the help I've given.
Have a nice day!
-
Hi Tom,
>> Wait until the dust settles and the graphic guys finally resolve the issue
>> with a later version. As soon as that happens, unhold the packages.
The time has come and so has the update (22.3.0-1 -> 22.3.0-2). You may now move on
to the recent version...
Wolfgang
-
Hi Wolfgang,
And that worked.
Once again, I thank you for sharing your knowledge.
Tom