Lector de Feeds

← 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

← Older revision Revision as of 08:31, 10 December 2025 Line 84: Line 84:     [[User:Nikos5446]] [[User:Nikos5446]]  +  +----  +[[User:Morgano|morgano]] ([[User talk:Morgano|talk]]) 08:31, 10 December 2025 (UTC)  +  +Thank you for the tip Nikos.  +  +But are you sure it really is noticeably faster?  It need to load the program from the USB anyway.  +  +I guess(have not tested) you need more than 2GB RAM for this method to work nicely, especially with a non minimalistic DE (think Plasma) and hungry program like Firefox?  +  +BTW, if you want to update or improve the page, please go ahead :)  I do not have much time anymore.  Just make sure you test things first :)  +  +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. Morgano

firejail

← Older revision Revision as of 08:16, 10 December 2025 Line 72: Line 72:     One big advantage with Live is that if the updates or settings foul up (been there), (i.e by glitchy connector) you can boot without the persistence. One big advantage with Live is that if the updates or settings foul up (been there), (i.e by glitchy connector) you can boot without the persistence.  +  +----  +  +We could add the following in the "Tips" section:  +  +- 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.  +  Example commands:  + "firejail --private falkon"  + "firejail --private firefox"  + "firejail --private --appimage ~/apps/librewolf/LibreWolf.x86_64.AppImage"  +  +[[User:Nikos5446]] Nikos5446