Plasma 5.21 is out

Desktop Environments Plasma
102

Seems to be a GPU/driver(?) issue. It’s working on my Netbook with Intel GPU.
On my Desktop :

inxi -G
Graphics:  Device-1: NVIDIA GF100 [GeForce GTX 465] driver: nvidia v: 390.141 
          Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia unloaded: fbdev,modesetting,vesa 
          resolution: 1920x1080~60Hz 
          OpenGL: renderer: GeForce GTX 465/PCIe/SSE2 v: 4.6.0 NVIDIA 390.14
103

Yep I installed plasma-wayland-session, rebooted, I just get a hard hang on a black screen on logging in. I’m not sure if it’s just my nvidia drivers, but for now I’m sticking with X11 which does what I need.

In terms of how to run it, - just install plasma-wayland-session and then choose it from the login screen? I don’t think it’s any more complicated than that…

1 Like
104

I had these as well. I switched to wayland and they went away. Something is up with x11 :thinking: i only have AMD hardware.

You might be on the right track here. I did the same and so far it appears to be working fine.

105

Getting the same locale releated x11 error messages.

Restarting kwin manually gives a more detailed error message.

& kwin_x11 --replace&
[1] 61475

kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)'
kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
kwin_xkbcommon: XKB: Failed to compile xkb_symbols
kwin_xkbcommon: XKB: Failed to compile keymap
OpenGL vendor string:                   AMD
OpenGL renderer string:                 Radeon RX 590 Series (POLARIS10, DRM 3.40.0, 5.10.16-zen1-1-zen, LLVM 11.0.1)
OpenGL version string:                  4.6 (Compatibility Profile) Mesa 20.3.4
OpenGL shading language version string: 4.60
Driver:                                 RadeonSI
GPU class:                              Arctic Islands
OpenGL version:                         4.6
GLSL version:                           4.60
Mesa version:                           20.3.4
X server version:                       1.20.10
Linux kernel version:                   5.10.16
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
kwin_core: XCB error: 10 (BadAccess), sequence: 1742, resource id: 1751, major code: 142 (Composite), minor code: 2 (RedirectSubwindows)
106

It’s a known issue that Nvidia and wayland don’t like each other …

1 Like
107

Hmm. Installed wayland and the first things that I noticed is latte dock won’t start and yakauke doesn’t work. First logged out then back into wayland, then restarted and chose wayland. No dice. Restarting latte didn’t work either.

Neither latte nor yakauke spit out any errors I could find in journalctl. Solaar & superpaper did dump core on me though.

108

Well then launch them from a terminal so you can see any errors it spits out (I’m sure it will spit some).

109

I switched from Gnome to Plasma after reading your enthusiastic messages and I like the most of you, I’m also very impressed.
The only little thing that surprised me is Plasma’s RAM consumption and I wouldn’t think I would say this ever, but Gnome uses less RAM (1.7 GB on idle) Plasma 2.7 GB on Idle. This was different a couple of years ago, but I have enough RAM.

For people like me who had trouble with eos-update-notifier not working, just use the command line eos-update-notifier -init and reboot. I just thought it would be nice to mention this, even though @manuel wrote this in his wiki article also.

1 Like
110

Huh…That’s a lot for Plasma, weird. :thinking:

On 32 Gb RAM system without swap i have ~900 Mb used on system start
Are you on X11 or Wayland?

111

I’m on X11, I also have to say that I’m using Latte dock and Plasma launcher, so it is not a minimal install but my Gnome set up wasn’t minimal either.

3 Likes
112

Yep i’m also on Latte dock :upside_down_face:
Still too much, something weird going on

Maybe if you have 128 / 256 Gb of RAM it’s ok, coz more RAM = more Plasma on start idle use, for example my 64 Gb RAM machine uses something like 1,4 Gb with exactly same setup as 32 Gb one…

3 Likes
113

I think that is the issue, my laptop has 16GB of RAM, I’m going to install the same set up on an older Thinkpad L440 I have over here with 6GB RAM, just to see how it performs in RAM usage.

2 Likes
114

did you also install akonadi and its dependencie like MariaDB? If you don’t use any services that require that, you can remove it as it is the most RAM-hungry part of KDE :wink: For me, freshly booted, KDE uses about 1.2 GB of RAM (without akonadi) and my system has 32GB available.

3 Likes
115

Good point!

Also that reminded me that it’s a very good idea to disable baloo (indexing service, which is hungry and buggy):

balooctl disable
balooctl purge
balooctl suspend
balooctl status
2 Likes
116

Thanks, I did install Mariadb and Akonadi, I thought they were essential for Plasma.

@keybreak I will certainly turn that off too.

EDIT: Yes removing MariaDB and Akonadi and disabling Baloo did the trick. It now uses 1.5 GB (I have some widgets running at startup like weather and cpu monitor)

4 Likes
117

I have 0.75GB in use and that includes latte and megasync on startup. X11 though, not wayland.

2 Likes
118

I’m also on X11 but I have quite some apps and widgets running at start-up. :wink:

1 Like
119

@keybreak So balooctl status, this will tell me IF its running? Safe to purge/remove?

120

You are checking to verify the previous commands worked. You are not so much as removing it as disabling it. :wink: Baloo is kind of like a zombie to kill. :zombie:

2 Likes
121

Yep…Juuuuuuuuuuust to make sure you’ve shot this :zombie: in a head…twice :rofl:

2 Likes