kde October 2020

kde@lists.fedoraproject.org

14 participants
14 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

What's loading Dolphin?
by Mark ＠ GMail 08 Nov '20

08 Nov '20

Every time I start Fedora it loads Dolphin, which I don't want. Where should I look for it doing that (so I can stop it)? I also notice that, even though I've closed it, there's still a (small) dolphin process running... what's that about? Thanks in advance Mark

5 14

Does F33 KDE graphic drivers work on...
by Barry Scott 31 Oct '20

31 Oct '20

Are the problem with graphics drivers restricted to the VMware graphics? I have a range of hardware that I want to update to F33 but I'd like confirmation that I am likely to having working KDE on them. At the moment I use plasma on X11 with F32. Does F33 KDE work on: i915: Intel Corporation HD Graphics 500 (rev 0b)? i915: Intel Corporation HD Graphics 5500 (rev 09)? nouveau: NVIDIA GP106 (136000a1) [Geforce GTX 1060 6GB]? Intel Corporation HD Graphics 5500 (rev 09) with nouveau: NVIDIA Corporation GM108M [GeForce 840M]? Barry

2 1

F33 KDE in VMware Fusion graphics issues
by Barry Scott 31 Oct '20

31 Oct '20

I have a F33 running on VMware Fusion. When I bring up the system menu (Click on the fedora icon) I see the menu but being with slashes of colours. When I move the mouse over the menu gets drawn with corrupted text. I also see that the image changes between a well draw image and a messed up one that cycles once a second. Apart from switching to X11 from wayland is there anything useful I can do to fix the issues? Report details to help get this improved? Barry

2 3

Error using kio gdrive on F33
by José Abílio Matos 30 Oct '20

30 Oct '20

Hi, in Fedora 33 I get an error when using the kio gdrive, both from dolphin and from the command line: $ kioclient5 exec gdrive:/ kf.kio.core: couldn't create slave: "klauncher said: Error loading '/usr/ lib64/qt5/plugins/kf5/kio/gdrive.so'." kf.kio.widgets: KRun(0x558b73a41ba0) ERROR 173 "Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'." Is anyone else seeing this? There are no open bugs on kio-gdrive. Regards, -- José Abílio

2 1

Feedback on qt5-unstable in f32
by laurent.rineau__fedora＠normalesup.org 29 Oct '20

29 Oct '20

I have enabled: copr:copr.fedorainfracloud.org:mkyral:qt5-unstable copr:copr.fedorainfracloud.org:mkyral:kf5-unstable And with `dnf update`, I have: Problem 1: package qt5-qtscript-5.15.1-1.fc32.x86_64 requires libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit), but none of the providers can be installed - package qt5-qtscript-5.15.1-1.fc32.x86_64 requires qt5-qtbase(x86-64) = 5.14.2, but none of the providers can be installed - cannot install both qt5-qtbase-5.15.1-5.fc32.x86_64 and qt5-qtbase-5.14.2-5.fc32.x86_64 - cannot install both qt5-qtbase-5.14.2-5.fc32.x86_64 and qt5-qtbase-5.15.1-5.fc32.x86_64 - cannot install the best update candidate for package qt5-qtscript-5.14.2-1.fc32.x86_64 - cannot install the best update candidate for package qt5-qtbase-5.14.2-5.fc32.x86_64 [...] I think the real issue is: qt5-qtscript-5.15.1-1.fc32.x86_64 requires libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) It seems qt-qtscripts of Qt 5.15 depends on internals of Qt-5.14, that is a different version.

4 12

Wayland session and Thunderbird blurred fonts
by Germano Massullo 29 Oct '20

29 Oct '20

Good day, I was testing Plasma Wayland 5.20.1 from zawertun/kde Copr repository, when I noticed Thunderbird fonts being blurred like when you use a photocamera with a lens that is a bit out of focus. I opened this KWin bugreport https://bugs.kde.org/show_bug.cgi?id=428367 but I have been told [1] that I need both xdg-desktop-portal-gtk and gnome-settings-daemon to be installed, I don't know why What can be the correlation between blurred fonts and these packages? [1]: https://bugs.kde.org/show_bug.cgi?id=428367#c3

1 0

theme on fc33
by Kim Bisgaard 22 Oct '20

22 Oct '20

Hi, After upgrade to fedora 33 i find some programs look as if they have no theme any longer. Programs I have noticed this far is: Amarok Audex Any package I might be missing? Regards, Kim

2 1

KDE on RHEL 8
by Syam Krishnan 22 Oct '20

22 Oct '20

Hi What is the recommended method to install KDE on RHEL 8? I tried adding EPEL repo and did: yum groupinstall "KDE Plasma Workspaces" But this fails with: ================ Error: Problem 1: conflicting requests - nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 2: package sddm-breeze-5.18.4.1-2.el8.noarch requires plasma-workspace = 5.18.4.1-2.el8, but none of the providers can be installed - conflicting requests - nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 3: package plasma-desktop-5.18.4.1-2.el8.1.x86_64 requires plasma-workspace >= 5.18, but none of the providers can be installed - conflicting requests - nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64 Problem 4: package kde-print-manager-19.12.3-2.el8.x86_64 requires plasma-workspace, but none of the providers can be installed - conflicting requests - nothing provides xmessage needed by plasma-workspace-5.18.4.1-2.el8.x86_64 ================ Do I need to do anything else to install KDE off EPEL? or is there another source? Thanks Syam

4 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde October 2020