Bug#762041: systemd: upgrading systemd results in /run/user/<uid> being emptied

[Michael Biebl]

Am 18.09.2014 um 21:22 schrieb Sven Joachim:
> On 2014-09-18 16:10 +0200, Uoti Urpala wrote:
> 
>> I checked that this did not happen on a system I just updated from 204
>> to 215; contents of /run/user/1000 remained unchanged after the upgrade.
> 
> Not here, upgrading from 208 to 215.
> 
>> Are you sure that the upgrade actually *removed* contents? A possibly
>> relevant change is that logind started to mount a per-user tmpfs
>> in /run/user/* (for per-user size limits). If something on your system
>> triggered a mount of a new tmpfs over the existing directory, that could
>> give similar symptoms.
> 
> This is exactly what I observe: before the upgrade /run/user was mounted
> on a tmpfs, after the upgrade another tmpfs appeared mounted on
> /run/user/1000, shadowing the files on /run/user.  Unmounting that new
> tmpfs brought the old files back to light.

I suspect what happened is, that you had a running (desktop) session,
which was started while still using logind v208.

You then logged in a second time after the upgrade to v215 (e.g. on the
console), while not logging out of your first session.

The start of the second (logind) session using v215 is causing the
per-user tmpfs to be mounted interfering with the state of the first
logind session.

Is this observation correct?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140921/a0996fba/attachment-0002.sig>