KDE Dolphin can't copy or move files [solved]

[jesnow]

Apparently some users (myself included) have been unable to move or copy files between folders with dolphin. A file manager not being capable of managing files is a bit of an issue when trying to get work done. Pcmanfm-qt works fine, CLU mv, cp, etc works fine.

The error message in dolphin is:

"The file or folder Message recipient disconnected from message bus without replying does not exist."

There appears to be a bug filed with KDE, on which there has been no action since July:
https://bugs.kde.org/show_bug.cgi?id=472591
https://bugs.kde.org/show_bug.cgi?id=463136

There is also a Gentoo bug:
https://bugs.gentoo.org/911175

Rebuilding the kernel with FUSE_FS seemed to help the previous poster, but my kernel has fuse module set.
[Edit: module is no good, you must recompile with fuse compiled in to end the pain]

This is incredibly frustrating.

Any help would be greatly appreciated.


Cheers,
JS

[Goverp]

...
There appears to be a bug filed with KDE, on which there has been no action since July:
...

I get the feeling the KDE support people are overwhelmed with bug reports. If that's the case, the way to get progress is to send patches that fix the bugs, not just reports. I reported a bug in dolphin (or more accurately kioslaves, which did the work involved) some years ago. After two or three years, I got a "does it still happen? if you don't update the report we'll mark it fixed" automated email.

I tried reading kioslaves - IMHO hideous code, full of flags to control special case behaviour - it screamed that it should be rewritten in a proper Object Oriented style using a lot of inheritance of common behaviour, but the chance of someone rewriting such a core component is low. I may be misjudging it - I didn't spend long looking. I certainly wasn't up to coding a patch to fix my problem!

[jesnow]

My other machines don't have this condition, so it's clearly a problem for which there is a cause and a solution. Probably yes KDE has an issue. It appears to be something with dbus. I don't know what dbus is supposed to look like but it seems to be putting up many more daemons on this machine than on my home machine.

Code: Select all

jesnow@vanaert ~ $ ps ax | grep dbus
 2475 ?        Ss     0:00 /usr/bin/dbus-daemon --system
 3239 ?        S      0:00 dbus-launch --autolaunch f602801a453dfa82f0b47d61637e825a --binary-syntax --close-stderr
 3240 ?        Ss     0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
 4128 ?        S      0:00 dbus-launch --autolaunch=f602801a453dfa82f0b47d61637e825a --binary-syntax --close-stderr
 4129 ?        Ss     0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
 4140 ?        S      0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_0
 4151 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/startplasma-x11
 4152 ?        Ss     0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
 4322 ?        Sl     0:00 /usr/bin/gmenudbusmenuproxy
 4487 ?        S      0:00 /usr/bin/python3.11 /usr/libexec/calculate/cl-dbus-core.py
 4985 pts/1    S+     0:00 grep --colour=auto dbus

This is from my home machine (which does not have the issue):

Code: Select all

jesnow@bartali ~ $ ps ax | grep dbus
  486 ?        S      0:03 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/tmp/runtime-jesnow/at-spi/bus_0
 1394 ?        Ss     0:00 /usr/bin/dbus-daemon --system
 2582 tty1     S      0:00 dbus-launch --exit-with-session startplasma-x11
 2583 ?        Ss     0:05 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
 2702 tty1     Sl     0:14 /usr/bin/gmenudbusmenuproxy
25440 pts/7    S+     0:00 grep --colour=auto dbus

[jesnow]

Update: Trying to find another file manager to use until I can get dolphin working.

Command line : Works, all normal. cp, mv, etc. --> This is not a permissions issue
pcmanfm-qt : Works, no errors, just not the greatest file manager
Konqueror : Fails, same error. Maybe no surprise, I will file a separate bug with KDE

[jesnow]

I'm getting no help from the Gentoo community. This is new and disappointing to me.

I really hope that someone can step in to help because I'm out of answers.

Cheers,
Jon

[pietinger]

I'm getting no help from the Gentoo community. [...]
I really hope that someone can step in to help because I'm out of answers.

I had the same problem because of a missing FUSE in kernel. Before I have got the info I installed MidnightCommander (mc) as alternative. After enabeling FUSE I had no problems anymore.

I am sure, if someone whould know what causes your problem you would have got an answer; so, I assume that we are also out of ideas. Because you have a working dolphin/kde it would be possible to compare both installations ... much work, I know ... but at the moment I dont see other chances.

[jesnow]

Thanks! Fuse isn't missing in my kernel.

Code: Select all

vanaert New Folder (1) # zgrep -i fuse  /proc/config.gz 
CONFIG_FUSE_FS=m
CONFIG_FUSE_DAX=y

What would fuse even be relevant to dbus? that makes no sense. But things sometimes just are. In any event I have fuse in the kernel.
I compared between the working one and the broken one everything I could think of that might be relevant. Both kde and dbus are reltaively opaque, so it's not even clear what there is to compare.

I'm getting no help from the Gentoo community. [...]
I really hope that someone can step in to help because I'm out of answers.

I had the same problem because of a missing FUSE in kernel. Before I have got the info I installed MidnightCommander (mc) as alternative. After enabeling FUSE I had no problems anymore.

I am sure, if someone whould know what causes your problem you would have got an answer; so, I assume that we are also out of ideas. Because you have a working dolphin/kde it would be possible to compare both installations ... much work, I know ... but at the moment I dont see other chances. :(

[Spanik]

I had the same thing and it did go away after including FUSE into my kernel as suggested here. And the " ps ax | grep dbus" returns identically the same as what your machine does where it works.

Are both machines on the same versions of kernel, dbus, kde, dolphin?

[pietinger]

I compared between the working one and the broken one everything I could think of that might be relevant. Both kde and dbus are reltaively opaque, so it's not even clear what there is to compare.

The last thing I would like to ask is, do you have FUSE also as <M>odule in your kernel where it works ? (If it would make a difference if static <*> or as <M>odule I cannot explain why; you see this is last hope)

[jesnow]

It is a module where it is broken and static where it works, so maybe. I will try it when I get back to that desk. If so that's a real bug, to have local file transfers depend on static fuse to succeed. But it is a known issue.

Cheers,
Jon.

[jesnow]

That worked. For the record for anybody googling that error message:

KDE and dbus throw a *ton* of error messages when CONFIG_FUSE_FS is not compiled static.

You can monitor those error messages with

$ dbus-monitor "type=error"

and after the initial

Code: Select all

signal time=1693523133.616185 sender=org.freedesktop.DBus -> destination=:1.59 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.59"
signal time=1693523133.616246 sender=org.freedesktop.DBus -> destination=:1.59 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.59"

You then get cascading errors form the moment you open dolphin. It doesn't actually fail until you try to drag and drop files though, and then you get a stupid error message in dolphin as reported above.

Thanks to all who helped.
Cheers,
Jon.

[Spanik]

Thank you for that extra bit of info.

I didn't experience it as I have the habit of compiling everything that I know I'm sure of I'll need as static.

[Goverp]

If FUSE is needed at all, does this implicate NTFS partitions, or is KDE doing something weird?

[jesnow]

I first noticed it with NFS mounts, but that doesn't use FUSE. But then realized that the behavior was the same on ext4. I'm not using ntfs at all.

No, it's a weakness of either dbus or KDE.

Cheers,
Jon.

If FUSE is needed at all, does this implicate NTFS partitions, or is KDE doing something weird?

[Spanik]

If FUSE is needed at all, does this implicate NTFS partitions, or is KDE doing something weird?

I don't see the relation with NTFS, my HD/SSD partitions are XFS. So I take it that this is Dolphin or KDE. Didn't try with another graphical filemanager. Moving and copying files in a terminal continued to work.

[pietinger]

That worked. For the record for anybody googling that error message:

KDE and dbus throw a *ton* of error messages when CONFIG_FUSE_FS is not compiled static.

Jon, we had a KDE Update; there was also an update of "kio-fuse" ... it would be interesting to know if this causes a change if FUSE has to be configured statically or modular in the kernel. (I cant test in the moment; no time).