#trinity-desktop < 2026/06/14 >
[02:55]micheleC has joined
[04:17]068AAR6YA has joined
[04:17]020AASOC0 has joined
[04:17]068AAR6YA has quit (Remote host closed the connection)
[04:17]020AASOC0 has quit (Remote host closed the connection)
[04:21]micheleC has quit (Ping timeout: 252 seconds)
[04:23]a-865 has quit (Ping timeout: 246 seconds)
[04:41]a-865 has joined
[05:19]inverted_rabbit has left (Disconnected: Hibernating too long)
[05:25]micheleC has joined
[05:57]ccx has quit (Ping timeout: 245 seconds)
[06:21]ccx has joined
[06:56]micheleC has quit (Read error: Connection reset by peer)
[07:05]micheleC has joined
[07:20]tde-bot has joined
[07:20]tde-bot started logging
[08:20]a-865 has quit (Ping timeout: 246 seconds)
[08:36]a-865 has joined
[09:21]ElCaracho has joined
[09:21]ElCaracho has quit (Changing host)
[09:21]ElCaracho has joined
[09:51]micheleC has quit (Ping timeout: 245 seconds)
[11:17]SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[11:52]micheleC has joined
[12:59]SlavekB has joined
[14:31]micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[15:37]ceux: morning
[15:37]ceux: will try to review the kdf feedback today
[15:51]ceux: oh found a nasty one
[15:52]ceux: check it: https://drop.ceux.org/shots/2026-06-14-115154_scrot.png
[15:52]ceux: udisks parsing issue? not sure.
[16:22]SlavekB: There is a flaw in tdehw-lib in detecting mounted devices. It reads /proc/mounts where a different device name - for example a symlink - may be used than the actual device node.
[16:23]SlavekB: Therefore, some devices appear as if they are not mounted, although they are actually mounted.
[16:23]ceux: ah so it is already mounted well... hum
[16:23]ceux: its not really mounted, its active...
[16:24]ceux: i dont know how to say this, its a luks device, so its in use as /dev/mapper/luks-root
[16:24]ceux: or... yeah i dont know lol
[16:25]SlavekB: For example, on my Pinebook the root partition is mounted as device /dev/root in the ramdisk, but the actual /dev/mmcblk1p2 appears to be unmounted.
[16:25]ceux: where does it get the device list from?
[16:25]ceux: i ask that because - maybe dm devices should be ignored? its a block device not a filesystem
[16:25]ceux: it's like listing /dev/sda instead of /dev/sda1
[16:26]ceux: the crypt device can have one ore more filesystems under it (if I understand it right)
[16:27]SlavekB: The device manager must react to everything - this also allows for invoking LUKS unlocking and subsequently mounting the resulting device => it can be just some "DM" with a real file system.
[17:04]ceux: thats a good point. I manage most of that from the /etc/fstab and /etc/cryptsetup so i think it may not be so relevant for me
[17:04]ceux: makes sense thanks SlavekB
[21:21]ccx has quit (Remote host closed the connection)
[21:21]ccx has joined
[22:16]SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[22:51]SlavekB has joined

#trinity-desktop < 2026/06/14 >