• Bug#1110221: release-notes: Desktop restarts during upgrade

    From Guillermo Torres Zamora@21:1/5 to All on Fri Aug 1 14:10:01 2025
    XPost: linux.debian.doc

    Package: release-notes
    Severity: minor
    X-Debbugs-Cc: [email protected]

    Dear Maintainer,

    * What led up to the situation?
    I wanted to upgrade to Trixie.
    * What exactly did you do (or not do) that was effective (or
    ineffective)?
    I run apt upgrade --without-new-pkgs
    * What was the outcome of this action?
    The desktop restarted at the end closing everything but I was not warned in the release notes only in the terminal itself
    * What outcome did you expect instead?
    Probably the same but with a warning in the release notes

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Lewis@21:1/5 to [email protected] on Sat Aug 2 16:10:01 2025
    XPost: linux.debian.doc

    On Fri, 1 Aug 2025, 16:31 Guillermo Torres Zamora, < [email protected]> wrote:

    On Fri, 1 Aug 2025 13:51:36 +0100 Justin B Rye
    <[email protected]> wrote:
    Guillermo Torres Zamora wrote:

    This can be triggered if you specifically tell needrestart to restart processes that are usually left un-restarted, but the package
    needrestart probably isn't even installed on your machine.



    Cinnamon desktop on Xorg and I do have install needrestart, which I
    forgot about, so it's probably that.


    should the release-notes tell people to do something to needrestart to
    prevent this happening? or is this a bug in needsrestart?

    <div dir="auto"><div><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 1 Aug 2025, 16:31 Guillermo Torres Zamora, &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<
    </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 1 Aug 2025 13:51:36 +0100 Justin B Rye <br>
    &lt;<a href="mailto:[email protected]" target="_blank" rel="noreferrer">[email protected]</a>&gt; wrote:<br>
     &gt; Guillermo Torres Zamora wrote:<br>  <br>
     &gt; This can be triggered if you specifically tell needrestart to restart<br>
     &gt; processes that are usually left un-restarted, but the package<br>
     &gt; needrestart probably isn&#39;t even installed on your machine.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="
    margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Cinnamon desktop on Xorg and I do have install needrestart, which I <br>
    forgot about, so it&#39;s probably that.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">should the release-notes tell people to do something to needrestart to prevent this happening?  or is this a bug in needsrestart?</div><div
    dir="auto"><br></div><div dir="auto"><br></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to Richard Lewis on Sat Aug 2 17:20:01 2025
    XPost: linux.debian.doc

    On Sat, Aug 02, 2025 at 02:58:19PM +0100, Richard Lewis wrote:
    On Fri, 1 Aug 2025, 16:31 Guillermo Torres Zamora, < [email protected]> wrote:

    On Fri, 1 Aug 2025 13:51:36 +0100 Justin B Rye
    <[email protected]> wrote:
    Guillermo Torres Zamora wrote:

    This can be triggered if you specifically tell needrestart to restart processes that are usually left un-restarted, but the package needrestart probably isn't even installed on your machine.



    Cinnamon desktop on Xorg and I do have install needrestart, which I
    forgot about, so it's probably that.


    should the release-notes tell people to do something to needrestart to prevent this happening? or is this a bug in needsrestart?

    needrestart in the default config prompts what should be restarted.
    I doubt intended behaviour of needrestart qualifies as a bug, and
    it's users need to remember they have it.

    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Holger Wansing@21:1/5 to All on Sat Aug 2 18:10:01 2025
    XPost: linux.debian.doc

    Hi,

    Am 2. August 2025 17:14:52 MESZ schrieb Chris Hofstaedtler <[email protected]>: >On Sat, Aug 02, 2025 at 02:58:19PM +0100, Richard Lewis wrote:
    On Fri, 1 Aug 2025, 16:31 Guillermo Torres Zamora, <
    [email protected]> wrote:

    On Fri, 1 Aug 2025 13:51:36 +0100 Justin B Rye
    <[email protected]> wrote:
    Guillermo Torres Zamora wrote:

    This can be triggered if you specifically tell needrestart to restart >> > > processes that are usually left un-restarted, but the package
    needrestart probably isn't even installed on your machine.



    Cinnamon desktop on Xorg and I do have install needrestart, which I
    forgot about, so it's probably that.


    should the release-notes tell people to do something to needrestart to
    prevent this happening? or is this a bug in needsrestart?

    needrestart in the default config prompts what should be restarted.
    I doubt intended behaviour of needrestart qualifies as a bug, and
    it's users need to remember they have it.

    At some time we had the recommendation, to start the upgrade from virtual console, not from X.
    Maybe we need that to come back ....

    I personally still do it like this.


    Holger



    --
    Sent from /e/ OS on Fairphone3

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Holger Wansing@21:1/5 to All on Sun Aug 3 09:40:02 2025
    XPost: linux.debian.doc

    Hi Justin,

    Am 3. August 2025 09:23:23 MESZ schrieb Justin B Rye <[email protected]>:
    Holger Wansing wrote:
    needrestart in the default config prompts what should be restarted.
    I doubt intended behaviour of needrestart qualifies as a bug, and
    it's users need to remember they have it.

    At some time we had the recommendation, to start the upgrade from virtual console, not from X.
    Maybe we need that to come back ....

    I personally still do it like this.

    Unfortunately if this was GNOME's killing-spree mode, being logged in >"outside" the graphical session wouldn't help, because these days with >desktop environment processes running as a big mess of independent
    services instead of all being children of a window manager, logind
    doesn't try to distinguish. Under at least some circumstances (one of
    them being if the option KillUserProcesses is set to "Yes", which has
    at times been the upstream default), restarting GNOME sprays userspace
    with kill signals to ensure no VT logins or cronjobs or detached tmux >sessions survive.

    Wow, this is getting way to complicated for me.
    I'm out here...

    Holger

    --
    Sent from /e/ OS on Fairphone3

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