[SOLVED] MX KDE shutdown takes a long time  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
~FLOW~
Posts: 294
Joined: Thu May 19, 2022 12:43 pm

[SOLVED] MX KDE shutdown takes a long time

#1 Post by ~FLOW~ »

Hello all,
I read about this thing on some thread but they not apply to my situation.
Whenever I restart/shutdown the OS it stays like frozen for 10 second then proceeds to restart/shutdown.
Well it's not really frozen because the last window that I open stays on the screen, like Firefox or VLC, and I cand still play around with the mouse in those 10 seconds.
This is really frustrating because If I'm in a hurry I have to wait until shutdown is complete, I have a SSD and also a HDD...
It's not always like this, sometimes is closes really fast(3 seconds), but 7 out of 10 times does this.
Is it some cache or swap that needs more time ? Never had a problem like this except on MX and it's the same on virtual machines with MX Linux.
I installed KSystemLog ... but have no ideea how to even begin to search what I'm looking for 9_9

On all the distros I also do this :

Code: Select all

sudo nano /etc/sysctl.conf
vm.swappiness=0
vm.dirty_bytes=15000000

Code: Select all

System:    Kernel: 5.17.0-2mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.17.0-2mx-amd64 
           root=UUID=<filter> ro 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.1_KDE_x64 Wildflower April 9  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Portable System: Dell product: Inspiron 3542 v: N/A serial: <filter> 
           Chassis: type: 8 serial: <filter> 
           Mobo: Dell model: 0926J6 v: A16 serial: <filter> UEFI: Dell v: A16 
           date: 09/02/2020 
Battery:   ID-1: BAT0 charge: 21.8 Wh (100.0%) condition: 21.8/41.4 Wh (52.7%) volts: 16.8 
           min: 14.8 model: SANYO DELL 4WY7C45 type: Li-ion serial: <filter> status: Full 
           Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech K520 serial: <filter> 
           charge: 70% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 45 (69) stepping: 1 microcode: 26 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 13567 
           Speed: 1386 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1386 2: 1220 3: 1662 
           4: 1514 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:0a16 class-ID: 0300 
           Device-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] 
           vendor: Dell driver: N/A alternate: nouveau bus-ID: 08:00.0 chip-ID: 10de:1140 
           class-ID: 0302 
           Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.5:5 
           chip-ID: 064e:9205 class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1280x720 s-dpi: 96 s-size: 337x190mm (13.3x7.5") 
           s-diag: 387mm (15.2") 
           Monitor-1: HDMI-1 res: 1280x720 hz: 60 dpi: 203 size: 160x90mm (6.3x3.5") 
           diag: 184mm (7.2") 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.2.5 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus-ID: 00:03.0 chip-ID: 8086:0a0c class-ID: 0403 
           Device-2: Intel 8 Series HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus-ID: 00:1b.0 chip-ID: 8086:9c20 class-ID: 0403 
           Sound Server-1: ALSA v: k5.17.0-2mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter vendor: Dell 
           driver: ath9k v: kernel modules: wl port: f040 bus-ID: 06:00.0 chip-ID: 168c:0036 
           class-ID: 0280 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: e000 bus-ID: 07:00.0 chip-ID: 10ec:8136 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] 
           type: USB driver: r8152 bus-ID: 3-1.4:4 chip-ID: 2357:0601 class-ID: 0000 
           serial: <filter> 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Qualcomm Atheros AR9462 Bluetooth type: USB driver: btusb v: 0.8 
           bus-ID: 1-1.6:8 chip-ID: 0cf3:0036 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: N/A rfk-block: 
           hardware: no software: no address: <filter> 
           Info: acl-mtu: 1022:8 sco-mtu: 183:5 link-policy: rswitch hold sniff 
           link-mode: slave accept 
Drives:    Local Storage: total: 2.49 TiB used: 1.2 TiB (48.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SHSS37A240G size: 223.57 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> rev: 001B scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10JPVX-75JC3T0 
           size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
           type: HDD rpm: 5400 serial: <filter> rev: 1A01 scheme: MBR 
           ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: Expansion 
           size: 1.36 TiB block-size: physical: 4096 B logical: 512 B type: N/A 
           serial: <filter> rev: 0502 scheme: GPT 
Partition: ID-1: / raw-size: 215.31 GiB size: 210.87 GiB (97.94%) used: 47.81 GiB (22.7%) 
           fs: ext4 dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) 
           fs: vfat dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 0 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda3 maj-min: 8:3 
Sensors:   System Temperatures: cpu: 50.0 C mobo: 50.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     Packages: note: see --pkg apt: 2666 lib: 1560 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/dropbox.list 
           1: deb [arch=i386,amd64] http://linux.dropbox.com/debian sid main
           No active apt repos in: /etc/apt/sources.list.d/mc3man-ubuntu-mpv-tests-kinetic.list 
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://it.mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://it.mxrepo.com/mx/repo/ bullseye ahs
           No active apt repos in: /etc/apt/sources.list.d/rvm-ubuntu-smplayer-kinetic.list 
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
           No active apt repos in: /etc/apt/sources.list.d/teejee2008-ubuntu-timeshift-kinetic.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 239 Uptime: 1h 34m wakeups: 79 Memory: 7.68 GiB used: 3 GiB (39.1%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: 
           gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 
           running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: UEFI
Last edited by ~FLOW~ on Sat May 28, 2022 11:46 am, edited 1 time in total.
MX-23.4 / KDE Plasma 5.27
Kernel: 6.XX

Be patient !!
What seams easy for you now, for a newbie might be a monumental helping hand.
An efficient pack will move as fast as the slowest member.

User avatar
Adrian
Developer
Posts: 9233
Joined: Wed Jul 12, 2006 1:42 am

Re: MX KDE shutdown takes a long time

#2 Post by Adrian »

I would look at the list of services that are stopped at shutdown time. The computer is probably waiting for one of them to finish. Maybe look with sysv-rc-conf (CLI tool), you can see which services start at which runlevel. You might be able to disable some that you don't need: samba if you don't use, mdadm and lvm2 if you don't use LVM or RAID, openvpn and so on. Just be careful what you disable because there's a chance to make your system unbootable.

User avatar
markol
Posts: 416
Joined: Sat Jan 30, 2021 8:33 am

Re: MX KDE shutdown takes a long time

#3 Post by markol »

It's a known KDE Connect problem, which was fixed in more recent Plasma versions.
I believe there is a patched version in MXPI Test Repo

User avatar
~FLOW~
Posts: 294
Joined: Thu May 19, 2022 12:43 pm

Re: MX KDE shutdown takes a long time

#4 Post by ~FLOW~ »

Adrian wrote: Thu May 26, 2022 11:12 am I would look at the list of services that are stopped at shutdown time. The computer is probably waiting for one of them to finish. Maybe look with sysv-rc-conf (CLI tool), you can see which services start at which runlevel. You might be able to disable some that you don't need: samba if you don't use, mdadm and lvm2 if you don't use LVM or RAID, openvpn and so on. Just be careful what you disable because there's a chance to make your system unbootable.
I use SAMBA, but I have no ideea how to use this and what are 1-5 0 6 S ??? :
Screenshot_20220526_223952.png

In Linux Mint there is a log viewing app, where I could see everything that the kernel did before shuting down, and how much time took for every service stuff to close. Doesn't KDE have such a tool ?



markol wrote: Thu May 26, 2022 2:49 pm It's a known KDE Connect problem, which was fixed in more recent Plasma versions.
I believe there is a patched version in MXPI Test Repo
How ???? I come from KDE Neon, and in Plasma 5.25 there were sooooo many bugs fixed...
Do I need to add reppos ?
Screenshot_20220526_223424.png
You do not have the required permissions to view the files attached to this post.
MX-23.4 / KDE Plasma 5.27
Kernel: 6.XX

Be patient !!
What seams easy for you now, for a newbie might be a monumental helping hand.
An efficient pack will move as fast as the slowest member.

User avatar
markol
Posts: 416
Joined: Sat Jan 30, 2021 8:33 am

Re: MX KDE shutdown takes a long time

#5 Post by markol »

~FLOW~ wrote: Thu May 26, 2022 3:48 pm Do I need to add reppos ?
No, just install KDE Connect from the Test repo


hint: some other KDE apps were backported by MX devs as well, check the test repo.

User avatar
baldyeti
Posts: 730
Joined: Sat Dec 05, 2009 3:37 pm

Re: MX KDE shutdown takes a long time

#6 Post by baldyeti »

As mentioned by markol, it seems you are affected by the same problem discussed here.

You can either un-install kdeconnect if you are not using it, or install kdeconnect and plasma-workspace from the MX test repo.

Just use the MX package installer and switch to its test tab.

User avatar
~FLOW~
Posts: 294
Joined: Thu May 19, 2022 12:43 pm

Re: MX KDE shutdown takes a long time

#7 Post by ~FLOW~ »

ohhhhh, so the problem is with kdeconnect ! got it
so just to be clear, [b]what method you recomend[/b] for un-install ? :
MX Package Installer --> Stable Repo
or
MX Package Installer --> MX Test Repo
or
sudo apt purge kdeconnect
or they all do the same thing ?

I'm asking this because for this I installed "Imput Remmaper" - deb file.
And I could not find a way to uninstall it. It doesn't show in MX Package Installer, Discovery, sudo apt purge doesn't find the package. And in the App Menu still appears even if I delete the shortcut
Screenshot_20220527_110708.png
I hate zombie programs
You do not have the required permissions to view the files attached to this post.
MX-23.4 / KDE Plasma 5.27
Kernel: 6.XX

Be patient !!
What seams easy for you now, for a newbie might be a monumental helping hand.
An efficient pack will move as fast as the slowest member.

User avatar
baldyeti
Posts: 730
Joined: Sat Dec 05, 2009 3:37 pm

Re: MX KDE shutdown takes a long time  [Solved]

#8 Post by baldyeti »

I am a CLI guy myself so would go with

Code: Select all

 sudo apt purge kdeconnect

but graphical package managers should work, too.

As to your other question, where did you get that package from ? It can be hazardous to install deb packages that are not certified for the debian release upon which your MX version is based (MX21 and bullseye according to your QSI)

User avatar
richb
Administrator
Posts: 11027
Joined: Wed Jul 12, 2006 2:17 pm

Re: MX KDE shutdown takes a long time

#9 Post by richb »

baldyeti wrote: Fri May 27, 2022 5:10 am I am a CLI guy myself so would go with

Code: Select all

 sudo apt purge kdeconnect

but graphical package managers should work, too.

As to your other question, where did you get that package from ? It can be hazardous to install deb packages that are not certified for the debian release upon which your MX version is based (MX21 and bullseye according to your QSI)
kdeconnect is in bullseye. I use it on my desktop with no shutdown delay. I suspect the long shutdown is due to his machine specs.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
baldyeti
Posts: 730
Joined: Sat Dec 05, 2009 3:37 pm

Re: MX KDE shutdown takes a long time

#10 Post by baldyeti »

I had the issue under plain debian/bullseye, too. Stevo's backport of kdeconnect and plasma-worspace solved it on MX21 for me and other testers. Not everyone may be affected but if you are, it is annoying.

Post Reply

Return to “MX KDE Official Release”