April 2021 - kde - Fedora mailing-lists

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 30 Oct '21

30 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

kwallet not unlocking on login
by Jan Drögehoff 01 May '21

01 May '21

After the Fedora 34 update on tuesday kded5 has been nagging me to unlock my KDE wallet which is strange considering it should be unlocked by SDDM usind the pam module. After asking around on irc and finding this [1] Ask Fedora post this seems to be more than a one time occurance but I haven't been able to found out why this happens. Can anyone shed a light on this?

4 12

Session Selection
by Ed Greshko 30 Apr '21

30 Apr '21

I just upgraded from F33 to F34 and everything went well. Had an issue with the kwallet but "magically" fixed it. One problem has me scratching my head. I use sddm and in F33 there was a selection at the bottom of the screen for running either "Plasma Wayland" or "Plasma". My session of choice has been "Plasma". But now there is no box at the bottom of the screen to make a selection. The good news is my previous selection is remembered an I'm running "Plasma". But I would like to continue to test "Plasma Wayland" but don't see a way to choose. Any ideas? These files exist. /usr/share/wayland-sessions/: plasma.desktop /usr/share/xsessions/: plasmax11.desktop -- Remind me to ignore comments which aren't germane to the thread.

4 10

copy/paste wayland
by Ed Greshko 30 Apr '21

30 Apr '21

I'm testing F34 in a VM trying to accept wayland. I've run into an issue which I hope is covered, but can't seem to find a solution. I want to copy/paste text from a konsole window into an email being written under thunderbird. I though, maybe, running thunderbird-wayland was the solution but it seems not the case. What I highlight in a konsole window doesn't show up in the clipboard on the systray. So, unable to paste in the email. Is there a solution for this? -- Remind me to ignore comments which aren't germane to the thread.

6 11

kwallet not unlocking on login
by Jan Drögehoff 30 Apr '21

30 Apr '21

After the Fedora 34 update on tuesday kded5 has been nagging me to unlock my KDE wallet which is strange considering it should be unlocked by SDDM usind the pam module. After asking around on irc and finding this[1] Ask Fedora post this seems to be more than a one time occurance but I haven't been able to found out why this happens. Can anyone shed a light on this? [1] https://ask.fedoraproject.org/t/kded5-asks-for-kdewallet-password/13726

1 0

Handling of sessions in F34
by José Abílio Matos 29 Apr '21

29 Apr '21

Hi, in F34 the session does not seems to be restored as it used before. In the "Desktop Session" settings I have the option "When logging in: Restore previous saved session" yet when I login the windows forget their location both in terms of the virtual desktop as well as the screen (I use an external screen). Looking into the ~/.config/ksmserverrc I see that file has the same date as the last logout (as I would expect). This is annoying because on start I have to manually restore the applications location. FWIW I am running Plasma on X11. Is this known? Best regards, -- José Abílio

3 7

Another dostro with same KDE, to test bugs?
by Mikhail Ramendik 26 Apr '21

26 Apr '21

Hello, I currently have two KDE bugs open for a few weeks but getting no attention: - https://bugzilla.redhat.com/show_bug.cgi?id=1945192 - https://bugzilla.redhat.com/show_bug.cgi?id=1947973 Three more are likely to come once I do more reproduction testing. I do understand the Fedora KDE team is very small so might not be able to get to all bugs, and that the bugs are likely to be from the upstream anyway. But I can't really raise them on bugs.kde.org unless I am sure they *are* upstream. And I would guess this would mean checking them in another distro, but the distro should have the same latest KDE version as Fedora has. Could anyone please advice which distro this would be? I don't really want to go building Plasma from source. Ideally I'd want a distro with a live boot of KDE, but if that is not possible, I do have a testing machine where I can install one. But which one should it be? Arch? Gentoo? Kubuntu? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization

2 1

KDE packages source files verification
by Mattia Verga 25 Apr '21

25 Apr '21

Looking at sources stored at download.kde.org I see that each package sources tarball is provided with a key to verify source integrity. Packaging guidelines recommend [1] to use the source file verification through keys whenever possible. However, I'm unable to find where KDE provides the keyring used to generate the keys... does anyone knows where to find it? Thanks Mattia [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_ver…

1 0

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

25 Apr '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-04-26 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://calendar.fedoraproject.org//meeting/9876/

1 0

kwin and plasma configuration files list
by Robin Laing 24 Apr '21

24 Apr '21

I am having weird issues on my system and it is pointing to a configuration issue. May be related to old config files or just a really weird configuration that is causing the issues. Is there a list of all the config files used for plasma and kwin that can affect keyboard operation and screen issues. I have had weird lockups between accounts. Full screen freezing on some accounts requiring a reboot. Moving from SDDM to GDM has stopped the weird black screen on logouts. The most recent issue is no keyboard operation in one account if Clementine is open. Works okay in other accounts. I really don't want to wipe out all the configuration files again as I have done in the past. Robin

1 0

Re: [Test-Announce] Fedora 34 Candidate RC-1.1 Available Now!
by Adam Williamson 22 Apr '21

22 Apr '21

On Thu, 2021-04-22 at 03:00 +0000, rawhide(a)fedoraproject.org wrote: > According to the schedule [1], Fedora 34 Candidate RC-1.1 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan Hey folks! This is the real-deal first RC for F34 Final, with all known blockers fixed. We only have a short time before the go/no-go meeting, but I am going to see if we can push that to Friday without impacting the schedule. In the meantime, please do help test it as much as possible. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

ssh ask pass on F34 not working on entry
by José Abílio Matos 21 Apr '21

21 Apr '21

For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass #!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null For F34 this is not working out of the box. That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there. It almost looks like that kwallet it is not opened when the autostart script runs. BTW in terms of F34 I have two other small nags. The first is that some windows forget their placement and are sent to the first desktop when booting. The other issue is that, at least for this account, plasma (wayland) freezes the machine while gnome (wayland) works. Although it had some issues there was no freeze in Fedora 33. Where can I find further informations to debug these issues? Best regards, -- José Abílio

7 10

Pulseaudio - mutliuser issues.
by Robin Laing 19 Apr '21

19 Apr '21

I use multiple accounts and recently a major headache has occurred with pulseaudio. My problem started last weekend. From what I have found so far is that one account takes over a media output device. On my present system, I use the onboard sound for all audio but the HDMI says that it has audio. Both computer monitors do have an audio output jack. Sound card is connected to 5.1 speaker system. On average, I have two or three accounts open for work and private stuff which has worked for many years with no problems. Recently, the issue has arose that the one account I use for general day to day stuff has taken over the sound card for only it's usage. The second account that is for work has tried to use the HDMI output but cannot even see the sound card as an option. If I restart pulseaudio, then no devices are found until I at least lock the account and log back in. If I open a third account which I have to use for online related work, I have no sound device to use until I do a reboot. I have looked at trouble shooting this but I am lost. Most online troubleshooting help is geared to a single account being used. To add to the issue, I use mplayer as my main player and in the second account, it refused to work if I had tried to restart pulseaudio. It works with no sound if the HDMI/Display port is the only device as there are no speakers It is not an mplayer configuration as I have cloned the configuration from the account that works. No changes to the /etc/pulse/* files since last November which would have been the upgrade to F33. Where do I start? Robin

2 7

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

18 Apr '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-04-19 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://calendar.fedoraproject.org//meeting/9876/

1 0

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

11 Apr '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-04-12 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://calendar.fedoraproject.org//meeting/9876/

1 0

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

04 Apr '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-04-05 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://calendar.fedoraproject.org//meeting/9876/

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde April 2021