Dolphin and automount unit no longer works

Support KDE Plasma
1

Hi all,

I’m using the following systemd units to mount a NAS device on start up:

[Unit]
Description=Automount daten share using SMB
ConditionPathExists=/ds/Daten

[Automount]
Where=/ds/Daten
TimeoutIdleSec=10

[Install]
WantedBy=multi-user.target

and:

[Unit]
Description=NAS SMB data share
#-Requires=dbus-org.freedesktop.nm-dispatcher.service
After=network-online.target
Wants=network-online.target

[Mount]
What=//192.168.0.7/Daten
Where=/ds/Daten
Type=cifs
Options=_netdev,iocharset=utf8,rw,file_mode=0777,dir_mode=0777,credentials=/home/andreash/smb.cred,vers=3.0
TimeoutSec=30

[Install]
WantedBy=default.target

this worked fine until a few weeks.

The mount works fine, until i open Dolphin. At this point the share is unmounted, mounted and unmounted again and so on.
Addition it is not longer possible to open any files with an application which is not Dolphin itself. Copy a file from the NAS to the local disk works, open a PDF from the NAS doesn’t work. Open the file on command line works.

Dolphin shows me the error:

Unit dbus-org.freedesktop.nm-dispatcher.service not found.

The status of the automount shows the following;

● ds-Daten.automount - Automount daten share using SMB
     Loaded: loaded (/etc/systemd/system/ds-Daten.automount; enabled; preset: disabled)
     Active: active (waiting) since Thu 2024-09-05 09:23:27 CEST; 17min ago
 Invocation: 33ec24c07d7b4519bbf8e4963baa70b1
   Triggers: ● ds-Daten.mount
      Where: /ds/Daten

Sep 05 09:36:11 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:36:41 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:37:11 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:37:41 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:38:11 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:38:31 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 3208 (dolphin)
Sep 05 09:39:11 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:39:41 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 2192 (Thread (pooled))
Sep 05 09:40:02 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 3234 (KIO::WorkerThre)
Sep 05 09:40:22 linux-pc systemd[1]: ds-Daten.automount: Got automount request for /ds/Daten, triggered by 3474 (KIO::WorkerThre)

the mount unit shows:

● ds-Daten.mount - NAS SMB data share
     Loaded: loaded (/etc/systemd/system/ds-Daten.mount; enabled; preset: disabled)
     Active: active (mounted) since Thu 2024-09-05 09:43:11 CEST; 2s ago
 Invocation: f07cf0be0943458d9ae9d87ba48b3bfc
TriggeredBy: ● ds-Daten.automount
      Where: /ds/Daten
       What: //192.168.0.7/Daten
      Tasks: 0 (limit: 38241)
     Memory: 28K (peak: 1.5M)
        CPU: 5ms
     CGroup: /system.slice/ds-Daten.mount

Sep 05 09:43:11 linux-pc systemd[1]: Mounting NAS SMB data share...
Sep 05 09:43:11 linux-pc systemd[1]: Mounted NAS SMB data share.

I have tried to add the nm-dispatcher.service to the mount unit

Requires = dbus-org.freedesktop.nm-dispatcher.service

but the error is still the same.

I would be happy to get a solution or a hint to solve my problem. Even google was not able to help me ( or I am googleing for the wrong topic xD). I hope I have provided all information needed to understand the problem, if not feel free to ask.

Thanks in advanced.
Leonerd

2

What you presented is two automount units. I am guessing that is a typo of sorts - because your log shows a corresponding mount unit - it looks like the mount is working as expected.

That is difficult to say - what would cause this.

One thought is permissions - but it is a cifs share so :thinking:, could you please provide the mount unit as well?

But I am thinking the kio backend is playing tricks on you.

3

you’re right I copied the automount unit twice. I corrected this in my first post.

the mount settings should be ok, I can work with the mounted files if i access them via terminal. And I can copy files from and to the share and it is possible to create new files and folders with dolphin.

Edit: I tried thunar and everything works.

4

I had some time to take a look on the problem and found this entries in the journal:

Sep 12 20:46:43 linux-pc systemd[1]: Mounting NAS SMB data share...
Sep 12 20:46:43 linux-pc kernel: CIFS: Attempting to mount //192.168.0.7/Daten
Sep 12 20:46:43 linux-pc plasmashell[1173]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Sep 12 20:46:43 linux-pc plasmashell[1173]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Sep 12 20:46:43 linux-pc systemd[1]: Mounted NAS SMB data share.
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc plasmashell[1173]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Sep 12 20:46:43 linux-pc plasmashell[1173]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Sep 12 20:46:43 linux-pc dolphin[1503]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Sep 12 20:46:43 linux-pc dolphin[1503]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 12 20:46:43 linux-pc dolphin[1503]: kf.kio.core: Connection::send() called with connection not inited

It seems that linux-aarhus is right with his assumption, that there is something wrong with kio. I have no idea how kio works.