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
2 weeks, 5 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>
2 weeks, 5 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
2 weeks, 5 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
2 weeks, 6 days
Akonadi wont start
by Patrick O'Callaghan
F40, KDE Wayland
I've noticed error messages in the journal related to Akonadi. I don't
really use any of the dependent apps such as Kmail etc. but I know some
Plasma widgets use it, so I decided to check:
$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
poc@Bree:~$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/libexec/mysqld"
org.kde.pim.akonadiserver: arguments: QList("--defaults-file=/home/poc/.local/share/akonadi/mysql.conf", "--datadir=/home/poc/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: ""
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
poc@Bree:~$ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_google_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mailmerge_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource
This seems to be quite common across multiple distros, but I've no idea
what to do about it.
poc
3 weeks, 2 days
Plasma 6-5 failure
by Mark @ GMail
I updated to F40 and got Plasma 6(.0.4), mostly working ok. However,
when I use the Krusader menu to start a root mode Krusader it
complains:
Cannot start root mode Krusader, /usr/libexec/kf5/kdesu not found or
not executable. Please verify that kde-cli-tools are installed
kde-cli-tools are installed (also v 6.0.4, release 1.fc40), and why is
it looking in the kf5 folder. It's right, kdesu isn't there, but it is
in /usr/libexec/kf6.
What should I look to correct?
Mark
3 weeks, 3 days
audiocd-kio-libs and ktp-accounts-kcm preventing F39->F40 upgrade
by Germano Massullo
Hi there, I many times have noticed that F39->F40 upgrade is halted
because of
1) audiocd-kio-libs
2) ktp-accounts-kcm
concerning 1) I saw an old bugreport not being handled
https://bugzilla.redhat.com/show_bug.cgi?id=2265260 What is the problem
of such update?
Concerning 2), I saw that the package has been orphaned. Don't we have a
way to automatically remove the package? It's not even removed with "dnf
autoremove"
Output of failed dnf sytstm upgrade to F40:
====
Problema 1: package audiocd-kio-libs-16.08.3-21.fc39.x86_64 from
@System requires audiocd-kio = 16.08.3-21.fc39, but none of the
providers can be installed
- audiocd-kio-16.08.3-21.fc39.x86_64 from @System does not belong to
a distupgrade repository
- problem with installed package audiocd-kio-libs-16.08.3-21.fc39.x86_64
Problema 2: package ktp-accounts-kcm-23.04.3-2.fc39.x86_64 from
@System requires kaccounts-integration(x86-64) >= 23.04, but none of the
providers can be installed
- kaccounts-integration-23.08.5-1.fc39.x86_64 from @System does not
belong to a distupgrade repository
- problem with installed package ktp-accounts-kcm-23.04.3-2.fc39.x86_64
Problema 3: package ktp-accounts-kcm-23.04.3-2.fc39.x86_64 from
@System requires kaccounts-integration(x86-64) >= 23.04, but none of the
providers can be installed
- package kaccounts-integration-23.08.5-1.fc39.x86_64 from @System
requires accounts-qml-module(x86-64), but none of the providers can be
installed
- package ktp-contact-list-23.04.3-2.fc39.x86_64 from @System
requires ktp-accounts-kcm, but none of the providers can be installed
- accounts-qml-module-0.7-10.fc39.x86_64 from @System does not
belong to a distupgrade repository
- problem with installed package ktp-contact-list-23.04.3-2.fc39.x86_64
Problema 4: problem with installed package
kio-gdrive-23.08.5-1.fc39.x86_64
- package kio-gdrive-24.02.1-1.fc40.x86_64 from fedora requires
accounts-qml-module-qt6, but none of the providers can be installed
- package kio-gdrive-24.02.2-1.fc40.x86_64 from updates requires
accounts-qml-module-qt6, but none of the providers can be installed
- package accounts-qml-module-qt6-0.7^20231216.05e79eb-3.fc40.x86_64
from fedora obsoletes accounts-qml-module < 0.7^20231216 provided by
accounts-qml-module-0.7-10.fc39.x86_64 from @System
- package kaccounts-integration-23.08.5-1.fc39.x86_64 from @System
requires accounts-qml-module(x86-64), but none of the providers can be
installed
- package ktp-accounts-kcm-23.04.3-2.fc39.x86_64 from @System
requires kaccounts-integration(x86-64) >= 23.04, but none of the
providers can be installed
- package ktp-text-ui-23.04.3-2.fc39.x86_64 from @System requires
ktp-accounts-kcm, but none of the providers can be installed
- kio-gdrive-23.08.5-1.fc39.x86_64 from @System does not belong to a
distupgrade repository
- problem with installed package ktp-text-ui-23.04.3-2.fc39.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
3 weeks, 3 days
Fedora40 and nouveau
by John Pilkington
I have posted on the fedora users list about my two systems previously
using the rpmfusion 470xx drivers. At present those have been removed
and I'm using nouveau. Single-boot box is largely ok, double-boot with
Win10 has HDMI video only, 800x600, and no vga output.
Here are inxi and kscreen-doctor results for both:
Selecting the HDMI audio on thedual-boot box gives an active volume
indication but no sound.
{{{
Single-boot system
[john@HPFed ~]$ inxi -GA
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: nouveau v: kernel
Device-2: Conexant Systems (Rockwell) Geniatech T230 DVB-T2 TV Stick
driver: dvb_usb_dvbsky type: USB
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: modesetting unloaded:
fbdev,vesa
dri: nouveau gpu: nouveau resolution: 1: 1360x768 2: 1680x1050
API: EGL v: 1.5 drivers: nouveau,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.0.6 renderer: NV106
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 82801I HD Audio driver: snd_hda_intel
Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-3: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder
driver: saa7134
API: ALSA v: k6.8.8-300.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active (process)
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$ kscreen-doctor -o
Output: 1 VGA-1
enabled
connected
priority 1
VGA
Modes: 0:1680x1050@60*! 1:1280x1024@75 2:1280x1024@60
3:1440x900@60 4:1280x800@60 5:1152x864@75 6:1280x720@60
7:1024x768@75 8:1024x768@70 9:1024x768@60 10:832x624@75
11:800x600@75 12:800x600@72 13:800x600@60 14:800x600@56
15:640x480@75 16:640x480@73 17:640x480@67 18:640x480@60
19:720x400@70 20:1280x1024@60 21:1024x768@60 22:1600x900@60
23:1368x768@60 24:1280x720@60
Geometry: 0,0 1680x1050
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Output: 2 HDMI-A-1
enabled
connected
priority 2
HDMI
Modes: 0:1360x768@60*! 1:1920x1080@60 2:1920x1080@60
3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1920x1080@50
7:1920x1080@30 8:1920x1080@30 9:1920x1080@24 10:1920x1080@24
11:1280x1024@60 12:1440x900@60 13:1280x720@60 14:1280x720@60
15:1280x720@50 16:1280x720@30 17:1280x720@30 18:1280x720@24
19:1280x720@24 20:1024x768@60 21:800x600@60 22:720x576@50
23:720x480@60 24:720x480@60 25:640x480@60 26:640x480@60
27:1024x768@60 28:1280x720@60
Geometry: 1680,0 1360x768
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
[john@HPFed ~]$
============
Dual boot system
john@FedWin4c1:~$
john@FedWin4c1:~$ inxi -GA
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1
256 bits)
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-3: C-Media USB PnP Sound Device
driver: hid-generic,snd-usb-audio,usbhid type: USB
API: ALSA v: k6.8.8-300.fc40.x86_64 status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$ kscreen-doctor -o
Output: 1 Unknown-1
enabled
connected
priority 1
Unknown
Modes: 0:800x600@60*!
Geometry: 0,0 800x600
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
john@FedWin4c1:~$
john@FedWin4c1:~$
}}}
Thanks for any insights
John P
3 weeks, 5 days