Just a thought

Things to try to get some debugging :
https://community.kde.org/Plasma/Debugging (Attach gdb to the plasmashell process)

I am finding saving and finding files in dolphin/kde to be tedious and error-prone. I "save as" a file in Okular and the location choice does not follow new directory creation, but seems to be guided by some other setting. Then I open Dolphin to move the file to where I wanted it and the file in nowhere to be found. I see it with Okular, but not with Dolphin. Is there some setting I am missing? (slackware64-current, 7/16)

kde gear 21.07.80 (release service) is available, it's devel version:

https://download.kde.org/unstable/re.../21.07.80/src/

compil and works here ;)

not the only one, some componentes release test/transitional version with same version number 21.07.80

If anyone who has had the dolphin/usb problem can report it to :

https://bugs.kde.org/buglist.cgi?com...resolution=---

A simple way to catch plasmashell logs

Open a terminal
- reproduce the case where the usb crashes dolphin
- eventually restart the session properly
- check inside the ~/plasmashell.log
- report it, if highlighted, to bugs.kde.org

It will be usefull :hattip:

Good advice! I will give it a go at earliest opportunity...

--
Pete

Hi,

In my case, removing USB drive allows me to use Alt+F2, and then typing brings Plasma back again.

--
Best regards,
Andrzej Telszewski

In my case, I can't remove the USB drive because the Slackware system is installed on it.

In fact, is an USB 3.0 SD card adapter, which hosts the 64GB micro-SD card where Slackware is installed.

The mini-PC has a SD card slot, but it still does not work properly on Linux, even with the latest kernel. And on Windows 10 (which is installed on eMMC) has a speed of 13MB/s which makes me to not have big hopes about it, considering that the USB 3.0 adapter gives 100MB/s read and 70MB/s write, which is quite decent and comparable with the performances of the first generation of SSD.

Today it hosts a second 64GB SD card which I use for storing data for Windows.

Hi,

but isn't that, that only mounting the drive from Plasma crashes Plasma?
I can insert and remove the USB drive, it shows up and disappears from Plasma Devices and only when I try to mount it, then Plasma crashes.

In your case, since you have rootfs on the USB drive, it is mounted long before the Plasma is started, so you should not have the issue. ;-)
You might want to ensure that auto-mounting in KDE is disabled. That was the reason that Plasma crashed upon inserting the USB drive, but now it does not crash any more. Unless I try to mount, of course. ;-)

--
Best regards,
Andrzej Telszewski

Unfortunately, even the F2FS rootfs is mounted long before starting Plasma5, the behavior is as I described. And I never had active the auto-mounting on Plasma5 or even KDE4.

That makes me believe that the issue is not literally about mounting the USB drive, but rather regarding some operations which Plasma5 does for that particular mounted filesystem or drive. Maybe it tries to check the SMART data and fails, who knows?

In the other thread on this subject, it has been suggested that the kernel version may be significant. I don't think so. The poster who suggested this was using 5.13, I'm using 5.12.15. I'm also getting the same problem on a raspberry Pi-400 running Slarm64.

--
Pete

WHAT IF the Plasma needs a rebuild against the new Frameworks?

Someone who's affected can try this rebuild - the Plasma itself is a relative small set of packages.
This is the command required for.

I for one, I have no issues of this type on my boxes. Maybe I am just lucky and Plasma5 likes all my USB drives.

We are about ten to post here
3 or 4 have the problem
the rest don't have it
No trace of the issue on bugs.kde.org

I strongly doubt, even if not everyone uses plasma5, that luck has something to do with it
I think more like bad luck for those who encounter the issue ... :-(

So, it's specific to Slackware, at least for me?

Let's list what we know:
- it's specific to Slackware more or less
- not all Plasma5 users are affected
- not all USB drives are "affected"
- looks like is not about mounting them, but something which Plasma5 do with them (processing or query) after the USB drives are mounted.
- the shipped KDE Plasma and KDE Applications are older builds that KDE Frameworks 5.84, which are in fact lots of libraries


Then, either our non-systemd system itself does not contains a particular feature OR we just we have a libraries conflict and there's needed a rebuild against Frameworks 5.84

That's WHY I believe that someone who's affected by this issue should try to rebuild at least KDE Plasma.

WHY someone who have those issues? Because s/he can verify the result.

yes
weird anyway