https://bugs.kde.org/show_bug.cgi?id=522308
Dennis Duda <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|'Scanning devices' tries to |'Scanning devices' tries to |mount all automounted CIFS |mount all automounted SMB |shares, twice per local |shares, twice per partition |disk | --- Comment #4 from Dennis Duda <[email protected]> --- (In reply to Andrius Štikonas from comment #3) > can you try running it manually? On my system it is instant. But perhaps on > your system lsblk triggers automount when reading mountpoints. > > If lsblk is indeed the culprit, perhaps we can replace it with findmnt. I'm trying udevadm, then lsblk --noheadings --nodeps --output mountpoint /dev/nvme0n1p1, then udevadm again, but cannot reproduce the automount issue from the terminal. :S With Partition Manager, the debug output hangs after the output of the first `udevadm` command, then, after all the timeouts are done, lsblk and the second udevadm commands run immediately after another. Somehow I forgot to check journalctl for this though, and got another hint as to what's going on: Jun 28 13:32:41 seripc systemd[1]: mnt-software.automount: Got automount request for /mnt/software, triggered by 12128 (m_DeviceScanner) 12128 seems to be the DeviceScanner thread, it exits after scanning is done. And with that, I found https://bugs.kde.org/show_bug.cgi?id=400540 as well, which is where you added KPMCORE_DEBUG ^^ I should be able to run/test whatever you suggest to help figure this out. Thanks for the help so far! -- You are receiving this mail because: You are watching all bug changes.
