kde June 2020

kde@lists.fedoraproject.org

23 participants
15 discussions

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

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

Crashes
by Steve Grubb 04 Aug '20

04 Aug '20

Hello, I was curious about something. KDE has its own crash handling system. How does this community track any metrics around code stability if upstream gets reports? Kontact has segfaulted 20 times on me today. Each time it says it cannot generate a bug report. Abrtd does not seem to pick up anything. Shouldn't it? How does this community track when a recent update suddenly starts making things crash? Kontact was fine 3 weeks ago. I updated today (3 weeks of patches) and its crashing all the time to the point its unusable. It won't generate a bug report, abrtd seems not to notice either. -Steve

1 1

Enable earlyoom for KDE Spin
by Ben Cotton 01 Jul '20

01 Jul '20

Hi KDE team, Workstation enabled earlyoom by default[1] in Fedora 32. A search of Bugzilla suggests it has been a pretty well-behaved change. How do we feel about submitting this as a self-contained change proposal for Fedora 33 KDE? [1] https://fedoraproject.org/wiki/Changes/EnableEarlyoom -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

11 16

Re: Btrfs for Fedora desktop variants
by Chris Murphy 27 Jun '20

27 Jun '20

They are using consumer drives. In the last 12 months I've done 100+ pull the power plug tests while compiling i.e. while writing. Every cold boot subsequent had no complaints, normal in every way. No special commands or repairs. Thing is? This isn't a scientific sample. It's not enough data to understand what are pseudorandom hardware problems. Do you think these tests prove I have good hardware? I don't. I know there are bugs in my SSD firmware. I just haven't been hit by one at the same time as a power plug pull. Btrfs is tested way more than this though. Both synthetically using xfstests, including dm-log-writes tests to demonstrate proper power fail behavior by the filesystem. Facebook does these tests continuously. So do many other companies. Things can still go wrong in ways no file system can completely project you from. But also other filesystems don't checksum my data. Why should I have confidence in my data otherwise? --- Chris Murphy

4 5

Btrfs for Fedora desktop variants
by Neal Gompa 26 Jun '20

26 Jun '20

Hey all, Chris Murphy and I are working on a change to switch Fedora's desktop variants to Btrfs[1]. The plan is for all Fedora desktop variants to switch over, which means both release-blocking desktops (Workstation/GNOME and KDE) will use Btrfs by default going forward. I expect this to be a smooth change, as Btrfs has been a release-blocking filesystem for many years now (at least since Fedora 20) and has had OpenQA tests to verify its functionality for nearly as long as OpenQA has been in use in Fedora for testing. And I've personally been using Btrfs on all my Fedora systems (~5 physical machines and ~100 virtual machines) since 2015 with no issues. My expectation is that there should be no work for the SIG to do (beyond me doing the work, of course). For all the words that are in the change proposal[1], the extent of the change is to flip the settings in Anaconda to use Btrfs by default on new installations. I'm interested in hearing about your feedback on the change proposal. I am excited about this, personally, as I think there's some serious opportunity to collaborate with KDE upstream and our friends at openSUSE on taking advantage of Btrfs features to make a smoother experience. Thanks in advance and best regards, Neal [1]: https://fedoraproject.org/wiki/Changes/BtrfsByDefault -- 真実はいつも一つ！/ Always, there's only one truth!

8 16

kwin_x11 issue - 94 to 99 % process.
by Robin Laing 23 Jun '20

23 Jun '20

Hello I am trying to find out why kwin_x11 is using one core on my machine at and showing 94 to 99% in top. It isn't consistent as some times this doesn't occur. This is on F30. I set up another account on this machine for working at home and switch between the users being logged in at the same time. User A and B KDE sessions are running. New user C was created for work. I login user C and switch back to B or A and then one core goes to 94 to 99% load on kwin_x11 for user C. If I go to a VT terminal session , the kwin_x11 load disappears so it is related to both kwin sessions. If I use a tree listing, there is nothing listed under kwin-x11 strace on the process provides ppoll([{fd=11, events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=6, events=POLLIN}, {fd=5, events=POLLIN}], 5, {tv_sec=0, tv_nsec=0}, NULL, 8) = 0 (Timeout) strace Summary of process calls. % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 100.00 0.713184 6 110466 ppoll ------ ----------- ----------- --------- --------- ---------------- 100.00 0.713184 6 110466 total It does seem to be worse if I have any applications open such as Firefox or LibreOffice. Robin

2 6

Help with an EPEL8 kde bug
by Troy Dawson 23 Jun '20

23 Jun '20

Hi All, I've been working on a configuration / system settings bug [1] on the rebuild of KDE on EPEL8. I'm running out of ideas. The problem: When you open system settings and click on certain areas (Global Theme, Plasma Style, and others) you get the following error file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml:87 Type NewStuff.Button unavailable /usr/lib64/qt5/qml/org/kde/newstuff/qml/Button.qml:125: Type NewStuff.Dialog unavailable /usr/lib64/qt5/qml/org/kde/newstuff/qml/Dialog.qml:95: Type NewStuff.DialogContent unavailable /usr/lib64/qt5/qml/org/kde/newstuff/qml/DialogContent.qml:64: Type NewStuff.Page unavailable /usr/lib64/qt5/qml/org/kde/newstuff/qml/Page.qml:108: Type NewStuff.QuestionAsker unavailable /usr/lib64/qt5/qml/org/kde/newstuff/qml/QuestionAsker.qml:45: "QtControls.Dialog.anchors" is not available due to component versioning. Versions of packages: qt5 - 5.12.5 / 5.12.8 plasma - 5.18 kf5 - 5.68 / 19.12 apps - 5.18 / 19.12 Any thoughts, ideas, comments, are welcome. Thanks Troy Dawson [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1838801

1 0

todo list
by Rex Dieter 22 Jun '20

22 Jun '20

FYI mostly (and in case anyone is interested in helping). What I've been working on recently: * kde apps 20.04.1 for rawhide: done * kf5 5.70.x for f31: done(*) Todos for the short-term future: 1 plasma-5.18.x for f31 2 Qt 5.14.x for f32 3 Qt 5.15 for rawhide (*) done in that builds are done, bodhi is apparently having issue this morning... initial attempts at submission failed. Will keep trying. -- Rex

7 9

cannot logout - sometimes.
by Robin Laing 19 Jun '20

19 Jun '20

Hello, I have had this issue in F30 but just upgraded to F32 hoping it would be fixed but now it is much worse. I use multiple accounts to isolate personal stuff from work so I usually have two or three different accounts open at any one time. Some accounts I only open for a short period of time and then close them. Lately I have been having more issues with logging out and the window just gets to a point I cannot do anything in it. Mouse pointer moves but no right or left click menus or anything else. Tonight, it happened with only one account open and went to close that as I was testing a weird issue with the mouse in that one account. I have to go into a different account or terminal window and close all the processes that are still running. I have to kill this process before the session will finally close. root 9191 0.0 0.0 171972 19764 ? SL Jun18 0:00 /usr/libexec/sddm-helper --socket /tmp/sddm-auth21ca2b7f-c9cc-4127-afa5-b1d0bf27cbec --id 5 --start /usr/bin/startplasma-x11 --user robin It has happened with all the accounts I have on this machine. It can be very frustrating. I am suspecting it is related to something that is waiting but I don't know what as I have just logged in for less than a minute and logged out and it has occurred. I have tried this but it doesn't fix the problem. https://wiki.archlinux.org/index.php/Systemd/User#Kill_user_processes_on_lo… This is a list of what is running according to top for the user after trying to "Leave". 43039 xxxx 20 0 21596 11816 9584 S 0.0 0.0 0:00.39 systemd 43053 xxxx 20 0 179196 6524 4 S 0.0 0.0 0:00.00 (sd-pam) 43121 xxxx 20 0 268728 4324 3908 S 0.0 0.0 0:00.01 dbus-broker-lau 43122 xxxx 20 0 6240 3996 2708 S 0.0 0.0 0:00.17 dbus-broker 43216 xxxx 20 0 376096 41736 35524 S 0.0 0.1 0:00.26 kglobalaccel5 43221 xxxx 20 0 156240 5704 5128 S 0.0 0.0 0:00.00 dconf-service 43262 xxxx 9 -11 344116 15844 12220 S 0.0 0.0 0:00.80 pulseaudio 43270 xxxx 20 0 384548 24352 19708 S 0.0 0.1 0:00.30 abrt-applet 43281 xxxx 20 0 340884 7016 6436 S 0.0 0.0 0:00.00 agent 43304 xxxx 20 0 642980 34648 30336 S 0.0 0.1 0:00.13 kactivitymanage 43310 xxxx 20 0 305316 6956 6288 S 0.0 0.0 0:00.01 at-spi-bus-laun 43322 xxxx 20 0 268468 3592 3300 S 0.0 0.0 0:00.00 dbus-broker-lau 43327 xxxx 20 0 5148 2968 2708 S 0.0 0.0 0:00.01 dbus-broker 43339 xxxx 20 0 343388 8076 7272 S 0.0 0.0 0:00.00 gvfsd 43384 xxxx 20 0 322024 15428 13428 S 0.0 0.0 0:00.04 mission-control 43465 xxxx 20 0 321776 20908 18260 S 0.0 0.1 0:00.10 kscreen_backend 43486 xxxx 20 0 17228 5568 4808 S 0.0 0.0 0:00.00 gconf-helper 43487 xxxx 20 0 121492 7008 6252 S 0.0 0.0 0:00.00 gconfd-2 43519 xxxx 20 0 160880 7844 7088 S 0.0 0.0 0:00.06 at-spi2-registr 45603 xxxx 20 0 453980 49044 41564 S 0.0 0.1 0:00.23 kdeconnectd As I close processes, gconf-helper doesn't want to close and goes into a zombie state. 43486 xxxx 20 0 0 0 0 Z 0.0 0.0 0:00.00 gconf-helper As I am using a different approach this time by using "top" to show the running processes, I noticed that pulse audio goes to 100% as I am killing proccesses. 43262 xxxx 9 -11 344116 15848 12220 R 100.0 0.0 4:22.43 pulseaudio Once I killed pulse audio, gconf-helper closed as well. One thing I noticed on this last one that was strange, the plasma session opened on the same terminal (TTY3) that I already had a terminal session open in. I have never seen that before. I hope someone can help me find this issue. I don't even know where to start to file a bug report. Robin

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde June 2020