Plasma "exit screen" black background
by Ian Pilcher
After upgrading from F32 to F33, I now have a black background in the
Plasma "exit screen." (This is screen that appears when you select
"Leave" from the desktop pop-up menu and offers the Sleep, Restart,
Shut Down, and Log Out options.
I remember having this issue before, but I can't remember how I fixed
it.
Anyone have any idea what could be causing this?
--
========================================================================
In Soviet Russia, Google searches you!
========================================================================
3 years, 3 months
Freezing Plasma in Fedora?
by Mikhail Ramendik
Hello,
I had to leave Fedora a year ago because of breaking KDE Plasma
updates mid-cycle (even on "current minus one" Fedora). I have since
learned that this problem is unavoidable because of the Plasma release
cycle, when the previous (non-LTS) release immediately stops being
supported; this forces an update mid-cycle to a new Plasma and
glitches can happen.
I am looking at trying again, but can I somehow freeze all Plasma
packages, while not disabling updates for all other stuff? I know what
"dnf versionlock" is, but how do I create a correct list for it?
The idea would be to freeze Plasma packages in advance of a Plasma
version update and unfreeze a month after the new version goes into
Fedora, watching for critical security issues in the meantime.
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
3 years, 3 months
Coordinating resolution of BZ 1912046
by Ben Cotton
I've been asked to coordinate a resolution of BZ 1912046 (BASH_FUNC
environment variables reigning havoc and it just keeps getting worse)
between systemd, GNOME, and KDE maintainers. Anyone want to volunteer
to be the contact?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1912046
Thanks,
BC
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 3 months
Are these rkhunter warnings serious?
by Lester M Petrie
Hi,
I am running KDE in Fedora 33. With some fairly recent update, I have started seeing the following warnings from rkhunter. They mostly seem tied to kde components.
[13:19:12] Warning: Checking for possible rootkit files and directories [ Warning ]
[13:19:12] Found file '/lib/libkeyutils.so.1.9'. Possible rootkit: Sniffer component
[13:19:12] Found file '/lib64/libkeyutils.so.1.9'. Possible rootkit: Sniffer component
[13:19:12] Found file '/usr/lib/libkeyutils.so.1.9'. Possible rootkit: Sniffer component
[13:19:12] Found file '/usr/lib64/libkeyutils.so.1.9'. Possible rootkit: Sniffer component
[13:19:12]
Warning: The following processes are using suspicious files:
Command: abrt-applet
UID: 1000 PID: 2505
Pathname:
Possible Rootkit: Spam tool component
Command: abrt-applet
UID: 2610 PID: 2505
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrt-applet
UID: 2611 PID: 2505
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrt-applet
UID: 2620 PID: 2505
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrtd
UID: 0 PID: 958
Pathname:
Possible Rootkit: Spam tool component
Command: abrtd
UID: 990 PID: 958
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrtd
UID: 992 PID: 958
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrt-dbus
UID: 0 PID: 2614
Pathname:
Possible Rootkit: Spam tool component
Command: abrt-dbus
UID: 2617 PID: 2614
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrt-dbus
UID: 2618 PID: 2614
Pathname: 3604249
Possible Rootkit: Spam tool component
Command: abrt-dump-journ
UID: 0 PID: 993
Pathname:
Possible Rootkit: Spam tool component
Command: abrt-dump-journ
UID: 0 PID: 994
Pathname:
Possible Rootkit: Spam tool component
Command: abrt-dump-journ
UID: 0 PID: 995
Pathname:
Possible Rootkit: Spam tool component
Command: akonadi_akonote
UID: 1000 PID: 2915
Pathname:
Possible Rootkit: Spam tool component
Command: akonadi_akonote
UID: 2929 PID: 2915
Pathname: 3604249
Possible Rootkit: Spam tool component
... many,many more entries
Command: sssd
UID: 0 PID: 924
Pathname:
Possible Rootkit: Spam tool component
Command: sssd_be
UID: 0 PID: 1015
Pathname:
Possible Rootkit: Spam tool component
Command: sssd_nss
UID: 0 PID: 1058
Pathname:
Possible Rootkit: Spam tool component
Command: trivial-rewrite
UID: 89 PID: 402543
Pathname:
Possible Rootkit: Spam tool component
This seems to have been introduced sometime between Jan 3 and Jan 8.
--
Lester
3 years, 3 months
plasmashell/krunning consuming 100% cpu
by Neal Becker
After restarting from last update, I have a new problem. After login, a
few minutes later I see krunner/plasmashell using a total of close to 100%
cpu (each one bouncing around 50%). I'm sure this never happened before.
--
*Those who don't understand recursion are doomed to repeat it*
3 years, 3 months
kde: unable to create io-slave
by Neal Becker
Uh oh, looks like there is some breakage for latest kde update. When I try
to attach a file to an email I get a dialog box saying:
unable to create io-slave: klauncher said: Error loading
'/usr/lib64/qt5/plugins/kf5/kio/file.so'
The usual file choosing dialog box is blank (no files shown).
--
*Those who don't understand recursion are doomed to repeat it*
3 years, 3 months
KDE update/stability policy on Fedora
by Mikhail Ramendik
Hello,
I would really like to understand the policy of the schedule of major
KDE component version updates in Fedora.
I know of the Plasma release schedule problem. But this is bigger
apparently. The bug that forced me to leave Fedora a year ago was
https://bugzilla.redhat.com/show_bug.cgi?id=1746465 . This bug was
caused by a version update of KDE Frameworks, affected usability, and
took over a month to fix.
Following this list, I see that breaking updates to KDE are kind of a
regular occurrence:
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org...
I would guess that the component version updates mid-cycle cause the
breaking updates. I would really appreciate some explanation of what
the version update policy is.
Also is there *any way at all* to have a reliable KDE environment on
Fedora, apart from not updating the entire system?
--
Yours, Mikhail Ramendik
Unless explicitly stated, all opinions in my mail are my own and do
not reflect the views of any organization
3 years, 3 months
/lib64/libKF5AkonadiContact.so.5: undefined symbol: _ZN7Akonadi16AttributeFactory17registerAttributeEPNS_9AttributeE
by Laurent Rineau
Hi,
I am a user of https://copr.fedorainfracloud.org/coprs/mkyral/ and I
have a runtime issue since the last upgrade:
[lrineau@bonnard]~% rpm -qf /usr/bin/kmail
/lib64/libKF5AkonadiContact.so.5 /usr/bin/kmail
/lib64/libKF5AkonadiCore.so.5
kmail-20.08.1-2.1.fc32.x86_64
kf5-akonadi-contacts-20.08.1-1.fc32.x86_64
kmail-20.08.1-2.1.fc32.x86_64
kf5-akonadi-server-20.12.0-1.fc32.x86_64
[lrineau@bonnard]~% kmail
kmail: symbol lookup error: /lib64/libKF5AkonadiContact.so.5: undefined
symbol: _ZN7Akonadi16AttributeFactory17registerAttributeEPNS_9AttributeE
The culprit is the recent rebuild of kf5-akonadi-server to version
20.12.0, without rebuilding the kf5-akonadi-* packages that are still
version 20.08.1.
So I am without kmail, and am writing from the old roundcube webmail
interface of my provider. Please excuse-me if the formatting is odd, or
old.
3 years, 3 months