This is generally not a problem. Occasionally this can happen when, for example, a background process needs to complete before shutting down. If you forget to terminate a process (a running app) then shutdown can be delayed (usually no more than 1-2 minutes in practice) with a Stop Job message until the process finishes.
Normally, you should likely wait for shutdown to continue of it’s own accord. Terminating the Stop Job prematurely often results in it appearing again at the next reboot/shutdown, in my experience.
You can always check your logs to see just what hadn’t finished closing.
It’s a pain in the backside when you have to wait a long time for a stop job if you need an urgent reboot. Annoyingly, the oft-found “fix” of changing DefaultTimeoutStopSec in /etc/systemd/system.conf doesn’t make any difference.
it’s not a fix but cutting off a limb when you have an itchy finger.
Linux asks all tasks to stop, and sometimes a task refuses in order to finish its job.
the bug is, if linux no ask and close all (looks like your fix)
All you have to do is find this job! Imagine it’s a backup, is it a good idea to cut it off before it’s finished ?
Generally this task is a backup service, cloud service or network service…
This is weird… as I am no longer experiencing the blank/black screen on lock.
Now that I’ve accepted the monitor’s DP demise and swapped connecting the monitor via its still working HDMI port, I cannot duplicate the blank/black SDDM on lock problem.
However, curiosity demanded I see what happens when I disconnect the monitor (unplug HDMI) and my next lock after doing so presented the blank/black screen.
Reconnected the HDMI connection, desktop spanned two monitors, locked the PC, and SDDM showed correctly; no more blank/black screen.
This got me even more curious, wondering if kscreen was holding on to the fact that there were 2 monitors, so I tried another test… disconnected HDMI, rm -rd ~/.local/share/kscreen, locked the PC, and SDDM was blank again.
Well, I’m confused, but it appears that a workaround to this issue under X11 is to have more than one monitor.
Just want to make a statement and offer a curious thought.
I applied this update in the worst way possible (logged in and actively using the system) and managed to only encounter a single “major issue” for which multiple solutions have already been brought and essentially is solved.
The curious thought about this.
Did my intentional switch to wayland about a year ago (roughly) allow me to apply this huge update with almost zero issues? Im thinking this may be the case due to seeing that lots of graphical issues were afflicting others post-update. I have suffered exactly 0 graphical issues.
Probably not. It was likely that you kept your environment in better shape than most; avoiding foreign gadgets and AUR packages, for example. I’ve seen a few reports of people having done nothing much in the way of preparation, but still without any issues to speak of.
All I did, basically, is remove a few incompatible widgets, delete the .cache directory, reboot and update. I only had minor issues (a widget I forgot about) which I took care of before the next reboot.
Understood. Must be that. I run a rather lean system with as little added graphical fluff as I can. That habit comes from running a $300 hp office machine, bought in 2009, up until 2019. Even with an added low-grade graphics card and maxed RAM, and running xcfe manjaro (or a distro very similar), I had to download yt videos and play them in vlc; they would not play in browser, even 480p.
Streaming audio with no video with hiccup sometimes too! I was about to migrate to an even less graphically heavy flavor, or no GUI at all, but choose to finally build a new machine, something I was looking to do for almost 3 years but kept putting it off as an unnecessary purchase.
Ill def be more actively involved in updating my system and watching announcements, after this last update. Id like to keep this install going for as long as possible … eventho a fresh install has its perks!
Hi,
I would like to inform that I got error with Plasma Network Management (plasmanetworkmanagement_l2tpui.so). I cannot add or edit L2TP network configuration. Here is the screenshot from dmesg:
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, beforeANDafter the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
Is it possible while having this update to keep my system components untouched? Like xserver, plasma 5.27. As I’m pretty sure if I install plasma 6 on wayland I’ll get my desktop broken.
… eventho a fresh install has its perks!
Tip 