I just did prior to checking the forum. So far, so good…
1 Like
Why not Plasma 6.1? It runs better than 6.0 on my Arch and Manjaro unstable installations.
3 Likes
Because the fact that it might run better on YOUR installations is no guarantee - otherwise there’d be just one test laptop and it’d go straight to Stable 
3 Likes
This is testing. The more people that test it, the sooner it can go to stable branch.
2 Likes
We won’t update to 6.1 Plasma any time soon. There are serious bugs which prevents that. You can find the Plasma 6 upstream release schedule and see when bug fixes are expected. Switch to unstable to help testing. Testing branch is a preparation branch for the Stable branch. So we will see when Plasma 6.1 is enough stable from our end to land here.
14 Likes
In addition to a considerable amount of bugs in 6.1, with NVIDIA 555.58 I have also had black screen problems when logging in and out in both Wayland and X11.
I have reverted to the stable branch.
1 Like
Hi, thanks for the update.
Lutris was not behaving normal right now, so I checked the command line output. It seems it has to be recompiled with the pushed python updates.
The log:
2024-07-01 19:09:32,621: The Battle.net source is unavailable because Google protobuf could not be loaded: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
1. Downgrade the protobuf package to 3.20.x or lower.
2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
EDIT:
Another issue I face and cannot fully resolve is regarding gamscope-plus (and also gamescope (while using lutris). The error:
gamescope: children shut down!
(EE) failed to read Wayland events: Broken pipe
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
Initial process has exited (return code: 0)
(I am on gnome wayland with an AMD graphics card). I tried to downgrade to the previous gamescope version with manjaro-downgrade to resolve the issue, but this warning kept me from doing it to be honest.
Warning: Cannot resolve "libdisplay-info.so=1-64" (a dependency of "gamescope-plus")
Maybe this information helps 
(I am on Gnome Wayland)
I did a rebuild of that package. Let me know if that helps.
1 Like
Can not boot in plasma Wayland with NVIDIA 555, but can in X11. 550 are fine with both sessions. Hyprland is fine with 555
Journalctl states it is OpenGL error:
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL vendor string: NVIDIA Corporation
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL renderer string: NVIDIA GeForce RTX 3060/PCIe/SSE2
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL version string: 3.1.0 NVIDIA 555.58
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Driver: NVIDIA
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Driver version: 555.58
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: GPU class: Unknown
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL version: 3.1
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: GLSL version: 1.40
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Requires strict binding: no
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Virtual Machine: no
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Timer query support: yes
июл 02 10:48:21 dannkuntPC tailscaled[1159]: open-conn-track: timeout opening (TCP 100.115.35.14:51262 => 116.203.91.91:80); no associated peer node
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Same with 6.9 xanmod and 6.6 lts from repos
And I have all recommended boot options:
GRUB_CMDLINE_LINUX_DEFAULT='apparmor=1 security=apparmor resume=UUID=9451eba8-7ab2-4f3a-8619-3a8c95b9ee84 udev.log_priority=3 nvidia-drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0'
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
Did I miss something or this is bug somewhere
Hi. The update went almost OK. The only issue is missing krdp package that is listed as dependency of plasma-meta package:
:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "krdp", a dependency of "plasma-meta"
:: The following package cannot be upgraded due to unresolvable dependencies:
plasma-meta
P.S.
This package status on testing branch is marked yellow in Manjaro packages page:
https://packages.manjaro.org/?query=krdp
There is no yellow status. The colors just separate branches.
The package however only exists in Unstable branch, so here’s your issue.
3 Likes
I’m getting the same error in testing. If krdp is only in unstable, is it necessary to wait before updating testing?
Hi, thank you! Unfortunately, I was not able to downgrade or resolve that issue - also because trying to downgrade also libdisplay-info then would break a dependency of wlroots. Therefore I (again) stepped back. As the issue occurs to me at both issues, I will report it then upstream, which I did not manage to do yesterday.
However, as it might be overlooked because I put two issues into one…: with the log shown at my original answer - does this indicate the need to rebuild of Lutris?
Somehow that got missed in the shuffle. I’ve just restored plasma-meta 6.0-2.
Not if you know how to manage issues like this manually.
Either way, once your mirror(s) update, there will be no issue.
2 Likes
No major problems preventing normal operation.
Slight stuttering in x11, which is theoretically fixed in NVIDIA version 555.58.02 (it’s in the unstable branch but I haven’t been able to get it to boot).
Considerable performance loss in Wayland.
Tests with glxgears:
██████████████████ ████████
██████████████████ ████████ -----------
██████████████████ ████████ OS: Manjaro Linux x86_64
██████████████████ ████████ Kernel: Linux 6.6.36-1-MANJARO
████████ ████████ Uptime: 44 seconds
████████ ████████ ████████ Packages: 2021 (pacman)[testing], 20 (flatpak)
████████ ████████ ████████ Shell: zsh 5.9
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz *
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz
████████ ████████ ████████ DE: KDE Plasma 6.0.5
████████ ████████ ████████ WM: KWin (X11)
████████ ████████ ████████ WM Theme: Breeze
████████ ████████ ████████ Theme: Breeze (Light) [QT], Breeze [GTK2/3/4]
Icons: Fluent-teal-dark [QT], Fluent-teal-dark [GTK2/3/4]
Font: Noto Sans (11pt) [QT], Noto Sans (11pt) [GTK2/3/4]
Cursor: breeze (32px)
Terminal: konsole 24.5.1
Terminal Font: Hack Nerd Font Mono (12pt)
CPU: AMD Ryzen 5 7600X (12) @ 5,53 GHz
GPU: NVIDIA GeForce RTX 4070 [Discrete]
Memory: 6,67 GiB / 62,52 GiB (11%)
Swap: Disabled
Locale: es_ES.UTF-8
~ __GL_SYNC_TO_VBLANK=0 glxgears ✔
198264 frames in 5.0 seconds = 39652.785 FPS
195439 frames in 5.0 seconds = 39087.754 FPS
197681 frames in 5.0 seconds = 39536.184 FPS
198120 frames in 5.0 seconds = 39623.797 FPS
199363 frames in 5.0 seconds = 39872.504 FPS
196710 frames in 5.0 seconds = 39341.812 FPS
S
██████████████████ ████████
██████████████████ ████████ -----------
██████████████████ ████████ OS: Manjaro Linux x86_64
██████████████████ ████████ Kernel: Linux 6.6.36-1-MANJARO
████████ ████████ Uptime: 3 mins
████████ ████████ ████████ Packages: 2021 (pacman)[testing], 20 (flatpak)
████████ ████████ ████████ Shell: zsh 5.9
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz
████████ ████████ ████████ Display (): 1920x1080 @ 144Hz
████████ ████████ ████████ DE: KDE Plasma 6.0.5
████████ ████████ ████████ WM: KWin (Wayland)
████████ ████████ ████████ WM Theme: Breeze
████████ ████████ ████████ Theme: Breeze (Light) [QT], Breeze [GTK2/3/4]
Icons: Fluent-teal-dark [QT], Fluent-teal-dark [GTK2/3/4]
Font: Noto Sans (11pt) [QT], Noto Sans (11pt) [GTK2/3/4]
Cursor: breeze (32px)
Terminal: konsole 24.5.1
Terminal Font: Hack Nerd Font Mono (12pt)
CPU: AMD Ryzen 5 7600X (12) @ 5,53 GHz
GPU: NVIDIA GeForce RTX 4070 [Discrete]
Memory: 6,57 GiB / 62,52 GiB (11%)
Swap: Disabled
Locale: es_ES.UTF-8
~ __GL_SYNC_TO_VBLANK=0 glxgears ✔
48999 frames in 5.0 seconds = 9799.771 FPS
49490 frames in 5.0 seconds = 9897.877 FPS
49726 frames in 5.0 seconds = 9943.802 FPS
48047 frames in 5.0 seconds = 9609.194 FPS
44814 frames in 5.0 seconds = 8962.757 FPS
49410 frames in 5.0 seconds = 9881.810 FPS
I just tried nvidia.NVreg_EnableGpuFirmware=0 in grub and the stuttering goes away in x11, on the other hand when waking up from hibernate it freezes.
I’m a little confused. If you check libdisplay-info you see that 2.0 is in testing and unstable. I compiled gamescope-plus against the new libdisplay-info package. Simply update to the latest packages and let me know if that solves your issue. Why downgrade? To which exact versions? @zar0nick
After testing I think that the best option for NVIDIA is version 555.58.02. And most of the problems are from plasma 6.1 version.
In the current NVIDIA version (555.58.) there is a considerable loss of performance.
So … from the Manjaro team, would it be possible for you to push version 555.58.02 to testing?
2 Likes
Yes, please