@Condobloke, is it forbidden to discuss unsupported distros here or you mean it's ok to use the workaround?
I gave it. If you need more, give me the commands needed I'm able to copy paste their outputs.
Yes, I wrote
right click -> empty trash.
No, how to check?
Literally it.
Code:
$ dolphin
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "stash"
org.kde.dolphin: Ignore KIO url: QUrl("timeline:/today")
org.kde.dolphin: Ignore KIO url: QUrl("timeline:/yesterday")
org.kde.dolphin: Ignore KIO url: QUrl("timeline:/thismonth")
org.kde.dolphin: Ignore KIO url: QUrl("timeline:/lastmonth")
org.kde.dolphin: Ignore KIO url: QUrl("search:/documents")
org.kde.dolphin: Ignore KIO url: QUrl("search:/images")
org.kde.dolphin: Ignore KIO url: QUrl("search:/audio")
org.kde.dolphin: Ignore KIO url: QUrl("search:/videos")
qt.accessibility.core: Cannot create accessible child interface for object: PlacesView(0x55feddd41a30) index: 11
kf5.kio.core: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf\nLoaded services file OK.\nWARNING: You have some share names that are longer than 12 characters.\nThese may not be accessible to some older clients.\n(Eg. Windows9x,
WindowsMe, and smbclient prior to Samba 3.0.)\n"
Aborting aboutToFinish handling.
^C
The last line was added when emptying the trash.
I'm not a dummy
Btw this forum has very good engine. WYSIWYG message editor is very convenient.
Okay, when I said specific info, I meant running the app in a terminal, or using
strace <app name here>, etc. as system calls are important indicators.
When I asked if it was "clicked" I didn't mean whether you clicked it, I meant whether the window registered the event and if the correct signal/event was sent.
...And yes, I didn't notice Ubuntu was 18 in your output and when I saw "unsupported", I thought, WTF? -- that's on me.
In this case, I strongly suggest you just upgrade to the latest LTS and call it a day.
That said, I'll try to troubleshoot this:
So that mostly, based on that output, it looks like you're doing this on a share which is a very different beast than locally. KDE has its own "way of doing things" making it that much harder. Also, minor thing, but try upgrading Qt -- minor thing just as GTK warnings, but all the same.
As for actual remediation, I'd backup my KDE configs, reboot into a CLI, and then uninstall a'la
--purge KDE completely, then ensure you samba configuration is correct (currently I see no issues, just complaints about names, but you may want to check things in any case). Once you are sure it all works properly, reinstall KDE and install all suggested packages
--install-suggests (I think this should fix missing things and work on Ubuntu, too).
But to reiterate, if your system is that out of date, it doesn't matter whether that's the cause or not, I encourage you to upgrade for security and stability reasons. Really, you will get more and more issues if you stay on an EOL system... If you don't like re-installing, move to a rolling release like Fedora, or try anything based on Debian Testing (which is more/less reliable for a desktop -- put it this way, AFAIK, many Ubuntu packages come from Debian Sid). Ultimately, my best advice is suck it up and do a reinstall every couple years. It ensures no upgrade debris, it gives you a clean start, and in many distros' cases, gives you a stable repo snapshot which is only updated to reflect well-tested upgrade packages.
PS: Never thought you were an idiot, just that most people who haven't been here too long tend to not be bothered (as in lazy, need reminding) and with long outputs, [spoiler ] tags keep posts neat and [code ] tags are there to maintain formatting, so you can imagine how messy things get.
