Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #245487 > unrolled thread
| Started by | Richmond <richmond@criptext.com> |
|---|---|
| First post | 2022-02-17 02:30 +0100 |
| Last post | 2022-02-17 15:30 +0100 |
| Articles | 10 — 3 participants |
Back to article view | Back to linux.debian.user
a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-02-17 02:30 +0100
Re: a stop job is running for user manager David Wright <deblis@lionunicorn.co.uk> - 2022-02-17 04:20 +0100
Re: a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-02-17 15:10 +0100
Re: a stop job is running for user manager David Wright <deblis@lionunicorn.co.uk> - 2022-02-18 02:30 +0100
Re: a stop job is running for user manager Махно <mindaugasceliesius@gmail.com> - 2022-02-18 14:10 +0100
Re: a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-02-18 22:40 +0100
Re: a stop job is running for user manager David Wright <deblis@lionunicorn.co.uk> - 2022-02-19 03:10 +0100
Re: a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-02-19 14:40 +0100
Re: a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-03-06 23:40 +0100
Re: a stop job is running for user manager Richmond <richmond@criptext.com> - 2022-02-17 15:30 +0100
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-02-17 02:30 +0100 |
| Subject | a stop job is running for user manager |
| Message-ID | <DRDMl-2jN1-7@gated-at.bofh.it> |
Since upgrading to Debian 11 I sometimes see "a stop job is running for user manager..." on shutdown and it waits 90 seconds. The last comment in this thread says "Installing systemd from backsports solved this issue." https://forums.debian.net/viewtopic.php?t=150080 I guess that means a backport from testing. Is that a good idea?
[toc] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-02-17 04:20 +0100 |
| Message-ID | <DRFuN-2kXM-1@gated-at.bofh.it> |
| In reply to | #245487 |
On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: > Since upgrading to Debian 11 I sometimes see "a stop job is running for > user manager..." on shutdown and it waits 90 seconds. The last comment > in this thread says "Installing systemd from backsports solved this issue." > > https://forums.debian.net/viewtopic.php?t=150080 > > I guess that means a backport from testing. Is that a good idea? No, it's not. testing: 250.3-2 BULLSEYE backports: 250.3-2~bpo11+1 The latter is lovingly crafted to suit your installed libraries. The former depends on bookworm/testing's libraries. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-02-17 15:10 +0100 |
| Message-ID | <DRPDP-2rjG-5@gated-at.bofh.it> |
| In reply to | #245488 |
David Wright <deblis@lionunicorn.co.uk> writes: > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved this issue." >> >> https://forums.debian.net/viewtopic.php?t=150080 >> >> I guess that means a backport from testing. Is that a good idea? > > No, it's not. > > testing: 250.3-2 > > BULLSEYE backports: 250.3-2~bpo11+1 > > The latter is lovingly crafted to suit your installed libraries. > The former depends on bookworm/testing's libraries. > Thanks, I see my mistake, I thought bullseye-backports meant backports from bullseye, but it means *to* bullseye. However when I tried it, apt says it will remove 92 packages which doesn't sound right to me. Is it supposed to do that? I had to include libsystemd0 for dependencies. sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. Need to get 5,167 kB of archives. After this operation, 383 MB disk space will be freed. Do you want to continue? [Y/n] n Abort.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-02-18 02:30 +0100 |
| Message-ID | <DS0fT-2xKA-3@gated-at.bofh.it> |
| In reply to | #245503 |
On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote:
> David Wright <deblis@lionunicorn.co.uk> writes:
> > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote:
> >> Since upgrading to Debian 11 I sometimes see "a stop job is running for
> >> user manager..." on shutdown and it waits 90 seconds. The last comment
> >> in this thread says "Installing systemd from backsports solved this issue."
> >>
> >> https://forums.debian.net/viewtopic.php?t=150080
> >>
> >> I guess that means a backport from testing. Is that a good idea?
> >
> > No, it's not.
> >
> > testing: 250.3-2
> >
> > BULLSEYE backports: 250.3-2~bpo11+1
> >
> > The latter is lovingly crafted to suit your installed libraries.
> > The former depends on bookworm/testing's libraries.
>
> Thanks, I see my mistake, I thought bullseye-backports meant backports
> from bullseye, but it means *to* bullseye. However when I tried it, apt
> says it will remove 92 packages which doesn't sound right to me. Is it
> supposed to do that? I had to include libsystemd0 for dependencies.
>
> sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports
>
> The following packages will be upgraded:
> libsystemd0 systemd
> 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded.
> Need to get 5,167 kB of archives.
> After this operation, 383 MB disk space will be freed.
> Do you want to continue? [Y/n] n
> Abort.
For me, the effect is very much smaller, and I don't think I'd miss
most of what it wants to remove. The difference may be because you run
a DE and I don't. (I've made no attempt to analyse the output below.)
The obvious alternative is either put up with the delay, or research
what might be causing it. There's a link near the top of the page you
referenced, with discussions that might help, though bear in mind that
shortening the timeout or hammering the three finger salute aren't solutions.
Perhaps backports isn't really a solution, either. There's no
explanation or justification given by ddebbb.
$ apt-get -s install systemd/bullseye-backports
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'systemd'
Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'libsystemd0' because of 'systemd'
The following packages were automatically installed and are no longer required:
colord-data gparted-common libcolorhug2 libgusb2 libjim0.79 libmbim-glib4 libmbim-proxy libpipewire-0.3-0
libpipewire-0.3-modules libqmi-glib5 libqmi-proxy libspa-0.2-modules pipewire pipewire-bin usb-modeswitch
usb-modeswitch-data xdg-desktop-portal
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
dbus-x11 libsystemd0
Suggested packages:
systemd-container libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0 policykit-1
Recommended packages:
systemd-timesyncd | time-daemon
The following packages will be REMOVED:
colord dbus-user-session gparted libnss-systemd libpam-systemd modemmanager policykit-1 systemd-timesyncd
xdg-desktop-portal-gtk
The following NEW packages will be installed:
dbus-x11
The following packages will be upgraded:
libsystemd0 systemd
2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded.
Remv colord [1.4.5-3]
Remv xdg-desktop-portal-gtk [1.8.0-1]
Remv dbus-user-session [1.12.20-2] [audacious:amd64 dconf-service:amd64 xdg-desktop-portal:amd64 ]
Inst dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64])
Remv gparted [1.2.0-1]
Remv libnss-systemd [247.3-6]
Remv modemmanager [1.14.12-0.2]
Remv policykit-1 [0.105-31+deb11u1]
Remv libpam-systemd [247.3-6]
Remv systemd-timesyncd [247.3-6] [systemd:amd64 ]
Inst systemd [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) []
Inst libsystemd0 [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64])
Conf libsystemd0 (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64])
Conf dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64])
Conf systemd (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64])
$
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | Махно <mindaugasceliesius@gmail.com> |
|---|---|
| Date | 2022-02-18 14:10 +0100 |
| Message-ID | <DSbbj-2F1p-1@gated-at.bofh.it> |
| In reply to | #245509 |
Hello! I would suggest that you report this issue to Debian BTS by using the reportbug program. Also, i think you should wait for a person, responsible for the maintenance of this package and wait for an answer. 2022-02-18, pn, 03:28 David Wright <deblis@lionunicorn.co.uk> rašė: > > On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote: > > David Wright <deblis@lionunicorn.co.uk> writes: > > > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: > > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for > > >> user manager..." on shutdown and it waits 90 seconds. The last comment > > >> in this thread says "Installing systemd from backsports solved this issue." > > >> > > >> https://forums.debian.net/viewtopic.php?t=150080 > > >> > > >> I guess that means a backport from testing. Is that a good idea? > > > > > > No, it's not. > > > > > > testing: 250.3-2 > > > > > > BULLSEYE backports: 250.3-2~bpo11+1 > > > > > > The latter is lovingly crafted to suit your installed libraries. > > > The former depends on bookworm/testing's libraries. > > > > Thanks, I see my mistake, I thought bullseye-backports meant backports > > from bullseye, but it means *to* bullseye. However when I tried it, apt > > says it will remove 92 packages which doesn't sound right to me. Is it > > supposed to do that? I had to include libsystemd0 for dependencies. > > > > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports > > > > The following packages will be upgraded: > > libsystemd0 systemd > > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. > > Need to get 5,167 kB of archives. > > After this operation, 383 MB disk space will be freed. > > Do you want to continue? [Y/n] n > > Abort. > > For me, the effect is very much smaller, and I don't think I'd miss > most of what it wants to remove. The difference may be because you run > a DE and I don't. (I've made no attempt to analyse the output below.) > > The obvious alternative is either put up with the delay, or research > what might be causing it. There's a link near the top of the page you > referenced, with discussions that might help, though bear in mind that > shortening the timeout or hammering the three finger salute aren't solutions. > > Perhaps backports isn't really a solution, either. There's no > explanation or justification given by ddebbb. > > $ apt-get -s install systemd/bullseye-backports > NOTE: This is only a simulation! > apt-get needs root privileges for real execution. > Keep also in mind that locking is deactivated, > so don't depend on the relevance to the real current situation! > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'systemd' > Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'libsystemd0' because of 'systemd' > The following packages were automatically installed and are no longer required: > colord-data gparted-common libcolorhug2 libgusb2 libjim0.79 libmbim-glib4 libmbim-proxy libpipewire-0.3-0 > libpipewire-0.3-modules libqmi-glib5 libqmi-proxy libspa-0.2-modules pipewire pipewire-bin usb-modeswitch > usb-modeswitch-data xdg-desktop-portal > Use 'apt autoremove' to remove them. > The following additional packages will be installed: > dbus-x11 libsystemd0 > Suggested packages: > systemd-container libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0 policykit-1 > Recommended packages: > systemd-timesyncd | time-daemon > The following packages will be REMOVED: > colord dbus-user-session gparted libnss-systemd libpam-systemd modemmanager policykit-1 systemd-timesyncd > xdg-desktop-portal-gtk > The following NEW packages will be installed: > dbus-x11 > The following packages will be upgraded: > libsystemd0 systemd > 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. > Remv colord [1.4.5-3] > Remv xdg-desktop-portal-gtk [1.8.0-1] > Remv dbus-user-session [1.12.20-2] [audacious:amd64 dconf-service:amd64 xdg-desktop-portal:amd64 ] > Inst dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64]) > Remv gparted [1.2.0-1] > Remv libnss-systemd [247.3-6] > Remv modemmanager [1.14.12-0.2] > Remv policykit-1 [0.105-31+deb11u1] > Remv libpam-systemd [247.3-6] > Remv systemd-timesyncd [247.3-6] [systemd:amd64 ] > Inst systemd [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) [] > Inst libsystemd0 [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) > Conf libsystemd0 (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) > Conf dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64]) > Conf systemd (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) > $ > > Cheers, > David. >
[toc] | [prev] | [next] | [standalone]
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-02-18 22:40 +0100 |
| Message-ID | <DSj8R-2JNi-5@gated-at.bofh.it> |
| In reply to | #245513 |
Махно <mindaugasceliesius@gmail.com> writes: > Hello! I would suggest that you report this issue to Debian BTS by > using the reportbug program. Also, i think you should wait for a > person, responsible for the maintenance of this package and wait for > an answer. Perhaps. Yesterday I found a site that suggested removing entries from ~/.config/autostart/ There were a few in there for applications I no longer have installed, so I removed them, and I am monitoring to see if I see the shutdown delay again. It maybe relates to a gnome bug which was not fixed in Mate. It is hard to tell from journalctl which error if any relates to the delay. > > 2022-02-18, pn, 03:28 David Wright <deblis@lionunicorn.co.uk> rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote: >> > David Wright <deblis@lionunicorn.co.uk> writes: >> > > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment >> > >> in this thread says "Installing systemd from backsports solved this issue." >> > >> >> > >> https://forums.debian.net/viewtopic.php?t=150080 >> > >> >> > >> I guess that means a backport from testing. Is that a good idea? >> > > >> > > No, it's not. >> > > >> > > testing: 250.3-2 >> > > >> > > BULLSEYE backports: 250.3-2~bpo11+1 >> > > >> > > The latter is lovingly crafted to suit your installed libraries. >> > > The former depends on bookworm/testing's libraries. >> > >> > Thanks, I see my mistake, I thought bullseye-backports meant backports >> > from bullseye, but it means *to* bullseye. However when I tried it, apt >> > says it will remove 92 packages which doesn't sound right to me. Is it >> > supposed to do that? I had to include libsystemd0 for dependencies. >> > >> > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports >> > >> > The following packages will be upgraded: >> > libsystemd0 systemd >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. >> > Need to get 5,167 kB of archives. >> > After this operation, 383 MB disk space will be freed. >> > Do you want to continue? [Y/n] n >> > Abort. >> >> For me, the effect is very much smaller, and I don't think I'd miss >> most of what it wants to remove. The difference may be because you run >> a DE and I don't. (I've made no attempt to analyse the output below.) >> >> The obvious alternative is either put up with the delay, or research >> what might be causing it. There's a link near the top of the page you >> referenced, with discussions that might help, though bear in mind that >> shortening the timeout or hammering the three finger salute aren't solutions. >> >> Perhaps backports isn't really a solution, either. There's no >> explanation or justification given by ddebbb. >> >> $ apt-get -s install systemd/bullseye-backports >> NOTE: This is only a simulation! >> apt-get needs root privileges for real execution. >> Keep also in mind that locking is deactivated, >> so don't depend on the relevance to the real current situation! >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'systemd' >> Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports [amd64]) for 'libsystemd0' because of 'systemd' >> The following packages were automatically installed and are no longer required: >> colord-data gparted-common libcolorhug2 libgusb2 libjim0.79 libmbim-glib4 libmbim-proxy libpipewire-0.3-0 >> libpipewire-0.3-modules libqmi-glib5 libqmi-proxy libspa-0.2-modules pipewire pipewire-bin usb-modeswitch >> usb-modeswitch-data xdg-desktop-portal >> Use 'apt autoremove' to remove them. >> The following additional packages will be installed: >> dbus-x11 libsystemd0 >> Suggested packages: >> systemd-container libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0 policykit-1 >> Recommended packages: >> systemd-timesyncd | time-daemon >> The following packages will be REMOVED: >> colord dbus-user-session gparted libnss-systemd libpam-systemd modemmanager policykit-1 systemd-timesyncd >> xdg-desktop-portal-gtk >> The following NEW packages will be installed: >> dbus-x11 >> The following packages will be upgraded: >> libsystemd0 systemd >> 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. >> Remv colord [1.4.5-3] >> Remv xdg-desktop-portal-gtk [1.8.0-1] >> Remv dbus-user-session [1.12.20-2] [audacious:amd64 dconf-service:amd64 xdg-desktop-portal:amd64 ] >> Inst dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64]) >> Remv gparted [1.2.0-1] >> Remv libnss-systemd [247.3-6] >> Remv modemmanager [1.14.12-0.2] >> Remv policykit-1 [0.105-31+deb11u1] >> Remv libpam-systemd [247.3-6] >> Remv systemd-timesyncd [247.3-6] [systemd:amd64 ] >> Inst systemd [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) [] >> Inst libsystemd0 [247.3-6] (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) >> Conf libsystemd0 (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) >> Conf dbus-x11 (1.12.20-2 Debian:11.2/stable [amd64]) >> Conf systemd (250.3-2~bpo11+1 Debian Backports:bullseye-backports [amd64]) >> $ >> >> Cheers, >> David. >>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-02-19 03:10 +0100 |
| Message-ID | <DSnm9-2MuM-1@gated-at.bofh.it> |
| In reply to | #245525 |
On Fri 18 Feb 2022 at 21:13:16 (+0000), Richmond wrote: > Махно <mindaugasceliesius@gmail.com> writes: > > 2022-02-18, pn, 03:28 David Wright rašė: > >> On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote: > >> > David Wright <deblis@lionunicorn.co.uk> writes: > >> > > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: > >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for > >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment > >> > >> in this thread says "Installing systemd from backsports solved this issue." > >> > >> > >> > >> https://forums.debian.net/viewtopic.php?t=150080 > >> > >> > >> > >> I guess that means a backport from testing. Is that a good idea? > >> > > > >> > > No, it's not. > >> > > > >> > > testing: 250.3-2 > >> > > > >> > > BULLSEYE backports: 250.3-2~bpo11+1 > >> > > > >> > > The latter is lovingly crafted to suit your installed libraries. > >> > > The former depends on bookworm/testing's libraries. > >> > > >> > Thanks, I see my mistake, I thought bullseye-backports meant backports > >> > from bullseye, but it means *to* bullseye. However when I tried it, apt > >> > says it will remove 92 packages which doesn't sound right to me. Is it > >> > supposed to do that? I had to include libsystemd0 for dependencies. > >> > > >> > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports > >> > > >> > The following packages will be upgraded: > >> > libsystemd0 systemd > >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. > >> > Need to get 5,167 kB of archives. > >> > After this operation, 383 MB disk space will be freed. > >> > Do you want to continue? [Y/n] n > >> > Abort. > >> > >> For me, the effect is very much smaller, and I don't think I'd miss > >> most of what it wants to remove. The difference may be because you run > >> a DE and I don't. (I've made no attempt to analyse the output below.) > >> > >> The obvious alternative is either put up with the delay, or research > >> what might be causing it. There's a link near the top of the page you > >> referenced, with discussions that might help, though bear in mind that > >> shortening the timeout or hammering the three finger salute aren't solutions. > >> > >> Perhaps backports isn't really a solution, either. There's no > >> explanation or justification given by ddebbb. > >> > >> $ apt-get -s install systemd/bullseye-backports > >> [ … ] > >> 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. > >> [ … ] > >> $ > > > Hello! I would suggest that you report this issue to Debian BTS by > > using the reportbug program. Also, i think you should wait for a > > person, responsible for the maintenance of this package and wait for > > an answer. > > Perhaps. Yesterday I found a site that suggested removing entries from > ~/.config/autostart/ > > There were a few in there for applications I no longer have installed, > so I removed them, and I am monitoring to see if I see the shutdown > delay again. It maybe relates to a gnome bug which was not fixed in > Mate. It is hard to tell from journalctl which error if any relates to > the delay. That seems like a step in the right direction. A quick question: do you logout before you shutdown or not? It might be possible to observe whether the delay is during logoff or shutdown. (It's not directly relevant, but when running bullseye in 512MB, it helps to kill the browser, terminate X, logout, and shutdown in turn, because the agressive parallelism of systemd works against you with such limited memory.) Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-02-19 14:40 +0100 |
| Message-ID | <DSy7T-2Tg4-1@gated-at.bofh.it> |
| In reply to | #245533 |
David Wright <deblis@lionunicorn.co.uk> writes: > On Fri 18 Feb 2022 at 21:13:16 (+0000), Richmond wrote: >> Махно <mindaugasceliesius@gmail.com> writes: >> > 2022-02-18, pn, 03:28 David Wright rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote: >> >> > David Wright <deblis@lionunicorn.co.uk> writes: >> >> > > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: >> >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment >> >> > >> in this thread says "Installing systemd from backsports solved this issue." >> >> > >> >> >> > >> https://forums.debian.net/viewtopic.php?t=150080 >> >> > >> >> >> > >> I guess that means a backport from testing. Is that a good idea? >> >> > > >> >> > > No, it's not. >> >> > > >> >> > > testing: 250.3-2 >> >> > > >> >> > > BULLSEYE backports: 250.3-2~bpo11+1 >> >> > > >> >> > > The latter is lovingly crafted to suit your installed libraries. >> >> > > The former depends on bookworm/testing's libraries. >> >> > >> >> > Thanks, I see my mistake, I thought bullseye-backports meant backports >> >> > from bullseye, but it means *to* bullseye. However when I tried it, apt >> >> > says it will remove 92 packages which doesn't sound right to me. Is it >> >> > supposed to do that? I had to include libsystemd0 for dependencies. >> >> > >> >> > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports >> >> > >> >> > The following packages will be upgraded: >> >> > libsystemd0 systemd >> >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. >> >> > Need to get 5,167 kB of archives. >> >> > After this operation, 383 MB disk space will be freed. >> >> > Do you want to continue? [Y/n] n >> >> > Abort. >> >> >> >> For me, the effect is very much smaller, and I don't think I'd miss >> >> most of what it wants to remove. The difference may be because you run >> >> a DE and I don't. (I've made no attempt to analyse the output below.) >> >> >> >> The obvious alternative is either put up with the delay, or research >> >> what might be causing it. There's a link near the top of the page you >> >> referenced, with discussions that might help, though bear in mind that >> >> shortening the timeout or hammering the three finger salute aren't solutions. >> >> >> >> Perhaps backports isn't really a solution, either. There's no >> >> explanation or justification given by ddebbb. >> >> >> >> $ apt-get -s install systemd/bullseye-backports >> >> [ … ] >> >> 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. >> >> [ … ] >> >> $ >> >> > Hello! I would suggest that you report this issue to Debian BTS by >> > using the reportbug program. Also, i think you should wait for a >> > person, responsible for the maintenance of this package and wait for >> > an answer. >> >> Perhaps. Yesterday I found a site that suggested removing entries from >> ~/.config/autostart/ >> >> There were a few in there for applications I no longer have installed, >> so I removed them, and I am monitoring to see if I see the shutdown >> delay again. It maybe relates to a gnome bug which was not fixed in >> Mate. It is hard to tell from journalctl which error if any relates to >> the delay. > > That seems like a step in the right direction. A quick question: > do you logout before you shutdown or not? It might be possible to > observe whether the delay is during logoff or shutdown. > > (It's not directly relevant, but when running bullseye in 512MB, > it helps to kill the browser, terminate X, logout, and shutdown > in turn, because the agressive parallelism of systemd works against > you with such limited memory.) > That autostart removal didn't work. So far this problem has occured only when shutting down an open session, although I don't think there necessarily needs to be any application open. Next I will try what you say (logoff) and see if there is any delay. Another option is to use startx rather than a display manager, although I think I may have tried that. Another option is to use a different, or no, desktop env. and try to close in by the process of elimination, Dr Watson.
[toc] | [prev] | [next] | [standalone]
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-03-06 23:40 +0100 |
| Message-ID | <DY7HH-6lKT-3@gated-at.bofh.it> |
| In reply to | #245552 |
Richmond <richmond@criptext.com> writes: > David Wright <deblis@lionunicorn.co.uk> writes: > >> On Fri 18 Feb 2022 at 21:13:16 (+0000), Richmond wrote: >>> Махно <mindaugasceliesius@gmail.com> writes: >>> > 2022-02-18, pn, 03:28 David Wright rašė: >>> >> On Thu 17 Feb 2022 at 13:44:46 (+0000), Richmond wrote: >>> >> > David Wright <deblis@lionunicorn.co.uk> writes: >>> >> > > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: >>> >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >>> >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment >>> >> > >> in this thread says "Installing systemd from backsports solved this issue." >>> >> > >> >>> >> > >> https://forums.debian.net/viewtopic.php?t=150080 >>> >> > >> >>> >> > >> I guess that means a backport from testing. Is that a good idea? >>> >> > > >>> >> > > No, it's not. >>> >> > > >>> >> > > testing: 250.3-2 >>> >> > > >>> >> > > BULLSEYE backports: 250.3-2~bpo11+1 >>> >> > > >>> >> > > The latter is lovingly crafted to suit your installed libraries. >>> >> > > The former depends on bookworm/testing's libraries. >>> >> > >>> >> > Thanks, I see my mistake, I thought bullseye-backports meant backports >>> >> > from bullseye, but it means *to* bullseye. However when I tried it, apt >>> >> > says it will remove 92 packages which doesn't sound right to me. Is it >>> >> > supposed to do that? I had to include libsystemd0 for dependencies. >>> >> > >>> >> > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports >>> >> > >>> >> > The following packages will be upgraded: >>> >> > libsystemd0 systemd >>> >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. >>> >> > Need to get 5,167 kB of archives. >>> >> > After this operation, 383 MB disk space will be freed. >>> >> > Do you want to continue? [Y/n] n >>> >> > Abort. >>> >> >>> >> For me, the effect is very much smaller, and I don't think I'd miss >>> >> most of what it wants to remove. The difference may be because you run >>> >> a DE and I don't. (I've made no attempt to analyse the output below.) >>> >> >>> >> The obvious alternative is either put up with the delay, or research >>> >> what might be causing it. There's a link near the top of the page you >>> >> referenced, with discussions that might help, though bear in mind that >>> >> shortening the timeout or hammering the three finger salute aren't solutions. >>> >> >>> >> Perhaps backports isn't really a solution, either. There's no >>> >> explanation or justification given by ddebbb. >>> >> >>> >> $ apt-get -s install systemd/bullseye-backports >>> >> [ … ] >>> >> 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. >>> >> [ … ] >>> >> $ >>> >>> > Hello! I would suggest that you report this issue to Debian BTS by >>> > using the reportbug program. Also, i think you should wait for a >>> > person, responsible for the maintenance of this package and wait for >>> > an answer. >>> >>> Perhaps. Yesterday I found a site that suggested removing entries from >>> ~/.config/autostart/ >>> >>> There were a few in there for applications I no longer have installed, >>> so I removed them, and I am monitoring to see if I see the shutdown >>> delay again. It maybe relates to a gnome bug which was not fixed in >>> Mate. It is hard to tell from journalctl which error if any relates to >>> the delay. >> >> That seems like a step in the right direction. A quick question: >> do you logout before you shutdown or not? It might be possible to >> observe whether the delay is during logoff or shutdown. >> >> (It's not directly relevant, but when running bullseye in 512MB, >> it helps to kill the browser, terminate X, logout, and shutdown >> in turn, because the agressive parallelism of systemd works against >> you with such limited memory.) >> > > That autostart removal didn't work. > > So far this problem has occured only when shutting down an open session, > although I don't think there necessarily needs to be any application > open. > > Next I will try what you say (logoff) and see if there is any > delay. Another option is to use startx rather than a display manager, > although I think I may have tried that. Another option is to use a > different, or no, desktop env. and try to close in by the process of > elimination, Dr Watson. For some time I used the procedure: log off Mate, then shut down from the display manager. I didn't get any delays. Then for some time I used icewm manager without any desktop environment and didn't get any delay in shutdown, even if I shutdown by pressing the power button without logout. I think the bug is somewhere in Mate therefore. Maybe it is caused by the ufw - uncomplicated firewall, as someone reported it causing problems at startup.
[toc] | [prev] | [next] | [standalone]
| From | Richmond <richmond@criptext.com> |
|---|---|
| Date | 2022-02-17 15:30 +0100 |
| Message-ID | <DRPXb-2rpP-1@gated-at.bofh.it> |
| In reply to | #245488 |
David Wright <deblis@lionunicorn.co.uk> writes: > On Thu 17 Feb 2022 at 01:00:30 (+0000), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved this issue." >> >> https://forums.debian.net/viewtopic.php?t=150080 >> >> I guess that means a backport from testing. Is that a good idea? > > No, it's not. > > testing: 250.3-2 > > BULLSEYE backports: 250.3-2~bpo11+1 > > The latter is lovingly crafted to suit your installed libraries. > The former depends on bookworm/testing's libraries. > > Cheers, > David. Here are the packages it says it wants to remove. Note: mate-desktop-environment: The following packages will be REMOVED: baloo-kf5 dbus-user-session dolphin gnome-software gstreamer1.0-plugins-good:i386 gufw kaccounts-providers kactivitymanagerd kde-cli-tools kdeconnect keditbookmarks kinit kio kio-extras kpackagelauncherqml libasound2-plugins:i386 libavahi-client3:i386 libcups2:i386 libdbus-1-3:i386 libfaudio0:i386 libkf5auth-dev libkf5auth5 libkf5authcore5 libkf5baloowidgets-bin libkf5baloowidgets5 libkf5bookmarks-dev libkf5bookmarks5 libkf5configwidgets-dev libkf5configwidgets5 libkf5declarative5 libkf5iconthemes-bin libkf5iconthemes-dev libkf5iconthemes5 libkf5kcmutils-dev libkf5kcmutils5 libkf5kio-dev libkf5kiocore5 libkf5kiofilewidgets5 libkf5kiogui5 libkf5kiowidgets5 libkf5newstuff5 libkf5newstuffcore5 libkf5notifyconfig-dev libkf5notifyconfig5 libkf5parts-plugins libkf5parts5 libkf5plasma5 libkf5plasmaquick5 libkf5purpose-bin libkf5purpose-dev libkf5purpose5 libkf5quickaddons5 libkf5textwidgets5 libkf5wallet-bin libkf5xmlgui-dev libkf5xmlgui5 libnss-systemd libpam-systemd libpcap0.8:i386 libpolkit-qt5-1-1 libpulse0:i386 libsane1:i386 libsdl2-2.0-0:i386 libsystemd0:i386 libwine:i386 lightdm mate-applet-brisk-menu mate-applets mate-control-center mate-desktop-environment mate-desktop-environment-core mate-panel mate-polkit mate-power-manager mate-settings-daemon modemmanager network-manager network-manager-gnome packagekit packagekit-tools plasma-framework policykit-1 qml-module-org-kde-kconfig qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-newstuff qml-module-org-kde-purpose rtkit synaptic systemd-timesyncd task-mate-desktop wine32:i386
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web