Devuan bug report logs -
#540
slim fails to get logind session if logout/login cycle is rapid
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your bug report
which was filed against the slim package:
#540: slim fails to get logind session if logout/login cycle is rapid
It has been closed by dak@devuan.org.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact dak@devuan.org by
replying to this email.
--
540: https://bugs.devuan.org/cgi/bugreport.cgi?bug=540
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
Version: 1.3.6-5.2+devuan1
Source package slim (1.3.6-5.2+devuan1) added to Devuan suite unstable.
This closes bug report 540.
Thanks
DAK managing the Devuan archive
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 21 Jan 2021 15:45:24 +0000
Source: slim
Architecture: source
Version: 1.3.6-5.2+devuan1
Distribution: unstable
Urgency: medium
Maintainer: Devuan Dev Team <devuan-dev@lists.dyne.org>
Changed-By: Mark Hindley <mark@hindley.org.uk>
Closes: 540
Changes:
slim (1.3.6-5.2+devuan1) unstable; urgency=medium
.
* Set slim PAM session as class greeter. This ensures sessions
are closed promptly on logout and we always get a session on
a rapid logout/login cycle (Closes: #540).
* Merge changes from debian 1.3.6-5.2 NMU.
* d/control: add Origin: Devuan
* d/control: update Vcs-* following Gitea migration.
Checksums-Sha1:
27cfbd8b51acec941688a682088571d13d3fded5 1820 slim_1.3.6-5.2+devuan1.dsc
1ac15bb91d18a6411e6561b5c1bd27268e1a1b55 34920 slim_1.3.6-5.2+devuan1.debian.tar.xz
871d2441196a63c99c3c8005e9df9f05168c8d8e 5140 slim_1.3.6-5.2+devuan1_source.buildinfo
Checksums-Sha256:
61219a1f733a8e8a2f68eda91018ecf8d5157b297de611c71b1b18d7054fe87e 1820 slim_1.3.6-5.2+devuan1.dsc
40bb4c9e245f8ed4d74812d8ea40dc13f909d97b0676d8723ac93a12e65d1ae4 34920 slim_1.3.6-5.2+devuan1.debian.tar.xz
0aebdf10f207f95702fb5837fa12749021b2316a4bfc6d70e3df1f4e69de0592 5140 slim_1.3.6-5.2+devuan1_source.buildinfo
Files:
0303aae3315c0bacfbb9acce3e161014 1820 x11 optional slim_1.3.6-5.2+devuan1.dsc
5882ad896f73c8e4563aeef8f78edba4 34920 x11 optional slim_1.3.6-5.2+devuan1.debian.tar.xz
424f2ff1f49888df6e323c141d18aa2f 5140 x11 optional slim_1.3.6-5.2+devuan1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEcuPLdzMV36LkZHQ9lFMhJFQZIvsFAmAJsF4ACgkQlFMhJFQZ
Ivt15AgAjbP9z+Jzh7NCsd9sK5bxnSvinjw60Fwu4zuLI6kUAxSf9lu227kVv5+O
NKtctWFWIqxRivQbEm3fCrOg8jOIDeyC9hKyTuq5udvtfbZ85fV8iFcgvV9dXK//
DDTN9ihQM/D8iZ3GX0fCCRYlSAEHFVOiv5e9mO6v42GNwGllf9nGA8VfW7vudf0R
QSR0UyjvJ8KW6UyXzthYGmLFSuV8+9CCBh97ulIIKM/i4d0VybSwPXzX046aGeuK
/cWweBh1U16vm37Pfe94Z4q+U9bSvMVTUReAfYSqkzgny8zSt9cHtoXpVtaEN4Gs
OMtd6exc6bompQrnMdhuNyj5LDut+Q==
=b6Iq
-----END PGP SIGNATURE-----
[Message part 3 (message/rfc822, inline)]
Package: elogind
Version: 241.4-2
elogind unmounts /run/user/$UID tmpfs filesystem after logging in again.
It should not do that.
Devuan was installed using the Refracta installer that is available on
the iso-file devuan_beowulf_3.0.0_amd64_desktop-live.iso.
Unable to reproduce the issue in a VM booted of iso-file
devuan_beowulf_3.0.0_i386_desktop-live.iso /
devuan_beowulf_3.0.0_amd64_desktop-live.iso.
Steps to reproduce (new install, new user, default settings):
1) login to the XFCE desktop environment.
2) in a terminal window, exec df. This shows, amongst others, a tmpfs
filesystem mounted at /run/user/$UID.
3) log out and log back in (rapidly).
4) in a terminal window, exec watch df. This shows, amongst others, the
same tmpfs filesystem mounted at /run/user/$UID.
5) wait and watch closely.
6) df no longer shows the tmpfs filesystem mounted at /run/user/$UID, it
was unmounted by elogind even though the user is still logged in.
Workaround: at "UserStopDelaySec=infinity" to section [Login] in config
file /etc/elogind/logind.conf. The tmpfs mounted at /run/user/$UID will
remain available until system reboot.
Workaround: after logout, wait for the tmpfs mounted at /run/user/$UID
to be unmounted.
Send a report that this bug log contains spam.