Bug 484580

Summary: No access to webdavs since plasma6
Product: [Frameworks and Libraries] frameworks-kio Reporter: Axel Braun <axel.braun>
Component: WebDAVAssignee: KIO Bugs <kio-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: bernhard, bg+kdex, claudius+kde, code-bugs, kdelibs-bugs-null, kfm-devel, ludovic-berthet, matrixfueller, metacryptic, meven29, miklcct, register-only, sander, stuart, tdejong282, wozniakg
Priority: NOR    
Version First Reported In: 6.0.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=496456
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot of error message
pcapc from connection to 10.100.100.1/dav/

Description Axel Braun 2024-03-27 08:48:11 UTC
Since update to Plasma 6 I cant access my webdavs share. Error message:
Folder webdavs://xxxx@webdav.mc.gmx.net/ does not exist

Any other info I cold provide? Please advise!

Operating System: openSUSE Tumbleweed 20240325
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: Wayland
Comment 1 Ben 2024-03-29 16:07:58 UTC
Hi Axel,

I had a similar problem, and could work around it with removing the user xxx@ from the url. KIO asked for username and password, saved it (again) to kwallet and connects fine now.

If that is the same for you, the bug is rather that the url handler does not recognize the user part correctly.
Comment 2 Axel Braun 2024-03-30 12:18:24 UTC
(In reply to Ben from comment #1)

> I had a similar problem, and could work around it with removing the user
> xxx@ from the url. KIO asked for username and password, saved it (again) to
> kwallet and connects fine now.

Hello Ben,
I needed to remove the user/PW from kwallet and log-in again, to get the folder overview working. 
But that did not bring complete success. As soon as I click a subfolder it claims 'invalid protocol'
journalctl:
Mär 30 13:15:15 X1E dolphin[25447]: kf.kio.core: Invalid URL: QUrl("")
(this time on wayland)
Comment 3 Méven Car 2024-03-30 12:42:15 UTC
(In reply to Axel Braun from comment #2)
> (In reply to Ben from comment #1)
> 
> > I had a similar problem, and could work around it with removing the user
> > xxx@ from the url. KIO asked for username and password, saved it (again) to
> > kwallet and connects fine now.
> 
> Hello Ben,
> I needed to remove the user/PW from kwallet and log-in again, to get the
> folder overview working. 
> But that did not bring complete success. As soon as I click a subfolder it
> claims 'invalid protocol'
> journalctl:
> Mär 30 13:15:15 X1E dolphin[25447]: kf.kio.core: Invalid URL: QUrl("")

Can you copy the url that dolphin is trying to access roughtly?
Does it work if you add or remove the trailing slash from the url ?

> (this time on wayland)

Hardly have any incidence here.
Comment 4 Axel Braun 2024-03-30 13:15:40 UTC
Created attachment 167940 [details]
Screenshot of error message

Backslash or not does not make any difference. It seems that the click on a folder does not return the proper folder name
If I go to the location bar and complete webdavs://webdav.mc.gmx.net/GNUHealth/ it determines the folder while I type and is able to change into that folder.
Comment 5 Axel Braun 2024-03-30 13:19:22 UTC
Another interesting fact - when in one subfolder, click on a subfolder is working as expected
Comment 6 Enno Gotthold 2024-04-20 09:10:37 UTC
(In reply to Ben from comment #1)
> Hi Axel,
> 
> I had a similar problem, and could work around it with removing the user
> xxx@ from the url. KIO asked for username and password, saved it (again) to
> kwallet and connects fine now.
> 
> If that is the same for you, the bug is rather that the url handler does not
> recognize the user part correctly.

For me this workaround didn't work. I still get "The file or folder ... doesn't exist".

I also found a downstream duplicate - https://bugzilla.suse.com/show_bug.cgi?id=1181988
Comment 7 Ben 2024-04-20 09:33:38 UTC
(In reply to Enno Gotthold from comment #6)
> I also found a downstream duplicate -
> https://bugzilla.suse.com/show_bug.cgi?id=1181988

It looks remotely similar but predates Plasma 6. These kind of problems pop up all the time and generally get dismissed by annoying self-proclaimed experts.

See e.g.: https://forums.opensuse.org/t/how-to-clear-dolphin-password-after-failed-sftp-login/170625/40
Comment 8 Méven Car 2024-05-02 11:45:14 UTC
(In reply to Enno Gotthold from comment #6)
> (In reply to Ben from comment #1)
> > Hi Axel,
> > 
> > I had a similar problem, and could work around it with removing the user
> > xxx@ from the url. KIO asked for username and password, saved it (again) to
> > kwallet and connects fine now.
> > 
> > If that is the same for you, the bug is rather that the url handler does not
> > recognize the user part correctly.
> 
> For me this workaround didn't work. I still get "The file or folder ...
> doesn't exist".
> 
> I also found a downstream duplicate -
> https://bugzilla.suse.com/show_bug.cgi?id=1181988

This might get fixed with https://invent.kde.org/frameworks/kio/-/merge_requests/1620 in KF 6.2
Comment 9 Bernhard Breinbauer 2024-06-02 10:12:41 UTC
I also can't connect to webdav servers since Plasma 6. I tried to produce a test case today with a public webdav server at https://www.dlp-test.com/webdav_pub/
I noticed the following:
When I enter the URL webdav://www.dlp-test.com/webdav/ in dolphin, the connection works. When I change the URL to webdavs://www.dlp-test.com/webdav/ it loads forever, but the connection is never established.
So it seems related to the secure connection.
Can't see any useful information in journalctl.
Comment 10 Enno Gotthold 2024-06-21 14:12:41 UTC
(In reply to Méven Car from comment #8)
> (In reply to Enno Gotthold from comment #6)
> > (In reply to Ben from comment #1)
> > > Hi Axel,
> > > 
> > > I had a similar problem, and could work around it with removing the user
> > > xxx@ from the url. KIO asked for username and password, saved it (again) to
> > > kwallet and connects fine now.
> > > 
> > > If that is the same for you, the bug is rather that the url handler does not
> > > recognize the user part correctly.
> > 
> > For me this workaround didn't work. I still get "The file or folder ...
> > doesn't exist".
> > 
> > I also found a downstream duplicate -
> > https://bugzilla.suse.com/show_bug.cgi?id=1181988
> 
> This might get fixed with
> https://invent.kde.org/frameworks/kio/-/merge_requests/1620 in KF 6.2

I am running openSUSE TW 20240613 with KDE Frameworks 6.3.0 (and Plasma 6.0.5) but the bug is still occurring. Same error message. Removing the user from the URI sadly still doesn't help.
Comment 11 Tim 2024-07-29 11:12:30 UTC
I encounter the same issue since upgrading Fedora 39 to 40. Now running plasma-workspace-common-6.1.3-2.fc40.x86_64).
Connecting to my photoprism webdav share (located at <baseurl>/originals) with Dolphin returns the error "The file or folder [...] does not exist.", when manually navigating to /originals/DCIM, the folder is listed and can be browsed recursively. 

When connecting to my Hetzner storage box Webdav, I can list the root (/) and see subdirectories, however entering those subdirectories returns the same "does not exist" error.

Both shares work using Thunar file browser.
Comment 12 Ludovic 2024-08-05 09:34:05 UTC
(In reply to Tim from comment #11)
> I encounter the same issue since upgrading Fedora 39 to 40. Now running
> plasma-workspace-common-6.1.3-2.fc40.x86_64).
> Connecting to my photoprism webdav share (located at <baseurl>/originals)
> with Dolphin returns the error "The file or folder [...] does not exist.",
> when manually navigating to /originals/DCIM, the folder is listed and can be
> browsed recursively. 
> 
> When connecting to my Hetzner storage box Webdav, I can list the root (/)
> and see subdirectories, however entering those subdirectories returns the
> same "does not exist" error.
> 
> Both shares work using Thunar file browser.

Hello,

I'm in the same case than you after update from F39 to F40 no more WebDav from my nextcloud... but from an other device it's working fine... 

does not exist error are haunting me... 


Thinking that we must continue wait as KF 6.2 suggered in comment #8
Comment 13 Bug Janitor Service 2024-10-12 16:00:29 UTC
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1738
Comment 14 Enno Gotthold 2024-10-14 07:37:52 UTC
After applying the linked MR I was able to browse the root folder of my Photoprism instance again. Verified on openSUSE Tumbleweed.
Comment 15 Fabian Vogt 2024-10-23 07:30:36 UTC
Git commit b382e97754a9cdb7c235ca11ef3959b63607ff87 by Fabian Vogt.
Committed on 23/10/2024 at 07:29.
Pushed by fvogt into branch 'master'.

[webdav] Handle redirections which add trailing slashes

KIO doesn't always send trailing slashes when referencing collections.
The RFC (quoted in the comment) requires that such clients handle
redirections, which KIO can't do correctly in this case.

Add explicit handling for such redirections in the http worker, such that
KIO and applications don't need to be aware of this.

M  +30   -27   src/kioworkers/http/http.cpp

https://invent.kde.org/frameworks/kio/-/commit/b382e97754a9cdb7c235ca11ef3959b63607ff87
Comment 16 jolic 2024-11-16 15:30:01 UTC
Hello, I can confirm this issue on Linux Manjaro KDE (stable). WebDAV functionality in KDE Dolphin has not worked since the KDE Frameworks update to 6.5.0 (I am currently using version 6.6.0). In contrast, it still worked correctly with Frameworks version 6.4.0.

I am receiving this error message:
>> The file or folder webdavs://domain.tld/daten does not exist

Interestingly, I can list the contents via the console, for example:
>> kioclient ls webdavs://domain.tld/daten/

As a temporary workaround, I am using Krusader, which works without any issues.

For additional details and user reports, please refer to this forum thread:
https://forum.manjaro.org/t/problem-with-dolphin-and-webdavs-since-update-2024-08-20/167439
Comment 17 jolic 2025-02-04 19:41:25 UTC
Hallo, first of all, a big thank you to all the developers and contributors who make KDE such a great project! I really appreciate the hard work of all the volunteers, and I understand that patience is often necessary.

However, I wanted to point out that WebDAVs has not been working in Dolphin for almost a year now, and since today's major Manjaro KDE update (stable 2025-02-04), it is also no longer working in Krusader. This makes managing files over WebDAV quite difficult.

As a temporary solution, I am currently using Nautilus, which works flawlessly. On my new PC, I have even switched to Cinnamon since I experience fewer issues with WebDAVs there.

I hope this issue will be resolved soon, and I sincerely appreciate all the great work you do!

System:
- Krusader Version 2.9.0 "Sixth Life"
- KDE Plasma 6.2.5
- KDE Frameworks 6.10.0
- Qt 6.8.1
- Manjaro Kernel 6.6.74  (Wayland)
Comment 18 Bill Goodman 2025-02-23 23:45:25 UTC
I confirm that this fails on:
Fedora 41
Dolphin 24.12.1
KDE Plasma 6.2.5
Comment 19 Grzegorz Wozniak 2025-03-10 21:33:23 UTC
Same issue on Debian 13 (Testing) since KF6 upgrade came in, both webdav and webdavs protocols stopped working in dolphin and krusader.

KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.7.2
Comment 20 Michael Tsang 2025-03-12 11:00:22 UTC
I can't connect to my PhotoPrism instance in Dolphin with the same error. My server log shows that 

2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/webdavs://storage.miklcct.com:8443/originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND / HTTP/1.1" 404 5575 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/webdavs://storage.miklcct.com:8443/originals/ HTTP/1.1" 404 345 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND / HTTP/1.1" 404 5575 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:28 +0000] "PROPFIND /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:35 +0000] "PROPFIND /originals/ HTTP/1.1" 207 4070 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"


despite that I have entered my correct user name and password.
Comment 21 Michael Tsang 2025-03-12 11:01:20 UTC
kioclient ls webdavs://michael@storage.miklcct.com:8443/originals/

works correctly
Comment 22 Grzegorz Wozniak 2025-03-12 11:06:22 UTC
(In reply to Michael Tsang from comment #20)
> I can't connect to my PhotoPrism instance in Dolphin with the same error. My
> server log shows that 
> 
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/webdavs://storage.miklcct.com:8443/originals/ HTTP/1.1" 401 3704
> "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> / HTTP/1.1" 404 5575 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/webdavs://storage.miklcct.com:8443/originals/ HTTP/1.1" 404 345
> "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6 kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> / HTTP/1.1" 404 5575 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:07 +0000] "PROPFIND
> /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:28 +0000] "PROPFIND
> /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:35 +0000] "PROPFIND
> /originals/ HTTP/1.1" 207 4070 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND
> /originals HTTP/1.1" 307 3526 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND
> /originals/ HTTP/1.1" 401 3704 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 2a02:6d0:5:1:57e1:caf2:c1f0:d88e - - [12/Mar/2025:10:58:38 +0000] "PROPFIND
> /originals/ HTTP/1.1" 207 767 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/6.6
> kioworker/6.6.0"
> 
> 
> despite that I have entered my correct user name and password.

I'm configming tha behaviour, seems like app is unable to parse response and goes into endless loop.
Comment 23 Grzegorz Wozniak 2025-03-12 11:09:47 UTC
Created attachment 179339 [details]
pcapc from connection to 10.100.100.1/dav/
Comment 24 metacryptic 2025-04-19 20:48:01 UTC
To add some matter if it can help :

- Local adress (192.168.00.XX)  : 
----------------------------------------------
Webdavs a local adress can be access, but, it needs to be execute several times to reach the directory shared. meanwhile it says that the directory doesn't exist.

- Over Internet : 
-------------------------
webdavs://name@myadress.fr:5001/mydirectory is extremely slow and when it manage to show the directory it is unusable because dowloading a file cause error (file doesn't exist) or crached.
previous version of dolphin was working pretty well.

I think that nowadays, a system that can't access to distant shared directory is a major bug.
Comment 25 metacryptic 2025-04-19 20:58:57 UTC
(In reply to metacryptic from comment #24)
> To add some matter if it can help :
> 
> - Local adress (192.168.00.XX)  : 
> ----------------------------------------------
> Webdavs a local adress can be access, but, it needs to be execute several
> times to reach the directory shared. meanwhile it says that the directory
> doesn't exist.
> 
> - Over Internet : 
> -------------------------
> webdavs://name@myadress.fr:5001/mydirectory is extremely slow and when it
> manage to show the directory it is unusable because dowloading a file cause
> error (file doesn't exist) or crached.
> previous version of dolphin was working pretty well.
> 
> I think that nowadays, a system that can't access to distant shared
> directory is a major bug.
============================
Dolphin Version 24.12.3
kio 6.12.0-1
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.12.23-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-1260P
Memory: 15.2 Gio of RAM
Graphics Processor: Intel® Iris® Xe Graphics
Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Product Name: 950XED
System Version: P12RGF

============================
dolphin in konsole accessing a webdavs adress :
============================
[me@NR-ArchLinux ~]$ dolphin
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: An error occurred during write. The worker terminates now.

============================
journal said :
============================
Process 63481 (kioworker) of user 1000 dumped core.
Stack trace of thread 69856:
#0  0x00007a42944b7624 n/a (libc.so.6 + 0x97624)
#1  0x00007a429445dba0 raise (libc.so.6 + 0x3dba0)
#2  0x00007a4293b354da _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x74da)
#3  0x00007a429445dcd0 n/a (libc.so.6 + 0x3dcd0)
#4  0x00007a4293fa8dcb _ZN7QObject10disconnectEPKS_PKcS1_S3_ (libQt6Core.so.6 + 0x1a8dcb)
#5  0x00007a4293d0f08f n/a (libQt6Network.so.6 + 0xe708f)
#6  0x00007a4293d0f264 n/a (libQt6Network.so.6 + 0xe7264)
#7  0x00007a4293fb6cc9 n/a (libQt6Core.so.6 + 0x1b6cc9)
#8  0x00007a4293cf9b35 _ZN12QHttp2Stream11streamErrorEN5Http210Http2ErrorE13QLatin1String (libQt6Network.so.6 + 0xd1b35)
#9  0x00007a4293cffbe8 _ZN12QHttp2Stream21uploadDeviceDestroyedEv (libQt6Network.so.6 + 0xd7be8)
#10 0x00007a4293fb6cc9 n/a (libQt6Core.so.6 + 0x1b6cc9)
#11 0x00007a4293fa434a _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1a434a)
#12 0x00007a4293d26002 n/a (libQt6Network.so.6 + 0xfe002)
#13 0x00007a4293fa58db _ZN14QObjectPrivate14deleteChildrenEv (libQt6Core.so.6 + 0x1a58db)
#14 0x00007a4293fa42dc _ZN7QObjectD2Ev (libQt6Core.so.6 + 0x1a42dc)
#15 0x00007a4293d2bc75 n/a (libQt6Network.so.6 + 0x103c75)
#16 0x00007a4293fa53be _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1a53be)
#17 0x00007a4293f59fbb _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x159fbb)
#18 0x00007a4293f5a3f2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x15a3f2)
#19 0x00007a429423de22 n/a (libQt6Core.so.6 + 0x43de22)
#20 0x00007a42940e4508 n/a (libQt6Core.so.6 + 0x2e4508)
#21 0x00007a42944b570a n/a (libc.so.6 + 0x9570a)
#22 0x00007a4294539aac n/a (libc.so.6 + 0x119aac)

Stack trace of thread 63481:
#0  0x00007a42944bdbe2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007a42944b1e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007a42944b24bc n/a (libc.so.6 + 0x924bc)
#3  0x00007a42944b7414 n/a (libc.so.6 + 0x97414)
#4  0x00007a42940e0236 n/a (libQt6Core.so.6 + 0x2e0236)
#5  0x00007a4294055433 _ZN7QThread4waitE14QDeadlineTimer (libQt6Core.so.6 + 0x255433)
#6  0x00007a4293c81bf2 n/a (libQt6Network.so.6 + 0x59bf2)
#7  0x00007a4293c87ce7 n/a (libQt6Network.so.6 + 0x5fce7)
#8  0x00007a4293c87f05 n/a (libQt6Network.so.6 + 0x5ff05)
#9  0x00007a42947b9bf6 n/a (kio_http.so + 0xdbf6)
#10 0x00007a42947ba647 n/a (kio_http.so + 0xe647)
#11 0x00007a42947bf1c9 n/a (kio_http.so + 0x131c9)
#12 0x00007a42947c1bc3 n/a (kio_http.so + 0x15bc3)
#13 0x00007a4294693f35 n/a (libKF6KIOCore.so.6 + 0x81f35)
#14 0x00007a429468ec1e n/a (libKF6KIOCore.so.6 + 0x7cc1e)
#15 0x00007a429473945f n/a (libKF6KIOCore.so.6 + 0x12745f)
#16 0x00007a42947b790d kdemain (kio_http.so + 0xb90d)
#17 0x000060aac4d2824d n/a (/usr/lib/kf6/kioworker + 0x124d)
#18 0x00007a4294447488 n/a (libc.so.6 + 0x27488)
#19 0x00007a429444754c __libc_start_main (libc.so.6 + 0x2754c)
#20 0x000060aac4d28515 n/a (/usr/lib/kf6/kioworker + 0x1515)

Stack trace of thread 63483:
#0  0x00007a429453788d syscall (libc.so.6 + 0x11788d)
#1  0x00007a4293138450 g_cond_wait (libglib-2.0.so.0 + 0x90450)
#2  0x00007a42930cddac n/a (libglib-2.0.so.0 + 0x25dac)
#3  0x00007a429313ead2 n/a (libglib-2.0.so.0 + 0x96ad2)
#4  0x00007a429313db3e n/a (libglib-2.0.so.0 + 0x95b3e)
#5  0x00007a42944b570a n/a (libc.so.6 + 0x9570a)
#6  0x00007a4294539aac n/a (libc.so.6 + 0x119aac)

Stack trace of thread 63798:
#0  0x00007a42944bdbe2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007a42944b1e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007a42944b1e74 n/a (libc.so.6 + 0x91e74)
#3  0x00007a429452ca06 ppoll (libc.so.6 + 0x10ca06)
#4  0x00007a4293169f67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5  0x00007a4293105615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#6  0x00007a42941cd59d _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3cd59d)
#7  0x00007a4293f65376 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x165376)
#8  0x00007a429405a4b9 _ZN7QThread4execEv (libQt6Core.so.6 + 0x25a4b9)
#9  0x00007a42938b58de n/a (libQt6DBus.so.6 + 0x2e8de)
#10 0x00007a42940e44ff n/a (libQt6Core.so.6 + 0x2e44ff)
#11 0x00007a42944b570a n/a (libc.so.6 + 0x9570a)
#12 0x00007a4294539aac n/a (libc.so.6 + 0x119aac)

Stack trace of thread 63485:
#0  0x00007a42944bdbe2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007a42944b1e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007a42944b1e74 n/a (libc.so.6 + 0x91e74)
#3  0x00007a429452ca06 ppoll (libc.so.6 + 0x10ca06)
#4  0x00007a4293169f67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5  0x00007a4293106ee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#6  0x00007a428f3eba84 n/a (libgio-2.0.so.0 + 0x114a84)
#7  0x00007a429313db3e n/a (libglib-2.0.so.0 + 0x95b3e)
#8  0x00007a42944b570a n/a (libc.so.6 + 0x9570a)
#9  0x00007a4294539aac n/a (libc.so.6 + 0x119aac)

Stack trace of thread 63484:
#0  0x00007a42944bdbe2 n/a (libc.so.6 + 0x9dbe2)
#1  0x00007a42944b1e33 n/a (libc.so.6 + 0x91e33)
#2  0x00007a42944b1e74 n/a (libc.so.6 + 0x91e74)
#3  0x00007a429452ca06 ppoll (libc.so.6 + 0x10ca06)
#4  0x00007a4293169f67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5  0x00007a4293105615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#6  0x00007a4293105672 n/a (libglib-2.0.so.0 + 0x5d672)
#7  0x00007a429313db3e n/a (libglib-2.0.so.0 + 0x95b3e)
#8  0x00007a42944b570a n/a (libc.so.6 + 0x9570a)
#9  0x00007a4294539aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Comment 26 Axel Braun 2025-06-12 11:23:46 UTC
In between a new bug arrived, when opening a webdavs session in dolphin:
Jun 12 13:19:24 P1 systemd[2430]: Started dbus-:1.2-org.kde.kpasswdserver6@14.service.
Jun 12 13:19:24 P1 kiod6[531796]: qt.qpa.xcb: could not connect to display :1
Jun 12 13:19:24 P1 kiod6[531796]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Jun 12 13:19:24 P1 kiod6[531796]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Jun 12 13:19:24 P1 kiod6[531796]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                  
                                  Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.
Jun 12 13:19:24 P1 systemd-coredump[531798]: Process 531796 (kiod6) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jun 12 13:19:24 P1 systemd[1]: Started Process Core Dump (PID 531798/UID 0).
Jun 12 13:19:24 P1 systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Jun 12 13:19:24 P1 systemd-coredump[531801]: [🡕] Process 531796 (kiod6) of user 1000 dumped core.
                                             
                                             Stack trace of thread 531796:
                                             #0  0x00007f5e8f89b37c __pthread_kill_implementation (libc.so.6 + 0x9b37c)
                                             #1  0x00007f5e8f841cb6 raise (libc.so.6 + 0x41cb6)
                                             #2  0x00007f5e8f82938b abort (libc.so.6 + 0x2938b)
                                             #3  0x00007f5e900f4108 n/a (libQt6Core.so.6 + 0xf4108)
                                             #4  0x00007f5e900f4fde _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xf4fde)
                                             #5  0x00007f5e909788b5 n/a (libQt6Gui.so.6 + 0x1788b5)
                                             #6  0x00007f5e90a16798 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x216798)
                                             #7  0x00007f5e901bc165 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x1bc165)
                                             #8  0x00007f5e90a206de _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x2206de)
                                             #9  0x00007f5e913db54d _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0x1db54d)
                                             #10 0x000055dd81d7f52b n/a (/usr/libexec/kf6/kiod6 + 0x352b)
                                             #11 0x00007f5e8f82b12e __libc_start_call_main (libc.so.6 + 0x2b12e)
                                             #12 0x00007f5e8f82b1f9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2b1f9)
                                             #13 0x000055dd81d7fb05 n/a (/usr/libexec/kf6/kiod6 + 0x3b05)
                                             
                                             Stack trace of thread 531797:
                                             #0  0x00007f5e8f8a1c32 __syscall_cancel_arch (libc.so.6 + 0xa1c32)
                                             #1  0x00007f5e8f89581c __internal_syscall_cancel (libc.so.6 + 0x9581c)
                                             #2  0x00007f5e8f895871 __syscall_cancel (libc.so.6 + 0x95871)
                                             #3  0x00007f5e8f90fd82 ppoll (libc.so.6 + 0x10fd82)
                                             #4  0x00007f5e8fb0b5ef n/a (libglib-2.0.so.0 + 0x615ef)
                                             #5  0x00007f5e8fb0bd0c g_main_context_iteration (libglib-2.0.so.0 + 0x61d0c)
                                             #6  0x00007f5e9041de83 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x41de83)
                                             #7  0x00007f5e901c3afb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1c3afb)
                                             #8  0x00007f5e902b771c _ZN7QThread4execEv (libQt6Core.so.6 + 0x2b771c)
                                             #9  0x00007f5e91a6557e n/a (libQt6DBus.so.6 + 0x3b57e)
                                             #10 0x00007f5e90332eae n/a (libQt6Core.so.6 + 0x332eae)
                                             #11 0x00007f5e8f899546 start_thread (libc.so.6 + 0x99546)
                                             #12 0x00007f5e8f91d94c __clone3 (libc.so.6 + 0x11d94c)
                                             ELF object binary architecture: AMD x86-64
Jun 12 13:19:24 P1 systemd[1]: systemd-coredump@14-531798-0.service: Deactivated successfully.
Jun 12 13:19:24 P1 systemd[2430]: dbus-:1.2-org.kde.kpasswdserver6@14.service: Main process exited, code=dumped, status=6/ABRT
Jun 12 13:19:24 P1 systemd[2430]: dbus-:1.2-org.kde.kpasswdserver6@14.service: Failed with result 'core-dump'.
Jun 12 13:19:24 P1 kioworker[530572]: kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)! "Could not activate remote peer 'org.kde.kpasswdserver6': unit failed"

Operating System: openSUSE Tumbleweed 20250606
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.1
Kernel Version: 6.15.0-1-default (64-bit)
Comment 27 metacryptic 2025-08-15 18:00:59 UTC
Hi
Seems that it is ok now, don't know if their is a changed since.
=> Webdavs ok
=> QNAP NAS changed the configuration process without saying anything. Probably it causes my trouble, in part if it is not totally.
=> Sorry for the noise if it is that.
===============================

(In reply to metacryptic from comment #24)
> To add some matter if it can help :
> 
> - Local adress (192.168.00.XX)  : 
> ----------------------------------------------
> Webdavs a local adress can be access, but, it needs to be execute several
> times to reach the directory shared. meanwhile it says that the directory
> doesn't exist.
> 
> - Over Internet : 
> -------------------------
> webdavs://name@myadress.fr:5001/mydirectory is extremely slow and when it
> manage to show the directory it is unusable because dowloading a file cause
> error (file doesn't exist) or crached.
> previous version of dolphin was working pretty well.
> 
> I think that nowadays, a system that can't access to distant shared
> directory is a major bug.
Comment 28 Axel Braun 2025-09-07 19:54:46 UTC
the protocol
webdavs://user@webdavsshare.com
still does not work. without user@ it works