×

[Testing Update] 2024-08-16 – Kernels, KDE Frameworks, Mesa, GNOME, Phosh – Testing Updates

Manjaro

[Testing Update] 2024-08-16 – Kernels, KDE Frameworks, Mesa, GNOME, Phosh – Testing Updates


Hello community, here we have another set of package updates.

Current Promotions

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

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.319
  • linux54 5.4.281
  • linux510 5.10.223
  • linux515 5.15.164
  • linux61 6.1.105
  • linux66 6.6.46
  • linux69 6.9.12 [EOL]
  • linux610 6.10.5
  • linux611 6.11.0 rc3
  • linux61-rt 6.1.102_rt37
  • linux66-rt 6.6.44_rt39
  • linux69-rt 6.9_rt5
  • linux610-rt 6.10.2_rt14

Package Changes (Fri Aug 16 06:08:14 CEST 2024)

  • testing core x86_64: 37 new and 37 removed package(s)
  • testing extra x86_64: 2097 new and 2089 removed package(s)
  • testing multilib x86_64: 31 new and 20 removed package(s)

Overlay Changes

  • testing core x86_64: 37 new and 37 removed package(s)
  • testing extra x86_64: 202 new and 315 removed package(s)
  • testing multilib x86_64: 0 new and 11 removed package(s)

A list of all package changes can be found 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)

Check if your mirror has already synced:



2 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:

:arrow_right: 2024-08-16

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

2024-05-18

Shutdown Issues on some AMD systems (fixed in latest kernels)

2024-05-14

No plasma interface with kernel 6.9 + Nvidia gpu + Wayland

If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.

To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub

Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

If it was not present, then run sudo mkinitcpio -P after adding it.

2024-05-08

Qemu: MacOS is not bootable with 9.0

Due to a bug MacOS is not bootable with 9.0: [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab
Workaround: remove virtio-serial and org.qemu.guest_agent.0 from libvirt XML until bug will be fixed.

2024-05-02

The default KDE Plasma session has been changed to X11

As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.

Split this topic




3

4 posts were split to a new topic: Ruby 3.2 mirgration support

Running gnome, update went well but when I rebooted no wifi adapter was detected. Rebooted for a second time and wifi adapter started working fine again. Hopefully just a gremlin but if it happens again I’ll grab some logs and post system info



1 Like

Arch repo does not contain pulseaudio-ctl, is it really needed to have it in Manjaro’s repo?

I’ve edited the inaccurate wiki statement above. It now reads:

Probably not–especially since Manjaro now uses PipeWire by default.



3 Likes

I noticed, that after this update, two packages vanished from repo and now are AUR packages:

xsane
xsane-gimp

Is there a reason for that? Is some other package taking over the functionality?

Upstream moved the packages to AUR – that reflects on Manjaro.

Check the sane packages instead – please see → SANE – ArchWiki



3 Likes

Yeah, I realized that, but does anyone knows why?

As far I know, this is needed for scanner support. Is there an alternative?

I checked the AUR and it was dropped because it won’t build. In AUR, they added a patch for it to build. Then I checked gitlab, and it wasn’t updated since 2 years and seems to be abandoned.

Xsane always felt a vital and core part to make the scanner work, so maybe I’m missing something and it’s not needed anymore?

UPDATE: Ah, thanks for the link @linux-aarhus. So xsane is not really needed, it’s sane that is the backbone. I also use Scanpage, which is way better then original xsane, so in theory, I can remove it safely, with the exception of gimp-plugin. But I can scan something outside of Gimp and open it in Gimp. It should be a core part of Gimp (no plugin needed).



1 Like

What you found is a valid reason for an Arch maintainer.

Arch policy is something like ‘We don’t fix upstream issues. Does it build? OK – otherwise – ditch it’ :wastebasket:

:slight_smile:



2 Likes

OK, thanks. I confused it for sane and thought to be a core component, but if it’s only a frontend, one of many, it’s not a big deal then. Case closed :wink: .



Source link