Bug#917293: Fix uploaded, but workaround neededuntil Qt is fixed

The root of this issue seems to be: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167 Arguably kinit's code needed a fix, which has been uploaded but it will not get built until the Qt transition is sorted out. In the meantime you can use the workaround described in the link above:

Bug#917293: marked as done (kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.)

Your message dated Thu, 27 Dec 2018 18:05:10 + with message-id and subject line Bug#917293: fixed in kinit 5.51.0-2 has caused the Debian Bug report #917293, regarding kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment. to be marked as done

Bug#917293:

El 27/12/18 a las 0:13, Bernhard Übelacker escribió: > Hello all, > that bug sounds like a duplicate of #917167. > > Kind regards, > Bernhard > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167 Ah. The fail is resolve adding line on /etc/security/limit.d/systemd. OK. In this moment only

Bug#917293:

Hello all, that bug sounds like a duplicate of #917167. Kind regards, Bernhard https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167

Bug#917293:

I can also confirm this bug, After entering login details in SDDM, plasma splash screen appears but the progress bar remains frozen at 0%. During that time, from a console using `top` I can see kdeinit5 running at 100% CPU. After a few minutes the plasma session finally opens normally. Loopback

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

El 26/12/18 a las 1:07, Lisandro Damián Nicanor Pérez Meyer escribió: > Hi Santiago! > > El mar., 25 dic. 2018 19:57, Santiago José López Borrazás > escribió: > > El 25/12/18 a las 23:31, Lisandro Damián Nicanor Pérez Meyer escribió: > > > > I mean your

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

Hi Santiago! El mar., 25 dic. 2018 19:57, Santiago José López Borrazás escribió: > El 25/12/18 a las 23:31, Lisandro Damián Nicanor Pérez Meyer escribió: > > > > I mean your internet loopback device. Please send the output of > > > > ip addr > > sjlopezb@local:~$ ip addr > > (...) > 2: eth0:

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

El 25/12/18 a las 23:31, Lisandro Damián Nicanor Pérez Meyer escribió: > > I mean your internet loopback device. Please send the output of > > ip addr sjlopezb@local:~$ ip addr (...) 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000     link/ether 00:1d:09:dd:a9:3e brd

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

El mar., 25 dic. 2018 18:35, Santiago José López Borrazás escribió: > El 25/12/18 a las 21:07, Lisandro Damián Nicanor Pérez Meyer escribió: > > > > Just a wild guess: is your loopback interface working? > > No. I am using XDM, to enter directly to KDE. > I mean your internet loopback device.

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

El 25/12/18 a las 21:07, Lisandro Damián Nicanor Pérez Meyer escribió: > > Just a wild guess: is your loopback interface working? No. I am using XDM, to enter directly to KDE. -- Saludos de Santiago José López borrazás.

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

El mar., 25 dic. 2018 14:51, Santiago José López Borrazás escribió: > Package: kinit > Version: 5.51.0-1 > Severity: important > > Dear Maintainer, > > When I want to enter the KDE, it takes me a lot to finish the session. It > consumes CPU and it takes, like an average of between 3 and 5

Bug#917293: kinit: The kdeinit5 consumes and takes about 3 ~ 5 minutes to give me control of the environment.

Package: kinit Version: 5.51.0-1 Severity: important Dear Maintainer, When I want to enter the KDE, it takes me a lot to finish the session. It consumes CPU and it takes, like an average of between 3 and 5 minutes to give me session control. I have tried creating another user and do the same.