Tumbleweed snapshot 20241127 update issue
During the update, following issue is visible (desktop switch to another tty with the logoff screen (tty1). But with <Ctrl>+<Alt>+<F3> switching to the running sessin in tty3 is still possible. The zypper dup - darcut script in the tmux session shows %posttrans(kernel-firmware-all-20241125-1.1.noarch) script output: /usr/lib/tmpfiles.d/connman_resolvconf.conf:1: Line references path below legacy directory /var/run/, updating /var/run/connman → /run/connman; please update the tmpfiles.d/ drop-in file accordingly. And hangs. After 30min, I type <ctrl>+<c> --> ^C Trying to exit gracefully ... Nothing happens since 10min. Will waite some time and reboot afterwards. Ulf
Desktop switched to another tty and i could switch back. But update hangs and after ctrl + c shows Trying to exit gracefully .... . In detail: "Script %posttrans(kernel-firmware-ath11k-20241125-1.1.noarch) wordt uitgevoerd ...........<8%> ^C Proberen netjes te eindigen... " -------- Ursprüngliche Nachricht -------- Von: Ulf via openSUSE Factory <factory@lists.opensuse.org> Antwort an: Ulf <ub22@gmx.net> An: Factory <factory@lists.opensuse.org> Betreff: Tumbleweed snapshot 20241127 update issue Datum: 28.11.2024 21:21:43 During the update, following issue is visible (desktop switch to another tty with the logoff screen (tty1). But with <Ctrl>+<Alt>+<F3> switching to the running sessin in tty3 is still possible. The zypper dup - darcut script in the tmux session shows %posttrans(kernel-firmware-all-20241125-1.1.noarch) script output: /usr/lib/tmpfiles.d/connman_resolvconf.conf:1: Line references path below legacy directory /var/run/, updating /var/run/connman → /run/connman; please update the tmpfiles.d/ drop-in file accordingly. And hangs. After 30min, I type <ctrl>+<c> --> ^C Trying to exit gracefully ... Nothing happens since 10min. Will waite some time and reboot afterwards. Ulf
After another ctrl + c : "Zypper is nu bezig met opschonen, zal zo spoedig mogelijk eindigen." Which means "Zypper is now cleaning up, will finish as soon as possible.". Well, it doesn't finish. :-( -------- Ursprüngliche Nachricht -------- Von: GMX via openSUSE Factory <factory@lists.opensuse.org> Antwort an: GMX <niclaas.grehling@gmx.net> An: Factory <factory@lists.opensuse.org> Betreff: Re: Tumbleweed snapshot 20241127 update issue Datum: 28.11.2024 21:28:10 Desktop switched to another tty and i could switch back. But update hangs and after ctrl + c shows Trying to exit gracefully .... . In detail: "Script %posttrans(kernel-firmware-ath11k-20241125-1.1.noarch) wordt uitgevoerd ...........<8%> ^C Proberen netjes te eindigen... " -------- Ursprüngliche Nachricht -------- Von: Ulf via openSUSE Factory <factory@lists.opensuse.org> Antwort an: Ulf <ub22@gmx.net> An: Factory <factory@lists.opensuse.org> Betreff: Tumbleweed snapshot 20241127 update issue Datum: 28.11.2024 21:21:43 During the update, following issue is visible (desktop switch to another tty with the logoff screen (tty1). But with <Ctrl>+<Alt>+<F3> switching to the running sessin in tty3 is still possible. The zypper dup - darcut script in the tmux session shows %posttrans(kernel-firmware-all-20241125-1.1.noarch) script output: /usr/lib/tmpfiles.d/connman_resolvconf.conf:1: Line references path below legacy directory /var/run/, updating /var/run/connman → /run/connman; please update the tmpfiles.d/ drop-in file accordingly. And hangs. After 30min, I type <ctrl>+<c> --> ^C Trying to exit gracefully ... Nothing happens since 10min. Will waite some time and reboot afterwards. Ulf
Op donderdag 28 november 2024 21:28:10 Midden-Europese standaardtijd schreef GMX via openSUSE Factory:
Desktop switched to another tty and i could switch back. But update hangs and after ctrl + c shows Trying to exit gracefully .... . In detail:
"Script %posttrans(kernel-firmware-ath11k-20241125-1.1.noarch) wordt uitgevoerd ...........<8%> ^C Proberen netjes te eindigen... " Saw exactly the same.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team openSUSE Mods Team
For me it looked just like "TW20241125 Update Issue" happened again. Was thrown out to the tty when running zypper both times. Den tors 28 nov. 2024 kl 23:11 skrev Knurpht-openSUSE <knurpht@opensuse.org
:
Op donderdag 28 november 2024 21:28:10 Midden-Europese standaardtijd schreef GMX via openSUSE Factory:
Desktop switched to another tty and i could switch back. But update hangs and after ctrl + c shows Trying to exit gracefully .... . In detail:
"Script %posttrans(kernel-firmware-ath11k-20241125-1.1.noarch) wordt uitgevoerd ...........<8%> ^C Proberen netjes te eindigen... " Saw exactly the same.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team openSUSE Mods Team
On Fri, Nov 29, 2024 at 1:39 AM Ernst Persson <ernstp@gmail.com> wrote:
For me it looked just like "TW20241125 Update Issue" happened again.
Was thrown out to the tty when running zypper both times.
Same for me, exactly the same behavior. At least plymouth works now after reboot and there is no a 20-30secs delay.
On Fri, 2024-11-29 at 12:20 +0200, Stratos Zolotas wrote:
On Fri, Nov 29, 2024 at 1:39 AM Ernst Persson <ernstp@gmail.com> wrote:
For me it looked just like "TW20241125 Update Issue" happened again.
Was thrown out to the tty when running zypper both times.
Same for me, exactly the same behavior. At least plymouth works now after reboot and there is no a 20-30secs delay.
I forcefully halted ( kill -KILL ) the zypper process to convince it to stop. Follow-up actions: 1. clean the RPM DB lock rm /usr/lib/sysimage/rpm/.rpm.lock 2. rebuild the RPM DB rpmdb --rebuilddb 3. reinstall the kernel-firmware-packages to rerun the posttrans scriptlets zypper in -f $(zypper se -i kernel-firmware | awk '/kernel-firmware/ {print $3}')^ After a reboot all seems fine. I updated from a snapshot before 20241125. Hope this helps others, but YMMV - what worked for my system may not work for you. Thanks, Robert
Robert Munteanu <rombert@apache.org> writes:
I forcefully halted ( kill -KILL ) the zypper process to convince it to stop.
Follow-up actions:
That all sounds quite scary. I have no idea whether this works for everyone, but all I had to do was kill plymouthd to unstick the posttrans script and thereby zypper. I picked plymouthd after noticing it consistently active for about a minute while the posttrans script hung at 3%. HTH -- Eric Gillespie <*> epg@pretzelnet.org
participants (7)
-
Eric Gillespie -
Ernst Persson -
GMX -
Knurpht-openSUSE -
Robert Munteanu -
Stratos Zolotas -
Ulf