Bug 471357 - Disk widget does not notice when a LUKS-encrypted disk was first unmounted from Dolphin's "Devices" section, and then also "Removable Devices"
Summary: Disk widget does not notice when a LUKS-encrypted disk was first unmounted fr...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Disks & Devices widget (other bugs)
Version First Reported In: 6.2.5
Platform: Other Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-23 00:29 UTC by junkblocker
Modified: 2025-01-18 08:14 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description junkblocker 2023-06-23 00:29:00 UTC 
SUMMARY

Disk Usage applet does not update frequently enough. If I attach a backup disk and then unmount it via Dolphin (eject from the sidebar but not safely disconnect), and then unplug the disk, the applet seems to (never?) recover again and keeps showing the combined values.

STEPS TO REPRODUCE
1. Attach an external USB drive.
2. Wait for the applet to catch up and show the new combined values.
3. Eject it from the eject icon next to it in Dolphin.
4. Unplug the USB drive.
5. The applet remains oblivious of the changes and keeps forever showing the combined values even when everything has disappeared from Dolphin's sidebar.

OBSERVED RESULT

The pie chart does not realize that the external disk has been removed and keep showing combined values for percentages etc.

EXPECTED RESULT

It should fall back to showing only the computer's internal storage.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-01-09 22:21:53 UTC 
Sorry it took us so long to get to this. I can't reproduce it in current git master, which will shortly become Plasma 6.3. Are you still able to reproduce the issue in Plasma 6.2.5 or later? Thanks!
Comment 2 junkblocker 2025-01-10 00:18:53 UTC 
(In reply to Nate Graham from comment #1)
> Sorry it took us so long to get to this. I can't reproduce it in current git
> master, which will shortly become Plasma 6.3. Are you still able to
> reproduce the issue in Plasma 6.2.5 or later? Thanks!

No, doesn't look like it is resolved in 

% plasmashell --version
plasmashell 6.2.5

1. Connected an encrypted disk. Unlocked and mounted it and the applet started showing new info.
2. Unmounted it. Applet did not update.
3. Safe unmounted the disk. Applet did not update.
4. Pulled the USB cable of the disk. Applet still did not update.
Comment 3 Nate Graham 2025-01-10 16:03:00 UTC 
In Dolphin, are you clicking the eject button next to the item that's in the "Devices" section, or in the "Removable devices" section?


Any chance you could attach a screen recording of this?
Comment 4 junkblocker 2025-01-15 02:04:08 UTC 
(In reply to Nate Graham from comment #3)
> In Dolphin, are you clicking the eject button next to the item that's in the
> "Devices" section, or in the "Removable devices" section?
> 
> 
> Any chance you could attach a screen recording of this?

I am clicking eject on the device in "Devices" section. After that I clicked eject in the "Removable Devices" section too for good measure. I can't attach a screen recording but here's relevant trimmer journal entries around this process.

░░ The unit session-119.scope has successfully entered the 'dead' state.
Jan 14 17:43:11 thishost kwin_wayland[2443]: kwin_scene_opengl: 0x1: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 14 17:43:25 thishost kwin_wayland[2443]: kwin_scene_opengl: 0x1: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 14 17:44:45 thishost kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
Jan 14 17:44:45 thishost kernel: usb 4-1: New USB device found, idVendor=1058, idProduct=264d, bcdDevice=30.12
Jan 14 17:44:45 thishost kernel: usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jan 14 17:44:45 thishost kernel: usb 4-1: Product: easystore 264D
Jan 14 17:44:45 thishost kernel: usb 4-1: Manufacturer: Western Digital
Jan 14 17:44:45 thishost kernel: usb 4-1: SerialNumber: 3151474150593056
Jan 14 17:44:45 thishost kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
Jan 14 17:44:45 thishost kernel: scsi host0: usb-storage 4-1:1.0
Jan 14 17:44:45 thishost mtp-probe[128190]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-1"
Jan 14 17:44:45 thishost mtp-probe[128190]: bus: 4, device: 3 was not an MTP device
Jan 14 17:44:45 thishost mtp-probe[128191]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-1"
Jan 14 17:44:45 thishost mtp-probe[128191]: bus: 4, device: 3 was not an MTP device
Jan 14 17:44:46 thishost kernel: scsi 0:0:0:0: Direct-Access     WD       easystore 264D   3012 PQ: 0 ANSI: 6
Jan 14 17:44:46 thishost kernel: scsi 0:0:0:1: Enclosure         WD       SES Device       3012 PQ: 0 ANSI: 6
Jan 14 17:44:46 thishost kernel: scsi 0:0:0:0: Attached scsi generic sg0 type 0
Jan 14 17:45:03 thishost kernel: ses 0:0:0:1: Attached Enclosure device
Jan 14 17:45:03 thishost kernel: ses 0:0:0:1: Attached scsi generic sg1 type 13
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Spinning up disk...
Jan 14 17:45:03 thishost kernel: ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8
Jan 14 17:45:03 thishost kernel: ses 0:0:0:1: Failed to get diagnostic page 0x1
Jan 14 17:45:03 thishost kernel: ses 0:0:0:1: Failed to bind enclosure -19
Jan 14 17:45:03 thishost kernel: .................ready
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] 39063650304 512-byte logical blocks: (20.0 TB/18.2 TiB)
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] No Caching mode page found
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan 14 17:45:03 thishost kernel:  sda: sda1
Jan 14 17:45:03 thishost kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jan 14 17:45:04 thishost udisksd[1391]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
                                        0000: f0 00 01 00  50 00 01 0a  80 00 00 00  00 1d 00 00    ....P...........
                                        0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                         (g-io-error-quark, 0)
Jan 14 17:45:04 thishost ksystemstats[2744]: org.kde.libksysguard.systemstats: Tried to add SensorObject with id "sda" to container "disk" that already contains an object with that ID, ignoring.
Jan 14 17:45:04 thishost systemd[1]: Started dbus-:1.3-org.kde.kded.smart@2.service.
░░ Subject: A start job for unit dbus-:1.3-org.kde.kded.smart@2.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit dbus-:1.3-org.kde.kded.smart@2.service has finished successfully.
░░ 
░░ The job identifier is 34160.
Jan 14 17:45:04 thishost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.3-org.kde.kded.smart@2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:45:06 thishost kioworker[127488]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Jan 14 17:45:06 thishost kioworker[127488]: kf.kio.core: An error occurred during write. The worker terminates now.
Jan 14 17:45:08 thishost kded6[2596]: QWindow::fromWinId(): platform plugin does not support foreign windows.
Jan 14 17:45:08 thishost kwin_wayland[2443]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5565b74c2070)
Jan 14 17:45:08 thishost plasmashell[2645]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Jan 14 17:45:08 thishost plasmashell[2645]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Jan 14 17:45:08 thishost plasmashell[2645]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Jan 14 17:45:08 thishost plasmashell[2645]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Jan 14 17:45:12 thishost audit[1391]: DM_CTRL module=crypt op=ctr ppid=1 pid=1391 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pool-udisksd" exe="/usr/libexec/udisks2/udisksd" subj=system_u:system_r:devicekit_disk_t:s0 dev=253:1 error_msg='success' res=1
Jan 14 17:45:12 thishost udisksd[1391]: Unlocked device /dev/sda1 as /dev/dm-1
Jan 14 17:45:12 thishost kernel: EXT4-fs (dm-1): mounted filesystem 85f3444f-ccad-4ae2-bf4e-c6dad0dbf1c1 r/w with ordered data mode. Quota mode: none.
Jan 14 17:45:12 thishost udisksd[1391]: Mounted /dev/dm-1 at /run/media/xxxx/Home20TB on behalf of uid 1000
Jan 14 17:45:12 thishost systemd[2103]: Started app-org.kde.dolphin@08e0fa85567248c7a80114450bf1a5f9.service - Dolphin - File Manager.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 1548.
Jan 14 17:45:13 thishost systemd[2103]: Started app-org.kde.dolphin@0c15fda5baa3412fa70391a9c4c14477.service - Dolphin - File Manager.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 1566.
Jan 14 17:45:14 thishost systemd[1]: dbus-:1.3-org.kde.kded.smart@2.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit dbus-:1.3-org.kde.kded.smart@2.service has successfully entered the 'dead' state.
Jan 14 17:45:14 thishost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.3-org.kde.kded.smart@2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 14 17:45:42 thishost systemd[2103]: Started app-org.kde.plasma\x2dsystemmonitor@71caf6520d484b92b7e42576f96a7def.service - System Monitor - System Monitor.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 1584.
Jan 14 17:45:42 thishost plasma-systemmonitor[128425]: file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:193:9: QML MouseArea: Binding loop detected for property "implicitHeight":
                                                       file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:208:13
Jan 14 17:45:42 thishost plasma-systemmonitor[128425]: file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:193:9: QML MouseArea: Binding loop detected for property "implicitHeight":
                                                       file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:208:13
Jan 14 17:45:42 thishost plasma-systemmonitor[128425]: file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:196:13: QML MouseArea: Binding loop detected for property "height"
Jan 14 17:45:42 thishost plasma-systemmonitor[128425]: file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:196:13: QML MouseArea: Binding loop detected for property "height"
Jan 14 17:45:42 thishost plasma-systemmonitor[128425]: file:///usr/lib64/qt6/qml/org/kde/kirigami/ScrollablePage.qml:196:13: QML MouseArea: Binding loop detected for property "height"
Jan 14 17:45:43 thishost plasma-systemmonitor[128425]: qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth":
                                                       qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:358:9
Jan 14 17:45:43 thishost plasma-systemmonitor[128425]: qrc:/qt/qml/org/kde/ksysguard/faces/ExtendedLegend.qml:58: TypeError: Cannot read property 'sensors' of null
Jan 14 17:45:43 thishost plasma-systemmonitor[128425]: qrc:/qt/qml/org/kde/ksysguard/faces/ExtendedLegend.qml:58: TypeError: Cannot read property 'sensors' of null
Jan 14 17:45:43 thishost plasma-systemmonitor[128425]: qrc:/qt/qml/org/kde/ksysguard/faces/ExtendedLegend.qml:58: TypeError: Cannot read property 'sensors' of null
Jan 14 17:46:01 thishost plasma-systemmonitor[128425]: QProcess: Destroyed while process ("/usr/libexec/ksysguard/ksgrd_network_helper") is still running.
Jan 14 17:46:01 thishost plasma-systemmonitor[128425]: org.kde.ksysguard.plugin.network: Helper process terminated abnormally: ""
Jan 14 17:46:01 thishost systemd[2103]: app-org.kde.plasma\x2dsystemmonitor@71caf6520d484b92b7e42576f96a7def.service: Consumed 2.768s CPU time, 166.9M memory peak.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit UNIT completed and consumed the indicated resources.
Jan 14 17:46:09 thishost systemd[1]: run-media-xxxx-Home20TB.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit run-media-xxxx-Home20TB.mount has successfully entered the 'dead' state.
Jan 14 17:46:09 thishost kernel: EXT4-fs (dm-1): unmounting filesystem 85f3444f-ccad-4ae2-bf4e-c6dad0dbf1c1.
Jan 14 17:46:09 thishost udisksd[1391]: Cleaning up mount point /run/media/xxxx/Home20TB (device 253:1 is not mounted)
Jan 14 17:46:09 thishost udisksd[1391]: Unmounted /dev/dm-1 on behalf of uid 1000
Jan 14 17:46:14 thishost dolphin[127357]: kf.kio.core: Invalid URL: QUrl("")
Jan 14 17:46:31 thishost kernel: usb 4-1: USB disconnect, device number 3
Jan 14 17:46:31 thishost audit[1391]: DM_CTRL module=crypt op=dtr ppid=1 pid=1391 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pool-udisksd" exe="/usr/libexec/udisks2/udisksd" subj=system_u:system_r:devicekit_disk_t:s0 dev=253:1 error_msg='success' res=1
Jan 14 17:46:31 thishost systemd-homed[1387]: block device /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1 has been removed.
Jan 14 17:46:31 thishost systemd-homed[1387]: block device /sys/devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sda has been removed.
Jan 14 17:46:31 thishost udisksd[1391]: Cleaning up LUKS device /dev/dm-1 (backing device 8:1 no longer exists)
Jan 14 17:46:31 thishost plasmashell[2645]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:128: TypeError: Cannot read property 'defaultActionIcon' of undefined
Jan 14 17:46:31 thishost plasmashell[2645]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:129: TypeError: Cannot read property 'defaultActionText' of undefined
Jan 14 17:46:31 thishost systemd-homed[1387]: block device /sys/devices/virtual/block/dm-1 has been removed.
Jan 14 17:46:31 thishost systemd-homed[1387]: block device /sys/devices/virtual/block/dm-1 has been removed.
Comment 5 Nate Graham 2025-01-16 20:53:18 UTC 
Thanks, can confirm the issue.