Bug#1062468: systemd: After dist-upgrade from buster, logout did not work
Bud Heal
budheal508 at gmail.com
Thu Feb 1 16:11:04 GMT 2024
Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: budheal508 at gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Libreoffice was crashing on MS Word (.docx) files so I decided to
upgrade
* What exactly did you do (or not do) that was effective (or
ineffective)?
The dist-upgrade went smoothly. I found the same Libreoffice problem before reboot. So, see if rebooting helps.
This system logs itself into one userid. Then I log it off and logs into
the userid I usually use. The logout failed, returning to the initial
user's desktop.
There is a switch user button. That worked. Libreoffice, not so much.
Reboot (from the System menu "Shut Down" and the Restart button), not at
all.
I didn't try anything in the shell. I was able to log out, where I was
back in the initial user's desktop.
I had a USB drive inserted. When I switched users I could not access the
USB drive. All I got was, pending mount. No eject widget, use the menu,
pull out, push back in, no help. That's when I decided to try to
restart.
Back on the initial user's desktop, I think 3 sets of dialogs telling me
all about the problems with the USB drive. The messages were not
descriptive. I could have said, Dave, I can't do that but if you only
reboot one more then system("Trust Me")d might start working again.
This looks like the kind of bug that you fix now or some later time
things might snowball. Or, since I occasionally have to correct
permissions, this shows what is starting to snowball into.
* What was the outcome of this action?
The UI error only occurred on the first (re)boot after dist-upgrade.
After another reboot, two USB drives (one inserted after switching
users) show both residing in the second (and current) user's
/media/(user) folder and nothing in the first's.
As for Libreoffice, I had to install the latest binaries.
* What outcome did you expect instead?
It is almost okay to work on the second try, but working seamlessly on
the first try would be better.
-- Package-specific info:
-- System Information:
Debian Release: 11.8
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-27-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118+deb11u1
ii libacl1 2.2.53-10
ii libapparmor1 2.13.6-10
ii libaudit1 1:3.0-2
ii libblkid1 2.36.1-8+deb11u1
ii libc6 2.31-13+deb11u7
ii libcap2 1:2.44-1
ii libcrypt1 1:4.4.18-4
ii libcryptsetup12 2:2.3.7-1+deb11u1
ii libgcrypt20 1.8.7-6
ii libgnutls30 3.7.1-5+deb11u3
ii libgpg-error0 1.38-2
ii libip4tc2 1.8.7-1
ii libkmod2 28-1
ii liblz4-1 1.9.3-2
ii liblzma5 5.2.5-2.1~deb11u1
ii libmount1 2.36.1-8+deb11u1
ii libpam0g 1.4.0-9+deb11u1
ii libseccomp2 2.5.1-1+deb11u1
ii libselinux1 3.1-3
ii libsystemd0 247.3-7+deb11u4
ii libzstd1 1.4.8+dfsg-2.1
ii mount 2.36.1-8+deb11u1
ii util-linux 2.36.1-8+deb11u1
Versions of packages systemd recommends:
ii dbus 1.12.28-0+deb11u1
ii ntp [time-daemon] 1:4.2.8p15+dfsg-1
Versions of packages systemd suggests:
ii policykit-1 0.105-31+deb11u1
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.140
ii libnss-systemd 247.3-7+deb11u4
ii libpam-systemd 247.3-7+deb11u4
ii udev 247.3-7+deb11u4
-- no debconf information
More information about the Pkg-systemd-maintainers
mailing list