fingerprint working on F40 kde?
by Neal Becker
In the past kde did not support unlocking the screen using fingerprint.
Now that we are on F40 I decided to try again. I was able to enroll a
fingerprint but when I try to use it to unlock the screen nothing happens.
Is this supposed to work?
Thanks,
Neal
4 hours, 3 minutes
window sharing stopped working
by Neal Becker
With recent updates on F40 on kde+wayland I cannot share a window in a
meeting anymore. When this option is selected a black window is shown in
the preview and to the other side of the conversation. Fortunately,
sharing the entire screen still works.
2 days, 15 hours
Notifications - fails to hide when no unread notifications
by John Horne
Hello,
Using plasma6/wayland I recently upgraded from Fedora 39 to Fedora 40. No
problems with that, however I have noticed that when a notification occurs a
pop appears (as it should), if I then clear/close the notification the popup
window remains saying "No unread notifications".
The issue is that the popup remains unless I click on something (e.g konsole),
it then hides itself. I am fairly sure that under F39 and before, if there were
no unread notifications then the popup itself would automatically hide itself
(after the relevant time). The hide popup configuration setting is set to 5
seconds.
So, do others see this too? Am I right that the popup used to automatically
hide itself (after 5 seconds in my case) if there were no unread notifications?
I have tried to find if this has already been reported, and it doesn't seem to
have been, so before doing so I just want to make sure that it is something
that has changed.
Thanks,
John.
--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
________________________________
[https://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
6 days, 15 hours
Default keyboard layout
by Patrick O'Callaghan
I use two kb layouts, UK and UK+International (for accents etc.). Up to
F39 the default layout on login has always been the former, but now
it's the latter, meaning I often have to edit text when I notice, and I
sometimes don't notice.
Where can I set the default layout?
poc
1 week, 2 days
Assistance with SSH Key Integration with KDE Wallet
by Lukas Ruzicka
Dear Fedora KDE team,
I am reaching out for assistance with an issue I'm encountering regarding
the storage of SSH key passwords in the KDE Wallet. I have set up my
environment to prompt for my SSH key password using a graphical dialog, but
I am facing difficulties with having the password stored or reused by KDE
Wallet.
1.
*Configuration Details*: I have configured my system by setting the
SSH_ASKPASS and SSH_ASKPASS_REQUIRE environment variables in
~/.config/environment.d/ssh_askpass.conf with the following contents
SSH_ASKPASS=/usr/bin/ksshaskpass
SSH_ASKPASS_REQUIRE=prefer
This setup successfully triggers a dialog box asking for my SSH key
password.
2.
*Issue*: Although the dialog appears and allows me to enter my password,
it does not store the password in the KDE Wallet, nor does it seem to
retrieve or use any stored passwords from there.
3.
*Current Workaround*: Currently, the only method that results in the
desired behavior is by exporting these variables directly in a terminal
session, which is not ideal for system-wide or automated use.
4.
*Question*: Could you provide guidance on how this integration is
supposed to function? Specifically, I am looking to understand the correct
setup to ensure that SSH passwords are both stored in and retrieved from
the KDE Wallet seamlessly.
I appreciate any documentation, tips, or personal experiences you could
share regarding this matter. Thank you very much for your support and for
the contributions you make to the Fedora KDE community.
Best regards,
--
Lukáš Růžička
FEDORA QE, RHCE
Red Hat
<https://www.redhat.com>
Purkyňova 115
612 45 Brno - Královo Pole
lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
1 week, 2 days
set a new screen resolution mode with Fedora 40 / Plasma 6 ?
by Sbob
Hi all;
I have just installed Fedora 40, on F39 I could use xrandr and set a
'new mode' something like 2048x1152'
but kscreen-doctor does not seem to have this capability, I can set a
mode that the screen already reports but cannot see a way to create a
new one.
Anyone know how to add a new mode with wayland / Plasma 6?
Thanks in advance
1 week, 2 days
kscreen-doctor ERROR - qt.accessibility.atspi: Error in contacting
registry
by Sbob
Hi;
I just installed Fedora 40 - KDE spin, I want to change the screen
resolution to a specific resolution but kscreen-doctor is throwing an error:
Running kscreen-doctor with no input parameters throws this error:
# kscreen-doctor
qt.accessibility.atspi: Error in contacting registry:
"org.freedesktop.DBus.Error.NameHasNoOwner" "Could not activate remote
peer 'org.a11y.atspi.Registry': unit failed"
If I run kscreen-doctor with a -o then I get the output but I still see
an error:
# kscreen-doctor -o
qt.accessibility.atspi: Error in contacting registry:
"org.freedesktop.DBus.Error.NameHasNoOwner" "Could not activate remote
peer 'org.a11y.atspi.Registry': unit failed"
Output: 33 eDP-1
enabled
connected
priority 1
Panel
Modes: 35:1920x1200@60*! 36:1600x1200@60 37:1440x1080@60
38:1400x1050@60 39:1280x1024@60 40:1280x960@60 41:1152x864@60
42:1024x768@60 43:800x600@59 44:640x480@59 45:320x240@60
46:1680x1050@60 47:1440x900@60 48:1280x800@60 49:1152x720@60
50:960x600@60 51:928x580@60 52:800x500@59 53:768x480@59
54:720x480@60 55:640x400@59 56:320x200@59 57:1920x1080@60
58:1600x900@60 59:1368x768@60 60:1280x720@60 61:1024x576@60
62:864x486@59 63:720x400@60 64:640x350@59
Geometry: 0,0 1920x1200
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: incapable
and if I run it to change the resolution of my screen I get this:
# kscreen-doctor output.eDP-1.mode.1352x852@60
qt.accessibility.atspi: Error in contacting registry:
"org.freedesktop.DBus.Error.NameHasNoOwner" "Could not activate remote
peer 'org.a11y.atspi.Registry': unit failed"
Output mode 1352x852@60 not found.
Thanks in advance for any help
1 week, 4 days
