https://bugs.kde.org/show_bug.cgi?id=522308
--- Comment #3 from Andrius Štikonas <[email protected]> --- (In reply to Dennis Duda from comment #2) > (In reply to Andrius Štikonas from comment #1) > > Can you check which command causes this scan. > > > > Either run KPMCORE_DEBUG=1 partitionmanager and observe terminal. > Thanks, with that I can tell that it seems to not be twice per disk, but > rather once per partition (which just happened to line up). > > The command that seems to cause the automounts is `udevadm info > --query=property /dev/nvme0n1p1` (same for the other partitions). However > when I run it (even including the preceding other commands) from either my > normal user account or as root, I cannot reproduce the rescan. From > Partition Manager it still reproduces on every rescan, including in an > already open window by pressing 'Refresh Devices'. > > Interestingly, I do see the output from the udevadm command when running > with KPMCORE_DEBUG=1 *before* it hangs, and it hangs before then running the > next command being `lsblk --noheadings --nodeps --output mountpoint > /dev/nvme0n1p1` > > (Additionally, after that mountpoint check, I see another run of `udevadm > info --query=property /dev/nvme0n1p1` which _doesn't_ cause the automount > tries, before proceeding to the next partition. Not sure if that's > important, but adding it here for completeness' sake.) udevadm info wouldn't cause automount/hang, it's just read-only db access. I'm thinking lsblk --noheadings --nodeps --output mountpoint /dev/nvme0n1p1` 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. -- You are receiving this mail because: You are watching all bug changes.
