https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #11 from Kwon-Young Choi <kwon-young.c...@hotmail.fr> ---
(In reply to Harald Sitter from comment #10)
> Thanks. There's something weird though...
>
> > "exit_status": 4
>
> shouldn't be filtered right now, so there must be something else going on
> additionally.
>
> It'd be great if you could get me the output of
>
> `QT_LOGGING_RULES="org.kde.plasma.disks=true" kded5 --replace`
Sorry for the delay.
Here's the output for:
```
$ `QT_LOGGING_RULES="org.kde.plasma.disks=true" kded5 --replace`
kf.kded: Couldn't register name "org.kde.kcookiejar5" with DBUS - another
process owns it already!
org.kde.plasma.disks: starting
org.kde.plasma.disks: !!!! "/org/freedesktop/UDisks2/block_devices/nvme0n1"
org.kde.plasma.disks: evaluating!
org.kde.plasma.disks: true true "org.kde.kded.smart"
KAuth::Action::AuthorizedStatus
org.kde.plasma.disks: !!!! "/org/freedesktop/UDisks2/block_devices/nvme0n1p1"
org.kde.plasma.disks: bad type Solid::StorageVolume::FileSystem
org.kde.wacomtablet.common: d->name.isEmpty? true
org.kde.wacomtablet.common: d->name.isEmpty? true
bluedevil: Created
Installing the delayed initialization callback.
kcm_touchpad: Using X11 backend
Delayed initialization.
Reloading the khotkeys configuration
Version 2 File!
true
1
Known activities: ("380a83a6-47ae-4f65-87be-08be5d57e561",
"4ca8abe1-deed-47b4-9b4b-627cfad25fd9")
Registering "org.kde.StatusNotifierItem-1224-1/StatusNotifierItem" to system
tray
Registering "org.kde.StatusNotifierHost-1059" as system tray
bluedevil: Bluetooth operational changed true
bluedevil: ObexManager operational changed true
Registering ":1.167/StatusNotifierItem" to system tray
Registering ":1.42/StatusNotifierItem" to system tray
Registering ":1.48/StatusNotifierItem" to system tray
bluedevil: ObexAgent registered
bluedevil: Agent registered
bluedevil: Requested default Agent
kf.auth: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
org.kde.plasma.disks: looks like we got no data back for "/dev/nvme0n1" 0 true
Warning from helper: QProcess: Destroyed while process ("smartctl") is still
running.
```
So, after contacting the smartmontools team, it turns out that this is a
firmware bug of my ssd but fortunately, it is easy to modify smartctl to hide
this bug. See the mail thread here:
https://listi.jpberlin.de/pipermail/smartmontools-support/2020-November/000544.html
Since we now know that this is an upstream bug, I believe we can close this bug
report.
--
You are receiving this mail because:
You are watching all bug changes.
