You don’t have to. I’m looking for comparative information. Solid reports the same as mine. Only kded6 is attempting to mount the share in your case. I think you should submit a bug report for it (showing that this doesn’t happen with an earlier TW snapshot). In the course of that dialogue they may well ask for additional information.
Are there any new kded6 modules that might be impacting perhaps?
ls -l /usr/lib*/qt6/plugins/kf6/kded/
Compare against the older snapshot?
Maybe check against the loaded modules…
qdbus6 org.kde.kded6 /kded org.kde.kded6.loadedModules
openSUSE Bugzilla or KDE Bugtracking System ?
I’m afraid I will no longer be able to do that as I updated the last of my systems yesterday (just to see if the problem would turn up afterwards - and it did).
Examine anyway. I can check against my Slowroll environment.
The documentation describes expected behaviour. On your system observed behaviour differs from expected behaviour. Trouble exists on dbus, see output of journalctl --user -b -u plasma-kded6.service.
I am trying to help. I set up the following cifs mount on host i4130:
i4130:~ # grep /fritz.box /etc/fstab
//fritz.box/FRITZ.NAS /fritz.box cifs x-systemd.automount,x-systemd.device-timeout=5,x-systemd.idle-timeout=10,credentials=/root/fritz.box.credentials 0 0
i4130:~ #
Current Tumbleweed 20250630 behaves exactly as expected:
i4130:~ # journalctl -b -u 'fritz.box*'
Jul 02 06:15:36 i4130 systemd[1]: Set up automount fritz.box.automount.
Jul 02 06:17:05 i4130 systemd[1]: fritz.box.automount: Got automount request for /fritz.box, triggered by 1532 (bash)
Jul 02 06:17:05 i4130 systemd[1]: Mounting /fritz.box...
Jul 02 06:17:05 i4130 systemd[1]: Mounted /fritz.box.
Jul 02 06:17:43 i4130 systemd[1]: Unmounting /fritz.box...
Jul 02 06:17:43 i4130 systemd[1]: fritz.box.mount: Deactivated successfully.
Jul 02 06:17:43 i4130 systemd[1]: Unmounted /fritz.box.
i4130:~ #
Presumably the change in behaviour you observed is unrelated to system upgrade.
@karlmistelberger It is NOT expected behaviour if the user (or user service) didn’t explicitly trigger the mount. It DOES appear to be a s result of the recent upgrade.
In the log snippet you shared, the mount is done via bash (a user running a shell via a script or from a terminal). So of course it would be expected.
> ls -l /usr/lib*/qt6/plugins/kf6/kded/
total 3020
-rwxr-xr-x 1 root root 243544 Jun 24 13:56 appmenu.so
-rwxr-xr-x 1 root root 93152 Jun 24 13:55 audioshortcutsservice.so
-rwxr-xr-x 1 root root 35296 Jun 9 22:29 baloosearchmodule.so
-rwxr-xr-x 1 root root 284504 Jun 24 13:53 bluedevil.so
-rwxr-xr-x 1 root root 35304 Jun 24 13:56 colorcorrectlocationupdater.so
-rwxr-xr-x 1 root root 39392 Jun 24 13:56 desktopnotifier.so
-rwxr-xr-x 1 root root 63968 Jun 24 13:55 device_automounter.so
-rwxr-xr-x 1 root root 64224 Jun 24 13:56 devicenotifications.so
-rwxr-xr-x 1 root root 39392 Jun 24 13:56 donationmessage.so
-rwxr-xr-x 1 root root 39392 Jun 3 23:12 filenamesearchmodule.so
-rwxr-xr-x 1 root root 68288 Jun 24 13:56 freespacenotifier.so
-rwxr-xr-x 1 root root 68312 Jun 24 13:56 geotimezoned.so
-rwxr-xr-x 1 root root 224984 Jun 24 13:53 gtkconfig.so
-rwxr-xr-x 1 root root 51672 Jun 24 13:53 kameleon.so
-rwxr-xr-x 1 root root 64056 Jun 24 13:55 kded_bolt.so
-rwxr-xr-x 1 root root 196696 Jun 24 13:55 kded_touchpad.so
-rwxr-xr-x 1 root root 245336 Jun 24 13:55 keyboard.so
-rwxr-xr-x 1 root root 197080 Jun 24 13:54 kscreen.so
-rwxr-xr-x 1 root root 39512 Jun 24 13:56 ktimezoned.so
-rwxr-xr-x 1 root root 39512 Jun 24 13:56 mprisservice.so
-rwxr-xr-x 1 root root 304608 Jun 24 13:55 networkmanagement.so
-rwxr-xr-x 1 root root 43736 Jun 24 13:56 oom-notifier.so
-rwxr-xr-x 1 root root 35304 Jun 24 13:56 plasma-session-shortcuts.so
-rwxr-xr-x 1 root root 76520 Jun 24 13:56 plasma_accentcolor_service.so
-rwxr-xr-x 1 root root 27224 Jun 9 22:29 remotenotifier.so
-rwxr-xr-x 1 root root 189008 Jun 24 13:55 smart.so
-rwxr-xr-x 1 root root 68440 Jun 3 23:12 smbwatcher.so
-rwxr-xr-x 1 root root 43480 Jun 24 13:56 soliduiserver.so
-rwxr-xr-x 1 root root 77024 Jun 24 13:56 statusnotifierwatcher.so
-rwxr-xr-x 1 root root 43480 Jun 3 23:12 wpad-detector.so
>
> qdbus6 org.kde.kded6 /kded org.kde.kded6.loadedModules
audioshortcutsservice
wpad-detector
devicenotifications
oom-notifier
ktimezoned
smbwatcher
statusnotifierwatcher
desktopnotifier
kded_touchpad
plasma_accentcolor_service
kameleon
kscreen
mprisservice
gtkconfig
freespacenotifier
remotenotifier
bluedevil
donationmessage
smart
kded_bolt
networkmanagement
>
I would report to KDE (once you have the kded6 info).
I do wonder if “smbwatcher” might have changed behaviour. You could try disabling that.
Disable it via Background Services…
kcmshell6 kcm_kded
Restart the desktop session. Does the problem remain?
Is it
...
Jul 02 05:29:40 SYSTEM1 kded6[1997]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.37'
Jul 02 05:29:40 SYSTEM1 kded6[1997]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.38'
...
you are pointing at or do you see any other problems?
> qdbus6 org.kde.kded6 /kded org.kde.kded6.loadedModules
kscreen
smart
donationmessage
networkmanagement
freespacenotifier
oom-notifier
mprisservice
ktimezoned
kameleon
audioshortcutsservice
kded_touchpad
remotenotifier
desktopnotifier
statusnotifierwatcher
gtkconfig
bluedevil
kded_bolt
plasma_accentcolor_service
wpad-detector
devicenotifications
>
> sudo journalctl -b | grep QNAP
[sudo] password for root:
Jul 02 07:01:23 SYSTEM1 systemd[1]: Set up automount mnt-LAN-QNAP_Backups.automount.
Jul 02 07:01:52 SYSTEM1 systemd[1]: mnt-LAN-QNAP_Backups.automount: Got automount request for /mnt/LAN/QNAP_Backups, triggered by 1969 (kded6)
Jul 02 07:01:52 SYSTEM1 systemd[1]: Mounting /mnt/LAN/QNAP_Backups...
Jul 02 07:01:52 SYSTEM1 systemd[1]: mnt-LAN-QNAP_Backups.mount: Mount process exited, code=exited, status=32/n/a
Jul 02 07:01:52 SYSTEM1 systemd[1]: mnt-LAN-QNAP_Backups.mount: Failed with result 'exit-code'.
Jul 02 07:01:52 SYSTEM1 systemd[1]: Failed to mount /mnt/LAN/QNAP_Backups.
>
No joy. The problem is still there.
I have to leave now. I will setup a bug report on the KDE Bugtracker later today and show a link here.
1 Like
Yep. Messages on the pristine system are:
i4130:~ # su - karl
karl@i4130:~> journalctl --user -b -g dbus
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Service file '/usr/share//dbus-1/services/org.jackaudio.service' is not named after the D-Bus name 'org.jackaudio.service'.
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jul 02 07:22:40 i4130 dbus-broker-launch[1676]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jul 02 07:22:40 i4130 systemd[1647]: Created slice Slice /app/dbus-:1.2-org.kde.KSplash.
Jul 02 07:22:40 i4130 systemd[1647]: Started dbus-:1.2-org.kde.KSplash@0.service.
Jul 02 07:22:41 i4130 baloo_file[1752]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.25'
Jul 02 07:22:41 i4130 baloo_file[1752]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.27'
Jul 02 07:22:41 i4130 kded6[1808]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
Jul 02 07:22:41 i4130 kded6[1808]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon
Jul 02 07:22:41 i4130 kded6[1808]: QDBusObjectPath: invalid path "/modules/wpad-detector"
Jul 02 07:22:41 i4130 kded6[1808]: kf.dbusaddons: The kded module name "wpad-detector" is invalid!
Jul 02 07:22:41 i4130 kded6[1808]: QDBusObjectPath: invalid path "/modules/oom-notifier"
Jul 02 07:22:41 i4130 kded6[1808]: kf.dbusaddons: The kded module name "oom-notifier" is invalid!
Jul 02 07:22:41 i4130 kded6[1808]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Jul 02 07:22:41 i4130 kded6[1808]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Jul 02 07:22:42 i4130 systemd[1647]: Started Proxies GTK DBus menus to a Plasma readable format.
Jul 02 07:22:44 i4130 systemd[1647]: app-at\x2dspi\x2ddbus\x2dbus@autostart.service: Skipped due to 'exec-condition'.
Jul 02 07:22:44 i4130 systemd[1647]: Created slice Slice /app/dbus-:1.55-org.a11y.atspi.Registry.
Jul 02 07:22:44 i4130 systemd[1647]: Started dbus-:1.55-org.a11y.atspi.Registry@0.service.
karl@i4130:~>I wouldn‘t call this a pristine system or a comparable system at all. This are messages which appear on all normal Plasma systems here.
@susejunky dont‘ let you confuse by ridiculous hosts. The dbus messages (UDisks2 and UPower) appear on all Plasma systems and seems to be a red herring.
It is quite useless to talk about „pristine“ systems. Hardware, patterns, package selections, firmware differs between machines.
1 Like
Sure. There is a correlation. However correlation doesn’t imply causation.
I am using and maintaining local as well as remote systemd automounts on dozens of Tumbleweed systems for several years. These systems get their daily unattended upgrade without ever running into the problem encountered by @susejunky.
https://www.freedesktop.org/software/systemd/man/latest/systemd.automount.html
However some software indeed tries unsolicited mounts. The maintainer says:
Re: plocate messes with pruned folders

From: “Steinar H. Gunderson” steinar+web@gunderson.no
To: Me
Date: 25.03.25 11:02
On Tue, Mar 25, 2025 at 10:53:34AM +0100, Karl Mistelberger wrote:
I my opinion plocate shouldn’t mount the folders, but skip them without mounting.
Hi,
This is a known bug; there was a fix in git but it had to be reverted
due to another issue (see a03412e91a80f7). I don’t have the time to look at
it closer at the moment, sorry.
/* Steinar */
Homepage: https://www.sesse.net/
My bug report on the KDE Bugracking System
Many thanks to everybody (especially to @deano_ferrari) who so far spent their time helping me to investigate the problem!
I have to admit: At the moment I’m completely lost as far as this auto-mount-problem is concerned. So I created a report on the KDE Bugtracking System (see #75) and hopefully that will shed some light onto the matter.
Same here. I will follow this with interest.
Looks like good news !
The very first answer to my bug report suggested the freespacenotifier could be the culprit.
I disabled it and now the error (and the auto-mount-request which lead up to the error) is gone (at least on this machine will have to check the others).
Many thanks to everybody who supported me on this journey.
Special thanks to @deano_ferrari who spent a lot of their time helping me to investigate the problem and who came quite close to the solution (by suggesting the smbwatcher).
2 Likes
I disabled the freespacenotifier on all my openSUSE Tumbleweed installations and there are no more unwanted auto-mount-request during login. So to me the problem is solved.
I marked the recommendation to file a bugreport to KDE as solution because the bugreport itself provided the final solution.
Is this something specific to the KDE on Tumbleweed (Plasma 6), or can Leap 15.6 users encounter the same problem?
This is partly because I never heard of it and I do not know where the switch is 