Bug#917293:

[Santiago José López Borrazás]

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 on 2 meter hozirontal, I working in all day. Thanks.

-- 
Saludos de Santiago José López borrazás.

Bug#917293:

[Bernhard Übelacker]

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:

[Theodore Lytras]

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 interface and other network interfaces are on.

My system is debian sid amd64, with intel CPU and intel graphics.

I'm standing by to provide any further information required.

Kind regards,
Theodore

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

[Santiago José López Borrazás]

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 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 ff:ff:ff:ff:ff:ff
>     inet 192.168.1.45/24  brd 192.168.1.255
> scope global eth0
>    valid_lft forever preferred_lft forever
>     inet6 fe80::21d:9ff:fedd:a93e/64 scope link
>    valid_lft forever preferred_lft forever
> sjlopezb@local:~$
>
> It is not a problem of routes. It's not a network problem either, because
> I'm using wicd.
>
> Network works perfect.
>
>
> I'm not asking for eth0 but the loopback (lo) interface. KDE needs it up
> and running to work.
>
> These days it's normal to have it in place, but it's safer to check :-)

In local I have no problem (or loopback as you say). No way:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever

I told you, everything is correct. It never fails me, nor in this position.
Everything is alright.

So. Why do you think I have something wrong? No way.

Thanks.

-- 
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.

[Lisandro Damián Nicanor Pérez Meyer]

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:  mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether 00:1d:09:dd:a9:3e brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.45/24 brd 192.168.1.255 scope global eth0
>valid_lft forever preferred_lft forever
> inet6 fe80::21d:9ff:fedd:a93e/64 scope link
>valid_lft forever preferred_lft forever
> sjlopezb@local:~$
>
> It is not a problem of routes. It's not a network problem either, because
> I'm using wicd.
>
> Network works perfect.


I'm not asking for eth0 but the loopback (lo) interface. KDE needs it up
and running to work.

These days it's normal to have it in place, but it's safer to check :-)

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

[Santiago José López Borrazás]

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 ff:ff:ff:ff:ff:ff
    inet 192.168.1.45/24 brd 192.168.1.255 scope global eth0
   valid_lft forever preferred_lft forever
    inet6 fe80::21d:9ff:fedd:a93e/64 scope link
   valid_lft forever preferred_lft forever
sjlopezb@local:~$

It is not a problem of routes. It's not a network problem either, because
I'm using wicd.

Network works perfect.

-- 
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.

[Lisandro Damián Nicanor Pérez Meyer]

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. Please send the output of

ip addr

>

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

[Santiago José López Borrazás]

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.

[Lisandro Damián Nicanor Pérez Meyer]

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 minutes to
> give me session control.
>
> I have tried creating another user and do the same.



Just a wild guess: is your loopback interface working?

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

[Santiago José López Borrazás]

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.

This bug has been playing for a week now. And it's pretty weird What I 
consider, that is a BUG, for that reason, and it is of great importance.

With htop I checked what it consumes, with this command when starting the 
graphical environment:

kdeinit5 --oom-pipe 4 --kded +kcminit_startup

I thought there was a package missing, but no. I do not miss any package in 
important dependencies.

This has never happened to me. In my life.

Thank you very much for your help.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.20.0 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kinit depends on:
ii  kio  5.51.0-1
ii  libc62.28-3
ii  libcap2  1:2.25-1.2
ii  libcap2-bin  1:2.25-1.2
ii  libkf5configcore55.51.0-1
ii  libkf5coreaddons55.51.0-1
ii  libkf5crash5 5.51.0-1
ii  libkf5i18n5  5.51.0-1
ii  libkf5kiocore5   5.51.0-1
ii  libkf5kiowidgets55.51.0-1
ii  libkf5service-bin5.51.0-1
ii  libkf5service5   5.51.0-1
ii  libkf5windowsystem5  5.51.0-1
ii  libqt5core5a 5.11.2+dfsg-7
ii  libqt5dbus5  5.11.2+dfsg-7
ii  libqt5gui5   5.11.2+dfsg-7
ii  libstdc++6   8.2.0-13
ii  libx11-6 2:1.6.7-1
ii  libxcb1  1.13.1-2

kinit recommends no packages.

kinit suggests no packages.

-- no debconf information