kde September 2021

kde@lists.fedoraproject.org

19 participants
17 discussions

List server mis-configured?
by Emmett Culley 22 Jul '25

22 Jul '25

I noticed recently that each time I send an email to the kde(a)lists.fedoraproject.org mailing list I get up to three failed DMARC reports from other email servers. The list is sending email "from" me with the source address: Source-IP: 38.145.60.11 (bastion-iad01.fedoraproject.org) Which, of course, does not match up with my email server's IP address, so SPF fails, It also appears that DKIM signature also does not match. I've had my server's DNS set up to request DMARK failure reports for a few years and haven't seen any reports lately except via this list. So I am wondering if something is mis-configured on this list server. Emmett

3 5

time to orphan/retire unmaintained uncommon kde4 language bindings?
by Rex Dieter 07 May '25

07 May '25

Looking over some broken deps reports, I came across some old packages: kdebindings smokeqt smokekde qyoto (csharp/mono) kimono (csharp/mono) ruby-qt ruby-korundum perl-Qt Of these, the only one that's not a pure leaf package is perl-Qt (debconf- kde depends on it). any comment or objection to considering orphaning most (all minus smokeqt/perl-Qt) or all of these ? -- Rex

4 3

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

List of packages for plasma mobile
by Troy Dawson 06 Oct '21

06 Oct '21

I'm looking to see what it would take to add plasma mobile to epel8-next, but I have one major problem. There is no list of packages, anywhere. At least not that I can find. Not in Fedora, nor in the plasma mobile site. Please. I think I've been patient enough. Take some time today, write them down, reply back to this email. I'll even put them in the comps.xml file to finish this ticket. https://pagure.io/fedora-kde/SIG/issue/104 Troy

2 4

kf5-kimageformats rebuild
by Mattia Verga 28 Sep '21

28 Sep '21

Please be advised that an OpenEXR side-tag update [1] is on its way for F35 (there was an older update that has been unpushed because the side-tag it's expired during the beta freeze). I tried to rebuild kf5-kimageformats in the side-tag before realizing that it is being updated in a kf5 side-tag itself... so, before pushing the kf5 side-tag into an update, please look if the OpenEXR update has already been pushed to stable or if a buildroot override is needed to build kf5-kimageformats against the newer OpenEXR. Mattia [1] https://bodhi.fedoraproject.org/updates/FEDORA-2021-c6d9aa26ae

1 0

Launcher problem after Fedora 33 to 34 upgrade: autofixed, but took several hours
by John Pilkington 26 Sep '21

26 Sep '21

Yesterday I upgraded two x86_64 boxes from F33 to F34, using the dnf plugin. Both systems had undergone similar one-version upgrades in the past, and this one appeared to go smoothly. Immediately after this upgrade the kde launcher was almost unusable, offering the same random-ish targets for all categories, and with a different menu on successive attempts. Fortunately, on the machine that I left running, the problem seems to have gone away. It seemed to affect both X11 and Wayland. I have just rebooted the other machine and at present the problem is still there. John P

1 0

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

26 Sep '21

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

Vertical expand issue on new Kwin
by Patrick O'Callaghan 23 Sep '21

23 Sep '21

Since updating to kwin-x11-5.22.4-1.fc34.x86_64 yesterday, the "expand vertically" function on the title bar controls (usually tied to the middle mouse button) has stopped working. The configuration panel is still the same and still set correctly. poc

1 1

autostart dropbox
by Enrique Artal 21 Sep '21

21 Sep '21

Hi, In Fedora 34 I am not able to autostart dropbox in KDE. I have tried with systemd with the following dropbox.service file put in .config/systemd/user: [Unit] Description=Dropbox as a user service After=local-fs.target network.target [Service] Type=simple ExecStart=/usr/bin/dropbox start ExecStop=/usr/bin/dropbox stop Restart=on-failure RestartSec=1 Environment=DISPLAY=:0 [Install] WantedBy=default.target It works with systemctl --user start dropbox but if I enable the service with systemctl --user enable dropbox, after login the service is dead. What am I missing? Thanks, Enrique.

4 17

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde September 2021