Lector de Feeds

Publication date: 31 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description Minor bug fixes and improvements. References

• https://bugs.mageia.org/show_bug.cgi?id=33963
• https://www.nvidia.com/en-us/drivers/details/238858/

SRPMS 9/nonfree

• nvidia-current-550.144.03-1.mga9.nonfree

Add a few more languages

← Older revision Revision as of 06:06, 31 January 2025 (5 intermediate revisions by the same user not shown)Line 45: Line 45:  # Ruby* # Ruby*  # OCaml # OCaml −# Nodejs (Javascript)*+# Javascript* (nodejs)  # PHP* # PHP*  # Erlang* # Erlang*  +# other compiled languages like FreeBASIC, gfortran, C# (mono)     <nowiki>*</nowiki> Interpreted languages that don't statically link dependencies into applications or modules <nowiki>*</nowiki> Interpreted languages that don't statically link dependencies into applications or modules Line 57: Line 58:  === Erlang, Nodejs, Perl, PHP, Python, Ruby === === Erlang, Nodejs, Perl, PHP, Python, Ruby ===    −These are all interpreted languages that either have no concept of bundling dependencies somehow into submodules (a static linking equivalent) or developers don't generally use them. They generally do, however, have means to automatically obtain dependent modules at build time (e.g. ''pip'', ''cpan'', ''npm'') that Mageia's current policies forbid. Generally, interpreted languages rely on modules being installed in the system when they are executed and do not compile/bind/link them into an independent blob like compiled languages are forced to do.+These are all interpreted languages that either have no concept of bundling dependencies somehow into submodules (a static linking equivalent) or developers don't generally use them. They generally do, however, have means to automatically obtain dependent modules at build time (e.g. ''pip'', ''cpan'', ''npm'') that Mageia's current policies forbid. Generally, interpreted languages rely on modules being installed in the system when they are executed and do not compile/bind/link them into an independent blob like compiled languages are forced to do. Vendoring can still be useful to greatly reduce the number of packages necessary to create for a new application.     === Go, Java, OCaml, Rust === === Go, Java, OCaml, Rust === Line 69: Line 70:  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.  +   +A script will be created to take care of the bulk of step 1 for the developer. It would scan the application source code to find out what dependencies are needed, then exclude any dependencies already supplied by packages in ''BuildRequires:'' leaving a list of outstanding ones. These would be downloaded using the language's normal package download mechanism and installed into a private temporary location. All these would then be archived into a compressed tarball along with an SBOM containing all the packaged dependency names and versions and stored in the ''SOURCES/'' directory under a standard name (maybe ''dependencies.tar.xz'').  This file would then be added to ''sha1.lst'' and uploaded to ''binrepo''. This could all be integrated into a ''mgarepo'' subcommand. ''TODO: who is responsible for ensuring that the licenses of all the dependencies are allowed, compatible and that the License: line in the .spec file matches?''  +   +The various RPM build macros would be updated to handle any dependencies stored in ''dependencies.tar.xz''. They would be extracted into a temporary location in ''BUILDROOT/'' and the compile command extended to look for missing dependencies in this location. For interpreted languages, the dependencies would instead by installed ''in the RPM'' in an appropriate location in ''/usr/share/'' (that doesn't conflict with other dependencies), and the application's launch command extended to find these dependencies (since they are private to that one application). ''TODO: how to handle locally patching these dependencies? patching before or after storing in dependencies.tar.xz''     === Go === === Go ===     The specifics listed in this section are for handling Go applications, but it can be generalized for other languages in the future. These should be able to be generalized to work for applications in other compiled languages as well. It is possible to develop infrastructure to support interpreted languages as well, but the benefits may not be as clear; any such applications that ship vendored modules ''would'' benefit, but it's unclear how many of those (if any) actually exist. The specifics listed in this section are for handling Go applications, but it can be generalized for other languages in the future. These should be able to be generalized to work for applications in other compiled languages as well. It is possible to develop infrastructure to support interpreted languages as well, but the benefits may not be as clear; any such applications that ship vendored modules ''would'' benefit, but it's unclear how many of those (if any) actually exist.  +  +The ''go list -json'' command can be used to generate the list of dependencies needed by an application (step 1).  +  +The [https://vuln.go.dev/ Go Vulnerability Database] can be used on an ongoing basis to find security issues in Go packages from the SBOMs of those packages.     ''details TBD'' ''details TBD'' Line 90: Line 101:  * [[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]  +* [https://vuln.go.dev/ Go Vulnerability Database]  +* [https://guac.sh/ GUAC] SBOM management tool  +* [https://github.com/anchore/grype grype], tool that can look up security issues from a SPDX SBOM     [[Category:Packaging]] [[Category:Packaging]] Danf

Publication date: 30 Jan 2025
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

SRPMS 9/tainted

• chromium-browser-stable-132.0.6834.110-1.mga9.tainted

Publication date: 30 Jan 2025
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

SRPMS 9/core

• git-lfs-3.2.0-1.1.mga9

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]] Danf

‎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 == Morgano

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]] Danf

Publication date: 27 Jan 2025
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

SRPMS 9/core

• virtualbox-7.0.24-1.mga9
• kmod-virtualbox-7.0.24-63.mga9

Publication date: 27 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description Fixes a mate-volume-control crash when Bluetooth disconnects. References

• https://bugs.mageia.org/show_bug.cgi?id=33918

SRPMS 9/core

• libmatemixer-1.26.1-1.mga9

Publication date: 27 Jan 2025
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

SRPMS 9/core

• phppgadmin-7.13.0-2.1.mga9

← Older revision Revision as of 12:00, 27 January 2025 Line 6: Line 6:     Am 15. Juni 2021 waren wir gezwungen, unsere [[Mageia IRC Kanäle-de|IRC Kanäle auf Freenode]] nach [https://libera.chat/ Liberachat]zu verlegen. Sie können diese im Libera Chat Netzwerk besuchen (ircs://irc.libera.chat:6697). Am 15. Juni 2021 waren wir gezwungen, unsere [[Mageia IRC Kanäle-de|IRC Kanäle auf Freenode]] nach [https://libera.chat/ Liberachat]zu verlegen. Sie können diese im Libera Chat Netzwerk besuchen (ircs://irc.libera.chat:6697). −  −Stellen Sie eine Verbindung zum Server ircs://irc.libera.chat:6697 her und geben Sie /join channelname ein, wobei Sie channelname durch den Namen des Kanals (einschließlich des führenden "#") ersetzen. Alle Kanäle verwenden Englisch, sofern nicht anders angegeben. Die Verwendung einer sicheren Verbindung mit SSL über Port 6697 ist obligatorisch.      Die Absicht war, ein Backup auf Liberachat für jeden unserer Kanäle auf Freenode zu haben. Sie können diese unten finden, aber einige sind vielleicht noch nicht bevölkert oder registriert. Wenn Sie eine Frage zu einem leeren Kanal haben, dann fragen Sie bitte in  [ircs://irc.libera.chat:6697/#mageia #mageia] Die Absicht war, ein Backup auf Liberachat für jeden unserer Kanäle auf Freenode zu haben. Sie können diese unten finden, aber einige sind vielleicht noch nicht bevölkert oder registriert. Wenn Sie eine Frage zu einem leeren Kanal haben, dann fragen Sie bitte in  [ircs://irc.libera.chat:6697/#mageia #mageia]     In den Kanälen finden regelmäßig Treffen statt (siehe [[Meetings-de|Meetings]]). In den Kanälen finden regelmäßig Treffen statt (siehe [[Meetings-de|Meetings]]).  +  +Alle Kanäle verwenden die englische Sprache, außer es ist etwas angegeben.     Einige Channels haben (werden) nützliche Bots, siehe [[IRC bots]]. Einige Channels haben (werden) nützliche Bots, siehe [[IRC bots]].  +  +Stellen Sie eine Verbindung zum Server ircs://irc.libera.chat:6697 her und geben Sie /join channelname ein, wobei Sie channelname durch den Namen des Kanals (einschließlich des führenden "#") ersetzen. Alle Kanäle verwenden Englisch, sofern nicht anders angegeben. Die Verwendung einer sicheren Verbindung mit SSL über Port 6697 ist obligatorisch.  +  +Verbinden über einen Browser: https://web.libera.chat/  +  +Verwenden eines IRC Clienten, wie zum Beispiel {{prog|hexchat}} : wählen Sie das Netwerk Libera.Chat aus und unter Menü Server > Einem Kanal beitreten > #mageia-irgendwas, aus der unten angezeigten Liste.     == Projektweite Kanäle == == Projektweite Kanäle == Psyca

← Older revision Revision as of 11:56, 27 January 2025 Line 13: Line 13:  * Die Mageia Webseiten (Forum, Wiki, Bugzilla, Mailinglisten) verwenden alle die gleichen Zugänge, welche du [https://identity.mageia.org/ hier] bearbeiten kannst, wie z.B. ändern deiner E-Mail-Adresse etc. Um dich bei einer Mailingliste einzuschreiben, meldest du dich am Anfang der Seite mit deiner registrierten E-Mail Adresse und Passwort an und klickst danach einfach auf "subscribe" bei der Liste, in der du dich einschreiben möchtest. * Die Mageia Webseiten (Forum, Wiki, Bugzilla, Mailinglisten) verwenden alle die gleichen Zugänge, welche du [https://identity.mageia.org/ hier] bearbeiten kannst, wie z.B. ändern deiner E-Mail-Adresse etc. Um dich bei einer Mailingliste einzuschreiben, meldest du dich am Anfang der Seite mit deiner registrierten E-Mail Adresse und Passwort an und klickst danach einfach auf "subscribe" bei der Liste, in der du dich einschreiben möchtest.  * Durch Anmelden auf der [https://ml.mageia.org/l/info/qa-discuss QA-Discuss] Mailingliste. Wenn du möchtest kannst du zudem ein Mail an diese Liste senden, um dich vorzustellen. * Durch Anmelden auf der [https://ml.mageia.org/l/info/qa-discuss QA-Discuss] Mailingliste. Wenn du möchtest kannst du zudem ein Mail an diese Liste senden, um dich vorzustellen. −* Durch Betreten des [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] IRC Kanal von Liberachat. Wie: Durch Aufrufen von https://web.libera.chat/ über einen Webbrowser, einem IRC Klienten, wie zum Beispiel {{prog|hexchat}}: wähle als Netzwerk Libera.Chat und im Menü Server > Einem Kanal beitreten > #mageia-qa+* Durch Betreten des [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] IRC Kanal von Liberachat. Wie: Durch Aufrufen von https://web.libera.chat/ über einen Webbrowser, einem IRC Klienten, wie zum Beispiel {{prog|hexchat}}: wähle als Netzwerk Libera.Chat und im Menü Server > Einem Kanal beitreten > #mageia-qa. Weitere Kanäle finden Sie auf der Seite [[Mageia_IRC_Channels_Liberachat|Mageia IRC Channels Liberachat]]  * Teamleiter: Thomas J Andrews (MageiaTJ) - andrewsfarm AT gmail dot com * Teamleiter: Thomas J Andrews (MageiaTJ) - andrewsfarm AT gmail dot com  * Stellvertreter: Jose Manuel Lopez (joselp) - joselp AT e dot email * Stellvertreter: Jose Manuel Lopez (joselp) - joselp AT e dot email Psyca

← Older revision Revision as of 11:02, 27 January 2025 Line 209: Line 209:  == Software == == Software ==  === Chromium Browser === === Chromium Browser === −Wir haben zur Zeit keinen Paketbetreuer um den Chromium Browser aktuell zu halten, {{Bug|33609}}. Workaround: Installieren Sie app/org.chromium.Chromium/x86_64/stable als [[Flatpak-de|Flatpak]], oder den Chrome Browser. Alternativ kann auch Chrome als rpm von Google installiert werden.+Wir haben zur Zeit keinen Paketbetreuer um den Chromium Browser aktuell zu halten, {{Bug|33609}}. Workaround: Installieren Sie app/org.chromium.Chromium/x86_64/stable als [[Flatpak-de|Flatpak]], oder den Chrome Browser. Alternativ kann auch Chrome als rpm von Google installiert werden. Aktualisierung Januar 2025: zur Zeit ist Chromium auf dem aktuellen Stand.     === Firefox ESR === === Firefox ESR === Line 244: Line 244:  === Verschiedene Software === === Verschiedene Software ===  {{Bug|27926}} - '''Xine''' stürzt möglicherweise beim Startvorgang ab oder schließt sich ohne Fehlermeldung, wenn versucht wird verschiedene Mediendateien abzuspielen. '''WORKAROUNDS:'''  1.)''' versuchen Sie einen anderen Abspieler. (Xine ist der Standard in LXDE). '''2.)''' Falls es nicht startet können Sie einen anderen Grafikkartentreiber versuchen? (z. B. modesetting anstelle von nvidia)  '''3.)''' ''(Wenn es eine Fehlermeldung über vdpau anzeigt)'' Um den Video- und Audio-Codec ändern zu können, ändern Sie zu erst "Erfahrenheit einstellen", in den Einstellungen, auf "Advanced" und wählen Sie danach den "Video Tab". Wählen Sie anschließend dort unter "Zu benutzender Videotreiber" "opengl2". Wählen Sie nun den "Audio Tab" und wählen Sie "Zu benutzender Audiotreiber" von "auto" auf "puleaudio". Klicken Sie danach auf OK und starten Sie Xine neu. {{Bug|27926}} - '''Xine''' stürzt möglicherweise beim Startvorgang ab oder schließt sich ohne Fehlermeldung, wenn versucht wird verschiedene Mediendateien abzuspielen. '''WORKAROUNDS:'''  1.)''' versuchen Sie einen anderen Abspieler. (Xine ist der Standard in LXDE). '''2.)''' Falls es nicht startet können Sie einen anderen Grafikkartentreiber versuchen? (z. B. modesetting anstelle von nvidia)  '''3.)''' ''(Wenn es eine Fehlermeldung über vdpau anzeigt)'' Um den Video- und Audio-Codec ändern zu können, ändern Sie zu erst "Erfahrenheit einstellen", in den Einstellungen, auf "Advanced" und wählen Sie danach den "Video Tab". Wählen Sie anschließend dort unter "Zu benutzender Videotreiber" "opengl2". Wählen Sie nun den "Audio Tab" und wählen Sie "Zu benutzender Audiotreiber" von "auto" auf "puleaudio". Klicken Sie danach auf OK und starten Sie Xine neu.  +  +{{Bug|28582}} - '''phppgadmin''' (upstream nicht weiterentwickelt) funktioniert nicht mit php8 - dies wurde durch unseren Patch BEHOBEN. Es funktioniert allerdings noch nicht mit postgresql15 - '''WORKAROUND:''' postgresql auf Version 13 herunterstufen. Beide Versionen sind in Mageia 9 verfügbar.     {{bug-de|28814}}, {{bug-de|28840}}, {{Bug|31989}} - '''Wine''' fehlen ein paar Abhängigkeiten, vor allem für die 32-Bit Bibliotheken. (Betrifft auch '''PlayOnLinux'''.) '''Manuelle Behebung''' und weitere Tipps [[Möglichkeiten_um_Anwendungen_zu_installieren-de#MS_Windows_Programme_ausf.C3.BChren|'''finden Sie hier''']]. Falls Sie eine Meldung erhalten, dass die geeignete Version fehlt, schauen Sie unter {{bug-de|16273}} {{bug-de|28814}}, {{bug-de|28840}}, {{Bug|31989}} - '''Wine''' fehlen ein paar Abhängigkeiten, vor allem für die 32-Bit Bibliotheken. (Betrifft auch '''PlayOnLinux'''.) '''Manuelle Behebung''' und weitere Tipps [[Möglichkeiten_um_Anwendungen_zu_installieren-de#MS_Windows_Programme_ausf.C3.BChren|'''finden Sie hier''']]. Falls Sie eine Meldung erhalten, dass die geeignete Version fehlt, schauen Sie unter {{bug-de|16273}} Psyca

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 fi

the 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.