[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 --- Comment #1 from Thomas H. --- Might also be related to this issue: https://bugs.kde.org/show_bug.cgi?id=248222 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 395023] New: $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 Bug ID: 395023 Summary: $topdir/.Trash not created or used on btrfs sub-volumes Product: frameworks-kio Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Trash Assignee: fa...@kde.org Reporter: commander.sirow+...@googlemail.com CC: kdelibs-b...@kde.org Target Milestone: --- It seems like kio does neither create nor detect existing $topdir/.Trash(-$uid) directories as mandated by the freedesktop.org trash specification when it comes to btrfs subvolumes. This is problematic because it means files will to be moved across subvolume boundaries, which means the files will actually be copied to ~/.local/share/Trash (and deleted in its original location afterwards). Eg. with the following btrfs layout: /dev/sda1 - @root (btrfs subvolume mounted to /) - @home (btrfs subvolume mounted to /home) - @workspace (btrfs subvolume mounted to /home/Workspace) And file-system layout /bin /boot [...] /home /home/Documents /home/Downloads [...] /home/Workspace /home/Workspace/.Trash (Permissions: drwxrwxrwt) /home/.local/share/Trash [...] /.Trash (Permission: drwx-T) [...] When deleting a file under workspace it will actually be moved (across the subvolume boundary) into /home/.local/share/Trash and not /home/Workspace/.Trash My guess is that kio does not "detect" (or treat) btrfs subvolumes as individual partions, thus there is no check happening. (Compare LVM issue described here: https://bugs.kde.org/show_bug.cgi?id=178479) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383962] The Num Block key status isn't remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=383962 Thomas H <iamtomhan...@gmail.com> changed: What|Removed |Added CC||iamtomhan...@gmail.com --- Comment #2 from Thomas H <iamtomhan...@gmail.com> --- I found some discussion of this and a temporary workaround on this thread: https://forum.kde.org/viewtopic.php?f=289=133089 Add a "Numlock=on" string inside /etc/sddm.conf -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381822] Akregator corrupts the opml file and crashes, always.
https://bugs.kde.org/show_bug.cgi?id=381822 Thomas H <iamtomhan...@gmail.com> changed: What|Removed |Added CC||iamtomhan...@gmail.com --- Comment #1 from Thomas H <iamtomhan...@gmail.com> --- There are a few recent duplicates of this same bug: https://bugs.kde.org/show_bug.cgi?id=383719 https://bugs.kde.org/show_bug.cgi?id=381929 https://bugs.kde.org/show_bug.cgi?id=378513 As one user mentioned, the frustrating part is that it attempts to save a backup to ~/.local/share/akregator/data//feeds.opml, but even that file is corrupted. All feeds are lost and replaced with the default feeds. I'm on KDE Neon user edition. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379524] Fontsettings crashes/stalls when installing/deleting multiple system fonts
https://bugs.kde.org/show_bug.cgi?id=379524 --- Comment #4 from Thomas H <iamtomhan...@gmail.com> --- After a few minutes more, this bug is avoidable if you run the Font Manager as a super user. In a terminal, run "sudo kcmshell5 fontinst" and voila, none of these issues occur. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379524] Fontsettings crashes/stalls when installing/deleting multiple system fonts
https://bugs.kde.org/show_bug.cgi?id=379524 Thomas H <iamtomhan...@gmail.com> changed: What|Removed |Added CC||iamtomhan...@gmail.com --- Comment #3 from Thomas H <iamtomhan...@gmail.com> --- Same issue here on the most recent update of KDE Neon user edition. I also occasionally experience the fontinst message getting stuck at 100% upon completion. Another issue with the font manager: After disabling a font, the font list is re-sorted and the first item is highlighted, regardless of previous position or sorting. -- You are receiving this mail because: You are watching all bug changes.
