Bug 2056118 - GDM login triggers systemd automounts
Summary: GDM login triggers systemd automounts
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-18 21:00 UTC by ismael.lezcano
Modified: 2022-06-08 00:56 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-08 00:56:05 UTC
Type: Bug

Attachments (Terms of Use)

Description ismael.lezcano 2022-02-18 21:00:29 UTC
Description of problem:
Logging in to GDM triggers automounts specified in fstab

Version-Release number of selected component (if applicable):
systemd 248.10
gnome-shell 40.8

How reproducible:
Log in via GDM

Steps to Reproduce:
1.Log in to GDM
2.Check findmnt --mtab
3.Check journalctl -m

Actual results:
automounts mount

Expected results:
automounts remain untriggered until applicable process does so

Additional info:
Problem started after an upgrade from Fedora 30 to 32. All systemd config files in /etc/systemd remain unchanged

/etc/fstab options for automounts are:  x-systemd.automount,x-systemd.idle-timeout=200

I attempted to set dconf to disable gnome automounts to fix as well.

Comment 1 ismael.lezcano 2022-02-20 01:10:21 UTC
I narrowed it down to the Dropbox daemon, as installed in the package that comes with Fedora 32, then 34. The triggers only occur when the dropbox daemon starts.

Whether this is dropbox itself, or the nautilus integration, I'm not sure yet. I haven't closed this yet only because I'm only 95% convinced that systemd isn't contributing to this.

Comment 2 Zbigniew Jędrzejewski-Szmek 2022-02-24 09:08:29 UTC
It sounds like the dropbox daemon scans the file system, triggering mounts. Most likely it should
do this more carefully, checking if a directory is an automountpoint before descending into it.

Comment 3 Ben Cotton 2022-05-12 16:36:27 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-06-08 00:56:05 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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

Note You need to log in before you can comment on or make changes to this bug.