Siduction Forum

Siduction Forum => Upgrade Warnings (DE / EN) => Topic started by: dibl on 2018/12/22, 23:33:13

Title: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: dibl on 2018/12/22, 23:33:13
With the new kernel installed, my desktop system boots quickly to the sddm splash and hangs for awhile, then after 1 minute the cursor appears, then after 2 more minutes the plasma desktop appears, and everything works as expected.  I booted 2 times to verify this behavior and it is the same each time. This installation is on a SSD and normally boots very quickly to the plasma desktop.

I looked at ~.xsession-errors, but I don't see anything abnormal there (not that I would know what to look for ....).

Code: [Select]
System:    Host: dibl-patience Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.14.3
           Distro: siduction 18.3.0 Patience - kde - (201805132121)
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X299-E GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends
           v: 1401 date: 05/21/2018
CPU:       Topology: Quad Core model: Intel Core i7-7740X bits: 64 type: MT MCP L2 cache: 8192 KiB
           Speed: 4111 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 4111 2: 3608 3: 2331 4: 4220 5: 4080 6: 4376 7: 4254
           8: 1957
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 396.54
           Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 1920x1200~60Hz, 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 396.54
Audio:     Device-1: Intel 200 Series PCH HD Audio driver: snd_hda_intel
           Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo
           Sound Server: ALSA v: k4.19.12-towo.1-siduction-amd64
Network:   Device-1: Intel Ethernet I219-V driver: e1000e
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
           IF-ID-1: br0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:    Local Storage: total: 2.27 TiB used: 916.85 GiB (39.4%)
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB @ size: 465.76 GiB
           ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
           ID-3: /dev/sdc vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
Partition: ID-1: / size: 58.81 GiB used: 9.89 GiB (16.8%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 393.18 GiB used: 51.34 GiB (13.1%) fs: ext4 dev: /dev/sda4
           ID-3: swap-1 size: 5.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 37 C
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info:      Processes: 246 Uptime: 11m Memory: 31.33 GiB used: 1.89 GiB (6.0%) Shell: bash inxi: 3.0.29

Edit: On an HP laptop with entirely different hardware, the problem is the same.

On a Dell laptop with LXQt desktop, the problem does not exist.  So I conclude it is a problem with KDE/Plasma desktop only (I don't have a gnome or xfce desktop to test).

Edit #2:The problem is NOT the new kernel.  Seeing the report of problems with systemd-240, I booted an earlier kernel, and the problem remains the same.  So ... maybe I need to downgrade systemd and see if that is the problem.
Title: Re: Plasma vs. kernel 4.19.12-towo.1
Post by: titan on 2018/12/23, 10:15:11
Same here hangs booting into Plasma but boots as normal into i3
Code: [Select]
CPU: Quad Core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT MCP-) speed/min/max: 1420/1600/3600 MHz
Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 Up: 8m Mem: 1485.9/6968.0 MiB (21.3%) Storage: 1.34 TiB (19.3% used) Procs: 228
Shell: bash 4.4.23 inxi: 3.0.29
Title: Re: Plasma vs. kernel 4.19.12-towo.1
Post by: hschn on 2018/12/23, 10:18:58
Hello
same here
Quote
System:    Host: siductionT430 Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc
           v: 8.2.0 Console: tty 2 Distro: siduction 13.2.1 December - kde - (201401272125)
           base: Debian GNU/Linux buster/sid
Machine:   Type: Laptop System: LENOVO product: 2347G5U v: ThinkPad T430 serial: PBP05A8
           Mobo: LENOVO model: 2347G5U serial: 1ZSLY37C68V UEFI [Legacy]: LENOVO v: G1ETB2WW (2.72 )
           date: 01/31/2017
Battery:   ID-1: BAT0 charge: 34.3 Wh condition: 35.2/47.5 Wh (74%) model: LGC 45N1005 status: Unknown
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge rev: 9
           L2 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20751
           Speed: 1201 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 1197 2: 1197 3: 1197 4: 1197
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel
           bus ID: 00:02.0
           Display: server: X.org 1.20.3 driver: modesetting tty: 109x25
           Message: Advanced graphics data unavailable in console for root.
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 6080
           bus ID: 00:19.0
           IF: eth0 state: down mac: 28:d2:44:1a:92:fc
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: efa0
           bus ID: 03:00.0
           IF: wlan0 state: up mac: 6c:88:14:f8:a6:d8
Drives:    Local Storage: total: 689.33 GiB used: 381.94 GiB (55.4%)
Info:      Processes: 195 Uptime: 8m Memory: 7.48 GiB used: 1.37 GiB (18.3%) Init: systemd runlevel: 5
           Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23 inxi: 3.0.29
Title: Re: Plasma vs. kernel 4.19.12-towo.1
Post by: Penyelam on 2018/12/23, 10:51:20
Here too
Code: [Select]
System:    Host: sidThinkpad Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64 Console: tty 1
           Distro: siduction 18.2.0 Patience - kde - (201803072323)
Machine:   Type: Laptop System: LENOVO product: 20AQ009CGE v: ThinkPad T440s serial: PC02XCHR
           Mobo: LENOVO model: 20AQ009CGE v: SDK0E50510 WIN serial: L1HF4AZ032Y UEFI [Legacy]: LENOVO v: GJET86WW (2.36 )
           date: 12/04/2015
Battery:   ID-1: BAT0 charge: 17.9 Wh condition: 17.9/23.2 Wh (77%)
           ID-2: BAT1 charge: 12.3 Wh condition: 16.9/23.2 Wh (73%)
CPU:       Dual Core: Intel Core i5-4210U type: MT MCP speed: 798 MHz min/max: 800/2700 MHz
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
           Display: server: X.org 1.20.3 driver: modesetting unloaded: fbdev,vesa tty: 176x31
           Message: Advanced graphics data unavailable in console for root.
Network:   Device-1: Intel Ethernet I218-V driver: e1000e
           Device-2: Intel Wireless 7260 driver: iwlwifi
Drives:    Local Storage: total: 465.76 GiB used: 291.57 GiB (62.6%)
Info:      Processes: 206 Uptime: 22m Memory: 11.44 GiB used: 1.84 GiB (16.1%) Init: systemd runlevel: 5 Shell: bash
           inxi: 3.0.29
Title: Re: Plasma vs. kernel 4.19.12-towo.1
Post by: piper on 2018/12/23, 13:54:42
https://forum.siduction.org/index.php?topic=7510.msg61185#msg61185

Perhaps 240 downgrade might help *some for now
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: dibl on 2018/12/23, 14:02:36
Yep, that fixed the problem with plasma starting.  Thank you piper!
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: DeepDayze on 2018/12/23, 17:53:51
Weird that this systemd 240 bug affects just KDE (and Java) as I booted into Fluxbox and it works fine there. Will test some java based apps to see if there's issues there.
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: dibl on 2018/12/23, 17:59:31
LXQt is fast as ever.  It must not be a qt-related issue.
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: DeepDayze on 2018/12/23, 18:01:11
Also what about other DE's like GNOME or XFCE? Anyone try these DE's to check if affected by systemd 240 issues?
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: vayu on 2018/12/23, 18:43:00
Quote
Perhaps 240 downgrade might help *some for now
I have the same long time to KDE desktop problem.  The downgrade here solved it easily: https://forum.siduction.org/index.php?topic=7510.msg61185#msg61185 (https://forum.siduction.org/index.php?topic=7510.msg61185#msg61185)

Thank you, Piper and Pit. I wasn't in the mood to troubleshoot today.
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: unklarer on 2018/12/23, 18:50:55
Quote from: DeepDayze
Also what about other DE's like GNOME or XFCE? Anyone try these DE's to check if affected by systemd 240 issues?

no problems here
Code: [Select]
inxi -SIxxx
System:    Host: siduction Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 8.2.0
           Desktop: LXDE 0.9.3 info: lxpanel wm: Openbox 3.6.1 dm: SLiM 1.3.6
           Distro: siduction 12.1 Desperado - lxde - (201205212234) base: Debian GNU/Linux buster/sid
Info:      Processes: 132 Uptime: 14m Memory: 3.75 GiB used: 282.2 MiB (7.3%) Init: systemd v: 240 runlevel: 5
           default: 5 Compilers: gcc: 8.2.0 alt: 4.7/4.8/4.9/5/6/7/8 Shell: bash v: 4.4.23
           running in: lxterminal inxi: 3.0.29
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: jure on 2018/12/23, 19:10:26
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917173
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: dibl on 2018/12/23, 20:10:34
Yep.  And we have the workaround, thanks to Pit, so I am marking this thread solved.
Title: Re: Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: hendrikL on 2018/12/23, 20:13:41
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167#37

that workaround fixed it for my system, but best is to wait till it is fixed.

Code: [Select]
inxi -SIxxx -c0
System:    Host: hhl Kernel: 4.19.12-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: KDE Plasma 5.14.3
           tk: Qt 5.11.2 wm: kwin_x11 dm: SDDM Distro: siduction 18.3.0 Patience - kde - (201809172151)
           base: Debian GNU/Linux buster/sid
Info:      Processes: 204 Uptime: 5m Memory: 7.60 GiB used: 1.36 GiB (18.0%) Init: systemd v: 240 runlevel: 5 Compilers:
           gcc: 8.2.0 alt: 7/8 Shell: bash v: 4.4.23 running in: yakuake inxi: 3.0.29
Title: Re: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: seasons on 2018/12/24, 08:10:40
This is why I've made it a personal policy to never upgrade to the first release of a new systemd version (version-1). I'll wait for at least (version-2). I still think systemd should release to experimental first.
Title: Re: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: melmarker on 2018/12/24, 13:56:13
@seasons - erm, no, we (sid+$foo) are the guinea pigs per definition
Title: Re: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: vilde on 2018/12/24, 13:59:11
@seasons - erm, no, we (sid+$foo) are the guinea pigs per definition
I do like that, that means that I as a user do a tiny bit of helping the development of debian.
Title: Re: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: seasons on 2018/12/24, 20:17:29
@seasons - erm, no, we (sid+$foo) are the guinea pigs per definition
@melmarker, we had this discussion before. You can say "erm, no" all you want, but it won't change my opinion that major systemd version bumps screw up more than most packages and in ways that are more than annoying/inconvenient (unbootable system). It also takes longer for the fixes to roll out (longer than towo's kernels, for example). I will be extra cautious upgrading to new major versions of systemd and encourage others to do the same. I'd also like to see systemd prereleases in experimental. That is my opinion. You are welcome to feel differently, but don't expect my opinion to change until the situation does.
Merry Christmas, Happy New Year, etc.
Title: Re: SOLVED (with workaround) Plasma vs. [s]kernel 4.19.12-towo.1[/s] systemd 240?
Post by: titan on 2018/12/25, 09:14:02
It looks more to me that the systemd upgrade exposed problems with a Debian only patch, apparently works fine on other distros and desktops.
from the bug report 
 pam_limits.so in Debian ships a custom patch, which reads the limits from PID 1 and set those for login sessions. So, ultimately, it's both a bug in pam_limits but also kinit, which should behave more sensibly if rlimit is set to a high value.