×

[Testing Update] 2024-10-15 – Kernels, KDE Gear, KDE Frameworks, Firefox, Thunderbird, Pamac – Testing Updates

[Testing Update] 2024-10-15 – Kernels, KDE Gear, KDE Frameworks, Firefox, Thunderbird, Pamac – 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.322
  • linux54 5.4.284
  • linux510 5.10.226
  • linux515 5.15.167
  • linux61 6.1.114
  • linux66 6.6.56
  • linux610 6.10.14 [EOL]
  • linux611 6.11.3
  • linux612 6.12.0-rc3
  • linux61-rt 6.1.111_rt42
  • linux66-rt 6.6.52_rt43
  • linux610-rt 6.10.2_rt14

Package Changes (Tue Oct 15 04:53:18 CEST 2024)

  • testing core x86_64: 8 new and 8 removed package(s)
  • testing extra x86_64: 1641 new and 1677 removed package(s)
  • testing multilib x86_64: 2 new and 2 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:




1 Like

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-10-15

Kernel 6.10 has been marked [EOL] on kernel.org

2024-09-13

:warning: Linux 6.9 is EOL

Linux 6.9 is EOL and has been removed from the repos.

Suggestion is to install latest LTS; i.e.,

sudo mhwd-kernel -i linux66
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.

System freezes for 60 seconds and then wakes back up or hangs after waking up

Since systemd v256, systemd freezes user.slice before sleeping. This process can fail due to kernel bugs, particularly when KVM is in use.[13][14]

Messages in the logs will contain Failed to freeze unit 'user.slice' before sleep. When such an issue occurs, trying to login (start another session) would fail with pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'.

To temporarily revert back to the old behavior, edit systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service with the following drop-in:

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

Power management/Suspend and hibernate – ArchWiki

KDE Plasma hangs on Shutdown, Restart and Logout

With KDE Plasma 6.1, the session saving feature can make Plasma hang.
A workaround is to disable it in System settings > Session > Desktop Session, by choosing “Start with an empty session”.

KDE Session auto login can’t be re-enabled for X11

Once session auto login for X11 gets disabled, it can’t be re-enabled in settings.
A workaround is to edit the /etc/sddm.conf.d/kde_settings.conf file and replace Session=Plasma (X11) by Session=plasma

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

Note, this was not just a Ruby rebuild, Ruby was upgraded from 3.2.5 to 3.3.5 and people need to rebuild their AUR packages that depend on it.

Compared to the previous update which was from Ruby 3.0 to Ruby 3.2 (from EOL and skipping a version), this bump should be quite safe and straightforward.

But due to how the Ruby gem path works, upgrading means system gems will now be placed in the /usr/lib/ruby/gems/3.3.0 directory (instead of 3.2.0), reason why AUR packages will break as they will still look in the old directory for the old gems, and those will be removed in the update process.



4 Likes

Seems protonmail-bridge no longer works.
Could not load QML component

>_ protonmail-bridge
Failed to initialize sentry
INFO[Oct 15 11:32:42.953] bridge-gui starting
INFO[Oct 15 11:32:42.953] Using Qt 6.8.0 (compiled against 6.7.3)
INFO[Oct 15 11:32:42.978] lock file created /home/steph/.cache/protonmail/bridge-v3/bridge-v3-gui.lock
INFO[Oct 15 11:32:42.978] bridge-gui executable: protonmail-bridge
INFO[Oct 15 11:32:42.978] Command-line invocation: <none>
INFO[Oct 15 11:32:42.978] New Sentry reporter - id: 1jBXXQP5Nlchb6IB1sOOt322hmCt6K1/vvx1Br9LK+I=.
DEBU[Oct 15 11:32:43.003] Bridge executable path: /usr/lib/protonmail/bridge/bridge
INFO[Oct 15 11:32:43.003] Launching bridge process with command "/usr/lib/protonmail/bridge/bridge" --grpc --parent-pid 15220 --launcher protonmail-bridge --session-id 20241015_113242953
INFO[Oct 15 11:32:43.003] Retrieving gRPC service configuration from '/home/steph/.config/protonmail/bridge-v3/grpcServerConfig.json'
INFO[Oct 15 11:32:43.636] Connecting to gRPC service
INFO[Oct 15 11:32:43.641] Connection to gRPC server at unix:///tmp/bridge4207. attempt #1
INFO[Oct 15 11:32:43.647] Successfully connected to gRPC server.
INFO[Oct 15 11:32:43.647] Client config file was saved to '/home/steph/.config/protonmail/bridge-v3/grpcClientConfig_0.json'
DEBU[Oct 15 11:32:43.648] checkTokens()
INFO[Oct 15 11:32:43.648] gRPC token was validated
INFO[Oct 15 11:32:43.648] Connected to backend via gRPC service.
DEBU[Oct 15 11:32:43.649] version()
DEBU[Oct 15 11:32:43.649] EventStreamReader started
DEBU[Oct 15 11:32:43.649] goos()
DEBU[Oct 15 11:32:43.654] logsPath()
DEBU[Oct 15 11:32:43.655] licensePath()
DEBU[Oct 15 11:32:43.657] mailServerSettings()
DEBU[Oct 15 11:32:43.658] getUserList()
ERRO[Oct 15 11:32:43.719] qrc:/qml/Bridge.qml:43 Type Notifications unavailable
qrc:/qml/Notifications/Notifications.qml:419 Type MainWindow unavailable
qrc:/qml/MainWindow.qml:174 Type SetupWizard unavailable
qrc:/qml/SetupWizard/SetupWizard.qml:242 Type Login unavailable
qrc:/qml/SetupWizard/Login.qml:206 ColorImage is not a type  pkg=frontend/bridge-gui
reportID: 00000000000000000000000000000000 Captured exception :Could not load QML component

Details:
qrc:/qml/Bridge.qml:43 Type Notifications unavailable
qrc:/qml/Notifications/Notifications.qml:419 Type MainWindow unavailable
qrc:/qml/MainWindow.qml:174 Type SetupWizard unavailable
qrc:/qml/SetupWizard/SetupWizard.qml:242 Type Login unavailable
qrc:/qml/SetupWizard/Login.qml:206 ColorImage is not a type



1 Like

Always the color problem in plasmoids
yet plasma 6.2 corrects it normally

see issue 2 on this message → [Testing Update] 2024-10-10 – Plasma 6.2, Gnome 47, Mesa, Firefox – #30 by Fred6681

With CachyOS it works perfectly



Source link