Bug 318792 - Plasma deadlocks on login when nfs network shares are used with systemd automounting
Summary: Plasma deadlocks on login when nfs network shares are used with systemd autom...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (other bugs)
Version First Reported In: 5.18.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-24 04:42 UTC by Wyatt
Modified: 2023-05-17 16:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wyatt 2013-04-24 04:42:55 UTC
I have 3 nfs mounts in my /etc/fstab. They use systemd automounting so that they don't mount until entered. KDE forces a chicken-egg problem:

* KDE waits for systemd to mount the shares before logging in completes.
* systemd cannot mount nfs shares until an internet connection is established.
* An internet connect isn't established until KDE has completed logging in.

The result is that KDE seems to wait forever at the last stage of logging in. systemd does have a configurable timeout, and KDE will login if you specify a really short one, but you shouldn't have to do that (it defeats the entire point of this systemd feature).

Reproducible: Always

Steps to Reproduce:
1. Setup a server to have an nfs mount
2. Find a client  computer with wifi capabilities and KDE and systemd installed (also recommend default ksplash theme)
3. Unplug any wired connections from this client
4. Setup an nfs share in /etc/fstab using systemd's automount feature. Should look like this:

server.address.com:/path/                 /mnt/point nfs         nolock,rw,noauto,x-systemd.automount    0 0

5. Reboot the client.
6. Try to login to a KDE session.
7. Notice that it stalls at the last stage.
8. Ctrl+Alt+F1, login, and use vim to disable the nfs share.
9. Use 'sudo systemctl restart kdm' to restart kdm.
10. Login again, and notice you login just fine.
Comment 1 Wyatt 2013-05-06 20:48:28 UTC
I've noticed that this doesn't only happen when x-systemd.automount is used. It instead seems to happen any time there is an unresponsive/inaccessable NFS mount.

Steps to reproduce:

1. Mount some nfs shares.
2. Disconnect from the internet.
3. Logout.
4. Attempt to login.
5. Notice that it stalls at the last stage.
8. Ctrl+Alt+F1, login, and unmount the nfs shares.
9. Use 'sudo systemctl restart kdm' to restart kdm.
10. Login again, and notice you login just fine.
Comment 2 mangus 2013-07-19 08:43:48 UTC
yeah this is pretty annoying , can't manage to login if my shares are down
Comment 3 Andrew Crouthamel 2018-11-10 03:23:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:43:58 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Nate Graham 2023-05-17 15:36:01 UTC
Should be fixed now with the new systemd boot process.