[plasmashell] [Bug 488593] Default language on login screen is not English, that prevents to fill English password field.
https://bugs.kde.org/show_bug.cgi?id=488593 Jiří Wolker changed: What|Removed |Added CC||kde-de...@jwo.cz --- Comment #1 from Jiří Wolker --- I am quite certain that this should be marked as SDDM issue (not PlasmaShell), maybe this can be related to multiple components. Could someone check that and change the Product/Component values on this bugreport appropriately? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488585] Shift-Return in KDE Connect SMS inserts newline at the end of field, not at cursor location
https://bugs.kde.org/show_bug.cgi?id=488585 Jiří Wolker changed: What|Removed |Added CC||kde-de...@jwo.cz -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488585] New: Shift-Return in KDE Connect SMS inserts newline at the end of field, not at cursor location
https://bugs.kde.org/show_bug.cgi?id=488585 Bug ID: 488585 Summary: Shift-Return in KDE Connect SMS inserts newline at the end of field, not at cursor location Classification: Applications Product: kdeconnect Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: kde-de...@jwo.cz Target Milestone: --- SUMMARY When composing a message in KDE Connect SMS app, pressing Shift-Return in the message input field should insert the newline at the location of the cursor, replacing the selection if a selection is not empty, as many other messaging apps do. Related source code part: https://invent.kde.org/network/kdeconnect-kde/-/blob/master/smsapp/qml/SendingArea.qml?ref_type=heads#L87 STEPS TO REPRODUCE 1. Start writing a new SMS. 2. Enter some text (≥ 2 chars) to the field. 3. Place the cursor at any position except the end. 4. Press Shift-Return. OBSERVED RESULT A newline is appended to the complete end of the message. EXPECTED RESULT The newline should be placed at the cursor, replacing the selection (if applicable). SOFTWARE/OS VERSIONS KDE Connect 24.05.1 (currently version) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 460099] Mouse icon change inside portal open/save dialogs
https://bugs.kde.org/show_bug.cgi?id=460099 Jiří Wolker changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED CC||wolj...@gmail.com --- Comment #1 from Jiří Wolker --- Could you attach an screenshot or provide more detailed description of the problem? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416271] Setting to not remember recent documents confusingly lives in the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=416271 Jiří Wolker changed: What|Removed |Added CC||wolj...@gmail.com --- Comment #8 from Jiří Wolker --- (In reply to Méven Car from comment #7) > I propose to move the PrivacyTab to a full fledge KCM and rename it to > Recent Files. I would also add some kind of control that allows choosing whether the configuration affects all activities (+ apps that are not aware of activities) or only the selected (in the KCM) activity to kee the current functionality. I would also add some notice, at least to the activity-specific config, something like “Not all applications will respect these settings.”. There is a lot of apps that simply do not respect that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455669] Password field becomes active when password checking takes a lot of time
https://bugs.kde.org/show_bug.cgi?id=455669 --- Comment #2 from Jiří Wolker --- (In reply to Nate Graham from comment #1) > What version of Plasma are you using? Is this a regression from previous > Plasma versions? > > Also, what distro are you using? Gentoo. And I now realized that I forgot updating Plasma for a while. I think that you can mark this as a duplicate/not-a-bug until I update it and eventually provide more information. I am sorry. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455672] New: Gesture to unlock the screen
https://bugs.kde.org/show_bug.cgi?id=455672 Bug ID: 455672 Summary: Gesture to unlock the screen Product: kscreenlocker Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wolj...@gmail.com CC: bhus...@gmail.com Target Milestone: --- Many people use so called gestures on Android to protect their devices. The user interface is designed to be used on touchscreens. It shows 3×3 grid of dots that can be connected by a line drawn by a finger or mouse pointer. I suggest adding option to protect the session using the gesture, maybe with user-configurable size of the grid. This could be done completely independently of the OS's authentication model (PAM etc.). On login, normal system password would be used, but then, for unlocking the screen (i.e. not by DM), the gesture could be used instead. The question is, how to store the gesture data? Plaintext (mode 600 file in home directory) should be safe enough, because whoever has access to the disk can change the even other files and access user data. A file encrypted by user's password would be better. A notice about that the gestures are not very secure would not be bad. Also, other “alternative” unlocking methods could be added: e.g. PIN. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 411698] Allow setting custom password
https://bugs.kde.org/show_bug.cgi?id=411698 Jiří Wolker changed: What|Removed |Added CC||wolj...@gmail.com --- Comment #2 from Jiří Wolker --- That sounds very much like having a PIN or gesture like on Android OS. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455670] New: Hide the password field when the password is being processed
https://bugs.kde.org/show_bug.cgi?id=455670 Bug ID: 455670 Summary: Hide the password field when the password is being processed Product: kscreenlocker Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: wolj...@gmail.com CC: bhus...@gmail.com Target Milestone: --- The password field on the lockscreen should disapprear while the password is being processed. I find it uncomfortable looking at the field with password length visible for other people. The hardware on which the Plasma runs is quite slow, therefore the password field is shown for several seconds. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455669] New: Password field becomes active when password checking takes a lot of time
https://bugs.kde.org/show_bug.cgi?id=455669 Bug ID: 455669 Summary: Password field becomes active when password checking takes a lot of time Product: kscreenlocker Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: wolj...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When I lock the screen in KDE and then I type the password, its processing takes tens of seconds (that is related to PAM, not KDE software). When the password processing starts, the password field becomes inactive (changes appearance and behavior, it does not respond to input). The problem is that is becomes active (and empty) again after some time, but before the screen is finally unlocked. I think that there is some timer implemented that makes the password field active, regardless of that the screen will unlock just few seconds after that. The specific hardware is quite slow. I expect the field to be inactive until the lockscreen disappears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455104] Please consider not entering a space character when space bar is pressed to wake up the login screen
https://bugs.kde.org/show_bug.cgi?id=455104 Jiří Wolker changed: What|Removed |Added CC||wolj...@gmail.com --- Comment #5 from Jiří Wolker --- (In reply to Rodney Gedda from comment #4) > In fact, pressing any character key inputs that character, not just space. > > So I would recommend using any keyboard input to "wake up" first then land > you in the password input field. > > How many people would actually want to start typing in their password before > they can see the characters being entered? I strongly disagree with you. I am one of the people who just sit down at the computer and type in the password while the screen is off (or showing the clock with password field hidden), if I think it is safe. I am a bit more comfortable with just typing the password, without doing anything else. If your suggestion would become implemented, it could take me probably weeks to re-learn the login procedure. For me, it is “reflex action”. I do not think about that I am going to enter the password. I simply see the login screen on my computer, type the password and hit return as if it would be a single operation. My suggestion is: Add an option to the system settings for that. Maybe three options: type immediately everything, ignore whitespace chars, and do not type the first char (when the password field is hidden). And there is also another reason for not-ignoring the first keypress: With some screens, it really takes ages (relatively: tens of seconds) to bring them back to working state when they are turned off using DPMS. Imagine the user that presses a key, waits for the screen to show the password field and then typing the password instead of just typing it and letting the screen to start up while they are typing. When done frequently, it can take a lot of time. There is one operating system that does this thing in the worst possible way: You press a key, then the user must wait for the password field and only then the operating system responds to the user's input. When the password is typed before the field is shown, some characters are dropped or even typed at wrong position (!). -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441529] Don't show welcome screen while loading archive
https://bugs.kde.org/show_bug.cgi?id=441529 --- Comment #2 from Jiří Wolker --- (In reply to Albert Astals Cid from comment #1) > Jiří can you have a look? The changes are ready to be merged. https://invent.kde.org/utilities/ark/-/merge_requests/62 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441529] Don't show welcome screen while loading archive
https://bugs.kde.org/show_bug.cgi?id=441529 Jiří Wolker changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|wolj...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441529] Don't show welcome screen while loading archive
https://bugs.kde.org/show_bug.cgi?id=441529 Jiří Wolker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
