Lector de Feeds

‎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

Publication date: 26 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description Fixed a bug that caused display corruption on LG Ultragear monitors when certain modes were used. Fixed a bug that caused corruption in X-Plane on workstation GPUs. Fixed a regression introduced in 580.65.06, that caused some mode timings, such as 1920x1080@75, to no longer be available. Reverted a change that led to a user regression in 580.105.08 that caused display modes to be invalidated on a number of monitors. Fixed a bug that caused the Dots Per Inch (DPI) to be incorrectly reported for some monitors such as the Samsung Odyssey Neo G9. Fixed several problems that prevented Vulkan applications from working on Venus VirtIO virtual GPU, on Volta and newer. Fixed the following EGL platform bugs that prevented multisample configurations from working. References

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

SRPMS 9/core

• ldetect-lst-0.6.63-1.mga9

9/nonfree

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

‎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

‎Backport kernels

← Older revision Revision as of 17:08, 23 December 2025 (One intermediate revision by the same user not shown)Line 84: Line 84:  '''Regarding kernel-*-userspace-headers''' contra ''kernel-userspace-headers for 6.6 kernels:'' The packages are used for building applications; use the one for the current kernel you build for. They conflict each other and are handled correctly by urpmi & drakrpm - when you have '''updated mageia-repos and meta-task packages''' to 9.4 versions - and using non backport kernel versions >= 6.6.105. '''Regarding kernel-*-userspace-headers''' contra ''kernel-userspace-headers for 6.6 kernels:'' The packages are used for building applications; use the one for the current kernel you build for. They conflict each other and are handled correctly by urpmi & drakrpm - when you have '''updated mageia-repos and meta-task packages''' to 9.4 versions - and using non backport kernel versions >= 6.6.105.    −'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add (for all backport versions):<br>  +'''Kernel modules''' are not supplied (at least not yet), so like for non backport kernel-linus (in contrast to desktop and server flavours) they need be built locally by dkms (automatically at install or boot) - if you need.  So for '''VirtualBox''', install dkms-virtualbox, for the proprietary '''nvidia'''<version> driver install dkms-nvidia<version>, etc. And, importantly, you need to install a kernel-*-'''devel'''-6.* package of exactly the version as your kernel-*-6.*.  +   +'''If running VirtualBox < 7.1.14,''' see {{Bug|34408#c7}}.  +   +'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels by default, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add (for all backport versions):<br>    kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source <br>  kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-source kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-source −  −  −'''If running VirtualBox < 7.1.14,''' see {{Bug|34408#c7}}.      == Kernel series in Cauldron == == Kernel series in Cauldron == Morgano

‎Removing user from group: Mention attribute error message

← Older revision Revision as of 05:57, 23 December 2025 Line 28: Line 28:        [root@duvel ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f remove.ldif    [root@duvel ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f remove.ldif  +  +If you see the error message  +  +  additional info: object class 'groupOfNames' requires attribute 'member'  +  + it means you are trying to remove the last member of a group which isn't allowed. Find someone else to replace that person in the group and add that user first.     = Removing owner of group = = Removing owner of group = Danf

Publication date: 22 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-68460 , CVE-2025-68461 Description Fix Cross-Site-Scripting vulnerability via SVG's animate tag reported by Valentin T., CrowdStrike. Fix Information Disclosure vulnerability in the HTML style sanitizer reported by somerandomdev. References

• https://bugs.mageia.org/show_bug.cgi?id=34863
• https://github.com/roundcube/roundcubemail/releases/tag/1.6.12
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68460
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68461

SRPMS 9/core

• roundcubemail-1.6.12-1.mga9

‎LXQt with Wayland: typos

← Older revision Revision as of 22:38, 22 December 2025 (3 intermediate revisions by the same user not shown)Line 315: Line 315:  ===== LXQt with Wayland ===== ===== LXQt with Wayland =====    −We provide {{prog|task-lxqt-wayland}} and {{prog|task-lxqt-wayaland-minimal}} in our repositories, you can install lxqt from the Classical ISO, add the online repositories and install one of the wayland task packages.+We provide {{prog|task-lxqt-wayland}} and {{prog|task-lxqt-wayaland-minimal}} in our repositories, you can install lxqt from the Classical ISO, after boot in the installed system add the online repositories and install one of the wayland task packages.    −You can choice the window manager you want to use. The choice includes kwin_wayland, labwc, niri and hyprland.+You can choose the window manager you want to use. The options include {{prog|kwin_wayland}}, {{prog|labwc}}, {{prog|niri}} and {{prog|hyprland}}, install one of them before installing the task packages or you get some default selection by the package manager.    −Some things will not work see the [[Mageia_10_Errata|Errata page]].+Some things will not work, see the [[Mageia_10_Errata|Errata page]].     ==== MATE ==== ==== MATE ==== Katnatek