Bug 1399425

Summary:	systemd + dconf combine to wipe out dconf database when used with pam_mount
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	dconf	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	mclasen, rhughes
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:11:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bill Nottingham 2016-11-29 04:12:58 UTC

Description of problem:

I am using pam_mount to mount an encrypted home directory when I log in.

The bug comes from the following steps:

1. Log in when pam_mount is not working right (thanks SELinux + F25 update eating pam configuration files)
2. Encrypted homedir fails to mount
3. Session starts with whatever happens to be in underlying unencrypted homedir
4. Including some random really old dconf database
5. <unfuck your pam_mount configuration here>
5. Log out of session
6. systemd --user session is *NOT* killed
7. ... which means old dconf daemon is still running
8. Log in again
9. pam_mount mounts encrypted homedir
10. existing (?) dconf daemon writes dconf database from (4) to the newly-mounted homedir, overwriting existing settings
11. user gets very angry

Version-Release number of selected component (if applicable):

systemd-231-10.fc25.x86_64
dconf-0.26.0-1.fc25.x86_64

How reproducible:

100%

Steps to Reproduce:
1. see above

Actual results:

old stale dconf daemon process overwrites homedir settings with whatever it has in memory

Expected results:

dconf daemon uses settings from homedir

Comment 1 Fedora End Of Life 2017-11-16 19:03:21 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:11:12 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.