[plasmashell] [Bug 466566] Implement optional per-widget min/max sizing feature
https://bugs.kde.org/show_bug.cgi?id=466566 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #14 from mcarans --- (In reply to Nate Graham from comment #12) > Yes, that does sound like a good solution that would solve other problems as > well. Re-opening. I'm really glad you reopened this. I also reported this problem a while back here: https://bugs.kde.org/show_bug.cgi?id=465099 It is not just the Application Launcher that is affected but also other widgets like the Clock, System Monitor and the Workrave Applet. The vertical size of these widgets is far too big for a wide vertical panel (my panel is 200 pixels wide). I really look forward to a solution to this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465099] New: Cannot resize widgets in panel
https://bugs.kde.org/show_bug.cgi?id=465099 Bug ID: 465099 Summary: Cannot resize widgets in panel Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mcar...@yahoo.co.uk CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I am not able to adjust the size of widgets in the panel. STEPS TO REPRODUCE 1. Enlarge panel (eg. mine on right side of screen is 192px) 2. Add widget eg. System Monitor to panel 3. Try to find a way to resize it OBSERVED RESULT No way to resize EXPECTED RESULT Ability to resize SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION A similar issue from 3 years ago says: "The systemmonitor widget has been rewritten from scratch for 5.19, tough some of those issues are still valid, this should probably be closed and reopen for the new version with the issues that still apply" (https://bugs.kde.org/show_bug.cgi?id=420086#c3). Therefore I am creating this new issue as the problem persists. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 482419] New: KDE Connect SMS treats direct chat with one person as a group chat and duplicates messages
https://bugs.kde.org/show_bug.cgi?id=482419 Bug ID: 482419 Summary: KDE Connect SMS treats direct chat with one person as a group chat and duplicates messages Classification: Applications Product: kdeconnect Version: 23.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: mcar...@yahoo.co.uk Target Milestone: --- SUMMARY I have a strange problem with KDE Connect SMS. I am in a direct SMS chat with one person. It isn't a group chat. However KDE Connect SMS treats it as a group chat and includes my phone number as an additional member of the group. What this means is that I get sent a copy of messages direct to my phone number as well as having 2 copies of messages in the "group". How can I fix this? STEPS TO REPRODUCE I have no idea how this chat with one person became a group chat in KDE Connect SMS (but not in Google Messages itself) so I don't know how to reproduce. OBSERVED RESULT Duplicate messages (both for me and the recipient) in the direct chat and an additional SMS sent direct to my phone number. EXPECTED RESULT One message only SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 263174] Fingerprint support for kwallet
https://bugs.kde.org/show_bug.cgi?id=263174 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480466] New: Logging in with fingerprint including unlocking of KWallet not possible
https://bugs.kde.org/show_bug.cgi?id=480466 Bug ID: 480466 Summary: Logging in with fingerprint including unlocking of KWallet not possible Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: mcar...@yahoo.co.uk CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- SUMMARY *** Login with fingerprint and unlocking of KWallet *** STEPS TO REPRODUCE 1. Set up KWallet to unlock with password as outlined here: https://wiki.archlinux.org/title/KDE_Wallet 2. Set up fingerprint under Users in settings (in there it says "Logging into system with your fingerprint is not yet supported") OBSERVED RESULT No option to log into system with my fingerprint. No way to unlock KWallet using fingerprint let alone do it on login. EXPECTED RESULT Fingerprint logs in and unlocks KWallet automatically SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.1112.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480466] Logging in with fingerprint including unlocking of KWallet not possible
https://bugs.kde.org/show_bug.cgi?id=480466 --- Comment #2 from mcarans --- (In reply to Joshua Goins from comment #1) > Am I understanding correctly that you tried to log into the system with your > fingerprint, despite the message saying that "Logging into system with your > fingerprint is not yet supported"...? I could not find an issue to track progress towards when it will be supported so this could be the issue for that. Also I wanted to include the fact that KWallet should be unlocked otherwise logging in with fingerprint is not particularly useful as you would then anyway have to type the password to unlock KWallet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480466] Logging in with fingerprint including unlocking of KWallet not possible
https://bugs.kde.org/show_bug.cgi?id=480466 --- Comment #4 from mcarans --- (In reply to Nate Graham from comment #3) > Right, this isn't implemented in SDDM yet. And SDDM is not a KDE project. > You can follow https://github.com/sddm/sddm/issues/284 to be notified when > it eventually (hopefully) gets implemented. Thanks! I understand SDDM is planned to become a KDE project in time from this comment: https://www.reddit.com/r/kde/comments/1afnw4r/comment/kobo5si/?utm_source=reddit&utm_medium=web2x&context=3 although if SDDM development ends up requiring too many resources, I wonder if it would be feasible to switch to another DM that is well maintained? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps due to lack of /usr/share/applications/kde-mimeapps.list file installed by default
https://bugs.kde.org/show_bug.cgi?id=305136 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #30 from mcarans --- (In reply to David Faure from comment #27) > The idea was that it's fine for Gnome to ignore our InitialPreference and > it's fine for KDE to ignore Gnome's global file, since we want different > defaults. But Gnome's global file was supposed to be called > gnome-mimeapps.list, not defaults.list. I find that double clicking a deb file in the Firefox download manager opens Ark. I understand from this Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1304650 that Firefox uses g_app_info_get_default_for_type to work out what to open. What should I change to make the correct application open when I double click deb in the Firefox download manager? I have a file /usr/share/applications/defaults.list in my distro (Kubuntu) if that's any help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 305136] File associations are broken in gtk/glib apps due to lack of /usr/share/applications/kde-mimeapps.list file installed by default
https://bugs.kde.org/show_bug.cgi?id=305136 --- Comment #32 from mcarans --- (In reply to Pols12 from comment #31) > (In reply to mcarans from comment #30) > > What should I change to make the correct application open when I double > > click deb in the > > Firefox download manager? I have a file > > /usr/share/applications/defaults.list in my distro > > (Kubuntu) if that's any help. > > If I remember correctly, KDE well edits `$HOME/.config/mimeapps.list` when > you customize your file associations. So, from ComponentChooser or from > Dolphin, change the default application for .deb, then change back to your > wanted application. I think that will solve your issue. I forgot to add that KDE itself opens the correct application. It is Firefox that opened the wrong one. However, I was alerted on r/kde to the Firefox config settings: widget.use-xdg-desktop-portal* which if all set to 1 force the use of portal and hence KDE associations. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461561] New: Confusing default device in Display Configuration when using monitor with laptop screen disabled
https://bugs.kde.org/show_bug.cgi?id=461561 Bug ID: 461561 Summary: Confusing default device in Display Configuration when using monitor with laptop screen disabled Classification: Plasma Product: KScreen Version: 5.26.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: mcar...@yahoo.co.uk Target Milestone: --- Created attachment 153563 --> https://bugs.kde.org/attachment.cgi?id=153563&action=edit Display Configuration for disabled laptop, enabled monitor SUMMARY The display information in Display Configuration is confusing because with an external monitor enabled and laptop screen disabled, by default on launch, the options shown are for the disabled laptop screen not the enabled monitor. STEPS TO REPRODUCE 1. Open System Settings -> Display Configuration 2. Enable monitor 3. Disable laptop 4. Close Display Configuration 5. Reopen System Settings -> Display Configuration OBSERVED RESULT When the Display Configuration is subsequently opened, it shows the disabled laptop (built in) display by default not the actually enabled display (monitor). EXPECTED RESULT Show the enabled display's configuration options by default SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 with KDE backports (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I have included a screenshot of what is shown on launching the Display Configuration. The BenQ GW2765 as my external monitor. However, by default, "Built-in Screen" is selected under Device. I was confused for a while wondering why the resolution listed did not match the monitor. It was not obvious to me that the wrong Device was selected. I think it would be best to default to showing the enabled screen, but failing that, an obvious visual cue (like showing the laptop screen greyed out at the top under "Drag screens to rearrange them") would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461567] New: Allow middle button single click to act like left button double click
https://bugs.kde.org/show_bug.cgi?id=461567 Bug ID: 461567 Summary: Allow middle button single click to act like left button double click Classification: Applications Product: systemsettings Version: 5.26.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: mcar...@yahoo.co.uk Target Milestone: --- SUMMARY I would like to be able to use my middle mouse button to double click so that a single click of it acts like a double click of the left button. STEPS TO REPRODUCE 1. Open mouse configuration OBSERVED RESULT There is no option to use the middle button as a double click EXPECTED RESULT Option to use middle button as double click SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I udnerstand that KDE 5.26 allows mapping of additional mouse buttons, but I don't see that option presumably because the middle button doesn't count as an additional mouse button. I think that either the middle mouse button could be treated like an additional mouse button with the option to map it to double click (or "open file or folder"). Alternatively, like the option "Press left and right button for middle click" there could be "Press middle button for double click". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #56 from mcarans --- I am running KDE Frameworks 5.99.0 and I think the problem I am having could be related. To prevent being asked for my ssh passphrase, I have an autostart .desktop file that launches /usr/bin/ssh-add -k PATH_TO_SSH_KEY. However, I could only make it work by launching after a delay rather than immediately. Similarly I have set up Skype to launch after a delay, otherwise it closes after starting. I can see Skype credentials in KWalletManager. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461123] When waking from standby or leaving the screenlocker a blackscreen shows "The screen locker is broken and unlocking is not possible anymore"
https://bugs.kde.org/show_bug.cgi?id=461123 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #8 from mcarans --- I have seen this error as well. I am running Kubuntu 22.10 with KDE Plasma 5.26.3, KDE Frameworks 5.99.0, Qt 5.15.6 and I am using Wayland. Here is some output from kscreenlocker_greet: > /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing > kf.kirigami: Failed to find a Kirigami platform plugin > Locked at 1668456920 > qt.qpa.wayland: Wayland does not support QWindow::requestActivate() -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461123] When waking from standby or leaving the screenlocker a blackscreen shows "The screen locker is broken and unlocking is not possible anymore"
https://bugs.kde.org/show_bug.cgi?id=461123 --- Comment #15 from mcarans --- (In reply to hiraniu from comment #14) > For people that just stumble over this thread looking for a solution: Switch > to X11 while in the lock screen after a reboot, that fixed the problem > entirely for me. Not the solution we hope for, but maybe a band-aid for now. Do you mean you switched from Wayland to x11 permanently to fix the problem or that after switching to x11 and then switching back to Wayland, you don't get the errors from kscreenlocker_greet any more? If the latter, can you tell me step by step what you did? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406450] "Remote" and "Recent" sections and "Trash" entry are missing in file open/save dialogs started by non-KDE Qt5 apps
https://bugs.kde.org/show_bug.cgi?id=406450 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #11 from mcarans --- I added a "place" in Dolphin that doesn't show up under places in either the Kate or Chrome save dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406450] "Remote" and "Recent" sections and "Trash" entry are missing in file open/save dialogs started by non-KDE Qt5 apps
https://bugs.kde.org/show_bug.cgi?id=406450 --- Comment #12 from mcarans --- (In reply to mcarans from comment #11) > I added a "place" in Dolphin that doesn't show up under places in either the > Kate or Chrome save dialog. Actually this is a different bug since I see earlier the reporter compared with Kate. I will make a new issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462221] New: Place added in Dolphin not showing in save dialog (eg. in Kate, Chrome)
https://bugs.kde.org/show_bug.cgi?id=462221
Bug ID: 462221
Summary: Place added in Dolphin not showing in save dialog (eg.
in Kate, Chrome)
Classification: Frameworks and Libraries
Product: frameworks-kio
Version: 5.100.0
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Open/save dialogs
Assignee: kio-bugs-n...@kde.org
Reporter: mcar...@yahoo.co.uk
CC: kdelibs-b...@kde.org
Target Milestone: ---
Created attachment 154007
--> https://bugs.kde.org/attachment.cgi?id=154007&action=edit
Dolphin and File Save Dialog (missing "Programming")
SUMMARY
I added a Place in Dolphin and it doesn't show in file save dialogs like those
in Kate or Chrome.
STEPS TO REPRODUCE
1. Create Place in Dolphin
2. Save a file in Kate or Chrome
3. Look under Places in th save dialog
OBSERVED RESULT
Default Places show
EXPECTED RESULT
Default Places + the one I added in Dolphin ("Programming" in the attached
example)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.10
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.6
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 462221] Place added in Dolphin not showing in save dialog (eg. in Kate, Chrome)
https://bugs.kde.org/show_bug.cgi?id=462221
--- Comment #1 from mcarans ---
Created attachment 154014
--> https://bugs.kde.org/attachment.cgi?id=154014&action=edit
Start Menu - Places missing place added in Dolphin
Also the Start Menu's Places seems to be missing the place added in Dolphin
("Programming")
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 484801] Multiple enter presses required to unlock screen following password entry
https://bugs.kde.org/show_bug.cgi?id=484801 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #2 from mcarans --- This happens for me in Plasma 6.1.5. I unlock with fingerprint rather than password and then get an unnecessary unlock button that I have to click. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497904] Additional "Unlock" button after fingerprint login
https://bugs.kde.org/show_bug.cgi?id=497904 --- Comment #1 from mcarans --- Same issue for me: Operating System: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-13-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS with Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: LENOVO Product Name: 82Y5 System Version: Legion Slim 5 14APH8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497904] Additional "Unlock" button after fingerprint login
https://bugs.kde.org/show_bug.cgi?id=497904 --- Comment #4 from mcarans --- Created attachment 177218 --> https://bugs.kde.org/attachment.cgi?id=177218&action=edit Recording of unlocking (In reply to Niccolò Venerandi from comment #3) > May I ask you for a recording? Please find attached a recording. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #25 from mcarans --- This issue persists after upgrading to Kubuntu 25.04. KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.14.0-15-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504641] New: System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4)
https://bugs.kde.org/show_bug.cgi?id=504641 Bug ID: 504641 Summary: System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4) Classification: Plasma Product: plasmashell Version First 6.3.4 Reported In: Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor widgets Assignee: plasma-b...@kde.org Reporter: mcar...@yahoo.co.uk CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY Every time I boot, the system monitor sensors I have set up are gone. This has happened since upgrading to Kubuntu 25.04 which has KDE Plasma 6.3.4. I have tried removing the widget altogether and then adding a new system monitor sensor widget. I've also tried clicking "Save Settings as Preset" but that doesn't make any difference. Is there any way to get them to be retained? STEPS TO REPRODUCE 1. Install Kubuntu 25.04 2. Add system monitor widget 3. Set up CPU usage or whatever 4. Reboot OBSERVED RESULT Sensors are gone - just a blank System Monitor Sensor widget remains EXPECTED RESULT Sensors are retained SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Kubuntu 25.04 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504641] System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4)
https://bugs.kde.org/show_bug.cgi?id=504641 --- Comment #2 from mcarans --- (In reply to Nate Graham from comment #1) > > 3. Set up CPU usage or whatever > Can you please be specific about exactly how you're setting it up? It's > possible that this is a key part of what causes the issue. Thanks for your reply. Here are the steps I tried: 1. Right click on widget 2. Select "Configure System Monitor Sensor..." 3. Under Appearance, choose Display Style "Line Chart" and Apply 4. Under Sensor Details - Sensors click cpu - all - Total Usage (%), cpu - all - Maximum CPU Temperature (C) and memory - physical - Used Physical Memory Percentage (%) 5. Click Apply - sensors appear in widget and are functioning fine 6. Under Appearance, click Save Settings As Preset (I've tried with and without this step) 7. Reboot 8. Sensor(s) are gone -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504641] System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4)
https://bugs.kde.org/show_bug.cgi?id=504641 --- Comment #3 from mcarans --- I posted on r/kubuntu to see if anyone else has this issue and it looks like I am not the only one: https://www.reddit.com/r/Kubuntu/comments/1ksbnn7/system_monitor_sensors_wont_save_in_2504/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499637] Lockscreen sometimes prompts for password immediately after locking, and sometimes doesn't
https://bugs.kde.org/show_bug.cgi?id=499637 --- Comment #25 from mcarans --- The temporary fix works for me on Kubuntu 25.04 (KDE Plasma Version: 6.3.4, KDE Frameworks Version: 6.12.0, Qt Version: 6.8.3) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 505222] New: Fingerprint unlock rarely works after upgrade to Plasma 6.3.4
https://bugs.kde.org/show_bug.cgi?id=505222 Bug ID: 505222 Summary: Fingerprint unlock rarely works after upgrade to Plasma 6.3.4 Classification: Plasma Product: plasmashell Version First 6.3.4 Reported In: Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Screen locking Assignee: plasma-b...@kde.org Reporter: mcar...@yahoo.co.uk Target Milestone: 1.0 SUMMARY With Kubuntu 24.10, I could lock the screen, leave it for a while, come back and unlock with fingerprint. After upgrading to Kubuntu 25.04, I can only log in with password in that case, but fingerprint works for sudo and sometimes works for immediate unlock after window-L lock. STEPS TO REPRODUCE 1. /etc/pam.d/kde looks like this: authsufficient pam_fprintd.so authsufficient pam_unix.so try_first_pass likeauth nullok Actually I have a slightly more sophisticated setup whereby login uses password and does not use the fingerprint (because it won't unlock KWallet) but screen lock and sudo use fingerprint first falling back on password. This is described in detail here: https://www.reddit.com/r/Kubuntu/comments/1aew6t3/comment/kodetid/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button 2. Test unlocking after sleep OBSERVED RESULT With Kubuntu 25.04 (Plasma 6.3.4), it doesn't work, but fingerprint for sudo works fine and window key-L to lock and immediate unlock sometimes works. EXPECTED RESULT With Kubuntu 24.10, it worked reliably ie. fingerprint works for immediate unlock and unlock after sleep as well as sudo. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 25.04 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484363] Sometimes screen locker fails to unlock screen and shows "Unlock" button that does nothing
https://bugs.kde.org/show_bug.cgi?id=484363 --- Comment #28 from mcarans --- Bug 'Additional "Unlock" button after fingerprint login' (https://bugs.kde.org/show_bug.cgi?id=497904) has been marked as a duplicate although it's not quite the same. It is probably related though and since it should be easier to reproduce than this one (since it happens all the time), it may be that fixing it fixes this bug too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 492565] Calibrate Controller button is missing.
https://bugs.kde.org/show_bug.cgi?id=492565 mcarans changed: What|Removed |Added CC||mcar...@yahoo.co.uk --- Comment #2 from mcarans --- (In reply to Nate Graham from comment #1) > AFAIK the feature was removed the the documentation is just out of date. In the absence of this feature, the best way to calibrate looks like to use jstest-gtk. It's a shame that there doesn't seem to be a KDE app for controller calibration now that this button has been removed. This seems like a regression albeit an intentional one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 504641] System monitor sensor config won't save. Blank widget after reboot (Plasma 6.3.4)
https://bugs.kde.org/show_bug.cgi?id=504641 --- Comment #5 from mcarans --- Interestingly, I'm still on Plasma 6.3.4 but a recent upgrade (I think of the Nvidia drivers) seems to have fixed it. -- You are receiving this mail because: You are watching all bug changes.
