[Unstable Update] July 2024 Edition

[philm]

Welcome to the new monthly unstable branch thread.

Recent News

Notable Package Changes

• NVIDIA 555.58.02
• GNOME 46.3
• KDE Gear 24.05.2
• LibreOffice 24.2.5
• Phosh 0.40.1
• KDE Frameworks 6.4.0
• VirtualBox 7.2.0
• Mesa 24.1.4
• KDE Plasma 6.1.3
• Thunderbird 115.13.0
• Firefox 128.0.3

Known Issues

The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 - Robin Candau

After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections (see Can't login after openssh 9.8p1-1 upgrade, MUST restart sshd (#5) · Issues · Arch Linux / Packaging / Packages / openssh · GitLab).
When upgrading remote hosts, please make sure to restart the sshd service using systemctl try-restart sshd right after upgrading.

We are evaluating the possibility to automatically apply a restart of the sshd service on upgrade in a future release of the openssh-9.8p1 package.

– Arch Linux - News: The sshd service needs to be restarted after upgrading to openssh-9.8p1

Additional Info

Info about AUR packages

AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.

For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.

---

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Check if your mirror has already synced:

• Mirror-Check Service

[Yochanan]

Known Issue added regarding OpenSSH.

[omano]

Am I the only one who can’t open this disk space/partition manager menu in Dolphin on KDE?
I can click on it, nothing happens (right side of the Zoom thing).

[ydar]

I get the option to open kDiskFree, and Filelight with the following options: current folder, current device, all devices.

[d20diceroller]

The latest Nvidia drivers have broken Steam gaming. Games either won’t start or freeze.

[anon60566263]

With nvidia version 555.58.02 I have not even managed to boot the computer.

No boot - The graphical interface is not reached

Thanks, it was very easy but… it doesn’t boot either… But this solution allows me to go back to another branch in the last case. I do, very bad…

[d20diceroller]

Flatpack Steam updated bringing it inline with the latest Nvidia drivers, fixing the problems. Everything is normal again.

[ydar]

No problems here using Steam Beta (not flatpak or snap) and playing a couple native Linux games.

[anon60566263]

I finally managed to boot my computer with the unstable branch.

In X11 NVIDIA 555.58.02 solves all the problems of previous versions, smooth animations and in general a similar experience to Wayland, I remind you that in multimonitor you must have monitors with the same refresh rate, anything else will not work.

In Wayland the flickering has totally disappeared but there is a performance loss and “Adaptive sync” must be set to “never” in multimonitor.

X11 Kernel 6.6.36 with the following parameters in grub:

nvidia_drm.modeset=0 nvidia_drm.fbdev=0 nvidia.NVreg_EnableGpuFirmware=0

Wayland Kernel 6.6.36 with the following parameters in grub:

nvidia_drm.modeset=1 nvidia_drm.fbdev=0 nvidia.NVreg_EnableGpuFirmware=0

Kernel 6.9 I have not tested it because it is necessary to fbdev=1, modify /etc/mkinitcpio.conf and any false step will cause the computer to freeze.

X11 glmark2

glmark2 -b :duration=15.0 -b shading -b build -b :duration=5.0 -b texture  
=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      NVIDIA Corporation
    GL_RENDERER:    NVIDIA GeForce RTX 4070/PCIe/SSE2
    GL_VERSION:     4.6.0 NVIDIA 555.58.02
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed
=======================================================
[shading] <default>: FPS: 31232 FrameTime: 0.032 ms
[build] <default>: FPS: 33102 FrameTime: 0.030 ms
[texture] <default>: FPS: 33426 FrameTime: 0.030 ms
=======================================================
                                  glmark2 Score: 32585

Wayland glmark2

glmark2 -b :duration=15.0 -b shading -b build -b :duration=5.0 -b texture 
=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      NVIDIA Corporation
    GL_RENDERER:    NVIDIA GeForce RTX 4070/PCIe/SSE2
    GL_VERSION:     4.6.0 NVIDIA 555.58.02
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed
=======================================================
[shading] <default>: FPS: 26254 FrameTime: 0.038 ms
[build] <default>: FPS: 26201 FrameTime: 0.038 ms
[texture] <default>: FPS: 26239 FrameTime: 0.038 ms
=======================================================
                                  glmark2 Score: 26230 

[annoying_daniel]

Unfortunately for me, nvidia 555 brought with it some really nasty firefox crashes (default hw acceleration) and system wake (from suspend) crashes as well. Par for the course I guess.

$ journalctl -b-1 -kp3

kernel: BUG: unable to handle page fault for address: ffffbd8024fdac34
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x0000) - not-present page
kernel: BUG: kernel NULL pointer dereference, address: 000000000000032c
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x0000) - not-present page
kernel: Fixing recursive fault but reboot is needed!
kernel: BUG: scheduling while atomic: irq/95-nvidia/49726/0x00000000

[Kjplay]

Some noteworthy issues with pipewire (reproducible for me):

Speakers muted at boot on `1.2.0` Pipewire version (#4084) · Issues · PipeWire...

Pipewire Errors on Boot: spa.alsa: 'plug:{SLAVE="a52:0,'hw:%f,3'"}': playback...

[openminded]

The latest batch of updates did something to sddm so it fails to load now (kernel 6.10, AMD 7840H). Intel i7 8550u, kernel 6.1: works fine.

[MrKiu]

I confirm there is an issue, but it’s not related to sddm. Seems linked to glib.
sddm segfault on boot.

Logs: Process 1103 (sddm-greeter-qt) of user 964 dumped core. - Pastebin.com

[VoodaGod]

somehow managed to delete my post by mistake:

got a usable system again by “downgrading” mesa to 24.1.3 (from 24.1.2 …)
in my case:

sudo downgrade mesa lib32-mesa mesa-vdpau lib32-mesa-vdpau libva-mesa-driver lib32-libva-mesa-driver vulkan-mesa-layers vulkan-radeon lib32-vulkan-radeon

i am on mesa-nonfree though

[mithrial]

LLVM had an upgrade, so mesa (and related packages) needs a rebuild.

[Yochanan]

Our Mesa packages were built with LLVM 18.

[Jaypee]

It seems startplasma-wayland via TTY doesn’t work either.

I’m using the non-free Mesa as well. Seems to be a common factor here.

---

Moderator edit: Removed photo of text on a monitor. Please copy and paste logs instead.

[Yochanan]

@VoodaGod

i am on mesa-nonfree

@Jaypee

I’m using the non-free Mesa

That’s a community repo and not officially supported. It also has absolutely nothing to do with official updates and is completely off-topic here. Also, it hasn’t been updated to match the current release.

[Jaypee]

Yup, very much aware of that. Had to give this a shot all the same, to see what happens

[Kjplay]

I can also confirm issues with the latest batch of updates, namely with the vulkan.
For a moment (before this batch) gamescope on nvidia as a secondary GPU was working properly, now it does not