[Testing Update] 2024-09-07 - Plasma 6.1.4, KDE Gear 24.08, Mauikit 4.0, Mesa 24.2.2

Hello community, here we have another set of package updates. This also marks the preview cycle of 24.1 release also to been known as Xahea. Preview ISOs will get released as we see fit.

Current Promotions

  • Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
  • Protect your personal data, keep yourself safe with Surfshark VPN: Get 3 months extra

Recent News

Previous News
Finding information easier about Manjaro

Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: News – Manjaro

image

Notable Package Updates

Additional Info

Nvidia driver downgrade

Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:

555 release feedback & discussion - Linux - NVIDIA Developer Forums
550.78 release feedback & discussion thread - Linux - NVIDIA Developer Forums

Python 3.12 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.11/ :

pacman -Qoq /usr/lib/python3.11/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.11)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

checkrebuild
Info about AUR packages

:warning: 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.


Our current supported kernels

  • linux419 4.19.320
  • linux54 5.4.282
  • linux510 5.10.224
  • linux515 5.15.165
  • linux61 6.1.106
  • linux66 6.6.47
  • linux69 6.9.12 [EOL]
  • linux610 6.10.6
  • linux611 6.11.0 rc4
  • linux61-rt 6.1.105_rt38
  • linux66-rt 6.6.44_rt39
  • linux69-rt 6.9_rt5
  • linux610-rt 6.10.2_rt14

Package Changes (Sat Sep 7 21:06:25 CEST 2024)

  • testing core x86_64: 38 new and 38 removed package(s)
  • testing extra x86_64: 3138 new and 3126 removed package(s)
  • testing multilib x86_64: 133 new and 134 removed package(s)

Overlay Changes

  • testing core x86_64: 2 new and 2 removed package(s)
  • testing extra x86_64: 36 new and 237 removed package(s)
  • testing multilib x86_64: 1 new and 1 removed package(s)

A list of all package changes can be found here and here

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)
0 voters

Check if your mirror has already synced:

4 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed


Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

:information_source: 2024-09-09

Added by @linux-arhus

System freeze on suspend

A feature in systemd 256 freezing a user session when suspending may freeze the system.

The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.

A workaround for this is to create a override config

/etc/systemd/system/systemd-suspend.service.d/disable_freeze_user_session.conf

containing

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

:arrow_right: 2024-09-07

2024-08-04

pulseaudio-ctl requires pulseaudio and is not compatible with pipewire

If one is using PipeWire, one will need to remove pulseaudio-ctl if prompted during the update as it’s only compatible with pulseaudio

2024-06-03

:warning: Linux 6.9 is EOL

Linux 6.9 is EOL and will - at some point - be removed from the repo.

Suggestion is to install latest LTS to be sure

sudo mhwd-kernel -i linux66

2024-07-14

Nvidia driver downgrade

Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:

555 release feedback & discussion - Linux - NVIDIA Developer Forums
550.78 release feedback & discussion thread - Linux - NVIDIA Developer Forums

2024-07-01

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

Previous testing threads:

Don’t upgrade new version kernels? 6.10.8 and RC?

very cool to see plasma 6.1.4 has moved into testing from unstable… will be watching this thread more to see how folks experience this update.

When it comes to the testing branch participation, is it at all useful to test it within a VM? or is it always best to test on real hardware?

1 Like

On a real hardware. You can still rollback update with a timeshift backup. I’ve been using testing branch for years, and it proved to be quite stable for me. I occasionally jump to unstable for quicker Plasma updates.

However, I cannot recommend unstable branch for a long run. I had in the past few problems with it when I used it for a longer time. There were sometimes Arch regressions and updates that broke the system, and it couldn’t boot. They fixed it quickly, within hours, but I still had a bad luck of installing it before it. Arch base is always risky. Testing branch mitigates those critical bugs. The rest of bugs that can happen is manageable and not so serious.

There were also times where I had very little time, so I wished my system to work and not bothered be with updates and potential issues, so I was switching to stable branch. However, 90% of time since few years I am using testing branch and it’s quite OK. Also it’s better for AUR packages since testing is not that far away from Arch.

5 Likes

No it’s not. It depends on your specific hardware, the DE, customization and packages you are using and your experience in managing your OS and updates. I also run for years a system on Arch and never had any nameable issues.

4 Likes

Seams to working great, went from Stable + Nvidia 560.x (nvidia-beta) to this branch + still Nvidia-beta, seam to working smooth

1 Like

Agree, and - according to Schedules/Plasma 6 - KDE Community Wiki - in approx. 3w’s time Plasma 6.2 is released.

1 Like

A post was split to a new topic: When we can wait NVIDIA R560 in Manjaro?

a bit exciting to upgrade to plasma 6.1 due to the amount of problems reported when it was first released, but turned out entirely without issues. Thanks for keeping even testing stable :slight_smile:

1 Like

Switched from stable to testing because I wanted to try the plasma update. For now I downgraded to stable again because I couldn’t exit KDE properly. On logout, reboot or shutdown, the system hangs with a black screen with a mousepointer. Also the logout screen is in English, whereas everything else is correctly localized (German). Reboot from tty is working.

System:
  Kernel: 6.10.6-10-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.0.5 Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ProArt X670E-CREATOR WIFI v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1904
    date: 01/29/2024
CPU:
  Info: 16-core model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 1024 KiB L2: 16 MiB L3: 128 MiB
  Speed (MHz): avg: 400 min/max: 400/5714 cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 21: 400 22: 400 23: 400
    24: 400 25: 400 26: 400 27: 400 28: 400 29: 400 30: 400 31: 400 32: 400
    bogomips: 268880
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA AD103 [GeForce RTX 4080 SUPER] driver: nvidia v: 550.107.02
    arch: Lovelace bus-ID: 01:00.0
  Device-2: Razer USA Gaming Webcam [Kiyo] driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 9-2:2
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 2560x1440~144Hz
  API: EGL v: 1.5 drivers: nvidia,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.107.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4080
    SUPER/PCIe/SSE2
  API: Vulkan v: 1.3.279 drivers: nvidia surfaces: xcb,xlib devices: 1
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 01:00.1
  Device-2: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 6a:00.6
  Device-3: Razer USA Gaming Webcam [Kiyo] driver: snd-usb-audio,uvcvideo
    type: USB bus-ID: 9-2:2
  API: ALSA v: k6.10.6-10-MANJARO status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.2.3 status: off
  Server-4: PulseAudio v: 17.0 status: active
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    port: N/A bus-ID: 08:00.0
  IF: eno1 state: up speed: 2500 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    bus-ID: 3-6:4
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 10.05 TiB used: 1.24 TiB (12.3%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SKC3000S1024G size: 953.87 GiB
    temp: 28.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X 4000GB
    size: 3.64 TiB temp: 39.9 C
  ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    temp: 37.9 C
  ID-4: /dev/nvme3n1 vendor: Kingston model: SKC3000S1024G size: 953.87 GiB
    temp: 25.9 C
  ID-5: /dev/sda vendor: Western Digital model: WDS400T2B0A-00SM50
    size: 3.64 TiB
Partition:
  ID-1: / size: 870.46 GiB used: 96.38 GiB (11.1%) fs: ext4
    dev: /dev/nvme3n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 300 KiB (0.1%) fs: vfat
    dev: /dev/nvme3n1p1
  ID-3: /home size: 3.58 TiB used: 786.33 GiB (21.4%) fs: ext4
    dev: /dev/nvme1n1p1
Swap:
  ID-1: swap-1 type: partition size: 68.14 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme3n1p3
Sensors:
  System Temperatures: cpu: 37.5 C mobo: 27.0 C gpu: nvidia temp: 46 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 543 fan-3: 0 fan-4: 825 fan-5: 0
    fan-6: 0 fan-7: 2738 gpu: nvidia fan: 0%
Info:
  Memory: total: 64 GiB available: 62.5 GiB used: 6.56 GiB (10.5%)
  Processes: 641 Uptime: 17m Init: systemd
  Packages: 2371 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9
    inxi: 3.3.36

Anything from logs to help troubleshooting?

Did not find anything significant in Xorg.log. Where else should I look?

journalctl yield anything?

Hi, check the thread here:

It probably has to do with session restore. For me it only works when I activate “start with empty session”. When I change it back, same problem.