[plasma-nm] [Bug 449984] Plasma 5.24.0 NetworkManager cannot get secrets using DBus
https://bugs.kde.org/show_bug.cgi?id=449984 Jonathan Doman changed: What|Removed |Added CC||jonathan.do...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389902] Android Remote Keyboard cannot input Enter/Return in some contexts
https://bugs.kde.org/show_bug.cgi?id=389902 Jonathan Doman changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Jonathan Doman --- I am using the KDE System Tray widget (aka plasmoid): 1. Open Gmail on phone, compose new email, and set focus on main text field. 2. Switch Android keyboard to KDE Connect Remote Keyboard 3. Open PC system tray widget in KDE, set focus to "Remote Keyboard" line input. 4. Press Enter, Enter, Enter Expected Result: Cursor in Gmail app jumps down three lines Actual Result: No effect at all. I don't think I've used this feature since I reported this bug, but I just tested and confirmed the exact same behavior with android app version 1.15.1 and Gmail app 2020.10.18. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391029] Remote control cursor sensitivity is not consistent for different DPI
https://bugs.kde.org/show_bug.cgi?id=391029 --- Comment #2 from Jonathan Doman --- Phone screen. I did not change any settings on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391029] New: Remote control cursor sensitivity is not consistent for different DPI
https://bugs.kde.org/show_bug.cgi?id=391029 Bug ID: 391029 Summary: Remote control cursor sensitivity is not consistent for different DPI Product: kdeconnect Version: unspecified Platform: Android OS: Android 7.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: jonathan.do...@gmail.com Target Milestone: --- KDE Connect v1.7.1, installed from play store Phone: Samsung Galaxy S8 Observed Behavior: When the device's resolution (pixel density) is increased, the remote control cursor sensitivity also increases. Then I have to adjust the plugin settings to decrease sensitivity to get a consistent experience. Expected Behavior: Ideally the app should transmit a constant cursor movement for a constant length input from the touchscreen (i.e. cursor movement should be based on centimeters rather than pixels). This is a really minor issue for me - just thought I'd report it in case it's an easy fix. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 390640] New: Remote control keyboard in android app hard to open
https://bugs.kde.org/show_bug.cgi?id=390640 Bug ID: 390640 Summary: Remote control keyboard in android app hard to open Product: kdeconnect Version: unspecified Platform: Android OS: Android 7.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: jonathan.do...@gmail.com Target Milestone: --- KDE Connect v1.7.1, installed from play store On the remote control screen (to pass input from phone to remote PC), there used to be an icon on the top bar to open the keyboard. Now the keyboard is hidden in the dot menu. I think the button should be restored. A compounding problem is that the keyboard is hidden whenever the screen is turned off. This might be something peculiar to my phone (Samsung Galaxy S8): in all apps, the keyboard is hidden when the screen turns off, and when the screen turns back on, it takes about 0.5 seconds for the input field to be re-focused and the keyboard reopened. But in KDE Connect, the keyboard does not reopen when the screen turns on (probably it doesn't have a normal input field). I like to use the keyboard in short bursts to control (non-mpris) multimedia playback on the remote PC. So when I go to use it, I have to 1) turn on screen, 2) tap dot menu, 3) tap show keyboard. Ideally they keyboard should stay up, removing steps 2+3. But it would be good just to remove step 2. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389902] New: Android Remote Keyboard cannot input Enter/Return in some contexts
https://bugs.kde.org/show_bug.cgi?id=389902 Bug ID: 389902 Summary: Android Remote Keyboard cannot input Enter/Return in some contexts Product: kdeconnect Version: unspecified Platform: Android OS: Android 7.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: jonathan.do...@gmail.com Target Milestone: --- KDE Connect v1.7.1, installed from play store When using the Android Remote Keyboard to pass keyboard input from the Plasmoid text field on PC to an Android app on the phone, the Enter/Return key does not work in some contexts. I noticed this behavior in the Samsung Notes app when editing a new note: Enter key will cause the cursor on the phone to jump from the "Title" field to the "Notes" field - so I know the key is being received. But once in the Notes field, pressing Enter will not create a new line - it does nothing at all. The Gmail app has essentially the same behavior when composing an email: Enter will jump to the next input field, but it will not create newlines within the main text editor. However, most apps work as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 369275] Virtual symlinks to large files are not visible
https://bugs.kde.org/show_bug.cgi?id=369275 --- Comment #6 from Jonathan Doman --- Thanks for that patch. I think you definitely found the bug - I can see the "readlink failed!" warning message in the system journal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 369275] Virtual symlinks to large files are not visible
https://bugs.kde.org/show_bug.cgi?id=369275 Jonathan Doman changed: What|Removed |Added Component|general |general Version|unspecified |5.26.0 Product|dolphin |frameworks-kio CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369275] Virtual symlinks to large files are not visible
https://bugs.kde.org/show_bug.cgi?id=369275
--- Comment #1 from Jonathan Doman ---
After a little debugging, I figured out that dolphin relies on KIO for
directory listings, and I confirmed the bug is in KIO with a simple test
program that basically calls
KCoreDirLister::openUrl("file://.../tmsu-mp/tags/file")
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 369275] New: Virtual symlinks to large files are not visible
https://bugs.kde.org/show_bug.cgi?id=369275 Bug ID: 369275 Summary: Virtual symlinks to large files are not visible Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jonathan.do...@gmail.com Some symlinks are not shown at all in Dolphin, even though they are perfectly visible in Thunar, Konqueror, and ls. I am using Dolphin 16.08.1 (Archlinux packages) to view files on a TMSU (https://github.com/oniony/TMSU) virtual filesystem. TMSU uses tags to generate a virtual hierarchical filesystem, with symlinks pointing to the actual files. Most of these links work fine in Dolphin, but any link pointing to a file bigger than exactly 2 GiB is totally missing. One thing I noticed is that unlike symlinks on a real filesystem which typically have a small size (< 100 B), the symlinks in the TMSU filesystem appear to be the same size as the file they point to, since they only exist in memory and have no disk size. The large files being pointed to show fine in Dolphin, as do symlinks to them made on a normal filesystem. Reproducible: Always Steps to Reproduce: 1. Install TMSU 2. mkdir test; cd test 3. truncate -s 2047M small.file 4. truncate -s 2048M large.file 5. tmsu init 6. tmsu tag --tags="file" *.file 7. mkdir tmsu-mp 8. tmsu mount tmsu-mp 9. ls -l tmsu-mp/tags/file (observe both symlinks) 9. dolphin tmsu-mp/tags/file (observe only 1 symlink to small.file) Actual Results: Dolphin does not show link to large.file Expected Results: Dolphin should show link to large.file, just like ls, Thunar, and Konqueror do. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 Jonathan Doman changed: What|Removed |Added CC||jonathan.do...@gmail.com --- Comment #23 from Jonathan Doman --- I upgraded to plasma-framework 5.18.0-2 and it did not change any behavior for me. I am *never* able to login through SDDM when breeze theme is used (tried up to ten times in a row). -- You are receiving this mail because: You are watching all bug changes.
