[SOLVED] Dolphin gives me a weird error when i try to access my WD MyCloud

[przxqgl]

i started out with a clean install of bionic. i used dolphin to access my WD MyCloud as a samba drive -- smb://salamandirCloud.local/ -- i added some location icons to the panel on the left, which accessed varios directories on the NAS, and everything worked fine for about three days.

ever since then, when i click on one of those icons, dolphin thinks about it for a LONG time, and then puts up this message:

Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: Unknown error 8216

sometimes, instead of saying "Unknown error 8216" it says "Unknown error", or “File exists” or “Software caused connection abort”. i tried reconnecting to the NAS, but it inevitably produces one of those errors, and does not connect.

i searched at bugs.kde.org and found a dolphin bug that is similar, but that bug is for MOVING files to a samba disk, and that results results in dolphin crashing. mine doesn't crash, it just gives me the error.

i tried installing dolphin-dbgsym, but, as this doesn't result in a crash, i'm not sure how much they will help.

[przxqgl]

this is for bionic... i'm not sure how it ended up in artful, but it did, and i'm sorry... could one of the mods move it to bionic software support? thanks.

[przxqgl]

okay, this is REALLY weird, but i have to follow up...

i looked at the URI that was in the dolphin window, after the weird "unknown error", and it was "smb://@/" which i thought was kind of odd.

so i put the username for the drive on the left hand side of the @ sign, and the name of the drive on the right side...

and it worked.

no clue how it got that way. no clue why it worked the other way before, and doesn't now. no clue what the weird "unknown error" means... i have absolutely NO CLUE why it works now and didn't before... but it does.

[GreyGeek]

Well, as the old saying goes, "If it ain't broken then don't fix it!"

[przxqgl]

if that were really the way it worked, i would still be back on precise. the fact is, it doesn't have to be completely broken to need an upgrade, and, if previous upgrades are any indication, the initial problems will all work themselves out, eventually. ;-)