Lector de Feeds
MGASA-2025-0029 - Updated chromium-browser-stable packages fix security vulnerabilities
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-0611 , CVE-2025-0612 Description Object corruption in V8. (CVE-2025-0611) Out of bounds memory access in V8. (CVE-2025-0612) References
- https://bugs.mageia.org/show_bug.cgi?id=33962
- https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_22.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0611
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0612
- chromium-browser-stable-132.0.6834.110-1.mga9.tainted
MGASA-2025-0028 - Updated git-lfs packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-53263 Description Git LFS permits exfiltration of credentials via crafted HTTP URLs. (CVE-2024-53263) References
- https://bugs.mageia.org/show_bug.cgi?id=33931
- https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/U4RACGLXZEZGUX7BZLFN4GQOHFBHL6FO/
- https://lists.debian.org/debian-security-announce/2025/msg00011.html
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53263
- git-lfs-3.2.0-1.1.mga9
Vendored dependencies
Add note on patches, links to see also
← Older revision Revision as of 08:36, 30 January 2025 (One intermediate revision by the same user not shown)Line 69: Line 69: Overview: Overview: −# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code for an application (i.e. vendoring it), including a software attestation+# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code for an application (i.e. vendoring it), including a SBOM −# The build system adds packaged dependencies to the software attestation+# The build system adds packaged dependencies to the SBOM # For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application # For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application −# The build system stores the software attestation at the end of the build into a central repository+# The build system stores the SBOM at the end of the build into a central repository −# A security scanner periodically scans all software attestations to look for dependencies that have reported security vulnerabilities+# A security scanner periodically scans all SBOMs to look for dependencies that have reported security vulnerabilities # If a security vulnerability is found, it outputs a list of packages that need to be updated and rebuilt and opens one or more bugs # If a security vulnerability is found, it outputs a list of packages that need to be updated and rebuilt and opens one or more bugs −# Each package needing a rebuild goes back to step 1 (if a local patch to fix a vulnerability has been added, it is noted in the software attestation)+# Each package needing a rebuild goes back to step 1 (if a local patch to fix a vulnerability has been added, it is noted in the SBOM) −Software attestations will be stored in the [https://spdx.dev/ SPDX] format.+SBOMs will be stored in the [https://spdx.dev/ SPDX] format. + +Security updates are assumed to consist of upgrading to a new upstream release. Those that require patching a dependency complicates this flow, since the same patch must then be applied to each vendored instance of that dependency. === Go === === Go === Line 90: Line 92: * [[Security Updates]] * [[Security Updates]] * [https://lwn.net/Articles/1005655/ Fedora proposing allowing vendored Go packages] * [https://lwn.net/Articles/1005655/ Fedora proposing allowing vendored Go packages] +* [https://fosdem.org/2025/schedule/event/fosdem-2025-5570-rust-rpms-and-the-fine-art-of-dependency-bundling/ Rust, RPMs, and the Fine Art of Dependency Bundling] +* [https://ml.mageia.org/l/arc/dev/2023-04/msg00579.html Thread on packages with many components/modules/subpackages] [[Category:Packaging]] [[Category:Packaging]] DanfAppearance of Mageia Tools
CLI: Text font & size: Just edit a line
← Older revision Revision as of 08:49, 28 January 2025 (One intermediate revision by the same user not shown)Line 10: Line 10: The Mageia Tools use the gtk toolkit, this is why it usually has a look similar to selected theme in desktops that also use gtk toolkit (Gnome, lxde, Xfce). The Mageia Tools use the gtk toolkit, this is why it usually has a look similar to selected theme in desktops that also use gtk toolkit (Gnome, lxde, Xfce). −If you like to change the appearance of Magiea Tools keep reading this page.+If you like to change the appearance of Magiea tools keep reading this page. + +A frequent question is '''how to enlarge the text size''' - best method see [[#GUI|Alternatives for all the Desktops#GUI]] at bottom of this page. Line 36: Line 38: ==== CLI ==== ==== CLI ==== + +To only change text and you do not want to install a tool for it, easiest way is to as root edit /root/.config/gtk-3.0/settings.ini. + +In that file, edit the line "gtk-font-name=Noto Sans, 10", for example change the size number "10" to "14" + + +===== Changing theme ===== First you must apply a gtk theme as user, then follow this procedure: First you must apply a gtk theme as user, then follow this procedure: Line 61: Line 70: ==== GUI ==== ==== GUI ==== −Install {{prog|lxappearance}}, run in a terminal as root {{prog|lxappearance}} and select by example Adwaita Dark+Install {{prog|lxappearance}}, and ''as root'' in a terminal launch {{prog|lxappearance}}. There you can select another theme, i.e Adwaita Dark. + +If you want to '''change the text size or typeface''' you can directly do that at the bottom of the dialogue, clicking the current typeface opens another dialogue. + +lxappearance itself adjust immediately to theme and typeface changes. Click Apply, and next time you start a Mageia tool it will use this setting. + +''Note that for example Mageia Control Center main page right pane do not follow theme nor text settings.'' == Recommendations == == Recommendations == MorganoVendored dependencies
Add an apropos link re: Fedora & Go
← Older revision Revision as of 05:39, 28 January 2025 Line 89: Line 89: * [[Packages carrying bundled copies of system libraries]] * [[Packages carrying bundled copies of system libraries]] * [[Security Updates]] * [[Security Updates]] +* [https://lwn.net/Articles/1005655/ Fedora proposing allowing vendored Go packages] [[Category:Packaging]] [[Category:Packaging]] DanfMGASA-2025-0027 - Updated virtualbox, kmod-virtualbox packages fix security vulnerabilities
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-21571 , CVE-2025-21533 Description Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 7.0.24 and prior to 7.1.6. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized read access to a subset of Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L) References
- https://bugs.mageia.org/show_bug.cgi?id=33952
- https://www.oracle.com/security-alerts/cpujan2025.html#AppendixOVIR
- https://www.virtualbox.org/wiki/Changelog-7.0#v24
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21571
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21533
- virtualbox-7.0.24-1.mga9
- kmod-virtualbox-7.0.24-63.mga9
MGAA-2025-0007 - Updated libmatemixer packages fix bug
Type: bugfix
Affected Mageia releases : 9
Description Fixes a mate-volume-control crash when Bluetooth disconnects. References SRPMS 9/core
- libmatemixer-1.26.1-1.mga9
MGAA-2025-0006 - Updated phppgadmin packages fix bug
Type: bugfix
Affected Mageia releases : 9
Description Fixed an issue which prevents executing pgadmin on php 8. Please note that just work with postgresql13. References
- https://bugs.mageia.org/show_bug.cgi?id=28582
- https://wiki.mageia.org/en/Mageia_9_Errata#Various_software
- https://github.com/phppgadmin/phppgadmin/issues/119
- phppgadmin-7.13.0-2.1.mga9
Mageia IRC Kanäle Liberachat-de
QA-Team-de
Mageia 9 Errata-de
Mageia 9 Errata
Various software
← Older revision Revision as of 17:22, 26 January 2025 (2 intermediate revisions by the same user not shown)Line 326: Line 326: {{Bug|27926}} - '''Xine''' may crash at launch, or exit silently when trying to play various multimedia files. '''WORKAROUNDS: 1.)''' try another player. (Xine is default in LXDE). '''2.)''' If not starting, can you use another video driver? (i.e modesetting instead of nvidia) '''3.)''' ''(At least if it throws an error about vdpau)'' To be able to change Video and Audio codec, first change "configuration experience level" to "Advanced", then select "video tab" and select "video driver to use", change from "Auto" to "opengl2". Now select "Audio tab" and select "audio driver to use", change from "auto" to "pulseaudio", click OK, close and restart Xine. {{Bug|27926}} - '''Xine''' may crash at launch, or exit silently when trying to play various multimedia files. '''WORKAROUNDS: 1.)''' try another player. (Xine is default in LXDE). '''2.)''' If not starting, can you use another video driver? (i.e modesetting instead of nvidia) '''3.)''' ''(At least if it throws an error about vdpau)'' To be able to change Video and Audio codec, first change "configuration experience level" to "Advanced", then select "video tab" and select "video driver to use", change from "Auto" to "opengl2". Now select "Audio tab" and select "audio driver to use", change from "auto" to "pulseaudio", click OK, close and restart Xine. + +{{Bug|28582}} - '''phppgadmin''' (umaintained upstream) did not work with php8 - that got FIXED by our patched update. But it still do not work with postgresql15 - '''WORKAROUND:''' downgrade to postgresql13. Both are in Mageia 9. {{Bug|28814}}, {{Bug|28840}}, {{Bug|31989}} - '''Wine''' missing a few dependencies, especially for 32 bit libs. (Thus also '''PlayOnLinux'''.) '''Manual fix''' and also other tips [[Ways_to_install_programs#Running_MSWindows_programs|'''here''']]. If launching a wine app gives warnings that suitable versions are missing, see {{Bug|16273}}. {{Bug|28814}}, {{Bug|28840}}, {{Bug|31989}} - '''Wine''' missing a few dependencies, especially for 32 bit libs. (Thus also '''PlayOnLinux'''.) '''Manual fix''' and also other tips [[Ways_to_install_programs#Running_MSWindows_programs|'''here''']]. If launching a wine app gives warnings that suitable versions are missing, see {{Bug|16273}}. Line 358: Line 360: {{Bug|33697}} - '''Nextcloud client''' - We fail to keep it updated. Instead, upstream AppImage can be used, see [[Nextcloud-client]]. {{Bug|33697}} - '''Nextcloud client''' - We fail to keep it updated. Instead, upstream AppImage can be used, see [[Nextcloud-client]]. + + <br> <br> MorganoMGASA-2025-0026 - Updated glibc packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-0395 Description When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size. (CVE-2025-0395) References
- https://bugs.mageia.org/show_bug.cgi?id=33953
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-0395
- glibc-2.36-55.mga9
MGASA-2025-0025 - Updated openssl packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-13176 Description Timing side-channel in ECDSA signature computation. (CVE-2024-13176) References
- https://bugs.mageia.org/show_bug.cgi?id=33942
- https://openssl-library.org/news/secadv/20250120.txt
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-13176
- openssl-3.0.15-1.2.mga9
MGASA-2025-0024 - Updated iperf packages fix security vulnerability
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-53580 Description It was discovered that iperf 3.17.1 contains a segmentation violation via the iperf_exchange_parameters() function. References
- https://bugs.mageia.org/show_bug.cgi?id=33914
- https://lists.almalinux.org/archives/list/announce@lists.almalinux.org/message/77I3GUDI3ZWMFAYZRZIRL3FI5TCBTNBQ/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53580
- iperf-3.18-1.mga9
New laptop and Silverblue update
Figured I'd post an update on how things are going with the new laptop (HP Omnibook Ultra 14, AMD Ryzen AI 9 365 "Strix Point", for the searchers) and with Silverblue.
I managed to work around the hub issue by swapping out the fancy $300 Thunderbolt hub for a $40 USB-C hub off Amazon. This comes with limitations - you're only going to get a single 4k 60Hz external display, and limited bandwidth for anything else - but it's sufficient for my needs, and makes me regret buying the fancy hub in the first place. It seems to work 100% reliably on startup, reboot and across suspend/resume. There's still clearly something wrong with Thunderbolt handling in the kernel, but it's not my problem any more.
The poor performance of some sites in Firefox turned out to be tied to the hanging problem - I'd disabled graphics acceleration in Firefox, which helped with the hanging, but was causing the appalling performance on Google sites and others. I've now cargo-culted a set of kernel args - amdgpu.dcdebugmask=0x800 amdgpu.lockup_timeout=100000 drm.vblankoffdelay=0 - which seem to be helping; I turned graphics acceleration back on in Firefox and it hasn't started hanging again. At least, I haven't had random hangs for the last few days, and this morning I played a video on youtube and the system has not hung since then. I've no idea how bad they are for battery life, but hey, they seem to be keeping things stable. So, the system is pretty workable at this point. I've been using it full-time, haven't had to go back to the old one.
I'm also feeling better about Silverblue as a main OS this time. A lot of things seem to have got better. The toolbox container experience is pretty smooth now. I managed to get adb working inside a container by putting these udev rules in /etc/udev/rules.d. It seems like I have to kill and re-start the adb server any time the phone disconnects or reboots - usually adb would keep seeing the phone just fine across those events - but it's a minor inconvenience. I had to print something yesterday, was worried for a moment that I'd have to figure out how to get hp-setup to do its thing, but then...Silverblue saw my ancient HP printer on the network, let me print to it, and it worked, all without any manual setup at all. It seems to be working over IPP, but I'm a bit surprised, as the printer is from 2010 or 2011 and I don't think it worked before. But I'm not complaining!
I haven't had any real issues with app availability so far. All the desktop apps I need to use are available as flatpaks, and the toolbox container handles CLI stuff. I'm running Firefox (baked-in version), Evolution, gedit, ptyxis (built-in), liferea, nheko, slack and vesktop (for discord) without any trouble. LibreOffice and GIMP flatpaks also work fine. Everything's really been pretty smooth.
I do have a couple of tweaks in my bashrc (I put them in a file in ~/.bashrc.d, which is a neat invention) that other Atomic users might find useful...
if [ -n "$container" ] then alias gedit="flatpak-spawn --host /var/lib/flatpak/exports/bin/org.gnome.gedit" alias xdg-open=flatpak-xdg-open else alias gedit=/var/lib/flatpak/exports/bin/org.gnome.gedit fithe gedit aliases let me do gedit somefile either inside or outside a container, and the file just opens in my existing gedit instance. Can't really live without that. You can adapt it for anything that's a flatpak app on the host. The xdg-open alias within containers similar makes xdg-open somefile within the container do the same as it would outside the container.
So it's still early days, but I'm optimistic I'll keep this setup this time. I might try rebasing to the bootc build soon.
And here is new MADb!
That was fast: we have only just explained why our Mageia Application Database was offline and now papoteur tells us that new MADb is ready to be used.
Open the site and at first glance you might think you have somehow connected to the old site as the differences between it and the new one are hard to spot (the top one is the old site):
However, this is only the outward appearance, as the style sheets (CSS) were re-used with little modification.
The tool itself, previously written in PHP, has been completely rewritten from scratch, using Python, Flask, Jinja2 and DNF5, so the runtime code is entirely new. Papoteur showed two code snippets as an example of what really changed (again, the top one is old):
That is as different as a page from an English book compared to a page from its Indonesian translation!
About 3000 new lines of code were written for this new MADb, which is now live and ready to answer your queries about Mageia applications.
As you use the site, we ask you to think about what questions you feel an integrated help function (not yet available) should answer, and also what you feel we should include in a new wiki article about MADb. Please note your suggestions in the comments to this post, as you are all the Mageia community and this tool is for you.
Thanks to the MLO community for hosting new MADb.
