Issue with kde plasma and udisks 2.10

[alexjp]

Nixos distro updated udisks to 2.10 some days ago, and since then, kde plasma starting up and at first login freezes for some 5 seconds ( and has other issues, which seems like plasma crashed, although logs don't show any crash ).

This only happens at the first login after boot, being the following ones without this issue.

Going back to 2.9 fixes this. Also disabling udisks fixes the freezing.

I also tested on archlinux, manually updating udisks2 and libblockdev packages and the issue happens also on archlinux.

I apologize because I don't have enough tecnical knowledge to give more detailed info, but I have 2 nvme disks and 2 hdd disks. I also see this on the systemd udisksd unit log:

udisksd[1486]: udisks daemon version 2.10.0 starting
udisksd[1486]: Failed to load config files: Failed to get contents of the config dir (/etc/libblockdev/3/conf.d/)Error opening directory “/etc/libblockdev/3/conf.d/”: No such file or directory. Using the buil
t-in config
udisksd[1486]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
udisksd[1486]: Acquired the name org.freedesktop.UDisks2 on the system message bus

If more info is required, feel free to ask. Sorry if this issue isn't valid.

Thanks!

[tisyang]

I have the same issues under KDE. And with additional bugs:

udisks will always auto-mount usb storage disks under mount point /tmp/xxxxx, even I have lable uuid with certain mount point in /etc/fstab . Before upgrade udisks2, it will not auto-mouunt, and when click mouunt, the mouunt point will be /media/${user}/${lable} or ${uuid} .

[tisyang]

I'm running Debian sid with KDE Plasma 5.27.5.
After downgrade udisk2 to 2.9.4-4, all thing goes right like before.

[bitseater]

Hi, same issue running Debian unstable with Gnome 43.6 . After last update udisks2 to 2.10 , login process delays more than 5 seconds. I can't see others ssd and usb drives. I can't run gnome-disks. If I try to launch it from terminal i have the following error:

Error getting udisks client: Timeout was reached

The output from journalctl -u udisks2.service is :

jul 12 00:56:54 andromeda systemd[1]: Started udisks2.service - Disk Manager.
jul 12 00:56:54 andromeda udisksd[718]: Acquired the name org.freedesktop.UDisks2 on the system message bus
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:21 andromeda udisksd[718]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
jul 12 01:03:22 andromeda systemd[1]: Stopping udisks2.service - Disk Manager...
jul 12 01:03:22 andromeda udisksd[718]: udisks daemon version 2.10.0 exiting
jul 12 01:03:22 andromeda systemd[1]: udisks2.service: Deactivated successfully.
jul 12 01:03:22 andromeda systemd[1]: Stopped udisks2.service - Disk Manager.
jul 12 01:03:22 andromeda systemd[1]: udisks2.service: Consumed 49.928s CPU time.

I have to downgrade udisks2 and libudisks2-0 to 2.9.4-4 (debian testing) and the issue has disappeared.

[Firestar-Reimu]

Maybe this is why Archlinux do not update udisks to 2.10.0

[amurzeau]

I got into this too, kde starting up freeze for almost one minute.

While it is freezing, udisks2 service is running ntfscluster and NTFS partitions. I saw that as I have a NTFS USB key which is blinking for > 30s when kde is frozen. Then same for the HDD (I have Windows as dual boot).

When running ntfscluster manually on my USB key, it takes 45s (each time I run ntfscluster on it).

Maybe this issue appeared since commit 2892d77.

Plugging a NTFS USB key after KDE start up will also trigger the same issue:

• Starting dolphin just after having pluged in the USB key will hang dolphin while ntfscluster is being run
• The usb key shows activity for some time (45s for my key)
• After ntfscluster complete, KDE shows the notification that a removable device was connected and dolphin resume from its hang.
• journalctl -b | grep udisk shows timeouts:

juil. 14 15:29:01 Debian2 org_kde_powerdevil[1387]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 org_kde_powerdevil[1387]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1983]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1305]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 kded5[1204]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1983]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 kded5[1204]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1305]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[3354]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 kded5[1204]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[3354]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 kded5[1204]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1983]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1983]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1305]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[3354]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[1305]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:01 Debian2 plasmashell[3354]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"
juil. 14 15:29:53 Debian2 plasmashell[3513]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." for "/org/freedesktop/UDisks2/block_devices/sda7"

• Dolphin shows duplicate USB key (probably related to the timeouts):
  
• Running time udisksctl status just after having plugged in the USB key will timeout:

$ time udisksctl status
Error connecting to the udisks daemon: Timeout was reached

real    0m25,033s
user    0m0,000s
sys     0m0,010s

Downgrading to udisks2 2.9.4 fixes theses issues.

[amurzeau]

Reposting here as maybe more related to udisks2:

Also while true; do udisksctl status; done since 2.10 will heavily use disks (their activity led is almost always on).

I guess 2.9 wasn't refreshing disk usage values explaining why it was faster.

But many programs seems to use the get_size or get_info API often, for example opening the KDE network applet panel will probably call these functions as it causes heavy disk usage.

Unplugging and plugging the network cable also trigger very high disk usage.

[vojtechtrefny]

Maybe this issue appeared since commit 2892d77.

But many programs seems to use the get_size or get_info API often, for example opening the KDE network applet panel will probably call these functions as it causes heavy disk usage.

The org.freedesktop.UDisks2.Filesystem.Size was always problematic and it looks like introducing support for more filesystems caused even more problems (see also #1145). I will probably revert 2892d77 or limit it back to Ext and XFS only.

This issue will be finally fixed when util-linux 2.39 will be generally available, we'll then get all the information from udev instead of running (possibly too intrusive) command line tools (see #1114). Unfortunately 2.39 is not yet available in Debian Unstable.

I am sorry for this and big thanks to @amurzeau for debugging this and the fix for libblockdev. I'll try to do a new bugfix build of libblockdev during the weekend and hopefully fix the problem for you all.

[tbzatek]

This issue will be finally fixed when util-linux 2.39 will be generally available, we'll then get all the information from udev instead of running (possibly too intrusive) command line tools (see #1114). Unfortunately 2.39 is not yet available in Debian Unstable.

FYI @mbiebl @seb128 having util-linux-2.39 in the distribution along with udisks-2.10.0 would bring great benefits of lowering I/O and faster startup due to libblkid providing the necessary info.

Nixos distro updated udisks to 2.10 some days ago, and since then, kde plasma starting up and at first login freezes for some 5 seconds ( and has other issues, which seems like plasma crashed, although logs don't show any crash ).

Congratulations, you've found a bug in KDE. In general UI should not actively wait for udisks reply over D-Bus method calls, everything should be async. This udisks issue only revealed deficiencies elsewhere.

I saw that as I have a NTFS USB key which is blinking for > 30s when kde is frozen.

juil. 14 15:29:01 Debian2 org_kde_powerdevil[1387]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sdb1”" for "/org/freedesktop/UDisks2/block_devices/sdb1"

Same cases, these should all by async calls, not blocking the UI.

[mbiebl]

FYI @mbiebl @seb128 having util-linux-2.39 in the distribution along with udisks-2.10.0 would bring great benefits of lowering I/O and faster startup due to libblkid providing the necessary info.

while I don't maintain util-linux, this is valuable information, thanks!

[tbzatek]

while I don't maintain util-linux, this is valuable information, thanks!

This was a gentle lobby attempt... ;-)

[zeha]

Unfortunately 2.39 is not yet available in Debian Unstable.

2.39.1 is now in Debian experimental, and it'd be useful if interested people tested that.

[tbzatek]

Unfortunately 2.39 is not yet available in Debian Unstable.

2.39.1 is now in Debian experimental, and it'd be useful if interested people tested that.

Forgot to add that you need recent udev (v252) as well: systemd/systemd@704116c