kde January 2021

kde@lists.fedoraproject.org

30 participants
24 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

No login screen after update for VMWare Fusion fedora 33 VM
by Barry Scott 23 Feb '21

23 Feb '21

I updated my VM and I no logged have a login screen. The only thing I have spotted at the moment is a problem with sddm-helper. # systemctl status sddm ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2021-01-23 16:30:10 GMT; 47s ago Docs: man:sddm(1) man:sddm.conf(5) Main PID: 934 (sddm) Tasks: 4 (limit: 5828) Memory: 84.7M CPU: 448ms CGroup: /system.slice/sddm.service ├─934 /usr/bin/sddm └─937 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{30741cdf-5986-4495-a598-b44f1a9f322d} -background none -noreset -displayfd 16 -seat > Jan 23 16:30:10 vmf33.chelsea.private systemd[1]: Started Simple Desktop Display Manager. Jan 23 16:30:11 vmf33.chelsea.private sddm-helper[943]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=995) by (uid=0) Jan 23 16:30:15 vmf33.chelsea.private sddm[934]: Auth: sddm-helper exited with 11 Any one else seeing this? I attempted to roll back the transaction but dnf history rollback did nothing and did not report an error either. I did try rolling back parts of the update to did not manage to find what might have been the cause. Barry

6 12

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

31 Jan '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-02-01 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

taglib in el7
by John Pilkington 27 Jan '21

27 Jan '21

Hi, This is essentially a rehash of my post yesterday to the elrepo list. I think it might be more appropriate here. For some time I have been building and running MythTV rpms to run under Scientific Linux, currently version 7.9. This has required some hoop jumping (just a little of it by me) as MythTV has evolved. No doubt I will have to abandon the builds fairly soon, but I would prefer not to do so immediately. Yesterday the MythTV project reset its minimum version of taglib to 1.11.1, and a bunch of updates depending on that has just been committed. rpms for taglib 1.11+ (and taglib-devel) are available for CentOS 8 and several other distributions, but the 'current' version in SL7 et al is 1.8-8.20130218git. This is in the core repos, and I understand that other repos cannot provide updates for such packages. I have not yet tried a personal rebuild of the taglib packages from el8, but is there any possibility that the taglib and taglib-devel in core el7 might be updated? Thanks, John P

2 2

Plasma on Wayland
by Adam Batkin 25 Jan '21

25 Jan '21

Since there is a plan to default Plasma to use Wayland, I thought I'd offer some feedback based on my testing over the past couple of weeks. I tested on two different systems, one with an NVidia video card (GTX 750 Ti, using the proprietary driver) and the other being a newer system with an AMD card (5600 XT, only stock Fedora drivers). On the NVidia system, the result was clear very early on: It was unusable. * The mouse cursor sometimes (usually?) had an almost-imperceptible lag/flicker as it moved, kinda like when one of those fluorescent lights is starting to die, and you can stare at it for as long as you want but you can't *see* the flicker, but you know it's happening, and now you have a migraine * Bits of Plasma would refuse to paint. For example KRunner (Alt+F2) would appear, sometimes I could type a letter or two, at which point it would appear to completely "freeze". Behind-the-scenes, it was still processing input, and I could arrow around and hit enter (having no idea what it was doing since I couldn't see anything) and it would launch whatever happened to be selected that I couldn't see. And next time I pressed Alt+F2, my previous text was pre-filled, so I knew it was working. There were other little Plasma things that worked similarly * Firefox and Thunderbird (X11-mode) worked, until suddenly they stopped working and turned into a big black box. Usually that was it until I rebooted, but sometimes if I resized something, I could get it to snap out of it and come back to life. Firefox with Wayland-mode was worse, as it would flash violently (even when not doing anything) - I assume trying to give someone a seizure. On to the AMD system. Things were "mostly" working, but I've still switched back to X11 because I need to get real work done. * I can't use CopyQ - oh well. I switched back to Klipper, which I hadn't used in like a decade. It's not terrible, and if this was my only issue, I'd survive * Something isn't right with the clipboard. Usually I'd copy something and then I could immediately paste it. But sometimes I'd paste and my clipboard was empty. So I'd Alt+Tab back to wherever I was, copy again, and then it would work. I did some searching, and there have been lots of complaints about clipboard issues like this going back 3+ years, with various different behaviors, suggested fixes, etc... but nothing concrete. Maybe it's a conflict with something klipper is doing (but honestly, if I can't use a clipboard manager at all, I can't use Wayland). Usually I'd copy from Firefox (X11) to a konsole terminal so that's where most of the "failures" happened, but once or twice it was from one konsole window to another (note: I use copy-to-clipboard-on-selection) * Some sort of kernel panic on startup, that didn't seem to affect functionality: https://bugzilla.redhat.com/show_bug.cgi?id=1911727 (I haven't seen this again since switching back to X11) * Firefox: X11-mode is fine. Wayland-mode caused terrible flicker making it unusable * JetBrains products (i.e. Java/Swing-based, IntelliJ IDEA specifically): Everything mostly worked, except occasionally it would open a dialog (like a file selector) and the whole UI would appear to freeze (it's a modal dialog after all, but the dialog hadn't "appeared" yet so there was nothing I could interact with). I'd minimize the whole IDE and bring it back, and usually after that or some other similar black-magic incantation, when it restored, the dialog would be present and I could carry on. I don't have a specific way of reproducing this, and every time I'd go back and try to re-open the same exact dialog in the same way, it would be fine * The thing that finally got me to switch back was when, in the middle of compiling something, kwin_wayland crashed, killing the whole session. If I had to guess, it had something to do with the fact that it was painting/scrolling the konsole window VERY fast during compilation and it got angry. I tried using the oops reporter thing, but it complained about something not working, so I gave up. I've put the system under load for plenty of other things (and I can dual-boot to Windows and stress-test the system for an hour and it's fine with temps hovering around ambient) In summary: On my AMD-based system, Wayland is _almost_ there. But this combination of intermittent problems makes me hesitant to use it as my daily-driver. Life is good under X11 for me: things are fast and stable and boring, which is just perfect. I'm happy to do more testing (i.e. run for a couple days under Wayland) to do more testing at some point, but not for day-to-day work. I hope this is helpful. -Adam Batkin

5 5

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

24 Jan '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-01-25 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

What package for widget bugzilla
by Ed Greshko 23 Jan '21

23 Jan '21

I want to write a bugzilla against the Bluetooth widget that appears on the System Tray. However, I can't seem to find what package it should be written against. How to determine that? -- The key to getting good answers is to ask good questions.

1 0

Notice: KDE Wayland virtual sprint this weekend
by Neal Gompa 18 Jan '21

18 Jan '21

Hey all, This weekend, the KDE community is going to have a virtual sprint for Plasma Wayland: https://community.kde.org/Sprints/Wayland/2020Virtual If any of y'all are interested in participating, feel free to come on by. :) -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

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

17 Jan '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-01-18 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde January 2021