During the distribution upgrade, I am experiencing random KDE and applications freeze. I’m using btrfs on a Xeon E3-1245 V3 with 32GB RAM. It also takes a long time to upgrade the distribution system. Previously, with linux-5, this did not occur on Celeron 1007U boards. Are there any adjustments I should make?
Maybe you should consider using Leap. Maybe Tumbleweed is not appropriate for you.
I used to use Leap, but it was missing some versions of the programs I needed. The freeze phenomenon has only recently occurred following a Linux upgrade to version 6.X. Tumbleweed with Linux-5.19 performed admirably on an Intel Celeron-1007U 1.5GHz dual core SoC with xfs.
This, I believe, is due to btrfs.
Best is to open a bugreport.
I’ll do that after upgrading the system next week, and include top, iotop, processes, and several other benchmarks/indicators.
Never seen here running Tumbleweed with 32 GB RAM and an Intel Core i5-4570.
Can you run the KDE System Monitor History during the install and see if there any peaks in CPU or Memory usage?
I had no idea such a thing existed on desktop, so I took a look at it right now. top -d 1 shows Kalendarac is consuming 100% of the CPU. I’ll provide more information once I’ve completed the upgrades. I need to figure out how to turn that thing off Screenshot https://imgur.com/X8ERd8l.
You are providing close to zero information about your system. Thus I suggest adjust your policy and provide more information. Freezes are due to high system load in most cases. Run “systemd-cgtop --cpu=time -1” in a root shell and post the output:
Control Group Tasks CPU Time Memory Input/s Output/s
/ 983 50min 1.170000s 3.4G - -
user.slice 717 45min 44.533700s 5.0G - -
user.slice/user-1000.slice 717 45min 42.226460s 4.7G - -
user.slice/user-1000.slice/user@1000.service 712 45min 41.343544s 4.7G - -
system.slice 59 4min 14.675021s 3.4G - -
system.slice/display-manager.service 9 2min 56.201905s - - -
system.slice/systemd-udevd.service 1 2.485817s - - -
init.scope 1 2.233978s 3.7M - -
system.slice/udisks2.service 5 1.258946s - - -
system.slice/dbus.service 1 1.169023s - - -
user.slice/user-1000.slice/session-3.scope 5 872.901ms 32.4M - -
system.slice/postfix.service 3 769.592ms - - -
system.slice/irqbalance.service 2 497.434ms - - -
system.slice/systemd-journald.service 1 472.965ms - - -
system.slice/minidlna.service 2 460.271ms - - -
system.slice/apache2.service 6 424.497ms - - -
system.slice/polkit.service 3 320.721ms - - -
system.slice/cups.service 1 211.875ms - - -
system.slice/systemd-logind.service 1 201.179ms - - -
system.slice/chronyd.service 1 179.630ms - - -
system.slice/rtkit-daemon.service 3 162.772ms - - -
system.slice/ModemManager.service 3 101.432ms - - -
system.slice/systemd-resolved.service 1 86.168ms - - -
system.slice/hd-idle.service 1 55.764ms - - -
system.slice/systemd-networkd.service 1 48.767ms - - -
system.slice/upower.service 3 40.200ms - - -
system.slice/rpcbind.service 1 29.475ms - - -
system.slice/sshd.service 1 26.741ms - - -
system.slice/nfs-mountd.service 1 26.711ms - - -
system.slice/power-profiles-daemon.service 3 26.444ms - - -
system.slice/rpc-statd.service 1 13.963ms - - -
system.slice/mcelog.service 1 12.453ms - - -
system.slice/nfsdcld.service 1 6.765ms - - -
system.slice/nfs-idmapd.service 1 6.546ms - - -
system.slice/system-getty.slice 1 6.204ms - - -
system.slice/system-getty.slice/getty@tty1.service 1 6.204ms - - -
**erlangen:~ #**
CPU Time is total time since boot. You may zoom into control groups and show details by running e.g. “systemd-cgtop --cpu=time -1 user.slice/user-1000.slice/user@1000.service”:
Control Group Tasks CPU Time Memory Input/s Output/s
user.slice/user-1000.slice/user@1000.service 710 46min 36.813442s 4.6G - -
user.slice/user-1000.slice/user@1000.service/app.slice 580 43min 35.802640s 3.5G - -
user.slice/user-1000.slice/user@1000.service/app.slice/app-firefox-ab282862cf9344e08746fe4ac635e512.scope 324 41min 48.222430s 1.8G - -
user.slice/user-1000.slice/user@1000.service/session.slice 92 2min 49.483000s 499.7M - -
user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service 18 2min 10.253651s 115.1M - -
user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kalendarac@autostart.service 218 1min 23.812042s 885.9M - -
user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service 14 28.274731s 194.8M - -
user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-1d4b1d0706124c65aa0f1ef0e9b32e72.scope 12 21.974787s 858.5M - -
user.slice/user-1000.slice/user@1000.service/background.slice 36 10.934533s 597.6M - -
user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service 3 7.867899s 539.8M - -
user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service 2 3.509942s 13.0M - -
user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service 2 2.448955s 7.2M - -
user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded.service 15 2.316424s 52.2M - -
user.slice/user-1000.slice/user@1000.service/session.slice/dbus.service 1 871.449ms 2.4M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service 6 736.924ms 7.8M - -
user.slice/user-1000.slice/user@1000.service/app.slice/save-jalbum-settings.service 2 677.218ms 1.2M - -
user.slice/user-1000.slice/user@1000.service/session.slice/plasma-ksmserver.service 7 651.673ms 42.8M - -
user.slice/user-1000.slice/user@1000.service/app.slice/app-kaccess@autostart.service 7 604.707ms 19.1M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service 3 588.031ms 5.1M - -
user.slice/user-1000.slice/user@1000.service/init.scope 2 576.464ms 3.5M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-polkit-agent.service 9 451.559ms 23.2M - -
user.slice/user-1000.slice/user@1000.service/session.slice/plasma-xdg-desktop-portal-kde.service 7 434.726ms 21.3M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kactivitymanagerd.service 6 363.634ms 7.3M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-xembedsniproxy.service 3 312.893ms 5.9M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kscreen.service 3 307.631ms 3.2M - -
user.slice/user-1000.slice/user@1000.service/background.slice/plasma-gmenudbusmenuproxy.service 3 305.959ms 4.1M - -
user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service 4 279.934ms 12.3M - -
user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal-gtk.service 8 271.167ms 23.1M - -
user.slice/user-1000.slice/user@1000.service/session.slice/xdg-desktop-portal.service 6 225.402ms 22.7M - -
user.slice/user-1000.slice/user@1000.service/session.slice/xdg-document-portal.service 7 39.543ms 6.0M - -
user.slice/user-1000.slice/user@1000.service/session.slice/gvfs-daemon.service 9 22.616ms 6.0M - -
user.slice/user-1000.slice/user@1000.service/app.slice/app-geoclue\x2ddemo\x2dagent@autostart.service 3 12.919ms 2.9M - -
user.slice/user-1000.slice/user@1000.service/app.slice/xdg-permission-store.service 3 7.210ms 2.7M - -
user.slice/user-1000.slice/user@1000.service/app.slice/dconf.service 3 6.319ms 816.0K - -
**erlangen:~ #**
Okay, you already found I think the culprit.
I did explicitly remove KDE Akonadi in the past as I do not like it:
sudo zypper rm libKF5AkonadiCore5
sudo zypper addlock libKF5AkonadiCore5
It removes more, zypper will tell you.
I apologize for not giving you enough details but I was examining the fundamental problems. I became confused after changing from xfs to btrfs as rapid changes sometimes do. I am supplying you with the information you requested -
Control Group Tasks CPU Time Memory Input/s Output/s
/ 1411 4h 26min 46.360000s 6.9G - -
user.slice 1116 3h 54min 3.573395s 9.0G - -
user.slice/user-1000.slice 1112 3h 53min 59.048819s 8.6G - -
user.slice/user-1000.slice/user@1000.service 1107 3h 53min 53.839447s 8.6G - -
system.slice 94 25min 45.695181s 1002.6M - -
system.slice/display-manager.service 4 21min 48.082510s - - -
system.slice/tor.service 18 3min 3.643284s - - -
system.slice/udisks2.service 5 9.295124s - - -
user.slice/user-1000.slice/session-6.scope 5 5.204721s 44.8M - -
system.slice/systemd-udevd.service 1 4.488186s - - -
system.slice/dbus.service 1 2.809456s - - -
init.scope 1 2.498167s 8.3M - -
system.slice/wickedd.service 1 2.120947s - - -
system.slice/systemd-journald.service 1 1.364558s - - -
system.slice/firewalld.service 2 1.115301s - - -
system.slice/postfix.service 3 656.715ms - - -
system.slice/libvirtd.service 2 604.880ms - - -
system.slice/irqbalance.service 2 595.837ms - - -
system.slice/wpa_supplicant.service 1 551.783ms - - -
system.slice/nscd.service 16 353.056ms - - -
system.slice/haveged.service 1 344.220ms - - -
user.slice/user-0.slice 4 326.299ms 8.1M - -
system.slice/polkit.service 3 312.062ms - - -
user.slice/user-0.slice/user@0.service 2 262.097ms - - -
system.slice/systemd-logind.service 1 260.642ms - - -
system.slice/smartd.service 1 229.520ms - - -
system.slice/chronyd.service 1 182.933ms - - -
system.slice/rtkit-daemon.service 3 168.014ms - - -
system.slice/cups.service 1 164.588ms - - -
system.slice/rsyslog.service 5 133.437ms - - -
system.slice/cron.service 1 127.409ms - - -
system.slice/privoxy.service 1 105.934ms - - -
system.slice/systemd-machined.service 1 87.696ms - - -
system.slice/ModemManager.service 3 77.082ms - - -
system.slice/avahi-daemon.service 1 65.214ms - - -
system.slice/auditd.service 2 61.040ms - - -
user.slice/user-0.slice/session-4.scope 2 58.965ms - - -
system.slice/wickedd-dhcp4.service 1 56.795ms - - -
system.slice/wickedd-nanny.service 1 55.287ms - - -
system.slice/wickedd-dhcp6.service 1 52.523ms - - -
system.slice/wickedd-auto4.service 1 46.746ms - - -
system.slice/upower.service 3 43.279ms - - -
system.slice/system-getty.slice 1 25.105ms - - -
system.slice/power-profiles-daemon.service 3 22.527ms - - -
These vitals that you requested come after kalendarac autostart has been disabled. After hiding “org.kde.kalendarac.desktop,” the problem seems to be fixed. The next time I upgrade my distribution, I’ll keep an eye on the events and let you know if I encounter any lags or freezes.
Yeah, it freaked me out. I copied ‘/etc/xdg/autostart/org.kde.kalendarac.desktop’ to ~/.config/autostart and appended Hidden=true after [Desktop Entry].
I never made a request. I made a suggestion. The output shown points to the user slice but fails to pinpoint the culprit. It will be exposed by running the second command I suggested.
By the way: Disabling kalendarac is an overreaction. It starts on all my machines and never caused trouble since many years:
karl@erlangen:~> journalctl --user -b 0 --identifier kalendarac
Okt 29 21:13:02 erlangen kalendarac[4857]: **Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.**
Okt 29 21:13:03 erlangen kalendarac[4948]: **Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.**
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.collectionattributetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.collectionmimetyperelation OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.collectionpimitemrelation OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.collectiontable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.flagtable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.mimetypetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.parttable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.parttypetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.pimitemflagrelation OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.pimitemtable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.pimitemtagrelation OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.relationtable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.relationtypetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.resourcetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.schemaversiontable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.tagattributetable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.tagremoteidresourcerelationtable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.tagtable OK
Okt 29 21:13:03 erlangen kalendarac[5088]: akonadi.tagtypetable OK
karl@erlangen:~>
**erlangen:~ #** systemd-cgtop --cpu=time -1 user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kalendarac@autostart.service
Control Group Tasks CPU Time Memory Input/s Output/s
user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kalendarac@autostart.service 218 3min 12.538338s 897.2M - -
**erlangen:~ #**
I deleted it; it’s no longer active, and the system functions just well without it.
PS.: A request is a specific requirement for something (information in this case). When you make a suggestion, you are telling someone that it would be better if they did something (not explicit). You requested more information, which does not imply a suggestion.