Hi,
the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and
Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/
Plasma 5 will be replaced, it is no longer part of the repository.
There are a few minor issues in this snapshot found by openQA but not
considered severe enough to actually block the snapshot from getting
published. They'll all be fixed with Plasma 6.0.2 in one of the next
snapshots, also for those installing or upgrading now.
1. For fresh installs, the GTK theme is not set correctly:
https://bugs.kde.org/show_bug.cgi?id=482763
Workaround is to either set it manually in systemsettings or run "kded5" once
in a terminal or krunner.
2. For upgrades (any version), the launcher icon switches to the Plasma one:
https://github.com/openSUSE/plasma-opensuse/pull/25
Workaround is to change the icon manually to "start-here-branding" for now.
3. Upgrades from very old systems fail due to "libksysguard5-helper":
https://bugzilla.opensuse.org/show_bug.cgi?id=1221350
When upgrading from Leap <= 15.3, you might encounter
Problem: libksysguard5-plugins-5.27.10-2.2.x86_64 requires
libprocesscore.so.9()(64bit), but this requirement cannot be provided
As workaround, select the "deinstallation of libksysguard5-helper" option.
4. Plasmashell takes 25s during start if bluetooth not available:
https://bugs.kde.org/show_bug.cgi?id=481870
If kdeconnect-kde is installed on a system without bluetooth HW, it delays
Plasma start by 25s. Workaround is to disable the KDE Connect systray icon.
5. The etesync resource is broken in kdepim-runtime 24.02.0. It will be back in
one of the next snapshots.
The Wayland session isn't default yet, that will have to be switched in a
separate step later. This also makes it possible to differentiate whether bugs
are more likely caused by Plasma 6 itself or the Wayland session.
Have a lot of fun,
the openSUSE KDE packaging team
the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and
Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/
Plasma 5 will be replaced, it is no longer part of the repository.
There are a few minor issues in this snapshot found by openQA but not
considered severe enough to actually block the snapshot from getting
published. They'll all be fixed with Plasma 6.0.2 in one of the next
snapshots, also for those installing or upgrading now.
1. For fresh installs, the GTK theme is not set correctly:
https://bugs.kde.org/show_bug.cgi?id=482763
Workaround is to either set it manually in systemsettings or run "kded5" once
in a terminal or krunner.
2. For upgrades (any version), the launcher icon switches to the Plasma one:
https://github.com/openSUSE/plasma-opensuse/pull/25
Workaround is to change the icon manually to "start-here-branding" for now.
3. Upgrades from very old systems fail due to "libksysguard5-helper":
https://bugzilla.opensuse.org/show_bug.cgi?id=1221350
When upgrading from Leap <= 15.3, you might encounter
Problem: libksysguard5-plugins-5.27.10-2.2.x86_64 requires
libprocesscore.so.9()(64bit), but this requirement cannot be provided
As workaround, select the "deinstallation of libksysguard5-helper" option.
4. Plasmashell takes 25s during start if bluetooth not available:
https://bugs.kde.org/show_bug.cgi?id=481870
If kdeconnect-kde is installed on a system without bluetooth HW, it delays
Plasma start by 25s. Workaround is to disable the KDE Connect systray icon.
5. The etesync resource is broken in kdepim-runtime 24.02.0. It will be back in
one of the next snapshots.
The Wayland session isn't default yet, that will have to be switched in a
separate step later. This also makes it possible to differentiate whether bugs
are more likely caused by Plasma 6 itself or the Wayland session.
Have a lot of fun,
the openSUSE KDE packaging team
kde.org
KDE MegaRelease 6
The KDE community proudly presents Plasma 6, Frameworks 6 and Gear 24.02
Another CPU related vulnerability
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00898.html
It feels already like a routine
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00898.html
It feels already like a routine
Intel
INTEL-SA-00898
Forwarded from [anywhere] Department of Ferrets, Memetics, Cognitohazards and чіназес (ܛܐܪܩ 🌲☀️🇵🇸)
Kernel Code Execution on Arm Mali GPUs:
A vulnerability affected Google’s Pixel 7 and 8 phones.
https://github.blog/2024-03-18-gaining-kernel-code-execution-on-an-mte-enabled-pixel-8/
A vulnerability affected Google’s Pixel 7 and 8 phones.
https://github.blog/2024-03-18-gaining-kernel-code-execution-on-an-mte-enabled-pixel-8/
The GitHub Blog
Gaining kernel code execution on an MTE-enabled Pixel 8
In this post, I’ll look at CVE-2023-6241, a vulnerability in the Arm Mali GPU that allows a malicious app to gain arbitrary kernel code execution and root on an Android phone. I’ll show how this vulnerability can be exploited even when Memory Tagging Extension…
Forwarded from ㅤUndi Snökatt - (that squeaky cat!) ^.ᆽ.^= ∫ ㅤㅤㅤ
This media is not supported in your browser
VIEW IN TELEGRAM
😁2
I wanted to post something silly but have nothing, so might y'all post something this time.
😁4
If you use podman or buildah, here's the critical CVE
https://bugzilla.redhat.com/show_bug.cgi?id=2265513
It allows a full container escape on the build stage.
It shouldn't affect running containers.
Also if you use SELinux (please tell me that you do), it'll be limited to R/O.
https://bugzilla.redhat.com/show_bug.cgi?id=2265513
It allows a full container escape on the build stage.
It shouldn't affect running containers.
Also if you use SELinux (please tell me that you do), it'll be limited to R/O.
I'm sorry but apparently Red Hat started working the new NVIDIA driver written by Rust, just like a few months after NVIDIA partially open-sourced its own driver.
Right now we already have 3 NVIDIA variants:
1. noveau - part of Linux kernel, open-source
2. propriety nvidia
3. open nvidia
We might have one more for no reason.
https://lists.freedesktop.org/archives/dri-devel/2024-March/446709.html
I'm not going to comment this as I'm not quite sure what my position about this is. I kinda see both positive and negative sides of this.
Right now we already have 3 NVIDIA variants:
1. noveau - part of Linux kernel, open-source
2. propriety nvidia
3. open nvidia
We might have one more for no reason.
https://lists.freedesktop.org/archives/dri-devel/2024-March/446709.html
I'm not going to comment this as I'm not quite sure what my position about this is. I kinda see both positive and negative sides of this.