Bug 475164 - udisks dbus timeouts cause delays
Summary: udisks dbus timeouts cause delays
Status: RESOLVED FIXED
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.110.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-03 08:41 UTC by iannwork
Modified: 2023-10-20 23:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27.8
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iannwork 2023-10-03 08:41:34 UTC
SUMMARY
***
After login to plasma desktop the background picture, mouse cursor and x-console shows (lists some bluez errors) but nothing else.
Eventually the rest of the desktop loads.
In system journal are multiple messages such as:
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/nvme1n1p1"

Same delay & udisks2 errors occur when opening Dolphin and Kate with the same errors when I run through gdb.
***


STEPS TO REPRODUCE
1. Login to user account


OBSERVED RESULT
Desktop wallpaper, cursor (can move but no response to clicks) and xconsole window in bottom left corner show.
No icons or task bar.
After delay taskbar & desktop icons show and desktop is usable.

EXPECTED RESULT
No delay after account login for full desktop to show and Dolphin to open immediately.

SOFTWARE/OS VERSIONS
openSuse Tumbleweed 20231001
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel version 6.5.4-1-default (64 bit)
Graphics Platform X11

ADDITIONAL INFORMATION
Previous versions of plasma did not experience this timeout delay.

nvme1n1p1 is an ntfs partition that is set as noauto in fstab.
The partition is used by a windows 11 virtual machine which can access the device with no issue. The windows 11 vm guest is manually started so is not somehow blocking the device. The host should not mount that partition, but I can manually mount the device using the fstab entry.

I have attempted some old suggestions around disabling auto-mounting devices in settings > removable storage > removable devices however no devices show in that window. Another suggestion was to remove ~/.config/kded_device_automounterrc but that did not make a difference.

Trace from gdb Dolphin showing the error, sorry not sure how to use this tool or use to capture login details - and it's not a crash per se.

GNU gdb (GDB; openSUSE Tumbleweed) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dolphin...

This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.opensuse.org/>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from /home/me/.cache/debuginfod_client/20f6df0cba769579bb68a9c76322679a2ccdcede/debuginfo...
(gdb) run                                                                       
Starting program: /usr/bin/dolphin 
[Thread debugging using libthread_db enabled]                                   
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffefaad6c0 (LWP 5405)]                                          
[New Thread 0x7fffef2ac6c0 (LWP 5406)]
[New Thread 0x7fffe7fff6c0 (LWP 5407)]                                          
[New Thread 0x7fffe77fe6c0 (LWP 5408)]
[New Thread 0x7fffe6ffd6c0 (LWP 5409)]
[New Thread 0x7fffe67fc6c0 (LWP 5410)]
[New Thread 0x7fffe5dfb6c0 (LWP 5411)]
[New Thread 0x7fffe55fa6c0 (LWP 5412)]
[Thread 0x7fffe55fa6c0 (LWP 5412) exited]
[Thread 0x7fffe5dfb6c0 (LWP 5411) exited]
[New Thread 0x7fffe5dfb6c0 (LWP 5413)]                                          
[New Thread 0x7fffe55fa6c0 (LWP 5415)]                                          
[New Thread 0x7fffc2bff6c0 (LWP 5416)]
[New Thread 0x7fffc23fe6c0 (LWP 5417)]
[New Thread 0x7fffc1bfd6c0 (LWP 5418)]
[New Thread 0x7fffc13fc6c0 (LWP 5419)]
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/nvme1n1p1"
[Thread 0x7fffc1bfd6c0 (LWP 5418) exited]
[Thread 0x7fffc23fe6c0 (LWP 5417) exited]
[Thread 0x7fffc2bff6c0 (LWP 5416) exited]
[Thread 0x7fffe55fa6c0 (LWP 5415) exited]
[Detaching after fork from child process 5430]
[Detaching after fork from child process 5432]
[New Thread 0x7fffc2bff6c0 (LWP 5434)]                                          
[New Thread 0x7fffe55fa6c0 (LWP 5436)]
[New Thread 0x7fffc23fe6c0 (LWP 5439)]
[New Thread 0x7fffc1bfd6c0 (LWP 5440)]
[New Thread 0x7fffaffff6c0 (LWP 5442)]
[New Thread 0x7fffaf7fe6c0 (LWP 5443)]
[New Thread 0x7fffaeffd6c0 (LWP 5444)]
[New Thread 0x7fffae7fc6c0 (LWP 5445)]
[New Thread 0x7fffadffb6c0 (LWP 5446)]
[Thread 0x7fffaffff6c0 (LWP 5442) exited]
[Detaching after fork from child process 5448]
[Detaching after fork from child process 5464]
[Detaching after fork from child process 5465]
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/nvme1n1p1"
[Thread 0x7fffadffb6c0 (LWP 5446) exited]
[Thread 0x7fffae7fc6c0 (LWP 5445) exited]
[Thread 0x7fffaeffd6c0 (LWP 5444) exited]
[Thread 0x7fffaf7fe6c0 (LWP 5443) exited]
[Thread 0x7fffc2bff6c0 (LWP 5434) exited]
[New Thread 0x7fffc2bff6c0 (LWP 5487)]
[New Thread 0x7fffaeffd6c0 (LWP 5488)]
[New Thread 0x7fffadffb6c0 (LWP 5489)]
[New Thread 0x7fffae7fc6c0 (LWP 5490)]
[Thread 0x7fffae7fc6c0 (LWP 5490) exited]
[Thread 0x7fffadffb6c0 (LWP 5489) exited]
[Thread 0x7fffaeffd6c0 (LWP 5488) exited]
[Thread 0x7fffc2bff6c0 (LWP 5487) exited]
[Thread 0x7fffe5dfb6c0 (LWP 5413) exited]
[Thread 0x7fffe55fa6c0 (LWP 5436) exited]
[Thread 0x7fffc1bfd6c0 (LWP 5440) exited]
[Thread 0x7fffc23fe6c0 (LWP 5439) exited]
[Thread 0x7fffef2ac6c0 (LWP 5406) exited]
[Thread 0x7fffe6ffd6c0 (LWP 5409) exited]
[Thread 0x7fffe67fc6c0 (LWP 5410) exited]
[Thread 0x7fffe77fe6c0 (LWP 5408) exited]
[Thread 0x7fffe7fff6c0 (LWP 5407) exited]
[Thread 0x7fffefaad6c0 (LWP 5405) exited]
[Thread 0x7ffff1eb9ec0 (LWP 5402) exited]
[Thread 0x7fffc13fc6c0 (LWP 5419) exited]
[New process 5402]
[Inferior 1 (process 5402) exited normally]
(gdb) set logging file ~/dolphin_backtrace.txt 
(gdb) set logging enabled on
Copying output to /home/me/dolphin_backtrace.txt.
Copying debug output to /home/me/dolphin_backtrace.txt.
(gdb) thread apply all bt full
(gdb) 
(gdb) c
The program is not being run.
(gdb) set logging enabled off
Done logging to /home/me/dolphin_backtrace.txt.
(gdb) quit
Comment 1 iannwork 2023-10-20 23:28:07 UTC
Issue is resolved after upgrade to 5.27.8; errors relating to the delays caused by the device are no longer appearing in startup logs and devices are not showing in Dolphin Devices section.
Setting this to resolved.
Cheers
Ian