Lector de Feeds

‎Various: fixed various typos and wording

← Older revision Revision as of 11:22, 31 December 2025 (One intermediate revision by the same user not shown)Line 215: Line 215:  {{Bug|27601}} - '''The boot hangs with a black screen''' and the mouse cursor still mobile. This is due to a change of hostname during '''SDDM''' start, set by avahi or networkmanager when the hostname is localhost. The workaround is to set the hostname to a personal value, for example with the command ''hostnamectl set-hostname myhost.local''. {{Bug|27601}} - '''The boot hangs with a black screen''' and the mouse cursor still mobile. This is due to a change of hostname during '''SDDM''' start, set by avahi or networkmanager when the hostname is localhost. The workaround is to set the hostname to a personal value, for example with the command ''hostnamectl set-hostname myhost.local''.    −{{Bug|32078}},{{bug|34836}} - '''LXQt :''' and other desktops after  Installing from installer media, default login is set to IceWM-session. This is due to alphabetical order of desktop session. '''Wokarround:''' Just select the session you want to start in the DM screen before hit {{keypress|Enter}} after or before type user and password.+{{Bug|32078}},{{bug|34836}} - '''LXQt and other desktops:''' After installation, the default login is set to IceWM-session. This is due to the alphabetical order of the desktop sessions. '''WORKAROUND:''' Simply select the desired desktop session on the login manager screen where you enter your username and password.     {{Bug|32805}} - '''SDDM :''' first login after boot shows no text, or characters as blocks. Seems to happen on some old/lower end machines with nouveau graphics driver.  '''WORKAROUND:''' use another Display Manager, such as XDM, LightDM, LXDM. {{Bug|32805}} - '''SDDM :''' first login after boot shows no text, or characters as blocks. Seems to happen on some old/lower end machines with nouveau graphics driver.  '''WORKAROUND:''' use another Display Manager, such as XDM, LightDM, LXDM. Line 398: Line 398:  <br> <br>    −=== Renew of key for sign packages ===+=== Renewal of gpg package signing key ===    −The gpg key we were using to sign our packages is near to expire on December 31 2025, we update in cauldron the key time ago and that was causing [[Cauldron#Upgrade_from_the_latest_stable_release_to_Cauldron_using_urpmi|conflicts in the process to upgrade mageia 9 to cauldron]], we switch to use the new key in mageia 9 repositories and sign all the current and future packages for mageia 9 with the updated key.+The GPG key we used to sign our packages expires on December 31, 2025. We updated the key in Cauldron some time ago, which caused [[Cauldron#Upgrade_from_the_latest_stable_release_to_Cauldron_using_urpmi|conflicts when upgrading from Mageia 9 to Cauldron.]] We are now switching to using the new key in the Mageia 9 repositories and signing all current and future packages for Mageia 9 with the updated key. −   −We take the necessary actions to make the switch painless to our users {{bug|34918}} & {{bug|34920}}, please reboot after get the related updates.        +We are taking the necessary measures to make the transition smooth for our users. Please restart your computer after receiving the relevant updates. For further informations see {{bug|34918}} & {{bug|34920}}.     === Mageia tools === === Mageia tools === Sturmvogel

Created page with "I wait untill tomorrow to remove one warning on Preparations section --~~~~"

New page

I wait untill tomorrow to remove one warning on Preparations section
--[[User:Katnatek|katnatek]] ([[User talk:Katnatek|talk]]) 01:22, 31 December 2025 (UTC) Katnatek

‎Preparations: typo

← Older revision Revision as of 01:18, 31 December 2025 (One intermediate revision by the same user not shown)Line 480: Line 480:  ** '''Remove packages''' now not in configured repositories, shown by {{cmd|urpmq --not-available}}. They may be re-installed after the upgrade if needed.   ** '''Remove packages''' now not in configured repositories, shown by {{cmd|urpmq --not-available}}. They may be re-installed after the upgrade if needed.    * Perform a normal full '''system update''' ''(most importantly rpm and urpmi)''. * Perform a normal full '''system update''' ''(most importantly rpm and urpmi)''.  +* Is very important to reboot your system after get the updates in {{bug|34918}} & {{bug|34920}}, this updates the key used to sign packages, ironing the migration.  * Some software may need special care, such as maybe not update Docker during system upgrade, see [[#Docker|Docker]] above. * Some software may need special care, such as maybe not update Docker during system upgrade, see [[#Docker|Docker]] above.  * It is good to '''free some space''', particularly uninstall old kernels, fat games... * It is good to '''free some space''', particularly uninstall old kernels, fat games... Katnatek

‎System: mga#34918 & mga#34920

← Older revision Revision as of 01:09, 31 December 2025 Line 397: Line 397:     <br> <br>  +  +=== Renew of key for sign packages ===  +  +The gpg key we were using to sign our packages is near to expire on December 31 2025, we update in cauldron the key time ago and that was causing [[Cauldron#Upgrade_from_the_latest_stable_release_to_Cauldron_using_urpmi|conflicts in the process to upgrade mageia 9 to cauldron]], we switch to use the new key in mageia 9 repositories and sign all the current and future packages for mageia 9 with the updated key.  +  +We take the necessary actions to make the switch painless to our users {{bug|34918}} & {{bug|34920}}, please reboot after get the related updates.  +  +  === Mageia tools === === Mageia tools ===    Katnatek

Publication date: 30 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description Vcdimager plug-in can't be enabled in brasero. This update fixes the issue. References

• https://bugs.mageia.org/show_bug.cgi?id=34915
• https://gitlab.gnome.org/GNOME/brasero/-/merge_requests/31

SRPMS 9/core

• brasero-3.12.3-5.2.mga9

Publication date: 30 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description The key we are current using to sign packages expires on 2025-12-31 and will no longer be accepted as trusted. In cauldron the key was updated some time ago causing some additional work in Mageia 9 to cauldron upgrades. These packages update the keys in your system (you need to reboot after the update). All packages have been resigned with the new key. References

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

SRPMS 9/core

• mageia-release-9-2.3.mga9

Publication date: 30 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description The key we are current using to sign packages expires on 2025-12-31 and will no longer be accepted as trusted. In cauldron the key has been updated sometime ago causing some additional work in mageia 9 to cauldron upgrades. These packages update the keys for dnf and to build with mock. References

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

SRPMS 9/core

• mageia-repos-9-4.1.mga9
• distribution-gpg-keys-1.89-1.1.mga9

‎32 Bit Support: More information

← Older revision Revision as of 22:04, 29 December 2025 (4 intermediate revisions by the same user not shown)Line 51: Line 51:  === 32 Bit Support === === 32 Bit Support ===  We increase hardware requirements for 32bit systems, you will require a CPU with SSE2 features. We increase hardware requirements for 32bit systems, you will require a CPU with SSE2 features. −You will find that extension for the packages change from i586 to i686.+You will find that extension for the packages and the part for architecture in the name of the ISO images have changed from i586 to i686.  Also, due most of the software projects are dropping 32bit support, you can find that the support is not as full as in the x86_64 systems. Also, due most of the software projects are dropping 32bit support, you can find that the support is not as full as in the x86_64 systems.    Line 457: Line 457:  This application that lets you monitor and control a group of computers replaces ''italc''. It is available in version 4.7.4. This application that lets you monitor and control a group of computers replaces ''italc''. It is available in version 4.7.4.    −== Upgrading from Mageia 9 ==+== Move to Mageia 10 ==  +=== Preparation for Installation or Upgrades ===  +{{note|'''CHECK''' the date & time in your machine is right, now the package signatures are as sensible like web pages certificates, this is '''very important''' in upgrades or clean installations if you add online repositories in the process.}}  +   +=== Upgrading from Mageia 9 ===  +{{warning|at moment we need fine tune instructions to upgrade from mageia 9, don't try it}}     Upgrading from Mageia 9 is supported, and has been fine-tuned over the past few months. Upgrading from Mageia 9 is supported, and has been fine-tuned over the past few months. Line 465: Line 470:  {{note|Please also read the Mageia 10 errata chapter [[Mageia_10_Errata#Upgrade_issues|"Upgrade issues"]].}} {{note|Please also read the Mageia 10 errata chapter [[Mageia_10_Errata#Upgrade_issues|"Upgrade issues"]].}}    −=== Preparations ===+==== Preparations ====  * Carefully read this document (Release Notes) and the [[Mageia_10_Errata|Errata]] to see if there is something you need to prepare for.   * Carefully read this document (Release Notes) and the [[Mageia_10_Errata|Errata]] to see if there is something you need to prepare for.    * '''Back up''' any important data. * '''Back up''' any important data. Line 485: Line 490:  - In these cases, you have to do a fresh installation. (Possibly keeping the {{folder|/home}} directory.) - In these cases, you have to do a fresh installation. (Possibly keeping the {{folder|/home}} directory.)    −=== Online-Upgrade ===+==== Online-Upgrade ====     The Mageia Update notification applet, Mageia Online, '''will notify you''' when a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary. The Mageia Update notification applet, Mageia Online, '''will notify you''' when a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary. Line 499: Line 504:  {{Note|Use a wired internet connection if possible, especially when you're using nonfree wlan drivers.}} {{Note|Use a wired internet connection if possible, especially when you're using nonfree wlan drivers.}}    −==== Online-Upgrade, using mgaonline (GUI) ====+===== Online-Upgrade, using mgaonline (GUI) =====     * Use Mageia Online icon in the system tray to start the upgrade. * Use Mageia Online icon in the system tray to start the upgrade. Line 510: Line 515:  {{Command|su -c 'mgaapplet-upgrade-helper --new_distro_version{{=}}10'}} {{Command|su -c 'mgaapplet-upgrade-helper --new_distro_version{{=}}10'}}    −==== Online-Upgrade, using {{cmd|urpmi}} (CLI) ====+===== Online-Upgrade, using {{cmd|urpmi}} (CLI) =====     This method is useful when the root partition is encrypted as the booted system is already decrypting the partition. The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running. Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess up the upgrade. This method is useful when the root partition is encrypted as the booted system is already decrypting the partition. The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running. Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess up the upgrade. Line 535: Line 540:  ** Using the MIRRORLIST method (which will select a mirror automatically based on your geographical location). {{prog|urpmi}} knows what to substitute for $ARCH. ** Using the MIRRORLIST method (which will select a mirror automatically based on your geographical location). {{prog|urpmi}} knows what to substitute for $ARCH.  *:{{cmd|urpmi.addmedia --distrib --mirrorlist <nowiki>'http://mirrors.mageia.org/api/mageia.10.$ARCH.list'</nowiki>}} *:{{cmd|urpmi.addmedia --distrib --mirrorlist <nowiki>'http://mirrors.mageia.org/api/mageia.10.$ARCH.list'</nowiki>}}  +{{warning|For 32bit systems,use i686 instead $ARCH}}  +  ** Or using a specific media mirror. You can get the mirror_url using the [https://mirrors.mageia.org/distrib Mageia mirrors web application]: ** Or using a specific media mirror. You can get the mirror_url using the [https://mirrors.mageia.org/distrib Mageia mirrors web application]:  *:{{cmd|urpmi.addmedia --distrib <mirror_url>}} *:{{cmd|urpmi.addmedia --distrib <mirror_url>}} Line 542: Line 549:  {{Note|It is often a good idea, when you have more than enough free disk space, to test the upgrade before carrying it out.<br />With this command: {{cmd|urpmi --auto-update --auto --force --download-all --test}} all the packages are downloaded and the 'upgrade' is only a simulation. This needs a lot of free space before starting the test - like more than 2GB free space on {{folder|/var}} partition ({{folder|/}} if you have no {{folder|/var}}). (If you have several large desktops and many programs you may need more - if only a lightweight desktop, less.) If you have space on another partition, you can specify the destination of downloaded files by adding a path pointing to this partition after the {{cmd|--download-all}} keyword.<br />If the result is good, then upgrade for real with the command {{cmd|urpmi --auto-update --auto --force --download-all}} (same but without --test). Add also the path of downloaded files if specified previously.<br />If the result is not good, restore the Mageia 9 repositories with {{cmd|urpmi.removemedia -a}} and {{cmd|<nowiki>urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.9.$ARCH.list'</nowiki>}} like above, and clean the cache by issuing {{cmd|urpmi --clean}}.}} {{Note|It is often a good idea, when you have more than enough free disk space, to test the upgrade before carrying it out.<br />With this command: {{cmd|urpmi --auto-update --auto --force --download-all --test}} all the packages are downloaded and the 'upgrade' is only a simulation. This needs a lot of free space before starting the test - like more than 2GB free space on {{folder|/var}} partition ({{folder|/}} if you have no {{folder|/var}}). (If you have several large desktops and many programs you may need more - if only a lightweight desktop, less.) If you have space on another partition, you can specify the destination of downloaded files by adding a path pointing to this partition after the {{cmd|--download-all}} keyword.<br />If the result is good, then upgrade for real with the command {{cmd|urpmi --auto-update --auto --force --download-all}} (same but without --test). Add also the path of downloaded files if specified previously.<br />If the result is not good, restore the Mageia 9 repositories with {{cmd|urpmi.removemedia -a}} and {{cmd|<nowiki>urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.9.$ARCH.list'</nowiki>}} like above, and clean the cache by issuing {{cmd|urpmi --clean}}.}}    −==== Online-Upgrade, using {{cmd|DNF}} (CLI) ====+===== Online-Upgrade, using {{cmd|DNF}} (CLI) =====     If you're using (or now change to use) DNF for software management (configured appropriately per [[Using DNF|our wiki page on using DNF]]), you can upgrade Mageia in just a few steps. If you're using (or now change to use) DNF for software management (configured appropriately per [[Using DNF|our wiki page on using DNF]]), you can upgrade Mageia in just a few steps. Line 560: Line 567:  : {{cmd|dnf system-upgrade reboot}} : {{cmd|dnf system-upgrade reboot}}    −=== Using the installer to Upgrade ===+==== Using the installer to Upgrade ====  {{warning|Right now with the status of some packages in cauldron is not recommended upgrade with the traditional installer in any of its presentations currrently exist conflicts in some packages}} {{warning|Right now with the status of some packages in cauldron is not recommended upgrade with the traditional installer in any of its presentations currrently exist conflicts in some packages}}    Line 571: Line 578:  If you have wired ethernet you can choose either, Netinstall or traditional DVD ISO.  The DVD is larger in initial download, but less need be downloaded during upgrade. If you have wired ethernet you can choose either, Netinstall or traditional DVD ISO.  The DVD is larger in initial download, but less need be downloaded during upgrade.    −=== Upgrading using the traditional DVD ISO ===+==== Upgrading using the traditional DVD ISO ====     * Follow [[#Preparations|Preparations]] above. * Follow [[#Preparations|Preparations]] above. Line 589: Line 596:  On the first reboot after upgrade, use the command '{{cmd|urpmi --auto-update}}' to make [https://bugs.mageia.org/show_bug.cgi?id=5687 sure] all packages were updated.  In case of problems see [[Mageia_10_Errata#Remedies|If upgrade failed]]. On the first reboot after upgrade, use the command '{{cmd|urpmi --auto-update}}' to make [https://bugs.mageia.org/show_bug.cgi?id=5687 sure] all packages were updated.  In case of problems see [[Mageia_10_Errata#Remedies|If upgrade failed]].    −=== Upgrading using the Netinstall ISO ===+==== Upgrading using the Netinstall ISO ====     Follow the same instructions above as for traditional DVD installer, it is very similar. Follow the same instructions above as for traditional DVD installer, it is very similar. Line 595: Line 602:  Also see [[Mageia_Netinstall_Iso_(Boot.iso)|Mageia Netinstall ISO]].   Also see [[Mageia_Netinstall_Iso_(Boot.iso)|Mageia Netinstall ISO]].      −=== Upgrading an encrypted install ===+==== Upgrading an encrypted install ====     ''Using Netinstall or DVD ISO.'' ''Using Netinstall or DVD ISO.'' Katnatek

Publication date: 29 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-46727 , CVE-2025-49007 , CVE-2025-59830 , CVE-2025-61770 , CVE-2025-61771 , CVE-2025-61772 , CVE-2025-61919 , CVE-2025-61780 Description Unbounded-Parameter DoS in Rack::QueryParser. (CVE-2025-46727) ReDoS Vulnerability in Rack::Multipart handle_mime_head. (CVE-2025-49007) Rack QueryParser has an unsafe default allowing params_limit bypass via semicolon-separated parameters. (CVE-2025-59830) Rack's unbounded multipart preamble buffering enables DoS (memory exhaustion). (CVE-2025-61770) Rack's multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion). (CVE-2025-61771) Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion). (CVE-2025-61772) Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing. (CVE-2025-61919) Rack has Possible Information Disclosure Vulnerability. (CVE-2025-61780) References

• https://bugs.mageia.org/show_bug.cgi?id=34755
• https://rack.github.io/rack/3.2/CHANGELOG_md.html
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-46727
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-49007
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-59830
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61770
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61771
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61772
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61919
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-61780

SRPMS 9/core

• ruby-rack-2.2.21-1.mga9

Publication date: 29 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-47866 Description RGW DoS attack with empty HTTP header in S3 object copy. (CVE-2024-47866) References

• https://bugs.mageia.org/show_bug.cgi?id=34741
• https://www.openwall.com/lists/oss-security/2025/11/11/3
• https://github.com/ceph/ceph/security/advisories/GHSA-mgrm-g92q-f8h8
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47866

SRPMS 9/core

• ceph-18.2.7-2.1.mga9

Publication date: 29 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description The current version does not set the environment variable LESSOPEN which means that you can't view gz, bz2, lzma, zip, rpm, html, etc. files. This update fixes the reported issue. After the update you should close the terminal emulator in use for the fix to take effect. References

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

SRPMS 9/core

• less-678-1.2.mga9

Create Mo to Mageia 10 section and move date & time warning

← Older revision Revision as of 17:57, 29 December 2025 (2 intermediate revisions by the same user not shown)Line 457: Line 457:  This application that lets you monitor and control a group of computers replaces ''italc''. It is available in version 4.7.4. This application that lets you monitor and control a group of computers replaces ''italc''. It is available in version 4.7.4.    −== Upgrading from Mageia 9 ==+== Move to Mageia 10 ==  +=== Preparation for Installation or Upgrades ===  +{{note|'''CHECK''' the date & time in your machine is right, now the package signatures are as sensible like web pages certificates, this is '''very important''' in upgrades or clean installations if you add online repositories in the process.}}  +   +=== Upgrading from Mageia 9 ===  +{{warning|at moment we need fine tune instructions to upgrade from mageia 9, don't try it}}     Upgrading from Mageia 9 is supported, and has been fine-tuned over the past few months. Upgrading from Mageia 9 is supported, and has been fine-tuned over the past few months. Line 465: Line 470:  {{note|Please also read the Mageia 10 errata chapter [[Mageia_10_Errata#Upgrade_issues|"Upgrade issues"]].}} {{note|Please also read the Mageia 10 errata chapter [[Mageia_10_Errata#Upgrade_issues|"Upgrade issues"]].}}    −=== Preparations ===+==== Preparations ====  * Carefully read this document (Release Notes) and the [[Mageia_10_Errata|Errata]] to see if there is something you need to prepare for.   * Carefully read this document (Release Notes) and the [[Mageia_10_Errata|Errata]] to see if there is something you need to prepare for.    * '''Back up''' any important data. * '''Back up''' any important data. Line 485: Line 490:  - In these cases, you have to do a fresh installation. (Possibly keeping the {{folder|/home}} directory.) - In these cases, you have to do a fresh installation. (Possibly keeping the {{folder|/home}} directory.)    −=== Online-Upgrade ===+==== Online-Upgrade ====     The Mageia Update notification applet, Mageia Online, '''will notify you''' when a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary. The Mageia Update notification applet, Mageia Online, '''will notify you''' when a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary. Line 499: Line 504:  {{Note|Use a wired internet connection if possible, especially when you're using nonfree wlan drivers.}} {{Note|Use a wired internet connection if possible, especially when you're using nonfree wlan drivers.}}    −==== Online-Upgrade, using mgaonline (GUI) ====+===== Online-Upgrade, using mgaonline (GUI) =====     * Use Mageia Online icon in the system tray to start the upgrade. * Use Mageia Online icon in the system tray to start the upgrade. Line 510: Line 515:  {{Command|su -c 'mgaapplet-upgrade-helper --new_distro_version{{=}}10'}} {{Command|su -c 'mgaapplet-upgrade-helper --new_distro_version{{=}}10'}}    −==== Online-Upgrade, using {{cmd|urpmi}} (CLI) ====+===== Online-Upgrade, using {{cmd|urpmi}} (CLI) =====     This method is useful when the root partition is encrypted as the booted system is already decrypting the partition. The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running. Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess up the upgrade. This method is useful when the root partition is encrypted as the booted system is already decrypting the partition. The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running. Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess up the upgrade. Line 542: Line 547:  {{Note|It is often a good idea, when you have more than enough free disk space, to test the upgrade before carrying it out.<br />With this command: {{cmd|urpmi --auto-update --auto --force --download-all --test}} all the packages are downloaded and the 'upgrade' is only a simulation. This needs a lot of free space before starting the test - like more than 2GB free space on {{folder|/var}} partition ({{folder|/}} if you have no {{folder|/var}}). (If you have several large desktops and many programs you may need more - if only a lightweight desktop, less.) If you have space on another partition, you can specify the destination of downloaded files by adding a path pointing to this partition after the {{cmd|--download-all}} keyword.<br />If the result is good, then upgrade for real with the command {{cmd|urpmi --auto-update --auto --force --download-all}} (same but without --test). Add also the path of downloaded files if specified previously.<br />If the result is not good, restore the Mageia 9 repositories with {{cmd|urpmi.removemedia -a}} and {{cmd|<nowiki>urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.9.$ARCH.list'</nowiki>}} like above, and clean the cache by issuing {{cmd|urpmi --clean}}.}} {{Note|It is often a good idea, when you have more than enough free disk space, to test the upgrade before carrying it out.<br />With this command: {{cmd|urpmi --auto-update --auto --force --download-all --test}} all the packages are downloaded and the 'upgrade' is only a simulation. This needs a lot of free space before starting the test - like more than 2GB free space on {{folder|/var}} partition ({{folder|/}} if you have no {{folder|/var}}). (If you have several large desktops and many programs you may need more - if only a lightweight desktop, less.) If you have space on another partition, you can specify the destination of downloaded files by adding a path pointing to this partition after the {{cmd|--download-all}} keyword.<br />If the result is good, then upgrade for real with the command {{cmd|urpmi --auto-update --auto --force --download-all}} (same but without --test). Add also the path of downloaded files if specified previously.<br />If the result is not good, restore the Mageia 9 repositories with {{cmd|urpmi.removemedia -a}} and {{cmd|<nowiki>urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.9.$ARCH.list'</nowiki>}} like above, and clean the cache by issuing {{cmd|urpmi --clean}}.}}    −==== Online-Upgrade, using {{cmd|DNF}} (CLI) ====+===== Online-Upgrade, using {{cmd|DNF}} (CLI) =====     If you're using (or now change to use) DNF for software management (configured appropriately per [[Using DNF|our wiki page on using DNF]]), you can upgrade Mageia in just a few steps. If you're using (or now change to use) DNF for software management (configured appropriately per [[Using DNF|our wiki page on using DNF]]), you can upgrade Mageia in just a few steps. Line 560: Line 565:  : {{cmd|dnf system-upgrade reboot}} : {{cmd|dnf system-upgrade reboot}}    −=== Using the installer to Upgrade ===+==== Using the installer to Upgrade ====  {{warning|Right now with the status of some packages in cauldron is not recommended upgrade with the traditional installer in any of its presentations currrently exist conflicts in some packages}} {{warning|Right now with the status of some packages in cauldron is not recommended upgrade with the traditional installer in any of its presentations currrently exist conflicts in some packages}}    Line 571: Line 576:  If you have wired ethernet you can choose either, Netinstall or traditional DVD ISO.  The DVD is larger in initial download, but less need be downloaded during upgrade. If you have wired ethernet you can choose either, Netinstall or traditional DVD ISO.  The DVD is larger in initial download, but less need be downloaded during upgrade.    −=== Upgrading using the traditional DVD ISO ===+==== Upgrading using the traditional DVD ISO ====     * Follow [[#Preparations|Preparations]] above. * Follow [[#Preparations|Preparations]] above. Line 589: Line 594:  On the first reboot after upgrade, use the command '{{cmd|urpmi --auto-update}}' to make [https://bugs.mageia.org/show_bug.cgi?id=5687 sure] all packages were updated.  In case of problems see [[Mageia_10_Errata#Remedies|If upgrade failed]]. On the first reboot after upgrade, use the command '{{cmd|urpmi --auto-update}}' to make [https://bugs.mageia.org/show_bug.cgi?id=5687 sure] all packages were updated.  In case of problems see [[Mageia_10_Errata#Remedies|If upgrade failed]].    −=== Upgrading using the Netinstall ISO ===+==== Upgrading using the Netinstall ISO ====     Follow the same instructions above as for traditional DVD installer, it is very similar. Follow the same instructions above as for traditional DVD installer, it is very similar. Line 595: Line 600:  Also see [[Mageia_Netinstall_Iso_(Boot.iso)|Mageia Netinstall ISO]].   Also see [[Mageia_Netinstall_Iso_(Boot.iso)|Mageia Netinstall ISO]].      −=== Upgrading an encrypted install ===+==== Upgrading an encrypted install ====     ''Using Netinstall or DVD ISO.'' ''Using Netinstall or DVD ISO.'' Katnatek

Add Bas V

← Older revision Revision as of 13:45, 28 December 2025 Line 83: Line 83:     User:justchris57 User:justchris57  +  +User:k9     User:karine User:karine Marja

‎Proprietary NVIDIA driver

← Older revision Revision as of 11:26, 28 December 2025 (3 intermediate revisions by the same user not shown)Line 215: Line 215:  NVIDIA's proprietary drivers are provided in the nonfree repositories, 64 bit only: NVIDIA's proprietary drivers are provided in the nonfree repositories, 64 bit only:    −* Recent GPUs are supported by the R535 series driver packaged as "nvidia-current", chosen by "Geforce 745 series and later" in our tools. We also have "nvidia-newfeature", chosen by "Driver: New feature" - It is intended as alternative for newest cards ''but note that we may not keep nvidia-newfeature up to date and in sync with kernel, and it may actually be less recent than nvidia-current.  Actual version can be seen by the package version. Not available on Mageia 10 ISOs nor in repositories at release time of Mageia 10.''+* Recent GPUs are supported by the R580 series driver packaged as "nvidia-current", chosen by "Geforce 745 series and later" in our tools.    −* For older GPUs, we supply R470 series drivers "nvidia470", chosen by "Geforce 635 to Geforce 920" in our tools. R470 was "nvidia-current" in Mageia 9, and some cards that used that then may need be manually set to R470 in Mageia 10.+: We also have "nvidia-newfeature", chosen by "Driver: New feature" - It is intended as alternative for newest cards - ''but note that we may not keep nvidia-newfeature up to date and in sync with kernel, and it may actually be less recent than nvidia-current.''  Both "nvidia-current" and "nvidia-newfeature" will apart from minor updates also jump to new Rxxx versions during a Mageia release lifetime. Actual version can be seen by the package version.''    −* NVIDIAs proprietary 390.x driver series, which supported older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022. Because the driver is not compatible with newer Kernel and newer X Server versions we had to drop it. Please try the free Xorg driver nouveau or modesetting.+* For older GPUs, we supply R470 series drivers "nvidia470", (same as for Mageia 9) chosen by "Geforce 635 to Geforce 920" in our tools. R470 was "nvidia-current" in Mageia 8, and some cards that used that then may now need to be manually set to R470.  ''Note that it is not supported upstream and is not receiving security updates but we provide it as is for convenience of our users who choose to use it.'' nvidia470 packages are not provided on Mageia 10 Live ISOs <!-- Ref: https://bugs.mageia.org/show_bug.cgi?id=34545#c165 --> but will be installed from our "nonfree" repository when you choose to. (And in Live you need [[Persistent_live_systems|persistence]] activated.)  +   +: The 390.x driver series, which supported older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022. Because the driver is not compatible with newer Kernel and newer X Server versions we had to drop it. Please try the free Xorg driver nouveau or modesetting.     * CUDA and OpenCL are supported for "nvidia-current". * CUDA and OpenCL are supported for "nvidia-current".    −* NEW: We now provide [[Setup_the_graphical_server#The_alternative_opensourced_nvidia_kernel_modules|alternative opensourced nvidia kernel modules]] (in Mageia 9 since Dec 24). <!-- I think we should write more about it here -->+* NEW: We now provide [[Setup_the_graphical_server#The_alternative_opensourced_nvidia_kernel_modules|alternative opensourced nvidia kernel modules]] (in Mageia 9 since Dec 2024). <!-- I think we should write more about it here -->    −* NEW: It is now possible to have nvidia driver loaded early, [[Setup_the_graphical_server#Loading_driver_in_initramfs|in initramfs]].  (in Mageia 9 since Jan 25)+* NEW: It is now possible to have nvidia driver loaded early, [[Setup_the_graphical_server#Loading_driver_in_initramfs|in initramfs]].  (in Mageia 9 since Jan 2025)    −''For more information see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].''+''For more information on all drivers see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].''     ====== Optimus laptops ====== ====== Optimus laptops ====== Morgano

‎Proprietary NVIDIA driver

← Older revision Revision as of 03:27, 28 December 2025 (2 intermediate revisions by the same user not shown)Line 215: Line 215:  NVIDIA's proprietary drivers are provided in the nonfree repositories, 64 bit only: NVIDIA's proprietary drivers are provided in the nonfree repositories, 64 bit only:    −* Recent GPUs are supported by the R535 series driver packaged as "nvidia-current", chosen by "Geforce 745 series and later" in our tools. We also have "nvidia-newfeature", chosen by "Driver: New feature" - It is intended as alternative for newest cards ''but note that we may not keep nvidia-newfeature up to date and in sync with kernel, and it may actually be less recent than nvidia-current.  Actual version can be seen by the package version. Not available on Mageia 10 ISOs nor in repositories at release time of Mageia 10.''+* Recent GPUs are supported by the R580 series driver packaged as "nvidia-current", chosen by "Geforce 745 series and later" in our tools.    −* For older GPUs, we supply R470 series drivers "nvidia470", chosen by "Geforce 635 to Geforce 920" in our tools. R470 was "nvidia-current" in Mageia 9, and some cards that used that then may need be manually set to R470 in Mageia 10.+: We also have "nvidia-newfeature", chosen by "Driver: New feature" - It is intended as alternative for newest cards - ''but note that we may not keep nvidia-newfeature up to date and in sync with kernel, and it may actually be less recent than nvidia-current.''  Both "nvidia-current" and "nvidia-newfeature" will apart from minor updates also jump to new Rxxx versions during a Mageia release lifetime. Actual version can be seen by the package version.''    −* NVIDIAs proprietary 390.x driver series, which supported older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022. Because the driver is not compatible with newer Kernel and newer X Server versions we had to drop it. Please try the free Xorg driver nouveau or modesetting.+* For older GPUs, we supply R470 series drivers "nvidia470", (same as for Mageia 9) chosen by "Geforce 635 to Geforce 920" in our tools. R470 was "nvidia-current" in Mageia 8, and some cards that used that then may now need to be manually set to R470.  ''Note that it is not supported upstream and is not receiving security updates but we provide it as is for convenience of our users who choose to use it.'' nvidia470 packages are not provided on Mageia 10 Live ISOs <!-- Ref: https://bugs.mageia.org/show_bug.cgi?id=34545#c165 --> but will be installed from our "nonfree" repository when you choose to. (And in Live you need [[Persistent_live_systems|persistence]] activated.)  +   +: The 390.x driver series, which supported older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022. Because the driver is not compatible with newer Kernel and newer X Server versions we had to drop it. Please try the free Xorg driver nouveau or modesetting.     * CUDA and OpenCL are supported for "nvidia-current". * CUDA and OpenCL are supported for "nvidia-current". Line 227: Line 229:  * NEW: It is now possible to have nvidia driver loaded early, [[Setup_the_graphical_server#Loading_driver_in_initramfs|in initramfs]].  (in Mageia 9 since Jan 25) * NEW: It is now possible to have nvidia driver loaded early, [[Setup_the_graphical_server#Loading_driver_in_initramfs|in initramfs]].  (in Mageia 9 since Jan 25)    −''For more information see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].''+:''For more information see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].''     ====== Optimus laptops ====== ====== Optimus laptops ====== Morgano

‎raster on ttys when using multiple displays of unequal resolutions

← Older revision Revision as of 02:16, 28 December 2025 (One intermediate revision by the same user not shown)Line 74: Line 74:     {{fixme|81}} ''Someone try on Mageia and document it here.'' {{fixme|81}} ''Someone try on Mageia and document it here.''  +  +===Raster on portions of tty(s) when using multiple displays of unequal resolutions===  +  +This is upstream bug https://gitlab.freedesktop.org/drm/nouveau/-/issues/214, applicable when plymouth is disabled, and a valid video= parameter is not included on the linu line in bootloader stanzas.     <br> <br> Mrmazda