Wiki Mageia

‎Various software: wording and formatting

← Older revision Revision as of 11:59, 31 December 2025 (9 intermediate revisions by the same user not shown)Line 77: Line 77:  ==== Crash before the end of install ==== ==== Crash before the end of install ====    −{{bug|31628}} At least one case is reported on where in an old BIOS laptop the installation process crash before the end.  It is possible that after reboot you get a bootable Mageia 9. Try immediately a full update.+{{bug|31628}} At least one case has been reported where the installation process crashes on an old BIOS laptop before completion.  It is possible that you will get a bootable Mageia 9 after restarting. Try a full update immediately.     <br> <br>  +  ==== Crash at end of install ==== ==== Crash at end of install ====    Line 87: Line 88:  === NetInstaller === === NetInstaller ===    −On some UEFI machines, the NetInstaller ISO boots with a '''Grub error message''': ''error: ../../grub-core/video/readers/png.c:595 invalid filter value'' And shows Grub2 menu using text mode instead of graphic. Functionality is not affected; it is just a cosmetic quirk. {{Bug|28225}}+{{Bug|28225}} On some UEFI machines, the NetInstaller ISO boots with a '''Grub error message''': ''error: ../../grub-core/video/readers/png.c:595 invalid filter value'' And shows Grub2 menu using text mode instead of graphic. Functionality is not affected; it is just a cosmetic quirk.         Line 103: Line 104:     <br> <br>  +  === To use the 32-bit Classic installer on USB as a repository === === To use the 32-bit Classic installer on USB as a repository ===    Line 142: Line 144:     === Various === === Various === −{{bug|34205}} In system upgraded from mageia 9, with LXDE desktop + {{prog|lxdm}} as desktop manager , some applications try to open a bus for root, you will see if run the application in terminal the message+{{bug|34205}} On systems which got upgraded from Mageia 9, with LXDE desktop + {{prog|lxdm}} as desktop manager, some applications try to open a bus for root. When run from a terminal, messages like this appear:    Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied   Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied    −'''Manual Fix''' In Desktop Session Settings ({{prog|lxsession-edit}}) -> Automatically Started Applications, enable AT-SPDI-D-Bus, close the session and start the session again.+'''Manual Fix''' In Desktop Session Settings {{prog|lxsession-edit}} -> {{prog|Automatically Started Applications}}, enable AT-SPDI-D-Bus, close and restart the session.       −{{bug|34836}} Due to alphabetical order of desktop session, when you boot in the installed system you will find the default session is IceWM. '''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|34836}} 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.     === GNOME === === GNOME === Line 170: Line 172:  ==== LXQt and Wayland ==== ==== LXQt and Wayland ====    −The Mageia Control Center and other gui tools just works if you use kwin_wayland as window manager for the LXQt Wayland session, you will not see a full window, {{bug|34495}}-+{{bug|34495}} The Mageia Control Center and other GUI tools may not open after entering the password. '''WORKAROUND:''' Use kwin_wayland as window manager for the LXQt Wayland session.       Line 180: Line 182:     === Chromium browser === === Chromium browser === −We do not have a maintainer for this software. Workarounds: As [[Flatpak|Flatpak]] install app/org.chromium.Chromium/x86_64/stable, or Chrome. Or use Chrome rpm from Google.+Currently we do not have a permanent maintainer for Chromium and cannot provide updates in time. '''WORKAROUND''': Install Chromium via [[Flatpak|Flatpak]] or use the Chrome rpm from Google.     === Firefox ESR === === Firefox ESR === Line 203: Line 205:     === Various software === === Various software === −{{Bug|34293}}, Some KDE applications like {{prog|plasmatube}}, can fail when are installed for use in systems that not include Plasma Desktop with '''module "org.kde.desktop" is not installed''' exist two workarounds see {{Bug|34812#c3}}+{{Bug|34293}} Some KDE applications like {{prog|plasmatube}}, may fail when installed on non Plasma Desktop systems. '''WORKAROUND:''' See {{Bug|34812#c3}}     {{Bug|34634}} - '''CodeBlocks:''' For now, we had to disable the wxSmith plugin. {{Bug|34634}} - '''CodeBlocks:''' For now, we had to disable the wxSmith plugin. Sturmvogel

‎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

‎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

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

add explanation for mga10a1 release date

← Older revision Revision as of 21:18, 27 December 2025 Line 23: Line 23:  | 2025-12-05 | 2025-12-05  | developers, packagers | developers, packagers −| 2025-12-09+| 2025-12-09 for QA, public release soon  |- |-  | Versions freeze | Versions freeze Filip

‎Package Ordering: Mention mageia-build-order

← Older revision Revision as of 22:56, 26 December 2025 Line 18: Line 18:  </pre> </pre>  This script is only available on duvel to sysadmins, as it looks at autobuild logs directly to get the list of packages that need to be installed while building each package (including basesystem). It is also not that smart as it works at src.rpm level and may find too many loops, for example if something needs a noarch subpackage and not the binary one needing a rebuild, there is no need to wait until it was rebuilt. This script is only available on duvel to sysadmins, as it looks at autobuild logs directly to get the list of packages that need to be installed while building each package (including basesystem). It is also not that smart as it works at src.rpm level and may find too many loops, for example if something needs a noarch subpackage and not the binary one needing a rebuild, there is no need to wait until it was rebuilt.  +  +A version of this script that can be used on developers' machines is available at https://github.com/pterjan/mageia-build-order but it uses a dependency metadata snapshot that might not be up-to-date.     == See Also == == See Also == Danf

‎Nvidia driver versions: update

← Older revision Revision as of 17:43, 26 December 2025 Line 200: Line 200:  To update when needed! To update when needed!    −: '''Listed as -- package name -- driver -- GPU range -- comment'''+===== Mageia 9 =====  +List of available drivers:  +: '''Listed as -- package name -- driver -- comment'''     * Driver: Latest Legacy -- nvidia470 -- R470 -- R470 was "nvidia-current" in Mageia 8. * Driver: Latest Legacy -- nvidia470 -- R470 -- R470 was "nvidia-current" in Mageia 8. −* Driver: Production -- nvidia-current -- R550 -- Intended for all recent Nvidia GPU  +* Driver: Production -- nvidia-current -- R535, 550, 570, 580 *) -- Intended for all recent Nvidia GPU. −* Driver: New Feature -- nvidia-newfeature -- R565 -- *usually* a later version than nvidia-current, sometimes this is upstream "beta". Can be seen as experimental in beginning of a new Mageia release - try this when your card is not fully supported by nvidia-current.  Note though that it may not be kept up to date as duly, i.e maybe not compatible with new kernel immediately, but usually is. CUDA and OpenCL support is only guaranteed for nvidia-current but may work for newfeature.+* Driver: New Feature -- nvidia-newfeature -- R545, 555, 565, (and 575 still in testing repo at time of writing) -- *usually* a later version than nvidia-current, sometimes this is upstream "beta". Can be seen as experimental in beginning of a new Mageia release - try this when your card is not fully supported by nvidia-current.  Note though that it may not be kept up to date as duly, i.e maybe not compatible with new kernel immediately, but usually is. CUDA and OpenCL support is only guaranteed for nvidia-current but may work for newfeature. −* GeForce 745 series and later --> same as Production+* GeForce 745 series and later --> same as Production. −* GeForce 635 to GeForce 920 --> same as Latest Legacy+* GeForce 635 to GeForce 920 --> same as Latest Legacy. −: We do not ship elder drivers, for security and compatibility reasons, as Nvidia do not update them.+* RIVA 128 --> installs free nv. −* RIVA 128 --> installs free nv+* [FIXME] other choices: --> installs free nouveau (Or possibly keep from previous Mageia release). −* [FIXME] other choices: --> installs free nouveau (Or possibly keep from previous Mageia release)     −''Caution: a rare bug: {{Bug|32579}} - switching nvidia driver, next boot fail graphical mode for the kernel that was running'' +When you install Mageia, a driver is automatically selected.  +   +Note *) Drivers base version change during the lifetime of a Mageia release. The list here might not be updated.  Note that we only keep the highest version per class (Legacy / Production / New Feature) updated - i.e if we ship 535 as nvidia-current, and later ship 550 as nvidia-current, only 550 is getting further updates, etc.  Do not worry, if you have nvidia-current installed, it will be updated to next version as normal updates.     - If none suits your GPU, try Xorg nouveau, modesetting, or possibly nv. - If none suits your GPU, try Xorg nouveau, modesetting, or possibly nv.    −: ''Driver versions noted for Mageia 9.''+''Caution: a rare bug: {{Bug|32579}} - switching nvidia driver, next boot fail graphical mode for the kernel that was running''       [https://forums.developer.nvidia.com/t/current-graphics-driver-releases Nvidia list of current drivers] [https://forums.developer.nvidia.com/t/current-graphics-driver-releases Nvidia list of current drivers]     ==== Elder Nvidia drivers ==== ==== Elder Nvidia drivers ====  +''We do not ship elder drivers, for security and compatibility reasons, as Nvidia do not update them.''    −Nvidia R390 driver series, available in Mageia 8, supporting older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022 so it no longer receive security and compatibility updates.+Nvidia R390 driver series, which was available in Mageia 8, supporting older graphic cards like the GF1xx series, is EOL (end of life) since the end of 2022 so it no longer receive security and compatibility updates.     In Mageia 9, because security and incompatibility with Kernel and X Server we had to drop R390.   In Mageia 9, because security and incompatibility with Kernel and X Server we had to drop R390.   Morgano

‎Various: Bug Fixed

← Older revision Revision as of 19:01, 25 December 2025 Line 149: Line 149:     {{bug|34836}} Due to alphabetical order of desktop session, when you boot in the installed system you will find the default session is IceWM. '''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|34836}} Due to alphabetical order of desktop session, when you boot in the installed system you will find the default session is IceWM. '''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|34846}} Fresh installed or ugraded mageia 10 systems runing as guest in {{prog|gnome-boxes}} not start in graphic mode, To determine the easiest workarround.      === GNOME === === GNOME === Katnatek

‎Access/Identity: Add Bugzilla link

← Older revision Revision as of 03:29, 24 December 2025 Line 24: Line 24:  * [[SOP Sysadmin access revocation]] * [[SOP Sysadmin access revocation]]  * [[SOP Adding groups]] * [[SOP Adding groups]] −* Blocking users in Bugzilla due to spammy behaviour ''(this is currently done by Bugzilla admins, not Sysadmins)''+* [[Blocking_spammers#Bugzilla|Blocking users in Bugzilla]] due to spammy behaviour ''(this is currently done by Bugzilla admins, not Sysadmins)''  * Unlock user account * Unlock user account  * [[SOP robot credentials renewal]] * [[SOP robot credentials renewal]] Danf

Basic info in dealing with spammers

New page

= Dealing with spammers =

Spam can be defined as ''unsolicited usually commercial messages (such as emails, text messages, or Internet postings) sent to a large number of recipients or posted in a large number of places'' and is prohibited (implicitly) by almost every clause in the Mageia [https://www.mageia.org/en-gb/about/code-of-conduct/ Code of Conduct]. While it's possible a new Internet user might not quite understand the finer points of online collaboration and could make an honest mistake (requiring a gentle correction), most spam that affects Mageia consists of overt commercial advertising that should be dealt with quickly and severely. Doing so appropriately depends on the system being spammed.

== Bugzilla ==

A Bugzilla administrator can visit the [https://bugs.mageia.org/editusers.cgi admin page] and search for the e-mail address (login name) of the spammer. Click on the user that shows up and add the word "spammer" to the ''Disable text'' and ''Real name'' boxes that appear, then hit ''Save Changes''. This will block the user from logging in and being able to add further comments. Then go back and hide any spam comments that user added.

== Mailing Lists ==

Mailing list administrators have access to remove users from mailing lists. One of the mailing list [https://people.mageia.org/g/mga-ml_moderators.html moderators] can remove the spammer from all mailing lists.

TBD

== Forums ==

TBD

== Source Code Control (Git/SVN) ==

By the time a Mageia user gains the right to submit to our git or svn system, he/she should have shown the appropriate level of understanding of our policies and won't be committing undesired artifacts deliberately. If someone is committing garbage to our source code control systems, it is likely the user has had his/her account hacked. Have a sysadmin take the appropriate action to block the user immediately (e.g. by removing the SSH key and password hash from LDAP), then follow up to found out what happened and how to prevent it from happening again. This level of access by a hacker will require a thorough forensic examination to determine what Mageia resources were manipulated. Danf

‎Desktops: mga#34846

← Older revision Revision as of 02:33, 24 December 2025 (2 intermediate revisions by the same user not shown)Line 142: Line 142:     === Various === === Various ===  +{{bug|34205}} In system upgraded from mageia 9, with LXDE desktop + {{prog|lxdm}} as desktop manager , some applications try to open a bus for root, you will see if run the application in terminal the message  + Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied  +  +'''Manual Fix''' In Desktop Session Settings ({{prog|lxsession-edit}}) -> Automatically Started Applications, enable AT-SPDI-D-Bus, close the session and start the session again.  +     {{bug|34836}} Due to alphabetical order of desktop session, when you boot in the installed system you will find the default session is IceWM. '''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|34836}} Due to alphabetical order of desktop session, when you boot in the installed system you will find the default session is IceWM. '''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|34846}} Fresh installed or ugraded mageia 10 systems runing as guest in {{prog|gnome-boxes}} not start in graphic mode, To determine the easiest workarround.     === GNOME === === GNOME === Katnatek

‎Upgrading from Mageia 9: Move warning

← Older revision Revision as of 01:42, 24 December 2025 (2 intermediate revisions by the same user not shown)Line 559: Line 559:     === 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}}     You can use both the minimal Netinstall, and the big traditional (so, non-Live) DVD ISOs to do clean installs, but also to perform an upgrade. You can use both the minimal Netinstall, and the big traditional (so, non-Live) DVD ISOs to do clean installs, but also to perform an upgrade. Line 569: Line 570:     === Upgrading using the traditional DVD ISO === === Upgrading using the traditional DVD ISO ===  +  * Follow [[#Preparations|Preparations]] above. * Follow [[#Preparations|Preparations]] above.  * Take note on what repositories are enabled (and have been enabled and installed from any time!) * Take note on what repositories are enabled (and have been enabled and installed from any time!) Katnatek

‎Notes: Link yo 10alpha1 bugs

← Older revision Revision as of 22:20, 23 December 2025 Line 18: Line 18:  ''THIS PAGE IS A WORK IN PROGRESS'' ''THIS PAGE IS A WORK IN PROGRESS''    −'' Note that we will be updating issues from the bugtracker, i.e [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA10 FOR_ERRATA10], [https://bugs.mageia.org/buglist.cgi?keywords=IN_ERRATA10 IN_ERRATA10], [https://bugs.mageia.org/buglist.cgi?keywords=FOR_RELEASENOTES10 FOR_RELEASENOTES10] as they are decided.  We try to keep it rather relaxed, but notorious even so, and each issue must be short and effectively described to not make the whole page too big.  So, to-the-point descriptions of symptom and possible remedy.  Sometime a link directly to a bug comment where a good workaround is described, or other resource that may help.''+'' Note that we will be updating issues from the [https://bugs.mageia.org/buglist.cgi?keywords=10alpha1%2C%20&keywords_type=allwords&order=Importance&query_format=advanced&resolution=--- bugtracker], i.e [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA10 FOR_ERRATA10], [https://bugs.mageia.org/buglist.cgi?keywords=IN_ERRATA10 IN_ERRATA10], [https://bugs.mageia.org/buglist.cgi?keywords=FOR_RELEASENOTES10 FOR_RELEASENOTES10] as they are decided.  We try to keep it rather relaxed, but notorious even so, and each issue must be short and effectively described to not make the whole page too big.  So, to-the-point descriptions of symptom and possible remedy.  Sometime a link directly to a bug comment where a good workaround is described, or other resource that may help.''     This English version errata is the master, German version usually kept updated, other languages often lag and miss being kept updated. This English version errata is the master, German version usually kept updated, other languages often lag and miss being kept updated. Katnatek