Question about Multitasking on Plasma
bingmybong at btinternet.com
Wed Mar 1 15:50:35 GMT 2017
On Wednesday, 1 March 2017 14:21:32 GMT Martin Steigerwald wrote:
> Am Mittwoch, 1. März 2017, 14:06:32 CET schrieb ianseeks:
> > On Wednesday, 1 March 2017 12:58:45 GMT Volker Wysk wrote:
> > > Am Mittwoch, 1. März 2017, 09:26:32 CET schrieb ianseeks:
> > > > I've found that if i context switch from Ctrl-Alt-F7 to Ctrl-Alt-F1
> > > > (e.g.
> > > > Just immediately after entering the password and pressing <cr>),
> > > > processing
> > > > seems to stop on the graphical login. Is this normal?
> > >
> > > I have this behaviour too.
> > >
> > > I addition, this also occurs when I log out. The log out process can
> > > take
> > > a
> > > while, when you have a lot of open windows. When I switch to a virtual
> > > console, it stops.
> > I've found that it doesn;t matter what is running on the VT7, it will
> > suspend, i only used the login as an example. Seems strange for a
> > multitasking OS to do this.
> I found this as well some time ago already when switching between two Plasma
> sessions, one on VT7 and one on VZ8.
> Even when I run something in the Konsole as a long running command it gets
> paused at some time. Yet when I first run screen and then run the command in
> a screen session it continues to work.
> I believe this to be part of systemd-logind session/seat management, but I
> didn´t find out yet for sure whether my belief matches reality.
> I do not agree with that new behavior and would like to have the old
> behavior back.
Yes, that would be ideal. The current situation seems to be a return to the
KDE Frameworks: 5.30.0
KDE Plasma: 5.9.2
More information about the kde