Lector de Feeds

‎Firefox ESR: #33812 30 bit colour depth

← Older revision Revision as of 20:35, 8 January 2025 Line 272: Line 272:     === Firefox ESR === === Firefox ESR ===  +  +{{Bug|33812}} - Problem with 30 bit colour depth. ''(Note that to encounter this problem, you need to have manually increased colour depth from 24 to 30 in xorg.conf, see bug.)''  Upstream. '''WORKAROUND''':  force hardware acceleration by setting: ''gfx.webrender.all = true'', when starting Firefox.     '''A few sites choose to not accept Firefox ESR''' (even upstream version), and demand non-ESR version.  Please help informing the problematic sites that [https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Firefox ESR does not come with the latest features but it has the latest security and stability fixes].  '''Workarounds: 1.)''' try using a user-agent switcher to spoof a non-ESR Firefox.  '''2.)''' install the Firefox non-ESR version for example by using [[Flatpak]] or other [[Ways_to_install_programs|Ways to install programs]]. '''3.)''' Use another browser. '''A few sites choose to not accept Firefox ESR''' (even upstream version), and demand non-ESR version.  Please help informing the problematic sites that [https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Firefox ESR does not come with the latest features but it has the latest security and stability fixes].  '''Workarounds: 1.)''' try using a user-agent switcher to spoof a non-ESR Firefox.  '''2.)''' install the Firefox non-ESR version for example by using [[Flatpak]] or other [[Ways_to_install_programs|Ways to install programs]]. '''3.)''' Use another browser. Morgano

Xgrind moved page Como pedir ajudar-pt-BR to Como pedir ajuda-pt-BR

New page

[[Category:Documentation]]
[[Category:Howtos]]

{{multi language banner-pt-BR|[[Wie_man_um_Hilfe_fragt-de|Deutsch]]; [[How_to_ask_for_help|English]]; [[Comment_demander_de_l'aide-fr|Francais]] ; [[Hoe vraag ik hulp-nl|Nederlands]] ; [[Como pedir ajuda-pt-BR|português brasileiro]] ; }}

{{introduction-pt-BR|O Linux é um sistema operacional muito complexo, e até mesmo aqueles de nós que usamos/ajudamos a suportar o Unix e o Linux há muitos anos têm dificuldades em identificar um problema, com base apenas na descrição básica de um problema.
Para evitar perder tempo e manter a compostura, é importante seguir algumas regras antes de pedir ajuda no fórum ou nas listas de discussão. Aqui estão algumas sugestões.<br />
Se você não souber nada sobre a linha de comando, pode começar lendo [[Primeiros_passos_com_a_linha_de_comando_e_exemplos_úteis-pt-BR|esta página]].}}

== Diagnosticar o problema ==

=== Primeiro, colete as informações ===

Se o software travar ou não agir como esperado, mantenha a calma e use sua mente. Abra seu processador de texto favorito e crie um novo documento chamado "Relatório" e anote o que você estava fazendo quando o problema ocorreu e todas as mensagens de erro. Essas mensagens devem ser copiadas exatamente como foram fornecidas pelo sistema. Se possível, use a ferramenta de copiar/colar. Em um terminal, você pode precisar usar o menu {{menu-pt-BR|Editar/Copiar}}.

Se o sistema travar antes do término da inicialização, pressione a tecla <Escape>, assim, verá mensagens detalhadas em vez do gráfico da tela de inicialização. Depois, copie as últimas mensagens antes do travamento para o relatório.

Se a inicialização for concluída sem problemas, aguarde o problema aparecer e, em seguida, em um terminal com privilégios de Root, digite {{cmd-pt-BR|tail /var/log/messages}}. Isso exibirá as últimas 10 linhas dos logs do sistema. Se você ver algumas linhas relacionadas ao seu problema, anote-as também no relatório.

Os erros de aplicativos gráficos geralmente estão no arquivo {{file-pt-BR|/home/<usuário>/.Xsession-errors}} ou {{file-pt-BR|/home/<usuário>/.xsession-errors}}. Não se esqueça do ponto antes do X, ou x, pois isso significa que o arquivo está oculto e você precisa permitir a visualização de arquivos ocultos no gerenciador de arquivos ({{menu-pt-BR|Visualizar/Mostrar arquivos ocultos}} no Dolphin, por exemplo). Então, as últimas 10 linhas dos logs podem ser vistas com o comando {{cmd-pt-BR|tail /home/<user>/.xsession-errors}}. Novamente, anote as linhas relacionadas ao seu problema.

Se alguma informação for encontrada nesses arquivos, execute o aplicativo a partir de um terminal (como o Konsole no KDE, por exemplo), e quando o bug ocorrer, algumas linhas relevantes podem aparecer.

{{Note-pt-BR|Quando for impossível usar ferramentas gráficas, uma interface de texto pode ser acessada pressionando Alt+Ctrl+F2. Volte à interface gráfica com Alt+Ctrl+F1.}}

=== É um problema conhecido? ===

Talvez o problema já tenha sido detectado pelas equipes do Mageia e uma solução alternativa esteja explicada nos avisos de lançamento. Por exemplo, [[Mageia_6_Errata| veja aqui]] para o Mageia 6.

Dê também uma olhada em [https://bugs.mageia.org Bugzilla]. Você pode não apenas obter ajuda aqui, mas também compartilhar sua experiência para contribuir com o reflexo do problema.

=== O problema é reproduzível? ===

Tente descobrir se o problema é facilmente reproduzível e qual é a maneira de fazê-lo aparecer. Proteja seus arquivos fazendo uma cópia de qualquer arquivo que possa ser afetado. Faça os testes em uma cópia dos dados, para evitar danos.

=== É um problema de hardware? ===

Problemas não reproduzíveis geralmente estão relacionados ao hardware. Se você acha que é o caso, veja os seguintes comandos:

==== Mageia 3 ou superior ====

Usa o systemd e, para mensagens de log, {{cmd-pt-BR|journalctl}} agora é a ferramenta certa. Aqui estão alguns exemplos:

{{command-pt-BR|journalctl -a}}
dá tudo, uma saída muito, muito grande. Use "espaço" para passar para a próxima página e "enter" para uma nova linha. Você pode escolher ver apenas as últimas 500 linhas, por exemplo, com
{{command-pt-BR|<nowiki>journalctl --lines=500 2>&1 | tee output.txt</nowiki>}}
isso cria no diretório atual um novo arquivo chamado {{file-pt-BR|output.txt}} que contém as últimas 500 linhas, você pode lê-lo com qualquer editor de texto.

{{command-pt-BR|journalctl -f}}
mostra as últimas linhas e adiciona novas linhas para novos registros.

{{command-pt-BR|journalctl -h}}
mostra um help curto.

=== Leia a documentação do software ===

Se um software parece não reagir corretamente, procure e leia sua documentação na Internet ou nas páginas de manual (em um terminal, digite {{cmd-pt-BR|man nome_do_programa}}), caso contrário, você pode receber uma resposta como "RTFM" (Leia o maldito manual).

{{pre-pt-BR|Leia o maldito manual!}}

=== Pesquise a mensagem de erro na Internet ===

Copie/cole a mensagem de erro em um motor de busca (como Ixquick ou Google) e adicione o nome do programa. Você certamente encontrará mensagens de fórum de pessoas com o mesmo problema. Leia o tópico completo, você pode encontrar uma solução.

=== Reúna mais informações sobre o problema ===

Se, após isso, você tem uma ideia sobre o problema, pode querer investigar mais. Os seguintes comandos podem ajudar a buscar mais informações sobre o sistema e o problema.

* {{cmd-pt-BR|lspcidrake -v}} para listar o hardware
* {{cmd-pt-BR|lsusb}} (com privilégios de Root) para listar os dispositivos USB
* {{cmd-pt-BR|cat /proc/cpuinfo}} para ver as características do processador
* {{cmd-pt-BR|free -m}} para saber a carga de memória

Aqui estão outros comandos úteis (com privilégios de Root):
* {{cmd-pt-BR|lsmod}} lista os módulos que foram carregados automaticamente em resposta à detecção de dispositivos pelo kernel
* {{cmd-pt-BR|modinfo modulenamefromlsmod}} lista detalhes de um módulo
* {{cmd|dmesg}} this lists recent kernel and system messages, including failure to load or identify a bit of hardware.
* {{cmd|ethtool}} a command to list lots of info about network
* {{cmd|ethtool -I eth0}} will list the version and details of your nic.
* {{cmd|ethtool -S eth0}} will list just about every counter related to an Ethernet card.
* {{cmd|dmidecode}} equivalent to MS system info gives lots of info about your hardware.
* {{cmd|rpm –qa}} will list all packages on a system, pipe it through grep to reduce this to relevant packages.
* {{cmd|ifconfig -a}} lists the tcpip settings set on your network cards.
* Linux more often will тще label each ethernet card eth0, eth1, eth2, eth3 in the order it finds them so if you have more that one network card check out the rest.

In Mageia 3 you will have a new tool called {{prog|inxi}} (you have to install the package), here are the main commands :
* {{cmd|inxi -F}} to have generalities
* {{cmd|inxi -n }}to provide the network card only
* {{cmd|inxi -uo}} the mounted and unmountend partitions only
* {{cmd|inxi -xG}} the graphic card
* {{cmd|inxi -t m5}} to have a snapshot of your 5 biggest memory users
* {{cmd|inxi -t c5}} to have a snapshot of your 5 biggest CPU users

Also, have a look on the directory {{file|/etc/sysconfig}} where many config files live, relating to network services etc, and in the config file for the Xdisplay server: {{file|/etc/X11/xorg.conf}}

=== Now, ask for help ===

If you haven't found a solution to the problem, it is time to ask help on the Mageia forum. Keep in mind that you will meet users like yourself. They aren't paid nor indemnified to answer your questions, they will try to help you find a solution on their personal time and they deserve respect and patience.

== Getting help ==

=== First, become familiar with the Mageia Forum ===

Subscribe to the [https://forums.mageia.org/en/index.php?sid=fbd84849348393400dcef2a89c787064 Mageia forum] if not already done (Click on Register at the top right). Read the [https://www.mageia.org/en/about/code-of-conduct/ rules], you can also have a look at the FAQ.

It is important to follow the [https://wiki.mageia.org/en/Forum_Rules rules] if you want to get answers.

If you prefer another language than English, forums about Mageia exist in several languages. [https://forums.mageia.org/en/viewforum.php?f=20 Make your choice], there is also a [https://forum.mageia.org/de/ German forum]

=== Don't be off-topic ===

Find the right sub-forum, the one which matches the problem. Don't post your message in several sub-forums, it is bad form to do that.

=== Choose a descriptive title ===

Don't write a general title such as "Help needed" or "I got a problem". It doesn't encourage members to read the post. The title should describe the problem in a concise way, so any reader who knows something about this problem will be inclined to read the entire message and post an answer.

Be as precise as possible, for example, "Impossible to get an IP address" is better than "Internet isn't working".

=== Give information ===

In the message text, give the distribution name, version and architecture you are using (eg: Mageia 2 i586); the program name and version that seems to be the problem; and if necessary, a short listing of hardware information ( eg: HP DC5000). Copy the error messages you may have collected in the report file (the file created at the beginning of this page), always in code tags, which makes your post(s) easier to read & will avoid a comment from the etiquette police. Screenshots can be helpful to show some errors. Describe exactly what you have done just before the problem arises and what you have done to attempt to solve it and the obtained results.

Once you have answers, post the information, files, etc.

=== No SMS (text speak) language ===

It's ambiguous & confusing! Nobody will read your message.

=== Don't miss an opportunity to learn ===

Don't follow any advice blindly, try to understand and learn something. If you are asked to use some command in a console, or to post a file; read the manual pages to discover what the purpose of this command or file (if any). Write somewhere (in a copybook or email to yourself) the problem, all the actions you are trying to resolve the problem and the results obtained, so :
* you will be able to give accurate information to your helpers in the forum
* you will know what to do if the problem arises again, after a re-installation for example, without wasting time or disturbing people
* you will be able, to help others people with a similar problem.

=== Say Hello and Thank You ===

Free Software is mainly based on the community. By Mageia, all the people are volunteers and they freely help other people to promote the Free Software and because they been helped themselves, '''we are all part of the FOSS [free open source software] community'''.

Here are the Mageia community [http://www.mageia.org/en/about/code-of-conduct/ code of conduct] :
* Be considerate,
* Be respectful,
* Be collaborative,
* Be pragmatic,
* Support others in the community,
* Get support from others in the community. Xgrind

Criando a página Como pedir ajuda-pt-BR

New page

[[Category:Documentation]]
[[Category:Howtos]]

{{multi language banner-pt-BR|[[Wie_man_um_Hilfe_fragt-de|Deutsch]]; [[How_to_ask_for_help|English]]; [[Comment_demander_de_l'aide-fr|Francais]] ; [[Hoe vraag ik hulp-nl|Nederlands]] ; [[Como pedir ajuda-pt-BR|português brasileiro]] ; }}

{{introduction-pt-BR|O Linux é um sistema operacional muito complexo, e até mesmo aqueles de nós que usamos/ajudamos a suportar o Unix e o Linux há muitos anos têm dificuldades em identificar um problema, com base apenas na descrição básica de um problema.
Para evitar perder tempo e manter a compostura, é importante seguir algumas regras antes de pedir ajuda no fórum ou nas listas de discussão. Aqui estão algumas sugestões.<br />
Se você não souber nada sobre a linha de comando, pode começar lendo [[Primeiros_passos_com_a_linha_de_comando_e_exemplos_úteis-pt-BR|esta página]].}}

== Diagnosticar o problema ==

=== Primeiro, colete as informações ===

Se o software travar ou não agir como esperado, mantenha a calma e use sua mente. Abra seu processador de texto favorito e crie um novo documento chamado "Relatório" e anote o que você estava fazendo quando o problema ocorreu e todas as mensagens de erro. Essas mensagens devem ser copiadas exatamente como foram fornecidas pelo sistema. Se possível, use a ferramenta de copiar/colar. Em um terminal, você pode precisar usar o menu {{menu-pt-BR|Editar/Copiar}}.

Se o sistema travar antes do término da inicialização, pressione a tecla <Escape>, assim, verá mensagens detalhadas em vez do gráfico da tela de inicialização. Depois, copie as últimas mensagens antes do travamento para o relatório.

Se a inicialização for concluída sem problemas, aguarde o problema aparecer e, em seguida, em um terminal com privilégios de Root, digite {{cmd-pt-BR|tail /var/log/messages}}. Isso exibirá as últimas 10 linhas dos logs do sistema. Se você ver algumas linhas relacionadas ao seu problema, anote-as também no relatório.

Os erros de aplicativos gráficos geralmente estão no arquivo {{file-pt-BR|/home/<usuário>/.Xsession-errors}} ou {{file-pt-BR|/home/<usuário>/.xsession-errors}}. Não se esqueça do ponto antes do X, ou x, pois isso significa que o arquivo está oculto e você precisa permitir a visualização de arquivos ocultos no gerenciador de arquivos ({{menu-pt-BR|Visualizar/Mostrar arquivos ocultos}} no Dolphin, por exemplo). Então, as últimas 10 linhas dos logs podem ser vistas com o comando {{cmd-pt-BR|tail /home/<user>/.xsession-errors}}. Novamente, anote as linhas relacionadas ao seu problema.

Se alguma informação for encontrada nesses arquivos, execute o aplicativo a partir de um terminal (como o Konsole no KDE, por exemplo), e quando o bug ocorrer, algumas linhas relevantes podem aparecer.

{{Note-pt-BR|Quando for impossível usar ferramentas gráficas, uma interface de texto pode ser acessada pressionando Alt+Ctrl+F2. Volte à interface gráfica com Alt+Ctrl+F1.}}

=== É um problema conhecido? ===

Talvez o problema já tenha sido detectado pelas equipes do Mageia e uma solução alternativa esteja explicada nos avisos de lançamento. Por exemplo, [[Mageia_6_Errata| veja aqui]] para o Mageia 6.

Dê também uma olhada em [https://bugs.mageia.org Bugzilla]. Você pode não apenas obter ajuda aqui, mas também compartilhar sua experiência para contribuir com o reflexo do problema.

=== O problema é reproduzível? ===

Tente descobrir se o problema é facilmente reproduzível e qual é a maneira de fazê-lo aparecer. Proteja seus arquivos fazendo uma cópia de qualquer arquivo que possa ser afetado. Faça os testes em uma cópia dos dados, para evitar danos.

=== É um problema de hardware? ===

Problemas não reproduzíveis geralmente estão relacionados ao hardware. Se você acha que é o caso, veja os seguintes comandos:

==== Mageia 3 ou superior ====

Usa o systemd e, para mensagens de log, {{cmd-pt-BR|journalctl}} agora é a ferramenta certa. Aqui estão alguns exemplos:

{{command-pt-BR|journalctl -a}}
dá tudo, uma saída muito, muito grande. Use "espaço" para passar para a próxima página e "enter" para uma nova linha. Você pode escolher ver apenas as últimas 500 linhas, por exemplo, com
{{command-pt-BR|<nowiki>journalctl --lines=500 2>&1 | tee output.txt</nowiki>}}
isso cria no diretório atual um novo arquivo chamado {{file-pt-BR|output.txt}} que contém as últimas 500 linhas, você pode lê-lo com qualquer editor de texto.

{{command-pt-BR|journalctl -f}}
mostra as últimas linhas e adiciona novas linhas para novos registros.

{{command-pt-BR|journalctl -h}}
mostra um help curto.

=== Leia a documentação do software ===

Se um software parece não reagir corretamente, procure e leia sua documentação na Internet ou nas páginas de manual (em um terminal, digite {{cmd-pt-BR|man nome_do_programa}}), caso contrário, você pode receber uma resposta como "RTFM" (Leia o maldito manual).

{{pre-pt-BR|Leia o maldito manual!}}

=== Pesquise a mensagem de erro na Internet ===

Copie/cole a mensagem de erro em um motor de busca (como Ixquick ou Google) e adicione o nome do programa. Você certamente encontrará mensagens de fórum de pessoas com o mesmo problema. Leia o tópico completo, você pode encontrar uma solução.

=== Reúna mais informações sobre o problema ===

Se, após isso, você tem uma ideia sobre o problema, pode querer investigar mais. Os seguintes comandos podem ajudar a buscar mais informações sobre o sistema e o problema.

* {{cmd-pt-BR|lspcidrake -v}} para listar o hardware
* {{cmd-pt-BR|lsusb}} (com privilégios de Root) para listar os dispositivos USB
* {{cmd-pt-BR|cat /proc/cpuinfo}} para ver as características do processador
* {{cmd-pt-BR|free -m}} para saber a carga de memória

Aqui estão outros comandos úteis (com privilégios de Root):
* {{cmd-pt-BR|lsmod}} lista os módulos que foram carregados automaticamente em resposta à detecção de dispositivos pelo kernel
* {{cmd-pt-BR|modinfo modulenamefromlsmod}} lista detalhes de um módulo
* {{cmd|dmesg}} this lists recent kernel and system messages, including failure to load or identify a bit of hardware.
* {{cmd|ethtool}} a command to list lots of info about network
* {{cmd|ethtool -I eth0}} will list the version and details of your nic.
* {{cmd|ethtool -S eth0}} will list just about every counter related to an Ethernet card.
* {{cmd|dmidecode}} equivalent to MS system info gives lots of info about your hardware.
* {{cmd|rpm –qa}} will list all packages on a system, pipe it through grep to reduce this to relevant packages.
* {{cmd|ifconfig -a}} lists the tcpip settings set on your network cards.
* Linux more often will тще label each ethernet card eth0, eth1, eth2, eth3 in the order it finds them so if you have more that one network card check out the rest.

In Mageia 3 you will have a new tool called {{prog|inxi}} (you have to install the package), here are the main commands :
* {{cmd|inxi -F}} to have generalities
* {{cmd|inxi -n }}to provide the network card only
* {{cmd|inxi -uo}} the mounted and unmountend partitions only
* {{cmd|inxi -xG}} the graphic card
* {{cmd|inxi -t m5}} to have a snapshot of your 5 biggest memory users
* {{cmd|inxi -t c5}} to have a snapshot of your 5 biggest CPU users

Also, have a look on the directory {{file|/etc/sysconfig}} where many config files live, relating to network services etc, and in the config file for the Xdisplay server: {{file|/etc/X11/xorg.conf}}

=== Now, ask for help ===

If you haven't found a solution to the problem, it is time to ask help on the Mageia forum. Keep in mind that you will meet users like yourself. They aren't paid nor indemnified to answer your questions, they will try to help you find a solution on their personal time and they deserve respect and patience.

== Getting help ==

=== First, become familiar with the Mageia Forum ===

Subscribe to the [https://forums.mageia.org/en/index.php?sid=fbd84849348393400dcef2a89c787064 Mageia forum] if not already done (Click on Register at the top right). Read the [https://www.mageia.org/en/about/code-of-conduct/ rules], you can also have a look at the FAQ.

It is important to follow the [https://wiki.mageia.org/en/Forum_Rules rules] if you want to get answers.

If you prefer another language than English, forums about Mageia exist in several languages. [https://forums.mageia.org/en/viewforum.php?f=20 Make your choice], there is also a [https://forum.mageia.org/de/ German forum]

=== Don't be off-topic ===

Find the right sub-forum, the one which matches the problem. Don't post your message in several sub-forums, it is bad form to do that.

=== Choose a descriptive title ===

Don't write a general title such as "Help needed" or "I got a problem". It doesn't encourage members to read the post. The title should describe the problem in a concise way, so any reader who knows something about this problem will be inclined to read the entire message and post an answer.

Be as precise as possible, for example, "Impossible to get an IP address" is better than "Internet isn't working".

=== Give information ===

In the message text, give the distribution name, version and architecture you are using (eg: Mageia 2 i586); the program name and version that seems to be the problem; and if necessary, a short listing of hardware information ( eg: HP DC5000). Copy the error messages you may have collected in the report file (the file created at the beginning of this page), always in code tags, which makes your post(s) easier to read & will avoid a comment from the etiquette police. Screenshots can be helpful to show some errors. Describe exactly what you have done just before the problem arises and what you have done to attempt to solve it and the obtained results.

Once you have answers, post the information, files, etc.

=== No SMS (text speak) language ===

It's ambiguous & confusing! Nobody will read your message.

=== Don't miss an opportunity to learn ===

Don't follow any advice blindly, try to understand and learn something. If you are asked to use some command in a console, or to post a file; read the manual pages to discover what the purpose of this command or file (if any). Write somewhere (in a copybook or email to yourself) the problem, all the actions you are trying to resolve the problem and the results obtained, so :
* you will be able to give accurate information to your helpers in the forum
* you will know what to do if the problem arises again, after a re-installation for example, without wasting time or disturbing people
* you will be able, to help others people with a similar problem.

=== Say Hello and Thank You ===

Free Software is mainly based on the community. By Mageia, all the people are volunteers and they freely help other people to promote the Free Software and because they been helped themselves, '''we are all part of the FOSS [free open source software] community'''.

Here are the Mageia community [http://www.mageia.org/en/about/code-of-conduct/ code of conduct] :
* Be considerate,
* Be respectful,
* Be collaborative,
* Be pragmatic,
* Support others in the community,
* Get support from others in the community. Xgrind

Add pt-BR

← Older revision Revision as of 01:01, 8 January 2025 Line 2: Line 2:     {{TranslationOverview-nl|First_step_with_the_command_line_and_useful_examples|13/11/2023|60072}} {{TranslationOverview-nl|First_step_with_the_command_line_and_useful_examples|13/11/2023|60072}} −{{multi language banner-nl|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]]}}+{{multi language banner-nl|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]] ; [[Primeiros passos com a linha de comando e exemplos úteis-pt-BR|português brasileiro]] ;}}     {{introduction| {{introduction| Xgrind

Add pt-BR

← Older revision Revision as of 01:00, 8 January 2025 Line 1: Line 1:  [[Category:Documentation-fr]] [[Category:Documentation-fr]]    −{{Multi language banner-fr|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]]}}+{{Multi language banner-fr|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]] ; [[Primeiros passos com a linha de comando e exemplos úteis-pt-BR|português brasileiro]] ;}}     {{introduction-fr|Cette page est écrite à l’intention des débutants (notamment des personnes qui viennent de Windows) et traite de la ligne de commande. Le but de cette page n’est pas d’enseigner la gestion de l’ordinateur avec la ligne de commande, il y a beaucoup de pages à ce sujet sur Internet et dans ce wiki (voir [[#Liens|Liens]]). <br> {{introduction-fr|Cette page est écrite à l’intention des débutants (notamment des personnes qui viennent de Windows) et traite de la ligne de commande. Le but de cette page n’est pas d’enseigner la gestion de l’ordinateur avec la ligne de commande, il y a beaucoup de pages à ce sujet sur Internet et dans ce wiki (voir [[#Liens|Liens]]). <br> Xgrind

Add pt-BR

← Older revision Revision as of 01:00, 8 January 2025 Line 1: Line 1:  [[Category:Documentation]] [[Category:Documentation]]    −{{multi language banner|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]]}}+{{multi language banner|[[Erste_Schritte_mit_der_Konsole_und_nützliche_Beispiele-de|Deutsch]] ; [[First_step_with_the_command_line_and_useful_examples|English]] ; [[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr|français]] ; [[Eerste stappen met de tekstconsole met voorbeelden-nl|Nederlands]] ; [[Primeiros passos com a linha de comando e exemplos úteis-pt-BR|português brasileiro]] ;}}     {{introduction|This page is written with absolute beginners in mind (mostly those coming from Windows) and deals with the Command line. The goal of this page isn't to teach the computer management with command line, there is plenty of pages about it in the Internet and in this wiki.(see [[#Links|Links]])<br> {{introduction|This page is written with absolute beginners in mind (mostly those coming from Windows) and deals with the Command line. The goal of this page isn't to teach the computer management with command line, there is plenty of pages about it in the Internet and in this wiki.(see [[#Links|Links]])<br> Xgrind

New year, new blog post! Fedora's going great...41 came out and seems to be getting good reviews, there's exciting stuff going on with atomic/bootc, we're getting a new forge, it's an exciting time to be alive...

Personally I've spent a large chunk of the last few weeks bashing my head against two awkward bugs - one kernel bug, one systemd bug. It's a bit of a slog, but hey. Also now working up to our next big openQA project, extending test coverage for the new installer.

But also! I bought myself a new laptop. For the last couple of years I've been using a Dell XPS 13 9315, the Alder Lake generation. I've been using various generations of XPS 13 ever since Sony stopped making laptops (previously I used a 2010 Vaio Z) - I always found it to be the best thin-and-light design, and this one was definitely that. But over time it felt really underpowered. Some of this is the fault of modern apps. I have to run a dumb amount of modern chat apps, and while they're much nicer than IRC, they sure use a lot more resources than hexchat. Of course I have a browser with about 50 tabs open at all times, Evolution uses quite a lot of memory for my email setup for some reason, and I have to run VMs quite often for my work obviously. Put all that together, and...I was often running out of RAM despite having 16GB, which is pretty ridiculous. But even aside from that, you could tell the CPU was just struggling with everything. Just being in a video chat was hard work for it (if I switched apps too much while in a meeting, my audio would start chopping up for others on the call). Running more than two VMs tend to hang the system irretrievably. Just normal use often caused the fan to spin up pretty high. And the battery life wasn't great. It got better with kernel updates over time, but still only 3-4 hours probably.

So I figured I'd throw some hardware at the problem. I've been following all the chipset releases over the last couple of years, and decided I wanted to get something with AMD's latest silicon, codenamed "Strix Point", the Ryzen AI 3xx chips. They're not massively higher-performing than the previous gen, but the battery life seems to be improved, and they have somewhat better GPUs. That pretty much brought it down to the Asus Vivobook S 14, HP Omnibook Ultra 14, and Lenovo T14S gen 6 AMD. The Asus is stuck with 24GB of RAM max and I'm not a huge Asus fan in general, and the HP came in like $600 cheaper than the Thinkpad with equivalent specs, and had a 3 year warranty included. So I went with the HP, with 1TB of storage and 32GB of RAM.

I really like the system as a whole. It's heavier than the XPS 13, obviously, the bezels are a little bigger, and the screen is glossier. But the screen is pretty nice, I like the keyboard, and the overall build quality feels pretty solid. The trackpad seems fine.

As for running Fedora (and Linux in general) on it...well, it's almost great. Everything more or less works out of the box, except the fingerprint reader. I don't care about that because I set up the reader on the XPS 13 and kinda hated it; it's nowhere near as nice as a fingerprint reader on a phone. Even if it worked on the HP I'd leave it off. The performance is fantastic (except that Google office sites perform weirdly terribly on Firefox, haven't tried on Chromium yet).

But...after using it for a while, the issues become apparent. The first one I hit is that the system seems to hang pretty reproducibly playing video in browsers. This seems to be affecting pretty much everyone with a Strix Point system, and the only 'fix' is to turn off hardware video acceleration in the browser, which isn't really great (it means playing video will use the CPU, hurting battery life and performance). Then I found even with that workaround applied the system would hang occasionally. Looking at the list of Strix Point issues on the AMD issue tracker, I found a few that recommended kernel parameters to disable various features of the GPU to work around this; I'm running with amdgpu.dcdebugmask=0x800, which disables idle power states for the GPU, which probably hurts battery life pretty bad. Haven't had a hang with that yet, but we'll see. But aside from that, I'm also having issues with docks. I have a Caldigit TS3+, which was probably overpowered for what I really need, but worked great with the XPS 13. I have a keyboard, camera, headset, ethernet and monitor connected to it. With the HP, I find that at encryption passphrase entry during boot (so, in the initramfs) the keyboard works fine, but once I reach the OS proper, only the monitor works. Nothing else attached to the dock works at all. A couple of times, suspending the system and resuming it seemed to make it start working - but then I tried that a couple more times and it didn't work. I have another Caldigit dock in the basement; tried that, same deal. Then I tried my cheap no-name travel hub (which just has power pass-through, an HDMI port, and one USB-A port on it) with a USB-A hub, and...at first it worked fine! But then I suspended and resumed and the camera and headset stopped working. Keyboard still worked. Sigh. I've ordered a mid-range hub with HDMI, ethernet, a card reader and four USB-A ports on it off Amazon, so I won't need the USB-A hub daisychain any more...I'm hoping that'll work well enough. If not, it's a bit awkward.

So, so far it's a bit of a frustrating experience. It could clearly be a fantastic Linux laptop, but it isn't quite one yet. I'd probably recommend holding off for a bit while the upstream devs (hopefully) shake out all the bugs...

‎Internet apps: Dropping Chromium

← Older revision Revision as of 15:14, 7 January 2025 Line 344: Line 344:     === Internet apps === === Internet apps === −* Chromium-browser have moved to Tainted because of patent issues and we do not want to strip popular functionality ; please, do activate this repo if you want to use Chromium.+* Chromium-browser have been dropped due to too much maintenance work. <!--#33609--> −* Firefox has been updated to 115+* Firefox has been updated to **  * We added browsers for Gemini protocol: Lagrange (SDL), Kristall (Qt), Offpunk (CLI). * We added browsers for Gemini protocol: Lagrange (SDL), Kristall (Qt), Offpunk (CLI).    Morgano

‎Internet apps: Dropping Chromium

← Older revision Revision as of 15:14, 7 January 2025 (One intermediate revision by the same user not shown)Line 215: Line 215:  * 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]] (already in Mageia 9 since December). <!-- 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 24). <!-- 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)     ''For more information see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].'' ''For more information see [[Setup_the_graphical_server#Nvidia_proprietary_drivers|here]].'' Line 342: Line 344:     === Internet apps === === Internet apps === −* Chromium-browser have moved to Tainted because of patent issues and we do not want to strip popular functionality ; please, do activate this repo if you want to use Chromium.+* Chromium-browser have been dropped due to too much maintenance work. <!--#33609--> −* Firefox has been updated to 115+* Firefox has been updated to **  * We added browsers for Gemini protocol: Lagrange (SDL), Kristall (Qt), Offpunk (CLI). * We added browsers for Gemini protocol: Lagrange (SDL), Kristall (Qt), Offpunk (CLI).    Morgano

‎Loading driver in initramfs

← Older revision Revision as of 19:47, 6 January 2025 (One intermediate revision by the same user not shown)Line 110: Line 110:     * Only supported on 64 bit. * Only supported on 64 bit.  +  +* Mageia normally provide one current version, one legacy version and one "new feature" version, details [[#Nvidia_Driver_versions|below]].     * To see the proprietary driver working and tweak it, launch {{prog|nvidia-settings}} (from package x11-driver-video-nvidia*). * To see the proprietary driver working and tweak it, launch {{prog|nvidia-settings}} (from package x11-driver-video-nvidia*).    −* Kernel module is prepared (this takes a few minutes depending on CPU) at install or change of proprietary driver, and also when a new kernel is installed.  If you install Nvidia driver and then boot a kernel that had no Nvidia module prepared, it will be prepared during next boot with that kernel - note that it may look like the boot stalled, but just be patient!+* Kernel module is prepared (this may take a few minutes depending on CPU) at install or change of proprietary driver, and also when a new kernel is installed.  If you install Nvidia driver and then boot a kernel that had no Nvidia module prepared, it will be prepared during next boot with that kernel - note that it may look like the boot stalled, but just be patient!     * You can change between one proprietary and free drivers back and forth without the proprietary driver packages gets uninstalled nor wait for the kernel module being prepared. * You can change between one proprietary and free drivers back and forth without the proprietary driver packages gets uninstalled nor wait for the kernel module being prepared.  +  +<br>  +  +=== Loading driver in initramfs ===  +''News January 2025:'' <!--https://bugs.mageia.org/show_bug.cgi?id=31841#c42-->  +Now we provide initramfs packages for the three supported nvidia branches: nvidia-{470,current,newfeature}-initramfs.  +'''Installing''' this package puts the related nvidia-current.ko and related sub-modules into the initramfs boot image for the running kernel by automatically also executing dracut.  To do it for all installed kernels, manually execute "dracut --regenerate-all" - but you may first want to see if current kernel boots nicely first.  +  +''This early loading of the driver might help in situations which else have slow loading or when there are concurrent racing with nouveau. It may help with Wayland issues.''  +  +'''Note:''' You must first have used drakx11 to set your graphics driver to nvidia proprietary of same version.  +  +'''Possible issues:''' when you switch from proprietary to free driver without uninstalling nvidia drivers, or in some rare particular situation of upgrading kernel and driver versions in same transaction.  +  +'''To uninstall:''' just uninstall the -initramfs package, and dracut gets called to generate a new boot image of running kernel. To remove it from all kernels images, execute "dracut --regenerate-all".     <br> <br> Line 170: Line 187:  * 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 -- R550 -- Intended for all recent Nvidia GPU   −* Driver: New Feature -- nvidia-newfeature -- R565 -- *usually* a later version than nvidia-current, 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 -- 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.  * 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 Line 222: Line 239:     ===== Self compiling R340 ===== ===== Self compiling R340 =====  +''This is information for really experienced or adventurous users.''     R340 need more work, maybe you need also to compile a kernel to use it. You will find information on the Internet. 340.xx is also not compatibile with Xorg 21.1.8 ABI (which is ABI 25), it's at most ABI 24 compatible (xorg-1.20) however with adding "IgnoreABI" "true" to ServerFlags section in /etc/X11/xorg.conf it would ignore the ABI mismatch error and could allow newer Xorg to start with the older driver (even with some restriction or incompatibility). Of course some desktop (e.g. Plasma) might be more picky and having more incompatibilities than others (e.g. icewm). On the other hand it's still offering 50% speedup or more than modesetting/nouveau. It is still even possible to have the former modules compiling even on newer kernels, by including the Arch (and suse/deb) patches that are around - e.g. https://aur.archlinux.org/packages/nvidia-340xx, that are also collected in other places. <!-- collected from https://ml.mageia.org/l/arc/qa-discuss/2023-06/msg00008.html --> R340 need more work, maybe you need also to compile a kernel to use it. You will find information on the Internet. 340.xx is also not compatibile with Xorg 21.1.8 ABI (which is ABI 25), it's at most ABI 24 compatible (xorg-1.20) however with adding "IgnoreABI" "true" to ServerFlags section in /etc/X11/xorg.conf it would ignore the ABI mismatch error and could allow newer Xorg to start with the older driver (even with some restriction or incompatibility). Of course some desktop (e.g. Plasma) might be more picky and having more incompatibilities than others (e.g. icewm). On the other hand it's still offering 50% speedup or more than modesetting/nouveau. It is still even possible to have the former modules compiling even on newer kernels, by including the Arch (and suse/deb) patches that are around - e.g. https://aur.archlinux.org/packages/nvidia-340xx, that are also collected in other places. <!-- collected from https://ml.mageia.org/l/arc/qa-discuss/2023-06/msg00008.html --> Morgano

+ History

← Older revision Revision as of 18:32, 6 January 2025 Line 107: Line 107:     If you have a non-English system and need the output in English, then put <code>LANGUAGE=C</code> on the same line before the command. If you have a non-English system and need the output in English, then put <code>LANGUAGE=C</code> on the same line before the command.  +  +== History ==  +One great benefit of DNF is the execution history.  It can also act on it, such as undo. Of course it do not log the actions by urpm* nor installer or default updater applet, so only after you changed to DNF.  +See [https://dnf.readthedocs.io/en/latest/command_ref.html#history-command documentation] and [https://linuxopsys.com/dnf-history example].     == Graphical interface == == Graphical interface == Morgano

Publication date: 04 Jan 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-21259 , CVE-2024-21263 , CVE-2024-21273 , CVE-2024-21248 , CVE-2024-21253 Description Vulnerabilities were found in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are prior to 7.0.22 and prior to 7.1.2. A difficult to exploit vulnerability allows a high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise an Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VirtualBox VMs. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H). References

• https://bugs.mageia.org/show_bug.cgi?id=33754
• https://www.oracle.com/security-alerts/cpuoct2024.html#AppendixOVIR
• https://www.virtualbox.org/wiki/Changelog-7.0#v22
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21259
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21263
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21273
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21248
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21253

SRPMS 9/core

• virtualbox-7.0.22-1.mga9
• kmod-virtualbox-7.0.22-62.mga9

Publication date: 04 Jan 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-35176 , CVE-2024-39908 , CVE-2024-41123 , CVE-2024-41946 , CVE-2024-43398 , CVE-2024-49761 Description The REXML gem before 3.2.6 has a denial of service vulnerability when it parses an XML that has many `<`s in an attribute value. (CVE-2024-35176) The REXML gem before 3.3.1 has some DoS vulnerabilities when it parses an XML that has many specific characters such as `<`, `0` and `%>`. (CVE-2024-39908) The REXML gem before 3.3.2 has some DoS vulnerabilities when it parses an XML that has many specific characters such as whitespace character, `>]` and `]>`. (CVE-2024-41123) The REXML gem 3.3.2 has a DoS vulnerability when it parses an XML that has many entity expansions with SAX2 or pull parser API. (CVE-2024-41946) The REXML gem before 3.3.6 has a DoS vulnerability when it parses an XML that has many deep elements that have same local name attributes. (CVE-2024-43398) The REXML gem before 3.3.9 has a ReDoS vulnerability when it parses an XML that has many digits between &# and x...; in a hex numeric character reference (&#x...;). (CVE-2024-49761) References

• https://bugs.mageia.org/show_bug.cgi?id=33576
• https://www.ruby-lang.org/en/news/2024/05/16/dos-rexml-cve-2024-35176/
• https://www.ruby-lang.org/en/news/2024/07/16/dos-rexml-cve-2024-39908/
• https://www.ruby-lang.org/en/news/2024/08/01/dos-rexml-cve-2024-41123/
• https://www.ruby-lang.org/en/news/2024/08/01/dos-rexml-cve-2024-41946/
• https://www.ruby-lang.org/en/news/2024/08/22/dos-rexml-cve-2024-43398/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RQWXWS2GDTKX4LYWHQOZ2PWXDEICDX2W/
• https://www.ruby-lang.org/en/news/2024/10/28/redos-rexml-cve-2024-49761/
• https://ubuntu.com/security/notices/USN-7091-1
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35176
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39908
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41123
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-41946
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43398
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49761

SRPMS 9/core

• ruby-3.1.5-46.mga9

Publication date: 04 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description Fixed a bug in i2c handling that caused the OpenRGB Application to set incorrect LED colors on some NVIDIA GPUs. https://github.com/NVIDIA/open-gpu-kernel-modules/issues/41 Changed the fallback preference from 10 BPC YUV422 to 8 BPC RGB + dithering when enabling HDR scanout with limited display bandwidth. Fixed a bug that could cause the nvidia-settings control panel to crash when using X11 forwarding on some systems. Added a new application profile key, "GLVidHeapReuseRatio", to control the amount of memory OpenGL may hold for later reuse, as well as some application profiles for several Wayland compositors using the new key to work around issues with excessive video memory usage. Fixed a bug that could lead to crashes when a Vulkan application waits on a VkFence created by importing a DRM syncobj. This solves some crashes observed with Unreal Engine and other applications on Wayland. Fixed a bug that could cause KDE Plasma 6 to crash when running as a Wayland compositor. Fixed a bug that would cause the driver stack to fail to load the correct state of a Quadro Sync board when GSP is enabled. This would lead to inaccuracies in reporting framelock state when using house sync or stereo signals. Updated the kernel module build process to use CONFIG_CC_VERSION_TEXT from the Linux kernel's Kconfig to detect the compiler used to build the kernel. This may help select the correct compiler on systems where the kernel was built with a compiler other than the default one. Fixed a bug that prevented kernel modules linked using precompiled kernel interface files from loading on recent Debian systems. Improved the ability of nvidia-modprobe to detect whether kernel modules are already loaded. This corrects an issue that prevented nvidia-persistenced from setting persistence mode on some systems. Please note, starting from this release it's provided also the package: dkms-nvidia-newfeature-open-565.77-1.mga9.nonfree This is an "alternative" package to 'dkms-nvidia-newfeature' which uses open source kernel modules instead of the closed source ones. Note that only NVidia cards of arch Turing and beyond are supported by this dkms-nvidia-newfeature-open Older NVidia cards, e.g. in the Maxwell or Pascal arch supports only the standard dkms-nvidia-newfeature. So for instance Quadro K620 is in the Maxwell arch and are not supported by the -open variant. GTX 1080 is in the Pascal arch and it's not supported. RTX 2070, GTX 1660 are in the Turing arch and are supported. Quadro RTX A6000 is in the Ampere arch and is supported, etc. Note also that such dkms-nvidia-newfeature-open package it's not installed automatically by the drakx11 utils, but could be installed manually (in that case the cards must be already configured by the utils). So only for the brave and with a minimal competence with manual package installing. References

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

SRPMS 9/nonfree

• nvidia-newfeature-565.77-5.mga9.nonfree
• cuda-z-0.11.291-9.mga9.nonfree

Publication date: 04 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description Minor bug fixes and improvements. Note that starting from this version, dkms-nvidia-current-open-550.142-1.mga9.nonfree is provided as the alternative open-sourced Nvidia kernel module (this package is not automatically retrieved from drakx11). Note that while the nvidia-current package works for cards of series GTX 745 and beyond, these modules, as we already seen for nvidia-newfeature, work only for cards of series Turing and beyond. References

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

SRPMS 9/core

• meta-task-9-3.mga9
• mageia-repos-9-3.mga9
• ldetect-lst-0.6.59-1.mga9

9/nonfree

• nvidia-current-550.142-3.mga9.nonfree
• nvidia470-470.256.02-3.mga9.nonfree