Since kde-plasma/plasma-workspace-5.22.5, the device notifier will wake up on ly the first time an usb key is attached.
Il that device is then detached, the device notifier will remain silent for all future attachements.
This bug has been reported on the KDE Bugtracking System : https://bugs.kde.org/show_bug.cgi?id=438874
A fix has been merged upstream : https://invent.kde.org/plasma/plasma-workspace/-/commit/61e2ea2323ae63c5805c87353701ba6fb722205a
Works for me.
Created attachment 740622 [details, diff]
Patch fixing notification of hotplug devices
This patch is a copy of upstream's patch adapted to the version of applets/devicenotifier/package/contents/ui/devicenotifier.qml found in plasma-workspace-5.22.5.tar.xz distfile.
Created attachment 740625 [details]
plasma-workspace ebuild implementing the above patch
Ebuild taking the patch into account.
The bug has been referenced in the following commit(s):
Author: Andreas Sturmlechner <email@example.com>
AuthorDate: 2021-09-22 20:53:47 +0000
Commit: Andreas Sturmlechner <firstname.lastname@example.org>
CommitDate: 2021-09-22 21:59:09 +0000
kde-plasma/plasma-workspace: Fix krunner cwd, device notifications
krunner starts applications with cwd "/" with init system other than systemd
Disk & Devices applet doesn't show removable devices after eject and reconnect
Upstream commit 61e2ea2323ae63c5805c87353701ba6fb722205a
Thanks-to: Eric F. Garioud <email@example.com>
Thanks-to: Andrea Arcangeli <firstname.lastname@example.org>
Package-Manager: Portage-3.0.23, Repoman-3.0.3
Signed-off-by: Andreas Sturmlechner <email@example.com>
...orkspace-5.22.5-fix-hotplug-notifications.patch | 33 ++++
...asma-workspace-5.22.5-krunner-cwd-at-home.patch | 30 +++
.../plasma-workspace-5.22.5-r2.ebuild | 210 +++++++++++++++++++++
3 files changed, 273 insertions(+)
With the latest fix I can crash plasma by ejecting a usb thumbdrive.
Created attachment 740790 [details, diff]
So, unfortunately I can not reproduce this kind of crash with any of my devices. I will rely on your testing to confirm that the attached patch fixes it.
This patch contains both the additional upstream commit 89c719113193a29bd608163a6f4d81e23e2a5513 from the linked MR as well as preceding commit cfbb1995ebd33ec3c49727b62713c81c3c7526d8 which is touching the same context in order to fix a duplicate bug of KDEbug 438874.
I tested the patch, it still crashes in the same way. What's interesting is that it doesn't crash if I eject the device from Dolphin, only if I do that from the device-notificator-applet-what's its name
Application: Plasma (plasmashell), signal: Segmentation fault
#4 0x00007f9b6c2059de in () at /usr/lib64/libQt5Qml.so.5
#5 0x00007f9b6c1aca94 in () at /usr/lib64/libQt5Qml.so.5
#6 0x00007f9b6c1ae24d in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Qml.so.5
#7 0x00007f9b6c0e457d in () at /usr/lib64/libQt5Qml.so.5
#8 0x00007f9b5064d2d3 in ()
#9 0x0000000000000000 in ()
[Inferior 1 (process 14389) detached]
(In reply to Michael from comment #6)
> I tested the patch, it still crashes in the same way. What's interesting is
> that it doesn't crash if I eject the device from Dolphin, only if I do that
> from the device-notificator-applet-what's its name
Which patch did you test ?
The one I posted in the first attachment (changing only 2 lines in a single .qml file and which should be sufficient for fixing the bug I reported here) or asturm's one going much farther ?
In the latter case, could you please test the first patch attached to this bug report ?
I tested attachment 740790 [details, diff] applied to plasma-workspace-5.22.5-r2, which should already have the other one, if I understood you correctly.
However. Upgrading to 5.22.90 from ::kde fixed my issue. And moreover, after some additional testing and recompiling plasma several times, I suspect that the crash that I was experiencing has nothing to do with this bug, so sorry for the noise.
(In reply to Michael from comment #9)
> ...I suspect that
> the crash that I was experiencing has nothing to do with this bug.
I share this opinion, at least as far as devicenotifier.qml is concerned.
Because at the end of the day, there should be no difference (for this file) between plasma-workspace-5.22.5-r2 patched with asturm's last attachment and the 5.23 beta (5.22.90) version.
AFAIU The first patch (from attachement 740790) only fixes very particular cases where unmounting via the applet generates a crash (cases in which you are unlikely to be as it would not have been possible for you to umount from dolphin) and the second just rewrites the logic of the first.
And indeed, all these fiddlings (while possibly being of non negligible interest in some cases) are not in the scope of this precise bug.
(In reply to Larry the Git Cow from comment #3)
> The bug has been referenced in the following commit(s):
> commit 61988d92de81544b00167a289258360b61c7261e
> Author: Andreas Sturmlechner <firstname.lastname@example.org>
> AuthorDate: 2021-09-22 20:53:47 +0000
> Commit: Andreas Sturmlechner <email@example.com>
> CommitDate: 2021-09-22 21:59:09 +0000
Thank you Andreas! This commit actually resolves/fixes this bug.
We'll use this bug for stabilisation.
all arches done