You are not logged in.

#1 2019-02-05 01:34:54

slytux
Member
From: New York
Registered: 2010-09-25
Posts: 129

KDE Plasma: plasmashell using 8GB after update

I upgraded some packages today and there seems to be a problem with memory usage (normal desktop was below 512MB).  plasmashell is part of plasma-workspace.  I also see a black taskbar briefly upon logging in.  Does it have to do with the qt update?  Please revert and remove any backdoors.

Last edited by slytux (2019-02-05 01:52:25)

Offline

#2 2019-02-05 17:32:02

alexandr05
Member
Registered: 2019-02-05
Posts: 1

Re: KDE Plasma: plasmashell using 8GB after update

I have the same problem when choosing the Oxygen theme. If I choose the Breeze theme, then the memory consumption is normal.

Offline

#3 2019-02-06 03:09:18

RickDeckard
Member
From: Acworth, Georgia, USA
Registered: 2016-02-19
Posts: 59

Re: KDE Plasma: plasmashell using 8GB after update

slytux wrote:

Please revert and remove any backdoors.

I'm also experiencing this problem.  There are any number of code issues that could lead to excessive memory use, which you would know if you took a proactive stance and contributed to the source for any of them.

Offline

#4 2019-02-06 09:06:37

Storm
Member
From: Hungary
Registered: 2014-09-12
Posts: 139
Website

Re: KDE Plasma: plasmashell using 8GB after update

Aye, same here.

In addition, the K menu dashboard is broken, nothing will launch from it - I can still launch applications from the run box (Alt+Space).


"Sic itur ad astra per aspera."

Offline

#5 2019-02-06 09:37:49

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,787
Website

Re: KDE Plasma: plasmashell using 8GB after update

Can we have a little less 'me-too', and a lot more 'relevant information', please. For a start, information about your hardware might prove useful, as well as a complete journal from an affected session, and pacman.log so we can see exactly which packages were upgraded, and from which versions.

https://bbs.archlinux.org/viewtopic.php?id=57855

Mod note: moving to NC.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#6 2019-02-06 10:21:18

Storm
Member
From: Hungary
Registered: 2014-09-12
Posts: 139
Website

Re: KDE Plasma: plasmashell using 8GB after update

Sorry, I have to work now.

But restoring system to 1st February state removed the issue, so the problem happened after that date.


P.s.: Not arguing just curious: why is a thread about a broken KDE/Plasma more relevant to NC than the Desktop environments forum? I thought NC is more for cases of having issues due to limited experience.


"Sic itur ad astra per aspera."

Offline

#7 2019-02-06 16:32:19

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: KDE Plasma: plasmashell using 8GB after update

Storm wrote:

P.s.: Not arguing just curious: why is a thread about a broken KDE/Plasma more relevant to NC than the Desktop environments forum? I thought NC is more for cases of having issues due to limited experience.

Because so far no-one in this thread has posted any sort of useful logs or other troubleshooting information - until this changes then the thread doesn't deserve to be anywhere else.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#8 2019-02-06 18:47:34

RickDeckard
Member
From: Acworth, Georgia, USA
Registered: 2016-02-19
Posts: 59

Re: KDE Plasma: plasmashell using 8GB after update

Since you asked and since I'm at my computer right now to get it done

Relevant section of pacman.log (from Feb. 1st onward as per Storm)

[2019-02-01 14:29] [PACMAN] Running 'pacman -Syw'
[2019-02-01 14:29] [PACMAN] synchronizing package lists
[2019-02-01 14:29] [PACMAN] Running 'pacman -Swu'
[2019-02-01 14:29] [PACMAN] starting full system upgrade
[2019-02-01 14:29] [PACMAN] Running 'pacman -Swu'
[2019-02-01 14:29] [PACMAN] starting full system upgrade
[2019-02-01 14:48] [PACMAN] Running 'pacman -Su'
[2019-02-01 14:48] [PACMAN] starting full system upgrade
[2019-02-01 14:48] [PACMAN] Running 'pacman -S archlinux-keyring'
[2019-02-01 14:48] [ALPM] transaction started
[2019-02-01 14:48] [ALPM] upgraded archlinux-keyring (20181218-1 -> 20190123-1)
[2019-02-01 14:48] [ALPM-SCRIPTLET] ==> archlinux.gpg からキーを追加...
[2019-02-01 14:48] [ALPM-SCRIPTLET] ==> キーリングの信頼されたキーに署名...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 DDB867B92AA789C165EEFA799B729B06A680C281...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 684148BB25B49E986A4944C55184252D824B18E8...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 91FFE0700E80619CEB73235CA88E23E377514E00...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キーに署名 AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2019-02-01 14:48] [ALPM-SCRIPTLET] ==> 所有者信頼値をインポート...
[2019-02-01 14:48] [ALPM-SCRIPTLET] gpg: setting ownertrust to 4
[2019-02-01 14:48] [ALPM-SCRIPTLET] ==> キーリングの破棄されたキーを無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 8F76BEEA0289F9E1D3E229C05F946DED983D4366 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 63F395DE2D6398BBE458F281F2DBB4931985A992 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 27FFC4769E19F096D41D9265A04F9397CDFD6BB0 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 39F880E50E49A4D11341E8F939E4F17F295AFBF4 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 5559BC1A32B8F76B3FCCD9555FA5E5544F010D48 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 07DFD3A0BC213FA12EDC217559B3122E2FA915EC を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 5A2257D19FF7E1E0E415968CE62F853100F0D0F0 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 7FA647CD89891DEDC060287BB9113D1ED21E1A55 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー BC1FBE4D2826A0B51E47ED62E2539214C6C11350 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 5696C003B0854206450C8E5BE613C09CB4440678 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 8CF934E339CAD8ABF342E822E711306E3C4F88BC を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 5E7585ADFF106BFFBBA319DC654B877A0864983E を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 40440DC037C05620984379A6761FAD69BA06C6A9 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 81D7F8241DB38BC759C80FCE3A726C6170E80477 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー E7210A59715F6940CF9A4E36A001876699AD6E84 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 5357F3B111688D88C1D88119FCF2CB179205AC90 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー FB871F0131FEA4FB5A9192B4C8880A6406361833 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 66BD74A036D522F51DD70A3C7F2A16726521E06D を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー B1F2C889CB2CCB2ADA36D963097D629E437520BD を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 40776A5221EF5AD468A4906D42A1DB15EC133BAD を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET]   -> キー 44D4A033AC140143927397D47EFD567D4C7EA887 を無効化...
[2019-02-01 14:48] [ALPM-SCRIPTLET] ==> 信用データベースを更新...
[2019-02-01 14:48] [ALPM-SCRIPTLET] gpg: 次回の信用データベース検査は、2019-10-03です
[2019-02-01 14:48] [ALPM] transaction completed
[2019-02-01 14:48] [ALPM] running 'systemd-update.hook'...
[2019-02-01 14:48] [ALPM] running 'zzz-relabel-selinux.hook'...
[2019-02-01 14:48] [ALPM-SCRIPTLET] Relabeling package files...
[2019-02-01 14:48] [ALPM-SCRIPTLET] Relabeling generated directories...
[2019-02-01 14:57] [PACMAN] Running 'pacman -Su'
[2019-02-01 14:57] [PACMAN] starting full system upgrade
[2019-02-01 15:01] [ALPM] transaction started
[2019-02-01 15:01] [ALPM] error: could not rename /etc/services.pacnew to /etc/services (許可されていない操作です)
[2019-02-01 15:01] [ALPM] error: problem occurred while upgrading iana-etc
[2019-02-01 15:01] [ALPM] upgraded iana-etc (20181219-1 -> 20190125-1)
[2019-02-01 15:01] [ALPM] transaction failed
[2019-02-01 15:02] [PACMAN] Running 'pacman -Su'
[2019-02-01 15:02] [PACMAN] starting full system upgrade
[2019-02-01 15:07] [ALPM] transaction started
[2019-02-01 15:07] [ALPM] upgraded libxml2 (2.9.8-8 -> 2.9.9-1)
[2019-02-01 15:07] [ALPM] upgraded glib2 (2.58.2-1 -> 2.58.3-1)
[2019-02-01 15:07] [ALPM] upgraded appstream (0.12.4-1 -> 0.12.5-1)
[2019-02-01 15:07] [ALPM] upgraded shared-mime-info (1.10-1 -> 1.12-1)
[2019-02-01 15:07] [ALPM] upgraded libdrm (2.4.96-1 -> 2.4.97-1)
[2019-02-01 15:07] [ALPM] upgraded libunwind (1.2.1-2 -> 1.3.1-1)
[2019-02-01 15:07] [ALPM] upgraded llvm-libs (7.0.1-1 -> 7.0.1-2)
[2019-02-01 15:07] [ALPM] upgraded mesa (18.3.1-1 -> 18.3.2-1)
[2019-02-01 15:07] [ALPM] upgraded tslib (1.18-1 -> 1.19-1)
[2019-02-01 15:07] [ALPM] upgraded libgpg-error (1.33-1 -> 1.35-1)
[2019-02-01 15:07] [ALPM] upgraded libsasl (2.1.26-13 -> 2.1.26-16)
[2019-02-01 15:07] [ALPM] upgraded libinput (1.12.5-1 -> 1.12.6-1)
[2019-02-01 15:07] [ALPM] upgraded harfbuzz (2.3.0-1 -> 2.3.1-1)
[2019-02-01 15:07] [ALPM] upgraded p11-kit (0.23.14-1 -> 0.23.15-1)
[2019-02-01 15:08] [ALPM] upgraded gnutls (3.6.5-4 -> 3.6.6-1)
[2019-02-01 15:08] [ALPM] upgraded zstd (1.3.7-1 -> 1.3.8-1)
[2019-02-01 15:08] [ALPM] upgraded qt5-base (5.12.0-2 -> 5.12.0-3)
[2019-02-01 15:08] [ALPM] upgraded appstream-qt (0.12.4-1 -> 0.12.5-1)
[2019-02-01 15:08] [ALPM] upgraded ca-certificates-mozilla (3.41-1 -> 3.42-1)
[2019-02-01 15:08] [ALPM] upgraded librsvg (2:2.44.11-1 -> 2:2.44.12-1)
[2019-02-01 15:08] [ALPM] upgraded gtk-update-icon-cache (3.24.3-1 -> 3.24.4+15+g80b5024239-1)
[2019-02-01 15:08] [ALPM] upgraded gtk3 (3.24.3-1 -> 3.24.4+15+g80b5024239-1)
[2019-02-01 15:08] [ALPM] upgraded nss (3.41-1 -> 3.42-1)
[2019-02-01 15:09] [ALPM] upgraded noto-fonts (20181024-1 -> 20190111-1)
[2019-02-01 15:09] [ALPM] upgraded libwebp (1.0.1-1 -> 1.0.2-1)
[2019-02-01 15:09] [ALPM] upgraded libva (2.3.0-1 -> 2.4.0-1)
[2019-02-01 15:10] [ALPM] upgraded chromium (71.0.3578.98-3 -> 72.0.3626.81-1)
[2019-02-01 15:10] [ALPM] upgraded libuv (1.24.1-1 -> 1.25.0-1)
[2019-02-01 15:10] [ALPM] upgraded cmake (3.13.2-1 -> 3.13.3-2)
[2019-02-01 15:10] [ALPM] upgraded cryfs (0.9.9-4 -> 0.9.10-1)
[2019-02-01 15:10] [ALPM] upgraded python-packaging (18.0-1 -> 19.0-1)
[2019-02-01 15:10] [ALPM] upgraded python-setuptools (1:40.6.3-1 -> 1:40.7.2-1)
[2019-02-01 15:10] [ALPM] upgraded cython (0.29.2-1 -> 0.29.3-1)
[2019-02-01 15:10] [ALPM] upgraded dnscrypt-proxy (2.0.19-1 -> 2.0.19-2)
[2019-02-01 15:10] [ALPM] upgraded exo (0.12.3-1 -> 0.12.4-1)
[2019-02-01 15:10] [ALPM] warning: /etc/firejail/firejail.config installed as /etc/firejail/firejail.config.pacnew
[2019-02-01 15:10] [ALPM] upgraded firejail (0.9.56-1 -> 0.9.58-1)
[2019-02-01 15:10] [ALPM] upgraded gcr (3.28.0-4 -> 3.28.1-1)
[2019-02-01 15:10] [ALPM] upgraded ghostscript (9.26-1 -> 9.26-2)
[2019-02-01 15:10] [ALPM] upgraded iso-codes (4.1-1 -> 4.2-1)
[2019-02-01 15:10] [ALPM] upgraded libpipeline (1.5.0-1 -> 1.5.1-1)
[2019-02-01 15:12] [ALPM] upgraded linux-firmware (20181218.0f22c85-1 -> 20190118.a8b75ca-1)
[2019-02-01 15:13] [ALPM] upgraded linux-hardened (4.19.15.a-1 -> 4.20.6.a-1)
[2019-02-01 15:14] [ALPM] upgraded linux-hardened-docs (4.19.15.a-1 -> 4.20.6.a-1)
[2019-02-01 15:15] [ALPM] upgraded linux-hardened-headers (4.19.15.a-1 -> 4.20.6.a-1)
[2019-02-01 15:17] [ALPM] upgraded linux-headers (4.20.3.arch1-1 -> 4.20.6.arch1-1)
[2019-02-01 15:17] [ALPM] upgraded meson (0.49.0-2 -> 0.49.1-1)
[2019-02-01 15:17] [ALPM] upgraded msmtp (1.8.1-1 -> 1.8.2-1)
[2019-02-01 15:17] [ALPM] upgraded msmtp-mta (1.8.1-1 -> 1.8.2-1)
[2019-02-01 15:20] [ALPM] upgraded noto-fonts-cjk (20181130-1 -> 20181130-2)
[2019-02-01 15:21] [ALPM] upgraded poppler (0.72.0-1 -> 0.73.0-1)
[2019-02-01 15:21] [ALPM] upgraded poppler-qt5 (0.72.0-1 -> 0.73.0-1)
[2019-02-01 15:21] [ALPM] upgraded python-decorator (4.3.0-2 -> 4.3.2-1)
[2019-02-01 15:21] [ALPM] upgraded python2-decorator (4.3.0-2 -> 4.3.2-1)
[2019-02-01 15:21] [ALPM] upgraded python2-packaging (18.0-1 -> 19.0-1)
[2019-02-01 15:21] [ALPM] upgraded python2-setuptools (1:40.6.3-1 -> 1:40.7.2-1)
[2019-02-01 15:21] [ALPM] upgraded python2-pbr (5.1.1-1 -> 5.1.2-1)
[2019-02-01 15:21] [ALPM] upgraded qt5-tools (5.12.0-1 -> 5.12.0-2)
[2019-02-01 15:21] [ALPM] warning: directory permissions differ on /etc/ipsec.d/certs/
[2019-02-01 15:21] [ALPM] warning: directory permissions differ on /etc/ipsec.d/private/
[2019-02-01 15:21] [ALPM] upgraded strongswan (5.7.1-1 -> 5.7.2-1)
[2019-02-01 15:21] [ALPM] upgraded thunar (1.8.2-2 -> 1.8.4-1)
[2019-02-01 15:21] [ALPM] upgraded usbmuxd (1.1.0+48+g1cc8b34-2 -> 1.1.0+48+g1cc8b34-3)
[2019-02-01 15:21] [ALPM] transaction completed
[2019-02-01 15:21] [ALPM] running '60-linux-hardened.hook'...
[2019-02-01 15:23] [ALPM] running '90-linux-hardened.hook'...
[2019-02-01 15:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'default'
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-hardened -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-hardened.img
[2019-02-01 15:23] [ALPM-SCRIPTLET] ==> Starting build: 4.20.6.a-1-hardened
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-02-01 15:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-02-01 15:24] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [usr]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2019-02-01 15:25] [ALPM-SCRIPTLET]   -> Running build hook: [shutdown]
[2019-02-01 15:25] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-02-01 15:25] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-hardened.img
[2019-02-01 15:26] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-02-01 15:26] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-hardened.preset: 'fallback'
[2019-02-01 15:26] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-hardened -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-hardened-fallback.img -S autodetect
[2019-02-01 15:26] [ALPM-SCRIPTLET] ==> Starting build: 4.20.6.a-1-hardened
[2019-02-01 15:26] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-02-01 15:26] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-02-01 15:26] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-02-01 15:26] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-02-01 15:27] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2019-02-01 15:27] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2019-02-01 15:29] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2019-02-01 15:29] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2019-02-01 15:29] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-02-01 15:29] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-02-01 15:30] [ALPM-SCRIPTLET]   -> Running build hook: [usr]
[2019-02-01 15:30] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2019-02-01 15:30] [ALPM-SCRIPTLET]   -> Running build hook: [shutdown]
[2019-02-01 15:30] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-02-01 15:30] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-hardened-fallback.img
[2019-02-01 15:32] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-02-01 15:32] [ALPM] running 'fontconfig.hook'...
[2019-02-01 15:32] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2019-02-01 15:32] [ALPM] running 'glib-compile-schemas.hook'...
[2019-02-01 15:32] [ALPM] running 'gtk-query-immodules-3.0.hook'...
[2019-02-01 15:32] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-02-01 15:32] [ALPM] running 'systemd-daemon-reload.hook'...
[2019-02-01 15:32] [ALPM] running 'systemd-sysusers.hook'...
[2019-02-01 15:32] [ALPM] running 'systemd-tmpfiles.hook'...
[2019-02-01 15:32] [ALPM] running 'systemd-udev-reload.hook'...
[2019-02-01 15:32] [ALPM] running 'systemd-update.hook'...
[2019-02-01 15:32] [ALPM] running 'texinfo-install.hook'...
[2019-02-01 15:32] [ALPM] running 'update-appstream-cache.hook'...
[2019-02-01 15:32] [ALPM-SCRIPTLET] AppStream cache update completed successfully.
[2019-02-01 15:32] [ALPM] running 'update-ca-trust.hook'...
[2019-02-01 15:33] [ALPM] running 'update-desktop-database.hook'...
[2019-02-01 15:33] [ALPM] running 'update-mime-database.hook'...
[2019-02-01 15:33] [ALPM] running 'xorg-mkfontdir.hook'...
[2019-02-01 15:33] [ALPM] running 'zzz-relabel-selinux.hook'...
[2019-02-01 15:33] [ALPM-SCRIPTLET] Relabeling package files...
[2019-02-01 15:48] [ALPM-SCRIPTLET] Relabeling generated directories...
[2019-02-01 16:35] [PACMAN] Running 'pacman -Su'
[2019-02-01 16:35] [PACMAN] starting full system upgrade
[2019-02-01 23:56] [PACMAN] Running 'pacman -Syw'
[2019-02-01 23:56] [PACMAN] synchronizing package lists
[2019-02-01 23:57] [PACMAN] Running 'pacman -Syw'
[2019-02-01 23:57] [PACMAN] synchronizing package lists
[2019-02-01 23:57] [PACMAN] Running 'pacman -Syw'
[2019-02-01 23:57] [PACMAN] synchronizing package lists
[2019-02-01 23:58] [PACMAN] Running 'pacman -Syw'
[2019-02-01 23:58] [PACMAN] synchronizing package lists
[2019-02-02 23:04] [PACMAN] Running 'pacman -Syw'
[2019-02-02 23:04] [PACMAN] synchronizing package lists
[2019-02-02 23:04] [PACMAN] Running 'pacman -Rns graphviz'
[2019-02-02 23:04] [PACMAN] Running 'pacman -Rns graphviz gd'
[2019-02-02 23:04] [ALPM] transaction started
[2019-02-02 23:04] [ALPM] removed graphviz (2.40.1-14)
[2019-02-02 23:04] [ALPM] removed gts (0.7.6-5)
[2019-02-02 23:04] [ALPM] removed gsfonts (20180524-2)
[2019-02-02 23:04] [ALPM] removed gd (2.2.5-1)
[2019-02-02 23:04] [ALPM] transaction completed
[2019-02-02 23:04] [ALPM] running 'fontconfig.hook'...
[2019-02-02 23:04] [ALPM] running 'systemd-update.hook'...
[2019-02-02 23:04] [ALPM] running 'xorg-mkfontdir.hook'...
[2019-02-02 23:05] [PACMAN] Running 'pacman -Swu'
[2019-02-02 23:05] [PACMAN] starting full system upgrade
[2019-02-03 17:55] [PACMAN] Running 'pacman -Syw'
[2019-02-03 17:55] [PACMAN] synchronizing package lists
[2019-02-03 17:55] [PACMAN] Running 'pacman -Swu'
[2019-02-03 17:55] [PACMAN] starting full system upgrade
[2019-02-04 12:18] [PACMAN] Running 'pacman -Syw'
[2019-02-04 12:18] [PACMAN] synchronizing package lists
[2019-02-04 12:18] [PACMAN] Running 'pacman -Swu'
[2019-02-04 12:18] [PACMAN] starting full system upgrade
[2019-02-04 13:08] [PACMAN] Running 'pacman -Su'
[2019-02-04 13:08] [PACMAN] starting full system upgrade
[2019-02-04 13:08] [PACMAN] Running 'pacman -Su'
[2019-02-04 13:08] [PACMAN] starting full system upgrade
[2019-02-04 13:09] [ALPM] transaction started
[2019-02-04 13:09] [ALPM] upgraded ca-certificates-mozilla (3.42-1 -> 3.42.1-1)
[2019-02-04 13:09] [ALPM] upgraded rhash (1.3.7-1 -> 1.3.8-1)
[2019-02-04 13:09] [ALPM] upgraded cmake (3.13.3-2 -> 3.13.4-1)
[2019-02-04 13:09] [ALPM] upgraded python-setuptools (1:40.7.2-1 -> 1:40.7.3-1)
[2019-02-04 13:09] [ALPM] upgraded cython (0.29.3-1 -> 0.29.4-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-base (5.12.0-3 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded kcodecs (5.54.0-1 -> 5.54.0-2)
[2019-02-04 13:10] [ALPM] upgraded qt5-sensors (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-script (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-x11extras (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-multimedia (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-speech (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-svg (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-declarative (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded ndctl (63-1 -> 64-1)
[2019-02-04 13:10] [ALPM] upgraded nss (3.42-1 -> 3.42.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-graphicaleffects (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-quickcontrols (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded qt5-quickcontrols2 (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:10] [ALPM] upgraded kwin (5.14.5-1 -> 5.14.5-2)
[2019-02-04 13:10] [ALPM] upgraded libgit2 (1:0.27.7-1 -> 1:0.27.8-1)
[2019-02-04 13:10] [ALPM] upgraded ninja (1.8.2-1 -> 1.9.0-1)
[2019-02-04 13:10] [ALPM] upgraded python2-setuptools (1:40.7.2-1 -> 1:40.7.3-1)
[2019-02-04 13:11] [ALPM] upgraded qt5-location (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:11] [ALPM] upgraded qt5-tools (5.12.0-2 -> 5.12.1-1)
[2019-02-04 13:11] [ALPM] upgraded qt5-webchannel (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:11] [ALPM] upgraded qt5-webengine (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:12] [ALPM] upgraded qt5-webkit (5.212.0alpha2-22 -> 5.212.0alpha2-23)
[2019-02-04 13:12] [ALPM] upgraded qt5-xmlpatterns (5.12.0-1 -> 5.12.1-1)
[2019-02-04 13:12] [ALPM] upgraded ruby (2.6.0-5 -> 2.6.1-1)
[2019-02-04 13:12] [ALPM] transaction completed
[2019-02-04 13:12] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-02-04 13:12] [ALPM] running 'systemd-daemon-reload.hook'...
[2019-02-04 13:12] [ALPM] running 'systemd-update.hook'...
[2019-02-04 13:12] [ALPM] running 'update-ca-trust.hook'...
[2019-02-04 13:12] [ALPM] running 'update-desktop-database.hook'...
[2019-02-04 13:12] [ALPM] running 'update-mime-database.hook'...
[2019-02-04 13:12] [ALPM] running 'zzz-relabel-selinux.hook'...
[2019-02-04 13:12] [ALPM-SCRIPTLET] Relabeling package files...
[2019-02-04 13:14] [ALPM-SCRIPTLET] Relabeling generated directories...
[2019-02-04 13:28] [PACMAN] Running 'pacman -S mariadb-libs'
[2019-02-04 13:43] [PACMAN] Running 'pacman -Syw'
[2019-02-04 13:43] [PACMAN] synchronizing package lists
[2019-02-04 13:43] [PACMAN] Running 'pacman -Syw'
[2019-02-04 13:43] [PACMAN] synchronizing package lists
[2019-02-04 13:43] [PACMAN] Running 'pacman -S mariadb-libs'
[2019-02-04 13:43] [ALPM] transaction started
[2019-02-04 13:43] [ALPM] installed mariadb-libs (10.3.12-5)
[2019-02-04 13:43] [ALPM] transaction completed
[2019-02-04 13:43] [ALPM] running 'systemd-update.hook'...
[2019-02-04 13:43] [ALPM] running 'zzz-relabel-selinux.hook'...
[2019-02-04 13:43] [ALPM-SCRIPTLET] Relabeling package files...
[2019-02-04 13:43] [ALPM-SCRIPTLET] Relabeling generated directories...
[2019-02-04 13:47] [PACMAN] Running 'pacman -Syw'
[2019-02-04 13:47] [PACMAN] synchronizing package lists
[2019-02-05 12:40] [PACMAN] Running 'pacman -Syw'
[2019-02-05 12:40] [PACMAN] synchronizing package lists
[2019-02-05 12:51] [PACMAN] Running 'pacman -Syw'
[2019-02-05 12:51] [PACMAN] synchronizing package lists
[2019-02-05 13:06] [PACMAN] Running 'pacman -Syw'
[2019-02-05 13:06] [PACMAN] synchronizing package lists

No plasma updates and lots of QT5 updates.

And now the specific failure notice in question, which contains said hardware information:

-- Logs begin at Fri 2019-02-01 15:46:48 EST, end at Tue 2019-02-05 17:34:21 EST. --
 2月 05 16:41:49 acidstar-four kernel: kded5 invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null), order=0, oom_score_adj=0
 2月 05 16:41:54 acidstar-four kernel: kded5 cpuset=/ mems_allowed=0
 2月 05 16:41:54 acidstar-four kernel: CPU: 0 PID: 878 Comm: kded5 Not tainted 4.20.6.a-1-hardened #1
 2月 05 16:41:56 acidstar-four kernel: Hardware name: TOSHIBA Satellite C655D/Portable PC, BIOS 1.50 07/02/2010
 2月 05 16:41:56 acidstar-four kernel: Call Trace:
 2月 05 16:41:56 acidstar-four kernel:  dump_stack+0x5c/0x78
 2月 05 16:41:56 acidstar-four kernel:  dump_header+0x6b/0x2ad
 2月 05 16:41:56 acidstar-four kernel:  ? do_try_to_free_pages+0x2ec/0x370
 2月 05 16:41:56 acidstar-four kernel:  ? _raw_spin_unlock_irqrestore+0x2b/0x40
 2月 05 16:41:56 acidstar-four kernel:  oom_kill_process.cold.7+0xb/0x1e4
 2月 05 16:41:57 acidstar-four kernel:  out_of_memory+0x1a3/0x450
 2月 05 16:41:57 acidstar-four kernel:  __alloc_pages_nodemask+0xc55/0x1090
 2月 05 16:41:57 acidstar-four kernel:  filemap_fault+0x3ff/0x640
 2月 05 16:41:59 acidstar-four kernel:  __do_fault+0x38/0x120
 2月 05 16:41:59 acidstar-four kernel:  __handle_mm_fault+0xe03/0x1620
 2月 05 16:41:59 acidstar-four kernel:  handle_mm_fault+0x10a/0x250
 2月 05 16:41:59 acidstar-four kernel:  __do_page_fault+0x231/0x510
 2月 05 16:41:59 acidstar-four kernel:  do_page_fault+0x32/0x130
 2月 05 16:41:59 acidstar-four kernel:  ? page_fault+0x8/0x30
 2月 05 16:41:59 acidstar-four kernel:  page_fault+0x1e/0x30
 2月 05 16:41:59 acidstar-four kernel: RIP: 0033:0x68e1025844f7
 2月 05 16:41:59 acidstar-four kernel: Code: Bad RIP value.
 2月 05 16:42:00 acidstar-four kernel: RSP: 002b:00007922b21ca938 EFLAGS: 00010206
 2月 05 16:42:00 acidstar-four kernel: RAX: 000068e0f8009200 RBX: 000000000000000f RCX: 0000000000000000
 2月 05 16:42:00 acidstar-four kernel: RDX: 000068e0fd868720 RSI: 0000000000000000 RDI: 000068e0f800dac0
 2月 05 16:42:00 acidstar-four kernel: RBP: 00007922b21cac80 R08: 0000000000000002 R09: 0000000000000001
 2月 05 16:42:00 acidstar-four kernel: R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000006
 2月 05 16:42:00 acidstar-four kernel: R13: 0000044a8d58afc0 R14: 00007922b21ca9d0 R15: 00007922b21caa30
 2月 05 16:42:00 acidstar-four kernel: Mem-Info:
 2月 05 16:42:01 acidstar-four kernel: active_anon:723695 inactive_anon:145484 isolated_anon:0
                                         active_file:274 inactive_file:2734 isolated_file:0
                                         unevictable:8 dirty:0 writeback:1246 unstable:0
                                         slab_reclaimable:8206 slab_unreclaimable:15493
                                         mapped:136 shmem:6 pagetables:7982 bounce:0
                                         free:20728 free_pcp:0 free_cma:0
 2月 05 16:42:01 acidstar-four kernel: Node 0 active_anon:2894780kB inactive_anon:581936kB active_file:1096kB inactive_file:10936kB unevictable:32kB isolated(anon):0kB isolated(file):0kB mapped:544kB dirty:0kB writeback:4984kB shmem:24kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? yes
 2月 05 16:42:01 acidstar-four kernel: Node 0 DMA free:14872kB min:284kB low:352kB high:420kB active_anon:956kB inactive_anon:52kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB kernel_stack:0kB pagetables:12kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
 2月 05 16:42:01 acidstar-four kernel: lowmem_reserve[]: 0 3452 3647 3647 3647
 2月 05 16:42:01 acidstar-four kernel: Node 0 DMA32 free:64448kB min:63700kB low:79624kB high:95548kB active_anon:2770708kB inactive_anon:578408kB active_file:812kB inactive_file:10712kB unevictable:32kB writepending:4968kB present:3648800kB managed:3560948kB mlocked:32kB kernel_stack:2880kB pagetables:30952kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
 2月 05 16:42:01 acidstar-four kernel: lowmem_reserve[]: 0 0 194 194 194
 2月 05 16:42:01 acidstar-four kernel: Node 0 Normal free:3592kB min:3592kB low:4488kB high:5384kB active_anon:123116kB inactive_anon:3476kB active_file:240kB inactive_file:212kB unevictable:0kB writepending:16kB present:262144kB managed:199492kB mlocked:0kB kernel_stack:2032kB pagetables:964kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
 2月 05 16:42:01 acidstar-four kernel: lowmem_reserve[]: 0 0 0 0 0
 2月 05 16:42:01 acidstar-four kernel: Node 0 DMA: 4*4kB (UM) 3*8kB (UM) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 2*1024kB (UM) 0*2048kB 3*4096kB (M) = 14872kB
 2月 05 16:42:01 acidstar-four kernel: Node 0 DMA32: 980*4kB (UE) 751*8kB (UE) 798*16kB (UME) 690*32kB (UME) 216*64kB (UME) 36*128kB (UME) 5*256kB (U) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 64488kB
 2月 05 16:42:01 acidstar-four kernel: Node 0 Normal: 19*4kB (UM) 13*8kB (UM) 136*16kB (UE) 39*32kB (UE) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3604kB
 2月 05 16:42:03 acidstar-four kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
 2月 05 16:42:03 acidstar-four kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
 2月 05 16:42:03 acidstar-four kernel: 4659 total pagecache pages
 2月 05 16:42:03 acidstar-four kernel: 1662 pages in swap cache
 2月 05 16:42:03 acidstar-four kernel: Swap cache stats: add 2186768, delete 2185106, find 49818/94168
 2月 05 16:42:03 acidstar-four kernel: Free swap  = 0kB
 2月 05 16:42:03 acidstar-four kernel: Total swap = 8388604kB
 2月 05 16:42:03 acidstar-four kernel: 981734 pages RAM
 2月 05 16:42:03 acidstar-four kernel: 0 pages HighMem/MovableOnly
 2月 05 16:42:03 acidstar-four kernel: 37647 pages reserved
 2月 05 16:42:03 acidstar-four kernel: 0 pages hwpoisoned
 2月 05 16:42:03 acidstar-four kernel: Tasks state (memory values in pages):
 2月 05 16:42:03 acidstar-four kernel: [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
 2月 05 16:42:03 acidstar-four kernel: [    395]     0   395    21619        0    57344       86             0 lvmetad
 2月 05 16:42:03 acidstar-four kernel: [    399]     0   399    11972       12   114688      767         -1000 systemd-udevd
 2月 05 16:42:03 acidstar-four kernel: [    597]     0   597     5778       18    73728       82         -1000 auditd
 2月 05 16:42:03 acidstar-four kernel: [    620]    81   620     5515       55    73728      307          -900 dbus-daemon
 2月 05 16:42:03 acidstar-four kernel: [    621] 62582   621   158250        0   184320     1898             0 dnscrypt-proxy
 2月 05 16:42:03 acidstar-four kernel: [    623]     0   623     3948       19    69632      172             0 crond
 2月 05 16:42:03 acidstar-four kernel: [    627]     0   627     8699       10   114688      592             0 systemd-logind
 2月 05 16:42:03 acidstar-four kernel: [    631]    64   631   180248        0  1245184   138409             0 clamd
 2月 05 16:42:03 acidstar-four kernel: [    660]     0   660   157733       46   221184      872             0 NetworkManager
 2月 05 16:42:03 acidstar-four kernel: [    674]   975   674     5241        0    86016     2158             0 unbound
 2月 05 16:42:03 acidstar-four kernel: [    680]   102   680   423782       18   204800     1660             0 polkitd
 2月 05 16:42:03 acidstar-four kernel: [    683]     0   683     4142       16    73728      191             0 wpa_supplicant
 2月 05 16:42:03 acidstar-four kernel: [    731]     0   731     1857        0    57344       95             0 starter
 2月 05 16:42:03 acidstar-four kernel: [    751]     0   751   173874        0   221184      887             0 charon
 2月 05 16:42:03 acidstar-four kernel: [    775]     0   775    60835        0   106496      453             0 lightdm
 2月 05 16:42:03 acidstar-four kernel: [    782]     0   782    64105       45   348160     4088             0 Xorg
 2月 05 16:42:03 acidstar-four kernel: [    811]     0   811    54500        4   196608      492             0 lightdm
 2月 05 16:42:03 acidstar-four kernel: [    824]  1000   824     9439        1   114688      399             0 systemd
 2月 05 16:42:05 acidstar-four kernel: [    826]  1000   826    43186        0   212992     1163             0 (sd-pam)
 2月 05 16:42:05 acidstar-four kernel: [    841]  1000   841     2357        1    61440      117             0 startkde
 2月 05 16:42:05 acidstar-four kernel: [    845]  1000   845     5342        0    61440      203             0 dbus-daemon
 2月 05 16:42:05 acidstar-four kernel: [    872]  1000   872      552        0    40960       24             0 start_kdeinit
 2月 05 16:42:05 acidstar-four kernel: [    873]  1000   873    29465       28   229376      810             0 kdeinit5
 2月 05 16:42:05 acidstar-four kernel: [    874]  1000   874    78019      140   315392     1023             0 klauncher
 2月 05 16:42:05 acidstar-four kernel: [    878]  1000   878   163629      561   450560     1799             0 kded5
 2月 05 16:42:05 acidstar-four kernel: [    892]  1000   892    81850       58   335872     1229             0 kaccess
 2月 05 16:42:05 acidstar-four kernel: [    894]  1000   894    12765        0   106496      146             0 kwrapper5
 2月 05 16:42:05 acidstar-four kernel: [    895]  1000   895   257831      158   417792     2120             0 ksmserver
 2月 05 16:42:05 acidstar-four kernel: [    899]  1000   899    77990        1   315392     1439             0 kglobalaccel5
 2月 05 16:42:05 acidstar-four kernel: [    911]  1000   911    39772        1    77824      147             0 dconf-service
 2月 05 16:42:05 acidstar-four kernel: [    914]  1000   914   722238      147   659456     4853             0 kwin_x11
 2月 05 16:42:05 acidstar-four kernel: [    917]  1000   917   153981      218   589824     4880             0 krunner
 2月 05 16:42:05 acidstar-four kernel: [    919]  1000   919 25418838   864008 22933504  1905433             0 plasmashell
 2月 05 16:42:05 acidstar-four kernel: [    925]  1000   925    63984       91   229376      481             0 xembedsniproxy
 2月 05 16:42:05 acidstar-four kernel: [    928]  1000   928    64230       88   225280      481             0 gmenudbusmenupr
 2月 05 16:42:05 acidstar-four kernel: [    931]  1000   931    14915      192   155648       68             0 xscreensaver
 2月 05 16:42:05 acidstar-four kernel: [    933]  1000   933   109706      387   315392     1059             0 org_kde_powerde
 2月 05 16:42:05 acidstar-four kernel: [    953]  1000   953   125081        0   286720      996             0 kactivitymanage
 2月 05 16:42:05 acidstar-four kernel: [    980]  1000   980   143529        1   258048      834             0 pulseaudio
 2月 05 16:42:05 acidstar-four kernel: [    993]  1000   993    11171        0    77824      207             0 obexd
 2月 05 16:42:05 acidstar-four kernel: [   1004]  1000  1004    63513        0   135168      286             0 gsettings-helpe
 2月 05 16:42:05 acidstar-four kernel: [   1007]     0  1007   102738       66   176128      778             0 udisksd
 2月 05 16:42:05 acidstar-four kernel: [   1075]  1000  1075    62285        0   212992      566             0 kscreen_backend
 2月 05 16:42:05 acidstar-four kernel: [   1085]  1000  1085    48081        0   233472      909             0 desktop.so
 2月 05 16:42:05 acidstar-four kernel: [   1089]  1000  1089    29574       27   225280      815             0 file.so
 2月 05 16:42:05 acidstar-four kernel: [   1092]  1000  1092    79006        0   323584     1243             0 kuiserver5
 2月 05 16:42:05 acidstar-four kernel: [   1103]  1000  1103    19070       38   143360      284             0 kcminit
 2月 05 16:42:05 acidstar-four kernel: [   1110]  1000  1110    44326      228   200704      227             0 kcminit
 2月 05 16:42:05 acidstar-four kernel: [   1112]     0  1112    23237       57   192512      159             0 systemd-journal
 2月 05 16:42:05 acidstar-four kernel: [   1126]     0  1126     1930        0    49152       33             0 agetty
 2月 05 16:42:05 acidstar-four kernel: [   1158]  1000  1158     7367      105   102400        0             0 bumps
 2月 05 16:42:05 acidstar-four kernel: [   1160]     0  1160     3974       82    69632      735             0 lvm
 2月 05 16:42:05 acidstar-four kernel: [   1163]     0  1163    10174       36   114688      217             0 crond
 2月 05 16:42:05 acidstar-four kernel: [   1167]     0  1167     2528      110    53248        4             0 lvm
 2月 05 16:42:05 acidstar-four kernel: Out of memory: Kill process 919 (plasmashell) score 912 or sacrifice child
 2月 05 16:42:05 acidstar-four kernel: Killed process 919 (plasmashell) total-vm:101675352kB, anon-rss:3456032kB, file-rss:0kB, shmem-rss:0kB
 2月 05 16:42:05 acidstar-four kernel: oom_reaper: reaped process 919 (plasmashell), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

Offline

#9 2019-02-07 17:33:27

hamelg
Member
From: France
Registered: 2008-06-19
Posts: 128

Re: KDE Plasma: plasmashell using 8GB after update

Same thing here sad
qt 5.12.1 is the culprit.
Downgrade to qt5 5.12.0 fix the issue :

pacman -U  qt5*5.12.0-1*

see here :
https://bugs.archlinux.org/task/61638

Last edited by hamelg (2019-02-07 19:44:09)

Offline

#10 2019-02-07 20:09:26

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

I have opened a bug report in upstream (kde and Qt5), for the moment no progress, it's difficult to debug because there is no useful infos in the logs, maybe there are environment variables to set for Qt5 and plasma in order to have a more verbose log ?

Last edited by Potomac (2019-02-07 20:09:47)

Offline

#11 2019-02-08 11:36:08

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

the bugreport in qt5 bugtracker :
https://bugreports.qt.io/browse/QTBUG-73691

although this is not suitable for beginners the best option to help solving this bug is to do a git-bisect, in order to find which modification in Qt5 5.12.1 triggers the bug :
https://git-scm.com/docs/git-bisect

we can also check the differences of features between oxygen theme and breeze theme by checking their source code, we know that oxygen theme uses some Qt5 functions that triggers a memory leak when using Qt5 5.12.1 libs

Offline

#12 2019-02-08 14:13:54

Storm
Member
From: Hungary
Registered: 2014-09-12
Posts: 139
Website

Re: KDE Plasma: plasmashell using 8GB after update

Actually I use Breeze Dark theme with a desktop theme of Simple Glass, and still had this issue.


"Sic itur ad astra per aspera."

Offline

#13 2019-02-08 20:26:24

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

Storm : maybe you have not the same bug,

here the symptoms are those described by alexandr05 :

I have the same problem when choosing the Oxygen theme. If I choose the Breeze theme, then the memory consumption is normal.

and there is a second and different bug which is solved by Qt5base 5.12.1-2 package,

but the original bug of this thread (memory leak when choosing oxygen) is still not solved, I tried Qt5base 5.12.1-2 package and the bug is still here,

to check if there is an excessive memory usage : open a terminal (ctrl-alt-f2), then type "free -mh", you will see how many ram is used by the system, when the bug occurs all ram is used and the swap file is used at 100%, which cause extreme slowness,

some users don't set swap file or have a too small swap file, so the system will crash as soon there is no more RAM left

Last edited by Potomac (2019-02-08 20:31:47)

Offline

#14 2019-02-08 21:34:28

RickDeckard
Member
From: Acworth, Georgia, USA
Registered: 2016-02-19
Posts: 59

Re: KDE Plasma: plasmashell using 8GB after update

Potomac wrote:

to check if there is an excessive memory usage : open a terminal (ctrl-alt-f2), then type "free -mh", you will see how many ram is used by the system, when the bug occurs all ram is used and the swap file is used at 100%, which cause extreme slowness,

some users don't set swap file or have a too small swap file, so the system will crash...

Opening a spare tty and sudo'ing to root before logging in KDE on tty7, and typing in "watch -n 1 free -mh", I began to notice effects not as soon as the Plasma widgets loaded (ie the little desktop switcher at the corner of the screen) but after the desktop background loaded.  My hard drive was noticeably active sound wise, and within 5 seconds of the background loading the "free" area of "Mem:" dropped to 112 Mi out of 3.6 Gi.  Swap file is 8GB and was unaffected, so it's not playing into this on my end.  I did a "pkill -15 plasmashell" in that same root console to restore normal operation, albeit without KDE.

Offline

#15 2019-02-10 15:58:32

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

@hamelg : what graphic card do you use ?

I want to know if the problem of excessive ram consumption (when using oxygen theme) concerns radeon users (the workaround in Qt5 5.12.1-2 targets only nvidia users with the nouveau driver), and if this problem can be reproduced in virtualbox/qemu, with the gpu generic driver.

Offline

#16 2019-02-10 16:10:54

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

Slithery wrote:
Storm wrote:

P.s.: Not arguing just curious: why is a thread about a broken KDE/Plasma more relevant to NC than the Desktop environments forum? I thought NC is more for cases of having issues due to limited experience.

Because so far no-one in this thread has posted any sort of useful logs or other troubleshooting information - until this changes then the thread doesn't deserve to be anywhere else.

it's because there is no change in the log (dmesg, journalctl)  when the memory leak occurs, I tried yesterday to see if there is a change in the log between the use of Qt5 5.12.0 and Qt5 5.12.1 --> it's exactly the same log, no new line, no new error/warning message,

the symptoms are just a massive memory leak (plasmashell uses 7.3 Gb on my PC, with swap disk usage), an extreme slowness (mouse pointer takes a long time to move), and it's impossible to launch a GUI software from the KDE menu,

so I suggest to the moderators to move this thread to the appropriate section : "Applications & Desktop Environment"

in the Qt5 and KDE bugreports I have detailled my configuration :

- graphic card : amd radeon HD4650 pcie, with the radeon driver
- CPU : intel quad core Q9650
- ram : 8 Gb ram DDR2
- oxygen theme
- openGL 2.0 acceleration in compositor in KDE settings
- one screen (no dual monitor)
- no wayland (I think I use defaults settings for plasma, X11 display)

I created also a new user (in order to have a new KDE/plasma profile in /home) --> the problem is still here when using oxygen theme,

the problem doesn't occur with the previous version of Qt5 (5.12.0), if I chose "breeze" (or another theme) then no problems with Qt5 5.12.1

Last edited by Potomac (2019-02-10 16:20:20)

Offline

#17 2019-02-10 16:29:44

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: KDE Plasma: plasmashell using 8GB after update

@Potomac how is your bisection of qt5 between v5.12.0 and v5.12.1 progressing for the upstream bug report?

Last edited by loqs (2019-02-10 16:31:32)

Offline

#18 2019-02-10 17:01:25

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

Is there a way to speed-up the compilation of Qt5-base ?

I tried yesterday and the git clone step takes a long time

Offline

#19 2019-02-10 17:08:47

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

for the git bisect : it's not finished, I will post the results

git bisect bad v5.12.1
git bisect good v5.12.0

Bissection : 223 revisions to test (8 steps)

Offline

#20 2019-02-10 17:09:21

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: KDE Plasma: plasmashell using 8GB after update

The clone from github or the clone makepkg does when it clones the repo locally into the src directory?
The first should only happen once.  The second I do not know of any way to improve the performance of that operation.
Edit:  The second should also be one time operation provide you run `makepkg -e`.

Last edited by loqs (2019-02-10 17:19:47)

Offline

#21 2019-02-10 18:07:01

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

I experience a problem when I want to create an archlinux package of qt5-base where the source is the content of a directory created by a git bisect command,

here what I have done, I type these commands :

- git clone https://github.com/qt/qtbase.git
- cd qt5base
- git bisect start
- git bisect bad v5.12.1
- git bisect good v5.12.0

all these files are in a directory "qt5base",

then I decided to use the content of this directory as a source for the PGKBUILD of qt5-base :
https://git.archlinux.org/svntogit/pack … s/qt5-base

So I have created a tar.gz compressed file of the directory "qt5base" :  qtbase-everywhere-src-5.12.1.tar.gz

and I modified the PKGBUILD for the line "source" :

source=("${_pkgfqn}.tar.gz"

instead of :

source=("https://download.qt.io/official_releases/qt/${pkgver%.*}/${_qtver}/submodules/${_pkgfqn}.tar.xz"

then I type : "makepkg -c"

but I get an error for the step "make", the headers for Qt can not be found, it's not normal because Qt headers are installed on my system (/usr/include/qt/)

Last edited by Potomac (2019-02-10 18:20:39)

Offline

#22 2019-02-10 18:51:59

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: KDE Plasma: plasmashell using 8GB after update

Please try the following using the PKGBUILD in the second code block in an empty directory.

makepkg -ors
cd src/qt5-base/
git checkout v5.12.0
cd ../..
makepkg -ersi # build v5.12.0 locally make sure it works
cd src/qt5-base/
git bisect start
git bisect good
git checkout v5.12.1
cd ../..
makepkg -ersi # build v5.12.0 locally make sure it fails
cd src/qt5-base/
git bisect bad
cd ../..
makepkg -ersi # test git bisection point
cd src/qt5-base/
git bisect $result
# Maintainer: Felix Yan <felixonmars@archlinux.org>
# Contributor: Andrea Scarpino <andrea@archlinux.org>

_pkgname=qt5-base
pkgbase=qt5-base-git
pkgname=(qt5-base-git qt5-xcb-private-headers-git)
pkgver=5.12.1.r152.g035d80407b
pkgrel=1
arch=('x86_64')
url='https://www.qt.io'
license=('GPL3' 'LGPL3' 'FDL' 'custom')
pkgdesc='A cross-platform application and UI framework'
depends=('libjpeg-turbo' 'xcb-util-keysyms' 'xcb-util-renderutil' 'libgl' 'fontconfig' 'xdg-utils'
         'shared-mime-info' 'xcb-util-wm' 'libxrender' 'libxi' 'sqlite' 'xcb-util-image' 'mesa'
         'tslib' 'libinput' 'libxkbcommon-x11' 'libproxy' 'libcups' 'double-conversion')
makedepends=('libfbclient' 'mariadb-libs' 'sqlite' 'unixodbc' 'postgresql-libs' 'alsa-lib' 'gst-plugins-base-libs'
             'gtk3' 'libpulse' 'cups' 'freetds' 'vulkan-headers' 'git')
optdepends=('qt5-svg: to use SVG icon themes'
            'qt5-translations: for some native UI translations'
            'postgresql-libs: PostgreSQL driver'
            'mariadb-libs: MariaDB driver'
            'unixodbc: ODBC driver'
            'libfbclient: Firebird/iBase driver'
            'freetds: MS SQL driver'
            'gtk3: GTK platform plugin')
conflicts=('qtchooser')
groups=('qt' 'qt5')

source=("$_pkgname::git://code.qt.io/qt/qtbase.git")
sha256sums=('SKIP')

pkgver() {
  cd ${_pkgname}
  git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
}

prepare() {
  cd ${_pkgname}

  # This also sets default {C,CXX,LD}FLAGS for projects built using qmake
  sed -i -e "s|^\(QMAKE_CFLAGS_RELEASE.*\)|\1 ${CFLAGS}|" \
    mkspecs/common/gcc-base.conf
  sed -i -e "s|^\(QMAKE_LFLAGS_RELEASE.*\)|\1 ${LDFLAGS}|" \
    mkspecs/common/g++-unix.conf
}

build() {
  cd ${_pkgname}

  ./configure -confirm-license -opensource -v \
    -prefix /usr \
    -docdir /usr/share/doc/qt \
    -headerdir /usr/include/qt \
    -archdatadir /usr/lib/qt \
    -datadir /usr/share/qt \
    -sysconfdir /etc/xdg \
    -examplesdir /usr/share/doc/qt/examples \
    -plugin-sql-{psql,mysql,sqlite,odbc,ibase} \
    -system-sqlite \
    -openssl-linked \
    -nomake examples \
    -no-rpath \
    -optimized-qmake \
    -dbus-linked \
    -system-harfbuzz \
    -journald \
    -no-use-gold-linker \
    -reduce-relocations
  make
}

package_qt5-base-git() {
  pkgdesc='A cross-platform application and UI framework'
  provides=(qt5-base)
  conflicts+=(qt5-base)

  cd ${_pkgname}
  make INSTALL_ROOT="${pkgdir}" install

  install -Dm644 LICENSE* -t "$pkgdir"/usr/share/licenses/$pkgbase

  # Drop QMAKE_PRL_BUILD_DIR because reference the build dir
  find "${pkgdir}/usr/lib" -type f -name '*.prl' \
    -exec sed -i -e '/^QMAKE_PRL_BUILD_DIR/d' {} \;

  # Fix wrong qmake path in pri file
  sed -i "s|${srcdir}/${_pkgfqn}|/usr|" \
    "${pkgdir}"/usr/lib/qt/mkspecs/modules/qt_lib_bootstrap_private.pri

  # Symlinks for backwards compatibility
  for b in "${pkgdir}"/usr/bin/*; do
    ln -s $(basename $b) "${pkgdir}"/usr/bin/$(basename $b)-qt5
  done
}

package_qt5-xcb-private-headers-git() {
  pkgdesc='Private headers for Qt5 Xcb'

  depends=("qt5-base-git=$pkgver")
  optdepends=()
  groups=()
  provides=(qt5-xcb-private-headers)
  conflicts=(qt5-xcb-private-headers)

  cd ${_pkgname}
  install -d -m755 "$pkgdir"/usr/include/qtxcb-private
  cp -r src/plugins/platforms/xcb/*.h "$pkgdir"/usr/include/qtxcb-private/
}

Edit:
added missing -e option to subsequent makepkg use.
Edit2:
fix provides / conflicts.

Last edited by loqs (2019-02-10 20:04:26)

Offline

#23 2019-02-10 19:01:09

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

I am not sure to understand yours quotes,

Do I need to put your new PKGBUILD (the content of the second quote) in an empty directory before typing the commands of your first quote ?

Offline

#24 2019-02-10 19:03:55

loqs
Member
Registered: 2014-03-06
Posts: 17,196

Re: KDE Plasma: plasmashell using 8GB after update

@Potomac yes

Offline

#25 2019-02-10 19:08:14

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: KDE Plasma: plasmashell using 8GB after update

Ok, so I try your modification, for the moment I am on the step :

makepkg -ors
cd src/qt5-base/
git checkout v5.12.0
cd ../..
makepkg -ersi # build v5.12.0 locally make sure it works

no error for the moment

Offline

Board footer

Powered by FluxBB