KDED causing long delay on shutdown?
by Patrick O'Callaghan
This has been happening for IIRC) several months now at least:
$ journalctl --boot=-1 --reverse
...
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Consumed 18.380s CPU time.
May 01 10:44:26 Bree systemd[1210]: Stopped KDE Daemon.
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Failed with result 'timeout'.
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Main process exited, code=killed, status=9/KILL
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Killing process 1791 (ProfilesWatcher) with signal SIGKILL.
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Killing process 1722 (kded5) with signal SIGKILL.
May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: State 'stop-sigterm' timed out. Killing. <-----------------------*
May 01 10:43:03 Bree systemd[1]: Unmounted /run/user/0.
May 01 10:43:03 Bree systemd[1]: run-user-0.mount: Deactivated successfully.
May 01 10:43:03 Bree systemd[1]: Unmounted /run/user/990.
May 01 10:43:03 Bree systemd[1]: run-user-990.mount: Deactivated successfully.
May 01 10:43:03 Bree systemd[1]: Stopped Network Manager Wait Online.
...
Any idea why? I see some apparently related BZ entries dating back a
couple of years, but nothing recently.
poc
8 months, 1 week
What is this icon/widget?
by John Horne
Hello,
Unfortunately it seems that picture attachments are not accepted, but the text
of my message was:
====
I use KDE/plasma/wayland, and have recently upgraded my laptop from Fedora 35
to Fedora 36. What I have noticed is an odd icon/widget has appeared on the
desktop - see attached screen snapshot, the icon/widget is between the 'U' and
'X' characters and appears as a thin white line.
I have no idea what it is, or how to remove it. I can move the icon/widget
around the desktop, but a left or right mouse click, or pressing the return or
escape key, does nothing. At the moment I have moved it as far as possible into
one of the desktop corners, so that it does interfere with anything else on the
desktop.
Anyone any idea what it is?
====
Obviously a picture would help, but as said it is basically a thin white line,
a couple of inches long, with a short grey bit in the middle. If anything it
looks a slider of some sort but it doesn't 'slide'.
Thanks,
John.
--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
9 months
Fwd: [Test-Announce] Fedora 36 Candidate RC-1.5 Available Now!
by Adam Williamson
Hey folks! Please see attached. Due to some late-breaking blockers and
fixes, we're now up to RC5 for F36 Final. Go/no-go is tomorrow. If
folks can help with testing, that'd be great.
Here's a quick summary of the changes between the RC composes:
RC1 -> RC2
gtk4-4.6.2-3.fc36 to fix #2071228
clevis-pin-tpm2-0.5.2-1.fc36 rust-tpm2-policy-0.6.0-1.fc36 to fix FTBFS
RC2 -> RC3
wpa_supplicant-2.10-4.fc36 to fix #2072070
tracker-miners-3.3.0-2.fc36 to fix #2079308
mutter-42.0-6.fc36 to fix #2081070
openssl-3.0.2-4.fc36 to fix #2069239
gzip-1.11-3.fc36 to fix #2073312
kernel-5.17.5-300.fc36 for #2080694
snapper-0.10.1-1.fc36 for FTBFS
selinux-policy-36.8-1.fc36 for #2065940
livecd-tools-30.0-1.fc36 for #2007045
xz-5.2.5-9.fc36 for #2080938
xdg-desktop-portal-1.12.4-1.fc36 for #2060990
sssd-2.7.0-1.fc36 for #2077856
gr-osmosdr-0.2.3-21.20210217gita100eb02.fc36 to fix FTBFS
RC3 -> RC4
firefox-100.0-2.fc36 for #2081488
RC4 -> RC5
sushi-41.2-1.fc36 for #2067969
gnome-photos-42.0-2.fc36 for #2079344 #2081291
aws-2020-7.fc36 matreshka-20.1-10.fc36 templates_parser-11.8.0-30.fc36 for FTBFS
So, RC3 had quite a lot of change in it. RC4 and RC5 are much more
limited. So we can count most tests from RC3 or later as being valid
for RC5; tests of Firefox, Nautilus and GNOME Photos should be re-
confirmed.
I have transferred results from RC3 and RC4 to RC5 in the matrix where
appropriate, leaving out things that are considered 'sanity tests'
(basic boot and install tests) which we try to run on every compose to
rule out some kind of cosmic bit-flip unexpectedly breaking an image.
So any spaces left on Basic/Beta/Final tests are ones we should try to
fill.
Special note on the Active Directory tests: it looks like tflink and
sgallagh ran these on RC1, thanks a lot. Since we did get a new sssd
between then and RC5 it would be *nice* if we could run them again, but
if not we can probably run with the RC1 results in the end.
Thanks again everyone!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
10 months, 3 weeks
