[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 --- Comment #15 from bugreporter42 --- (In reply to bugreporter42 from comment #14) > Me too. Global shortcuts initially work, but after a reboot they likely > disappear/stop working. That's been broken since Arch switched to Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 bugreporter42 changed: What|Removed |Added CC||bugreporte...@protonmail.co ||m --- Comment #14 from bugreporter42 --- Me too. Global shortcuts initially work, but after a reboot they likely disappear/stop working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486509] Broken icon scaling with panel.
https://bugs.kde.org/show_bug.cgi?id=486509 bugreporter42 changed: What|Removed |Added Summary|Broken icon scaling.|Broken icon scaling with ||panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486509] Broken icon scaling.
https://bugs.kde.org/show_bug.cgi?id=486509 --- Comment #1 from bugreporter42 --- Created attachment 169141 --> https://bugs.kde.org/attachment.cgi?id=169141&action=edit This is what a working setup with Plasma 5 looks like. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486509] New: Broken icon scaling.
https://bugs.kde.org/show_bug.cgi?id=486509 Bug ID: 486509 Summary: Broken icon scaling. Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bugreporte...@protonmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 169140 --> https://bugs.kde.org/attachment.cgi?id=169140&action=edit Panel screenshot The icon scaling in a vertical panel is broken. When the panel width is increased, icons scale to an insane size (see attachment). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388071] KMountPoint doesn't handle bind mounts correctly, breaks Trash
https://bugs.kde.org/show_bug.cgi?id=388071 --- Comment #1 from bugreporter42 --- Bug 349617 is related. If Solid was able to report the correct mount point for devices, it might make sense to take the device id from the file and use Solid to determine the mount paths based on the device id. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388071] New: KMountPoint doesn't handle bind mounts correctly, breaks Trash
https://bugs.kde.org/show_bug.cgi?id=388071
Bug ID: 388071
Summary: KMountPoint doesn't handle bind mounts correctly,
breaks Trash
Product: frameworks-kio
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: bugreporte...@protonmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
KMountPoint doesn't determine the correct mount point, if there are bind
mounts. This breaks the Trash handling, files from other devices are moved to
the home directory trash folder instead of the trash folder on the other
device.
dd if=/dev/zero of=/tmp/test-disk1 bs=1024 count=1
dd if=/dev/zero of=/tmp/test-disk2 bs=1024 count=1
mkfs.ext4 /tmp/test-disk1
mkfs.ext4 /tmp/test-disk2
mkdir /mnt/test-disk1
mkdir /mnt/test-disk2
mount -o loop /tmp/test-disk1 /mnt/test-disk1
mount -o loop /tmp/test-disk2 /mnt/test-disk2
mkdir -p /mnt/test-disk1/aaa
mkdir -p /mnt/test-disk2/aaa/bbb
touch /mnt/test-disk2/aaa/bbb/file
mount --bind /mnt/test-disk2/aaa/bbb /mnt/test-disk1/aaa
Stat:
# stat /mnt/test-disk1
File: /mnt/test-disk1
Size: 1024Blocks: 2 IO Block: 1024 directory
Device: 701h/1793d Inode: 2 Links: 4
# stat /mnt/test-disk2
File: /mnt/test-disk2
Size: 1024Blocks: 2 IO Block: 1024 directory
Device: 702h/1794d Inode: 2 Links: 4
# stat /mnt/test-disk1/aaa/file
File: /mnt/test-disk1/aaa/file
Size: 0 Blocks: 0 IO Block: 1024 regular empty file
Device: 702h/1794d Inode: 13 Links: 1
--
KMountPoint::currentMountPoints():
#include
#include
int main() {
const QString origPath = "/mnt/test-disk1/aaa/file";
KMountPoint::Ptr mp =
KMountPoint::currentMountPoints().findByPath(origPath);
qDebug() << mp->mountPoint();
}
---
Which returns: "/mnt/test-disk1/aaa", while the file resides on test-disk2.
People complaining about Trash not working correctly:
https://www.reddit.com/r/kde/comments/59cefq/are_there_options_to_manage_how_the_trash_is/
--
You are receiving this mail because:
You are watching all bug changes.
[kio] [Bug 349617] Clicking on device of which a subdir is bound opens that bound subdir instead of the device's root
https://bugs.kde.org/show_bug.cgi?id=349617 --- Comment #10 from bugreporter42 --- udisks2 bug report: https://github.com/storaged-project/udisks/issues/478 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 349617] Clicking on device of which a subdir is bound opens that bound subdir instead of the device's root
https://bugs.kde.org/show_bug.cgi?id=349617 bugreporter42 changed: What|Removed |Added CC||bugreporte...@protonmail.co ||m --- Comment #9 from bugreporter42 --- It's still broken. This looks non-trivial to fix, the udisks2 interfaces don't appear to have the required information in a reasonably digestable form. org.freedesktop.UDisks2.Filesystem has a MountPoints property that returns an alphabetically sorted list of mountpoints for a block device, including bind mounts. As far as I can tell, it's impossible to tell which of the mountpoints in the list is the mount point where the device was mounted using the udisks2 interfaces. (You can do a 'udisksctl dump' to get the info udisks2 provides.) -- You are receiving this mail because: You are watching all bug changes.
