• apt running on crashed gnome-terminal

    From Enrico Zini@21:1/5 to All on Sun Dec 29 18:30:01 2024
    Hello,

    today I decided to upgrade from bookworm to trixie/testing[1][2]. I ran
    the upgrade in a gnome-terminal, and of course all gnome terminals in
    the system crashed halfway through the upgrade[1][3].

    Unexpectedly, apt and dpkg kept doing their thing in their own headless wonderland. I tried to track progress via top and pstree, killed a
    couple of whiptail processes[4], and eventually decided to kill apt and
    restart things from a new terminal.

    I'm not sure how to start reporting bugs here. gnome-terminal should
    clearly not have crashed (and I do not know why it did, and I'm not sure
    I want to go through all the trouble to setup a bullworm[2] VM with
    gnome and upgrade it to trixie to see if it crashed again.

    At the same time, it was surprising that apt and dpkg continued unfazed
    after the terminal died. That may be easier to reproduce: start doing
    something with apt and kill gnome-terminal. I still need a bookseye[2]
    VM with gnome to try that out, and I have an annoying cold, so it's not something I'd embark on right this afternoon[5].

    Not sure there's much more to be done here, given the complexity of the
    whole stack, and especially if this affected just me just this once. If
    it doesn't, this mail can act a friendly "hey, it wasn't just you" for a
    fellow traveler.

    Trixie otherwise just works, and thank us all for it! <3


    Enrico

    [1] One reason was to see if gnome is less infuriating[3]
    [2] One reason was to finally get out of release names starting with
    'b', which have been confusing the hell out of me for half of a
    decade
    [3] Spoiler warning: not particularly
    [4] Likely warnings that this or that go or rust program or qt chromium
    embedding monster cannot be supported by the Security Team, for
    which I have heartfelt support and which however stopped the
    upgrade flow at least 5 times
    [5] Do we have a thing that clones the running system into a throwaway
    VM?
    --
    GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mo Zhou@21:1/5 to Enrico Zini on Sun Dec 29 19:40:02 2024
    Hi Enrico,

    Dist upgrade is something I'd prefer to do in a terminal muxer, e.g.,
    tmux, screen, zellij, or wrappers like byobu. Even if the whole
    desktop environment crashed during the upgrade, you can still check
    the status in tty without losing the process handling the stdout/err
    of apt.

    I think apt/dpkg are well-designed to be failure/fault-proof. In my
    memory I did lots of reboot/poweroff during apt upgrade since forgotten. Powerloss is also safe in my experience, which is also discussed in the
    dpkg fsync() on -devel concurrently.

    Back to gnome crash -- I did not encounter desktop crash during the
    past 6 years of using Debian Sid as daily drive. Maybe there is
    something wrong in detecting which service (like gdm) needs a restart?


    On 12/29/24 12:20, Enrico Zini wrote:
    Hello,

    today I decided to upgrade from bookworm to trixie/testing[1][2]. I ran
    the upgrade in a gnome-terminal, and of course all gnome terminals in
    the system crashed halfway through the upgrade[1][3].

    Unexpectedly, apt and dpkg kept doing their thing in their own headless wonderland. I tried to track progress via top and pstree, killed a
    couple of whiptail processes[4], and eventually decided to kill apt and restart things from a new terminal.

    I'm not sure how to start reporting bugs here. gnome-terminal should
    clearly not have crashed (and I do not know why it did, and I'm not sure
    I want to go through all the trouble to setup a bullworm[2] VM with
    gnome and upgrade it to trixie to see if it crashed again.

    At the same time, it was surprising that apt and dpkg continued unfazed
    after the terminal died. That may be easier to reproduce: start doing something with apt and kill gnome-terminal. I still need a bookseye[2]
    VM with gnome to try that out, and I have an annoying cold, so it's not something I'd embark on right this afternoon[5].

    Not sure there's much more to be done here, given the complexity of the
    whole stack, and especially if this affected just me just this once. If
    it doesn't, this mail can act a friendly "hey, it wasn't just you" for a fellow traveler.

    Trixie otherwise just works, and thank us all for it! <3


    Enrico

    [1] One reason was to see if gnome is less infuriating[3]
    [2] One reason was to finally get out of release names starting with
    'b', which have been confusing the hell out of me for half of a
    decade
    [3] Spoiler warning: not particularly
    [4] Likely warnings that this or that go or rust program or qt chromium
    embedding monster cannot be supported by the Security Team, for
    which I have heartfelt support and which however stopped the
    upgrade flow at least 5 times
    [5] Do we have a thing that clones the running system into a throwaway
    VM?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Lewis@21:1/5 to Enrico Zini on Sun Dec 29 20:50:01 2024
    Enrico Zini <enrico@enricozini.org> writes:

    today I decided to upgrade from bookworm to trixie/testing[1][2]. I ran
    the upgrade in a gnome-terminal, and of course all gnome terminals in
    the system crashed halfway through the upgrade[1][3].

    not much consolation, but: i supose this is why the release-notes
    recommend upgrading inside screen (see also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035401)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?utf-8?Q?Hakan_Bay=C4=B1nd=C4=B1r?@21:1/5 to All on Sun Dec 29 22:40:01 2024
    On 29 Dec 2024, at 20:20, Enrico Zini <enrico@enricozini.org> wrote:

    Hello,

    Hi,


    today I decided to upgrade from bookworm to trixie/testing[1][2]. I ran
    the upgrade in a gnome-terminal, and of course all gnome terminals in
    the system crashed halfway through the upgrade[1][3].

    This is strange. I’m not a GNOME user myself, but in the KDE land, Konsole (or any other app) never crashed during between similar large dist-upgrades.


    Unexpectedly, apt and dpkg kept doing their thing in their own headless wonderland. I tried to track progress via top and pstree, killed a
    couple of whiptail processes[4], and eventually decided to kill apt and restart things from a new terminal.

    I'm not sure how to start reporting bugs here. gnome-terminal should
    clearly not have crashed (and I do not know why it did, and I'm not sure
    I want to go through all the trouble to setup a bullworm[2] VM with
    gnome and upgrade it to trixie to see if it crashed again.

    From my perspective, the GNOME terminal shouldn’t behave like that. Probably recreating the crash and debugging it, and solving is eventually is the key. apt did what it was designed to do, and did it well, apparently.


    At the same time, it was surprising that apt and dpkg continued unfazed
    after the terminal died. That may be easier to reproduce: start doing something with apt and kill gnome-terminal. I still need a bookseye[2]
    VM with gnome to try that out, and I have an annoying cold, so it's not something I'd embark on right this afternoon[5].

    apt has some superpowers which allows it to continue when the terminal it has been reporting to disappears. This allows safe upgrades over flaky SSH sessions. The best practice is to run a terminal multiplexer before these long and big operations, but
    apt is more resilient than it looks.


    Not sure there's much more to be done here, given the complexity of the
    whole stack, and especially if this affected just me just this once. If
    it doesn't, this mail can act a friendly "hey, it wasn't just you" for a fellow traveler.

    Trixie otherwise just works, and thank us all for it! <3


    Trixie is already in a pretty good shape from my experience, yes, and thanks everyone for it, too.

    Have a nice year,

    Hakan


    Enrico

    [1] One reason was to see if gnome is less infuriating[3]
    [2] One reason was to finally get out of release names starting with
    'b', which have been confusing the hell out of me for half of a
    decade
    [3] Spoiler warning: not particularly
    [4] Likely warnings that this or that go or rust program or qt chromium
    embedding monster cannot be supported by the Security Team, for
    which I have heartfelt support and which however stopped the
    upgrade flow at least 5 times
    [5] Do we have a thing that clones the running system into a throwaway
    VM?
    --
    GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Lewis@21:1/5 to Enrico Zini on Sun Dec 29 23:10:01 2024
    Enrico Zini <enrico@enricozini.org> writes:

    [5] Do we have a thing that clones the running system into a throwaway
    VM?

    systemd-nspawn claims to support this -- https://0pointer.net/blog/running-an-container-off-the-host-usr.html

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jochen Sprickerhof@21:1/5 to All on Sun Dec 29 23:40:01 2024
    Hi Enrico,

    * Enrico Zini <enrico@enricozini.org> [2024-12-29 18:20]:
    Unexpectedly, apt and dpkg kept doing their thing in their own headless >wonderland. I tried to track progress via top and pstree, killed a
    couple of whiptail processes[4], and eventually decided to kill apt and >restart things from a new terminal.

    You could also just do:

    tail -f /var/log/apt/term.log

    Cheers Jochen

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmdxz20ACgkQW//cwljm lDP6KA//fkOjojVgACj77jFxeuYkulLFGqsb8bmRf4EZzNK0FhCUm+UG/ZzO7EHh EL56WFQAm4Qa0bNFuZiCqYL6gYqRkkOwfQcDnH3d4aoBjVGJuwlQdDE7P+dbHPZF SWWb0k3u5i8q5cOMQfXI7hWSBbgvDKXyCiQ9O0irbwIzgYKVoSAUeEZqE8KCgg+0 zWkjXQZaU/XG1ha8AI46fIs2ju/GdAGDcD+PP2RgTHiukC9zXBxmn5Wpr4+u6bVs yDLaCBXFrThpH23pdyfdSFNhaoPOGelHwUrLlGtiqpPJGqGXuTVpxAhwCWQS8gI5 SPt0wpcguLINaZKlhv1/jn2oFn6wiWOeJC1dxQ8lvlgyra1WIIEN1Ayf2O3/5A0B hRFb3csW3akdvNl0zQ0HfNDFqnjI6VV+Fr8kGeh6jwzvPCCDAYWb8lP/Z0FaUvHZ 7s9+8USfHQ//1Iw6HJRyBE8uqNZV20pQknMiQ7SVGE3ekbI9t4c3XqThLsVQIIHN XaZtBKBdBea1ZyGvvO7CGrPMWLPHuqrn8WttN+6iT9cqsd6lFieVVlWnawWdHVuN LPz+LKoReVe8Sfwg228UMMNPjFxgh34Eqwk2GdymRa6QSNgl35akW7hApA0Ahx2A kV1NFwfXnGx0932TjplPp2JUnEqDef0U8Epm0jX+NUEJQ86AHVo=
    =OJWu
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Noah Meyerhans@21:1/5 to Richard Lewis on Mon Dec 30 01:30:01 2024
    On Sun, Dec 29, 2024 at 07:43:23PM +0000, Richard Lewis wrote:
    today I decided to upgrade from bookworm to trixie/testing[1][2]. I ran
    the upgrade in a gnome-terminal, and of course all gnome terminals in
    the system crashed halfway through the upgrade[1][3].

    not much consolation, but: i supose this is why the release-notes
    recommend upgrading inside screen (see also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035401)

    Yes, but the discussion in #1035401 and the corresponding MR shows that
    this has limits as well.

    IMO, an upgrade between releases should happen with as few layers of
    software involved as possible. Local tty login or serial console is
    ideal. This is, of course, not always feasible.

    noah

    1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035401
    2. https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/213

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tzafrir Cohen@21:1/5 to Enrico Zini on Mon Dec 30 09:00:01 2024
    Hi,

    On Sun, Dec 29, 2024 at 06:20:11PM +0100, Enrico Zini wrote:

    At the same time, it was surprising that apt and dpkg continued unfazed
    after the terminal died. That may be easier to reproduce: start doing something with apt and kill gnome-terminal. I still need a bookseye[2]
    VM with gnome to try that out, and I have an annoying cold, so it's not something I'd embark on right this afternoon[5].

    Not that you can install it with an apt install running, but reptyr
    helped me recover somewhat similar issues and seems to be a tool worth
    having installed. I had not had a chance to try using it to recover an
    apt install.

    --
    mail / xmpp / matrix: tzafrir@cohens.org.il

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)