Wiki de Mageia

‎Dorsync

← Older revision Revision as of 16:59, 14 December 2025 (One intermediate revision by the same user not shown)Line 197: Line 197:     The ''dorsync'' tool is downloaded by   The ''dorsync'' tool is downloaded by   −  $ wget https://dl.dropboxusercontent.com/u/4147101/QA/dorsync+  $ wget https://gitweb.mageia.org/qa/dorsync/tree/dorsync  See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools|Wiki page]] for a fuller note, and setting it up ("Dorsync->Preparation"). If you ''only'' want it as an ISO dumping tool, then just the following item should need defining: See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools|Wiki page]] for a fuller note, and setting it up ("Dorsync->Preparation"). If you ''only'' want it as an ISO dumping tool, then just the following item should need defining:    # location is where you stored the ISOs    #   # location is where you stored the ISOs    # Line 207: Line 207:  USB drives found: USB drives found:       Device Size When Found Model      Device Size When Found Model −1) /dev/sdb 4Gb Dydd Llun 17 mis Tachwedd 2014 18:29:29 CET CBM Flash Disk+1) /dev/sdb 4Gb Monday, November 17, 2014 18:29:29 CET CBM Flash Disk  Please choose which USB to use or Q to quit and press <enter>: 1 </nowiki> Please choose which USB to use or Q to quit and press <enter>: 1 </nowiki>  Then it shows a list of ISO images it finds in your ISO directories, for you to chose which one to write out, e.g. Then it shows a list of ISO images it finds in your ISO directories, for you to chose which one to write out, e.g. Line 220: Line 220:    <nowiki>   <nowiki>  About to dump /mnt/common/Mageia/KDE64/Mageia-5-beta1-LiveDVD-KDE4-x86_64-DVD.iso About to dump /mnt/common/Mageia/KDE64/Mageia-5-beta1-LiveDVD-KDE4-x86_64-DVD.iso −onto /dev/sdb (4Gb CBM Flash Disk found at Dydd Llun 17 mis Tachwedd 2014 18:29:29 CET)+onto /dev/sdb (4Gb CBM Flash Disk found at Monday, November 17, 2014 18:29:29 CET)  This will destroy any data already on the USB device. This will destroy any data already on the USB device.  Press Y to confirm or Q to quit: y Press Y to confirm or Q to quit: y Lpsolit

‎Development Schedule

← Older revision Revision as of 00:57, 14 December 2025 Line 23: Line 23:  | 2025-12-05 | 2025-12-05  | developers, packagers | developers, packagers −|  +| 2025-12-09  |- |-  | Versions freeze | Versions freeze Bcornec

‎Various software

← Older revision Revision as of 18:03, 13 December 2025 (One intermediate revision by the same user not shown)Line 197: Line 197:     === Various software === === Various software ===  +  +{{Bug|34634}} - '''CodeBlocks:''' For now, we had to disable the wxSmith plugin.     === External software === === External software === Morgano

‎Various software: CodeBlocks is finally back.

← Older revision Revision as of 17:49, 13 December 2025 Line 348: Line 348:  '''FIXED BY [https://advisories.mageia.org/MGAA-2023-0077.html UPDATE]:''' September 2023: now support ext4 feature C12. {{Bug|32136}} - '''fsarchiver''' do not handle [[#ext4_feature_C12_is_not_recognized_by_older_fsck|the new ext4 version]] which some distros and future Mageia use. (And Mageia 9 did for installs up to beta2.)  Same problem for '''qt-fsarchiver / qt-fsarchiver-terminal''', with the twist that qt-fsarchiver seem not maintained upstream. Problems concern ''making'' backups - it works to restore an old backup regardless of the format on the target partition, as any fsarchiver reformats the partition per that backup. Also, '''qt-fsarchiver'''have some quirks: needs sudo, and asks an extra time for user password - ''Details: see bugs.'' Tip: Add yourself to the wheel group. '''FIXED BY [https://advisories.mageia.org/MGAA-2023-0077.html UPDATE]:''' September 2023: now support ext4 feature C12. {{Bug|32136}} - '''fsarchiver''' do not handle [[#ext4_feature_C12_is_not_recognized_by_older_fsck|the new ext4 version]] which some distros and future Mageia use. (And Mageia 9 did for installs up to beta2.)  Same problem for '''qt-fsarchiver / qt-fsarchiver-terminal''', with the twist that qt-fsarchiver seem not maintained upstream. Problems concern ''making'' backups - it works to restore an old backup regardless of the format on the target partition, as any fsarchiver reformats the partition per that backup. Also, '''qt-fsarchiver'''have some quirks: needs sudo, and asks an extra time for user password - ''Details: see bugs.'' Tip: Add yourself to the wheel group.    −{{Bug|32262}} - '''CodeBlocks''' was removed from Mageia 9 by accident, will be back.+'''FIXED BY UPDATE''' {{Bug|32262}} - '''CodeBlocks''' got missing at Mageia 9 release by accident, but is now in updates repository. If you need avr-gcc like in Mageia 8, you need to provide a solution yourself.     {{Bug|32278}} - '''pdfmod crashes''' when opening some .pdf files. Upstream development is dead. Please use another software such as packaged {{prog|pdfarranger}}. {{Bug|32278}} - '''pdfmod crashes''' when opening some .pdf files. Upstream development is dead. Please use another software such as packaged {{prog|pdfarranger}}. Line 354: Line 354:  '''FIXED BY [https://advisories.mageia.org/MGAA-2024-0074.html UPDATE]:''' {{Bug|32467}} - '''Waydroid''' not was working on mageia 9 an update fixing the issues was published on 27/Feb/2024, take care of get the right lxc version see bug 32687 on lxc here below!  For kernels before 6.6.14 you need dkms-anbox plus manual actions described in the bugs. For kernels 6.6.14 *avoid* dkms-anbox! Is no longer needed - see bug 32797 here below. '''FIXED BY [https://advisories.mageia.org/MGAA-2024-0074.html UPDATE]:''' {{Bug|32467}} - '''Waydroid''' not was working on mageia 9 an update fixing the issues was published on 27/Feb/2024, take care of get the right lxc version see bug 32687 on lxc here below!  For kernels before 6.6.14 you need dkms-anbox plus manual actions described in the bugs. For kernels 6.6.14 *avoid* dkms-anbox! Is no longer needed - see bug 32797 here below.    −'''FIXED BY UPDATE''' of {{Bug|32525}} (fontconfig) : '''Font rendering in i.e PDF preview in Firefox and Thunderbird''' displays bad for some PDF documents not embedding standard fonts.  ''Workaround in Firefox before shipped fix: in the address field type "about:config", and in search field enter "browser.display.use_document_fonts", change value "1" to "0".''+'''FIXED BY UPDATE''' {{Bug|32525}} (fontconfig) : '''Font rendering in i.e PDF preview in Firefox and Thunderbird''' displays bad for some PDF documents not embedding standard fonts.  ''Workaround in Firefox before shipped fix: in the address field type "about:config", and in search field enter "browser.display.use_document_fonts", change value "1" to "0".''     {{Bug|32636}} - '''Bitmap fonts broken''' by fontconfig update {{bug|32525}}. {{Bug|32636}} - '''Bitmap fonts broken''' by fontconfig update {{bug|32525}}. Morgano

‎Nextcloud: is back :-)

← Older revision Revision as of 09:00, 13 December 2025 Line 449: Line 449:  ==== Nextcloud ==== ==== Nextcloud ====    −See [[Nextcloud]]+In Mageia 10 we brought [[Nextcloud|Nextcloud server]] back, as well as the [[Nextcloud-client|Nextcloud client]].     ==== Veyon ==== ==== Veyon ==== Morgano

‎All other active iso-testers:: Removing seperate section for Bugsquad

← Older revision Revision as of 11:08, 12 December 2025 Line 50: Line 50:     =='''All other active iso-testers:'''== =='''All other active iso-testers:'''== −Adding a separate list for BugSquad iso-testers, because BugSquad needs its members so very badly that avoiding the slightest impression that they're a member of QA team seems needed.<br>  −--[[User:Marja|marja]] 06:30, 9 February 2016 (UTC)     −==='''For BugSquad:'''===  −Some are already listed as QA team member or team leader of some involved teams.   −If no one else steps forward, then this section will be removed.      ==='''For Qa team:'''=== ==='''For Qa team:'''=== Marja

‎Mageia Nextcloud package: Is in Cauldron for Mga10 at alpha1

← Older revision Revision as of 16:34, 11 December 2025 Line 45: Line 45:  '''Mageia 8:''' We intended to introduce Nextcloud 21 in Mageia 8 backports, but unfortunately we failed that {{bug|28511}}. '''Mageia 8:''' We intended to introduce Nextcloud 21 in Mageia 8 backports, but unfortunately we failed that {{bug|28511}}.    −'''Mageia 9:''' We thought maybe we will have fresh versions in backport. Still not 2024 December and not in Cauldron.+'''Mageia 9:''' Still not in 2025 December. Abandoned, {{Bug|31762}}.  +   +'''Mageia 10:''' '''Reintroduced.''' ''December 2025 Nextcloud server is of current version in Cauldron.''     ==== Past and current problems ==== ==== Past and current problems ==== Morgano

‎Mageia packaging: Updated for current status and Mageia 10

← Older revision Revision as of 16:12, 11 December 2025 Line 10: Line 10:  == Mageia packaging == == Mageia packaging ==    −=== Mageia problem ===+=== Mageia 9 problem ===    −Currently beginning December 2024 we have problems updating it ({{Bug|33697}}).+Since December 2024 we have problems updating it ({{Bug|33697}}). −# It do not compile on Mageia 9 due to that the Qt6 stack need be updated first, which may not happen.  −# We have no maintainer for it.     −So for now use [[#Using_upstream_official_AppImage|upstream official AppImage]]!+Newer versions do not compile on Mageia 9 due to that the Qt6 stack need be updated first, which will not happen in Mageia 9 due to other constraints.  +   +So on Mageia 9 use [[#Using_upstream_official_AppImage|upstream official AppImage]]!     === Mageia packages === === Mageia packages === −''Kept for reference, if we supply packages for Mageia 10 or later.''+(At Mageia 9 release, and in Mageia 10)     Basic: Basic: Line 26: Line 26:       nextcloud-client      nextcloud-client  Optional integrations to file managers: Optional integrations to file managers: −     nextcloud-client-caja-3.13.4-1.mga9.x86_64.rpm+     nextcloud-client-caja −     nextcloud-client-dolphin-3.13.4-1.mga9.x86_64.rpm+     nextcloud-client-dolphin −     nextcloud-client-nautilus-3.13.4-1.mga9.x86_64.rpm+     nextcloud-client-nautilus −     nextcloud-client-nemo-3.13.4-1.mga9.x86_64.rpm+     nextcloud-client-nemo     === Usage === === Usage === Line 38: Line 38:     <br> <br> −      == Using upstream official AppImage == == Using upstream official AppImage == Morgano

← Older revision Revision as of 11:49, 11 December 2025 Line 168: Line 168:  | Kingdom Come Delivrance | Kingdom Come Delivrance  | werkt erg goed met Heroic Game Launcher en Proton-GE-proton10-17 | werkt erg goed met Heroic Game Launcher en Proton-GE-proton10-17  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Limbo  +| werkt heel goed met Heroic Game Launcher en Proton-GE-Proton 10-17  +Environment variable : PROTON_USE_WINED3D=1     |- |- Scroll44

← Older revision Revision as of 11:47, 11 December 2025 Line 165: Line 165:  | Kingdom Come Delivrance | Kingdom Come Delivrance  | works very well with Heroic Game Launcher and Proton-GE-proton10-17. | works very well with Heroic Game Launcher and Proton-GE-proton10-17.  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Limbo  +| works very well with Heroic Game Launcher and Proton-GE-Proton 10-17  +Environment variable : PROTON_USE_WINED3D=1     |- |- Scroll44

← Older revision Revision as of 11:46, 11 December 2025 Line 164: Line 164:  | Kingdom Come Delivrance | Kingdom Come Delivrance  | marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17 | marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Limbo  +| marche très bien avec Heroic Game Launcher and Proton-GE-Proton 10.17  +Variable d’environnement : PROTON_USE_WINED3D=1     |- |- Scroll44

← Older revision Revision as of 10:31, 11 December 2025 Line 110: Line 110:     [[User:Nikos5446]] [[User:Nikos5446]]  +  +----  +[[User:Morgano|morgano]] ([[User talk:Morgano|talk]]) 10:31, 11 December 2025 (UTC)  +  +Thanks.  +  +I believe the benefit comes from restricting the programs to write to the USB - writing is the slowest bottleneck, especially with some USB.  +(I guess it will also speed up Firefox a bit on old slow spinning disc computers.)  +  +If you can come up with a trick to enable users to i.e save files from Firefox, it would be a great addition to that tip :-) Morgano

added name

← Older revision Revision as of 09:15, 11 December 2025 Line 106: Line 106:     Unfortunately, time is a luxury I don't have either. Unfortunately, time is a luxury I don't have either.  +  +I just added the tip about firejail.  +  +[[User:Nikos5446]] Nikos5446

‎Tips: firejail

← Older revision Revision as of 09:13, 11 December 2025 Line 468: Line 468:  * Use a lightweight desktop such as Xfce, or one of our even lighter desktops - IceWM is installed in all Lives already. ''Note that you can have several desktops installed and choose at each login which to use.'' * Use a lightweight desktop such as Xfce, or one of our even lighter desktops - IceWM is installed in all Lives already. ''Note that you can have several desktops installed and choose at each login which to use.''  * Use light weight programs. i.e Falkon for web browsing, and Gwenview for browsing-cropping-resizing photos. ''(Even Xfce by default use the heavy Firefox and Gimp, respectively)'' * Use light weight programs. i.e Falkon for web browsing, and Gwenview for browsing-cropping-resizing photos. ''(Even Xfce by default use the heavy Firefox and Gimp, respectively)''  +* If you have more than 2GBs of RAM available in your old computer, you could install firejail to run certain programs on the RAM. It is significantly faster than the USB stick (especially USB 2.0). But it also means that you will not be able to save almost anything. The following have been tested with lightweight window managers.  + Example commands:  + firejail --private falkon  + firejail --private firefox  + firejail --private --appimage ~/apps/librewolf/LibreWolf.x86_64.AppImage     == Caution == == Caution == Nikos5446

tested

← Older revision Revision as of 09:09, 11 December 2025 Line 97: Line 97:     Also, by now, I think we now can remove the stuff that is elder than Mageia 8, like suggested by sturmvogel earlier, see top post above. Also, by now, I think we now can remove the stuff that is elder than Mageia 8, like suggested by sturmvogel earlier, see top post above.  +  +----  +  +It will save you a lot of waiting and freezing.  +For example, opening a youtube page will certainly lead to freezing when using the standard method, in my live system (USB 2.0 connection).  +But when having everything working on the RAM, I can actually watch youtube videos.  +I have only tested this with lightweight window managers.  +  +Unfortunately, time is a luxury I don't have either. Nikos5446

← Older revision Revision as of 17:59, 10 December 2025 Line 163: Line 163:  | Invincible Presents: Atom Eve   | Invincible Presents: Atom Eve    | werkt heel goed met Heroic Game Launcher en Proton-GE-Proton 8.32 | werkt heel goed met Heroic Game Launcher en Proton-GE-Proton 8.32  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Kingdom Come Delivrance  +| werkt erg goed met Heroic Game Launcher en Proton-GE-proton10-17     |- |- Scroll44

← Older revision Revision as of 17:57, 10 December 2025 Line 160: Line 160:  | Invincible Presents: Atom Eve   | Invincible Presents: Atom Eve    | works very well with Heroic Game Launcher and Proton-GE-Proton 8.32 | works very well with Heroic Game Launcher and Proton-GE-Proton 8.32  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Kingdom Come Delivrance  +| works very well with Heroic Game Launcher and Proton-GE-proton10-17.     |- |- Scroll44

← Older revision Revision as of 17:56, 10 December 2025 (One intermediate revision by the same user not shown)Line 159: Line 159:  | Invincible Presents: Atom Eve   | Invincible Presents: Atom Eve    | marche très bien avec Heroic Game Launcher and Proton-GE-Proton 8.32   | marche très bien avec Heroic Game Launcher and Proton-GE-Proton 8.32    +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Kingdom Come Delivrance  +| marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17     |- |- Scroll44

Updated LO bugtracker, minor fixes

← Older revision Revision as of 16:21, 10 December 2025 Line 113: Line 113:  If sufficient information has not yet been provided, you should add the '''NEEDINFO''' status to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information. If sufficient information has not yet been provided, you should add the '''NEEDINFO''' status to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information.    −===Commands that give much information about a user's system===+=== Commands that give much information about a user's system ===     {{command|lspcidrake -v}} {{command|lspcidrake -v}} Line 182: Line 182:  === Printer problems === === Printer problems ===    −==== detection ====+==== Detection ====     If there are problems with pluggable hardware which does not work correctly or is not recognized properly/at all, the needed information can be shown via the following procedure: Open a terminal before you plug in the printer, as root run the following command: If there are problems with pluggable hardware which does not work correctly or is not recognized properly/at all, the needed information can be shown via the following procedure: Open a terminal before you plug in the printer, as root run the following command: Line 205: Line 205:  ** http://foo2qpdl.rkkda.com/ ** http://foo2qpdl.rkkda.com/    −==== all other issues ====+==== All other issues ====     Ask for the output of {{code|rpm -qa cups}} and of {{code|systemctl status cups.service cups.socket -al -n50}} Ask for the output of {{code|rpm -qa cups}} and of {{code|systemctl status cups.service cups.socket -al -n50}} Line 395: Line 395:     Current keywords can be found [https://bugs.mageia.org/describekeywords.cgi here] Current keywords can be found [https://bugs.mageia.org/describekeywords.cgi here] −At least some of our Whitboard strings should become keywords, see also [https://bugs.mageia.org/show_bug.cgi?id=19637 bug 19637]+At least some of our Whiteboard strings should become keywords, see also [https://bugs.mageia.org/show_bug.cgi?id=19637 bug 19637]       Line 426: Line 426:  * [https://bugs.mageia.org/show_bug.cgi?id=16620#c74 about non-seeming-duplicates being duplicates] * [https://bugs.mageia.org/show_bug.cgi?id=16620#c74 about non-seeming-duplicates being duplicates]    −== Need discuss ==+== Need discussion ==     What must we do with: What must we do with: Line 440: Line 440:  * [http://bugzilla.gnome.org GNOME Bugzilla] * [http://bugzilla.gnome.org GNOME Bugzilla]  * [http://bugzilla.mozilla.org Mozilla Bugzilla] (Firefox, Thunderbird, Seamonkey) * [http://bugzilla.mozilla.org Mozilla Bugzilla] (Firefox, Thunderbird, Seamonkey) −* [https://bugs.freedesktop.org LibreOffice] (by selecting the LibreOffice Component)+* [https://bugs.documentfoundation.org/ LibreOffice]  * [https://bugs.freedesktop.org/ Freedesktop.org Bugzilla] * [https://bugs.freedesktop.org/ Freedesktop.org Bugzilla]  * [https://rt.cpan.org/Public/ Cpan /Perl Bug Tracker] * [https://rt.cpan.org/Public/ Cpan /Perl Bug Tracker] Morgano

‎Whiteboard:: Remove strings that already became keywords for Mageia 9 and later

← Older revision Revision as of 11:16, 10 December 2025 (4 intermediate revisions by the same user not shown)Line 93: Line 93:  === Thirdly, is the bug filed on a supported release? === === Thirdly, is the bug filed on a supported release? ===    −If the Mageia release on which the bug is filed is no longer supported, add the '''NEEDINFO''' keyword and ask the reporter for testing if it's still valid with the latest cauldron or any still supported products.+If the Mageia release on which the bug is filed is no longer supported, set the report to the "NEEDINFO" status and ask the reporter for testing if it's still valid with the latest cauldron or any still supported products.  Ping him if he doesn't reply within two weeks. If he doesn't reply within another two weeks, you can set it to the '''RESOLVED OLD''' resolution with a comment explaining the reason. This doesn't apply to enhancement requests as most of them should be set to '''Cauldron''' version (modify version field if needed). Ping him if he doesn't reply within two weeks. If he doesn't reply within another two weeks, you can set it to the '''RESOLVED OLD''' resolution with a comment explaining the reason. This doesn't apply to enhancement requests as most of them should be set to '''Cauldron''' version (modify version field if needed).    Line 111: Line 111:  A very good way to check whether all necessary information has been provided is to see whether you can reproduce the issue yourself using the information provided in the bug report. Triage team members are advised to keep copies of all currently supported Mageia releases available to help with this. You may want to consider using VirtualBox, VMware, qemu... etc for this purpose. A very good way to check whether all necessary information has been provided is to see whether you can reproduce the issue yourself using the information provided in the bug report. Triage team members are advised to keep copies of all currently supported Mageia releases available to help with this. You may want to consider using VirtualBox, VMware, qemu... etc for this purpose.    −If sufficient information has not yet been provided, you should add the '''NEEDINFO''' keyword to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information.+If sufficient information has not yet been provided, you should add the '''NEEDINFO''' status to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information.  +   +===Commands that give much information about a user's system===  +   +{{command|lspcidrake -v}}  +   +In Mageia 9: {{command|inxi -F}}  +In Mageia 10 and later: {{command|inxi -e}}     == Special cases of specific information required == == Special cases of specific information required == Line 384: Line 391:     see [[Becoming a Mageia Packager]] see [[Becoming a Mageia Packager]]  +  +== Keywords ==  +  +Current keywords can be found [https://bugs.mageia.org/describekeywords.cgi here]  +At least some of our Whitboard strings should become keywords, see also [https://bugs.mageia.org/show_bug.cgi?id=19637 bug 19637]  +     == Whiteboard: == == Whiteboard: ==    −* FOR_ERRATA7 : needs to be added to the [[Mageia 7 Errata]] page.+  −* IN_ERRATA7 : has been added to the [[Mageia 7 Errata]] page.  −* FOR_RELNOTES7: to be added to the [[Mageia 7 Release Notes]] page.  −* IN_RELNOTES7: has been added to the [[Mageia 7 Release Notes]] page.  −* FOR_ERRATA6 : needs to be added to the [[Mageia 6 Errata]] page.  −* IN_ERRATA6 : has been added to the [[Mageia 6 Errata]] page.   * check : for bug to close * check : for bug to close  * cauldron : for package requests, when the package already exists in cauldron - also for when the cauldron version of a package is requested to be backported for stable * cauldron : for package requests, when the package already exists in cauldron - also for when the cauldron version of a package is requested to be backported for stable Marja