kde March 2021

kde@lists.fedoraproject.org

8 participants
10 discussions

Release criteria proposal: networking requirements
by Adam Williamson 01 Mar '22

01 Mar '22

Hi folks! So at this week's blocker review meeting, the fact that we don't have explicit networking requirements in the release criteria really started to bite us. In the past we have squeezed networking-related issues in under other criteria, but for some issues that's really difficult, notably VPN issues. So, we agreed we should draft some explicit networking criteria. This turns out to be a big area and quite hard to cover (who'd've thought!), but here is at least a first draft for us to start from. My proposal would be to add this to the Basic criteria. I have left out some wikitext stuff from the proposal for clarity; I'd add it back in on actually applying the proposed changes. It's just formatting stuff, nothing that'd change the meaning. Anyone have thoughts, complaints, alternative approaches, supplements? Thanks! === Network requirements === Each of these requirements apply to both installer and installed system environments. For any given installer environment, the 'default network configuration tools' are considered to be those the installer documents as supported ways to configure networking (e.g. for anaconda-based environments, configuration via kernel command line options, a kickstart, or interactively in anaconda itself are included). ==== Basic networking ==== It must be possible to establish both IPv4 and IPv6 network connections using DHCP and static addressing. The default network configuration tools for the console and for release-blocking desktops must work well enough to allow typical network connection configuration operations without major workarounds. Standard network functions such as address resolution and connections with common protocols such as ping, HTTP and ssh must work as expected. Footnote titled "Supported hardware": Supported network hardware is hardware for which the Fedora kernel includes drivers and, where necessary, for which a firmware package is available. If support for a commonly-used piece or type of network hardware that would usually be present is omitted, that may constitute a violation of this criterion, after consideration of the [[Blocker_Bug_FAQ|hardware-dependent- issues|normal factors for hardware-dependent issues]]. Similarly, violations of this criteria that are hardware or configuration dependent are, as usual, subject to consideration of those factors when determining whether they are release-blocking ==== VPN connections ==== Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VNC servers with typical configurations. Footnote title "Supported servers and configurations": As there are many different VPN server applications and configurations, blocker reviewers must use their best judgment in determining whether violations of this criterion are likely to be encountered commonly enough to block a release, and if so, at which milestone. As a general principle, the more people are likely to use affected servers and the less complicated the configuration required to hit the bug, the more likely it is to be a blocker. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

4 7

How to set default session type to Plasma for sddm
by Roderick Johnstone 29 Oct '21

29 Oct '21

Hi How do I set the default session type for sddm to offer to be Plasma? I'm currently getting Gnome Classic? This is F22. Thanks Roderick Johnstone

7 13

Disk authentication required to start up???
by Mark ＠ GMail 01 Apr '21

01 Apr '21

On starting up (or rebooting, obviously) this machine it always presents me with a box with the heading Authentication is required to mount WDC WD20EARX-00PASB0 (/dev/sda1) (screenshot attached). I'm running the latest versions of everything (F33 workstation, KDE 5.20.5) presented to me but this has been happening for a long time, I don't even remember how many Fedora versions (I started at F15 I think). It appears after the KDE login (I autostart KDE), but doesn't happen at all if I simply log out of my KDE session and then log back in. Normally I give it my password (not the supervisor password, though my account is in the sudo-ers group) and carry on. To send this message I have purposely *not* given it the password and haven't closed the window, so it's still there but everything seems to function normally, so it's even not true, the disk must be mounted (it's the only hard drive mounted) so the authentication is *not* required. Just closing the window seems to be fine, too. Any idea what's being upset here? TIA

4 16

F34 beta - VMware won't resize desktop
by Gerald Henriksen 30 Mar '21

30 Mar '21

Upgraded one of my vm's from 33 to the 34 beta, logging in with either Wayland or X11 results in an inability to resize the desktop. Any suggestions on things to try, or what to file a bug against?

2 3

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 28 Mar '21

28 Mar '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-03-29 from 13:00:00 to 14:00:00 US/Eastern At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://apps.fedoraproject.org/calendar/meeting/9876/

1 0

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 21 Mar '21

21 Mar '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-03-22 from 18:00:00 to 19:00:00 UTC At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://apps.fedoraproject.org/calendar/meeting/9876/

1 0

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 14 Mar '21

14 Mar '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-03-15 from 18:00:00 to 19:00:00 UTC At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://apps.fedoraproject.org/calendar/meeting/9876/

1 0

Add options to display configuration?
by S Bob 07 Mar '21

07 Mar '21

All; I'm running Fedora 33 on an LG Gram 17. I have a BenQ EX2780Q External Monitor. If I go to System Settings --> Display and Monitor I can set the external monitor to a range of resolutions, however the resolution I want is not on the list. I have a script I can run as root to set the resolution I want: #!/bin/bash # cvt 2160 1200 60 xrandr --newmode "2160x1200_60.00" 217.25 2160 2312 2536 2912 1200 1203 1213 1245 -hsync +vsync xrandr --addmode HDMI-1 "2160x1200_60.00" xrandr --output HDMI-1 --mode "2160x1200_60.00" However, I would like the 2160x1200 setting to be added to the list in System Settings --> Display and Monitor permanently, how do I do this? Can I add an xorg.conf file? If so does anyone have any simple examples? Thanks in advance

2 1

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 07 Mar '21

07 Mar '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-03-08 from 18:00:00 to 19:00:00 UTC At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://apps.fedoraproject.org/calendar/meeting/9876/

1 0

KWallet/kded5 prompt at startup and Plasma not starting
by Mikhail Ramendik 02 Mar '21

02 Mar '21

Hello, I have Fedora 33, the KDE spin, and am using Plasma. I found that when I log out and in again (but not when I log in after booting up) I get a black screen and the prompt that kded5 needs the kwallet password. I type my user password but am still stuck in the black screen until I reboot by Ctrl+Alt+F2 and then Ctrl+Alt+Del. To work around this I disabled KDE Wallet in settings, but then the Network Manager applet silently failed to save the Wi Fi password and the Wi Fi password prompt appears at login. SOmetimes it appears, again, on a black screen,. and leaves me with a black screen after I type the password! I worked around this, too, by going into the network settings and saving the password for all users. But this setup has too many workarounds. Is there any way to troubleshoot the black screen situation, and also to make sure the wallet auto-unlocks on login? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde March 2021