Argent Linux Wiki - User contributions [en]

https://wiki.argentlinux.io/api.php?action=feedcontributions&feedformat=atom&user=Stefan Argent Linux Wiki - User contributions [en] 2026-04-17T08:52:38Z User contributions MediaWiki 1.45.1 https://wiki.argentlinux.io/index.php?title=Documentation&diff=54 Documentation 2025-09-29T20:44:36Z

<p>Stefan: /* Table of contents */</p> <hr /> <div>= Table of contents =<br /> <br /> *[[Installation]]<br /> <br /> *[[System administration]]<br /> <br /> *[[Packages:Package Manager]]<br /> <br /> *[[Troubleshoot]]<br /> <br /> *[[Known Issues]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=53 Installation 2025-09-29T09:45:09Z

<p>Stefan: /* When burning ISO on stick via Rufus */</p> <hr /> <div>=== Click based install via desktop icon called Install Argent (which is Calamares) ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)<br /> <br /> == When burning ISO on stick via Rufus ==<br /> <br /> Give it label '''"ARGENT"''' (case-sensitive, capital letters).<br /> <br /> Partition scheme '''GPT'''</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=52 Installation 2025-09-29T09:44:41Z

<p>Stefan: /* When burning ISO on stick via Rufus */</p> <hr /> <div>=== Click based install via desktop icon called Install Argent (which is Calamares) ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)<br /> <br /> == When burning ISO on stick via Rufus ==<br /> <br /> Give it label "ARGENT" (case-sensitive, capital letters).<br /> <br /> Partition scheme GPT</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=51 Installation 2025-09-29T09:41:28Z

<p>Stefan: /* Click based install via desktop icon called Install Argent (which is Calamares) */</p> <hr /> <div>=== Click based install via desktop icon called Install Argent (which is Calamares) ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)<br /> <br /> == When burning ISO on stick via Rufus ==<br /> <br /> Give it label "ARGENT" (case-sensitive, capital letters).</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=50 Installation 2025-09-29T09:28:16Z

<p>Stefan: /* Click based install via desktop icon called Argent Installer (which is Calamares) */</p> <hr /> <div>=== Click based install via desktop icon called Install Argent (which is Calamares) ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=49 Installation 2025-09-29T09:25:19Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via desktop icon called Argent Installer (which is Calamares) ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=48 Installation 2025-09-24T15:58:46Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via Calamares ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=47 Installation 2025-09-24T15:57:49Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via Calamares ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)<br /> <br /> [[File:Argent_installation_1.png|thumb]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=46 Installation 2025-09-24T15:36:09Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via Calamares ===<br /> <br /> If you don't know how to do it, I'd suggest letting someone else click "next-next-install" for you. :-)</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=45 Installation 2025-09-23T14:49:54Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via Calamares ===<br /> <br /> If you don't know how to do it, I'd recommend starting with other Linux distributions.</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=44 Installation 2025-09-23T14:15:39Z

<p>Stefan: /* Click based install via Calamares */</p> <hr /> <div>=== Click based install via Calamares ===</div>

Stefan https://wiki.argentlinux.io/index.php?title=Installation&diff=43 Installation 2025-09-23T14:15:24Z

<p>Stefan: Created page with "== Click based install via Calamares =="</p> <hr /> <div>== Click based install via Calamares ==</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=42 Known Issues 2025-09-22T18:00:10Z

<p>Stefan: /* When switching to avasile --devmode you can't compile stuff due to missing deps */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ( pre-1.5.3-RC5-SLIM ISOs ) ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ( pre-1.5.3-RC5-SLIM ISOs ) ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.<br /> <br /> Or if you mistakenly destroyed your repositories in trying to fix this issue above, you can simply reset everything via:<br /> <br /> <code>avasile --usermode</code><br /> <br /> == When switching to avasile --devmode you can't compile stuff due to missing build tools ==<br /> <br /> We have recently changed some things and packages in the ISO image, and we have removed the build-only dependencies (such as <code> meson, ninja, make, automake, autoconf </code>).<br /> <br /> The solution to this is rather simple:<br /> <br /> <code> epkg o --with-bdeps y dev-build/autoconf dev-build/autoconf dev-build/automake dev-build/libtool dev-build/make dev-build/ninja dev-libs/md4c </code><br /> <br /> Run it before starting to emerge or epkg recompile stuff.</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=41 Known Issues 2025-09-22T17:59:46Z

<p>Stefan: /* Pipewire: No sound after installation */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ( pre-1.5.3-RC5-SLIM ISOs ) ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ( pre-1.5.3-RC5-SLIM ISOs ) ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.<br /> <br /> Or if you mistakenly destroyed your repositories in trying to fix this issue above, you can simply reset everything via:<br /> <br /> <code>avasile --usermode</code><br /> <br /> == When switching to avasile --devmode you can't compile stuff due to missing deps ==<br /> <br /> We have recently changed some things and packages in the ISO image, and we have removed the build-only dependencies (such as <code> meson, ninja, make, automake, autoconf </code>).<br /> <br /> The solution to this is rather simple:<br /> <br /> <code> epkg o --with-bdeps y dev-build/autoconf dev-build/autoconf dev-build/automake dev-build/libtool dev-build/make dev-build/ninja dev-libs/md4c </code><br /> <br /> Run it before starting to emerge or epkg recompile stuff.</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=40 Known Issues 2025-09-22T17:59:26Z

<p>Stefan: /* EPKG Update takes a long time */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ( pre-1.5.3-RC5-SLIM ISOs ) ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.<br /> <br /> Or if you mistakenly destroyed your repositories in trying to fix this issue above, you can simply reset everything via:<br /> <br /> <code>avasile --usermode</code><br /> <br /> == When switching to avasile --devmode you can't compile stuff due to missing deps ==<br /> <br /> We have recently changed some things and packages in the ISO image, and we have removed the build-only dependencies (such as <code> meson, ninja, make, automake, autoconf </code>).<br /> <br /> The solution to this is rather simple:<br /> <br /> <code> epkg o --with-bdeps y dev-build/autoconf dev-build/autoconf dev-build/automake dev-build/libtool dev-build/make dev-build/ninja dev-libs/md4c </code><br /> <br /> Run it before starting to emerge or epkg recompile stuff.</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=39 Known Issues 2025-09-22T17:59:10Z

<p>Stefan: Added extra known issue.</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.<br /> <br /> Or if you mistakenly destroyed your repositories in trying to fix this issue above, you can simply reset everything via:<br /> <br /> <code>avasile --usermode</code><br /> <br /> == When switching to avasile --devmode you can't compile stuff due to missing deps ==<br /> <br /> We have recently changed some things and packages in the ISO image, and we have removed the build-only dependencies (such as <code> meson, ninja, make, automake, autoconf </code>).<br /> <br /> The solution to this is rather simple:<br /> <br /> <code> epkg o --with-bdeps y dev-build/autoconf dev-build/autoconf dev-build/automake dev-build/libtool dev-build/make dev-build/ninja dev-libs/md4c </code><br /> <br /> Run it before starting to emerge or epkg recompile stuff.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=38 EPKG Package Manager 2025-09-20T19:09:17Z

<p>Stefan: /* To update */</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> <br /> If <code>epkg update</code> takes too long, you can:<br /> <br /> <br /> <code>cd /etc/portage && git pull && cd /var/db/repos/gentoo && git pull && cd /var/db/repos/argent-ws && git pull && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.<br /> <br /> === Post kernel recompilation ===<br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=37 EPKG Package Manager 2025-09-20T19:08:50Z

<p>Stefan: /* To update */</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> If <code>epkg update</code> takes too long, you can:<br /> <br /> <code>cd /etc/portage && git pull && cd /var/db/repos/gentoo && git pull && cd /var/db/repos/argent-ws && git pull && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.<br /> <br /> === Post kernel recompilation ===<br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=36 EPKG Package Manager 2025-09-20T19:08:34Z

<p>Stefan: /* To update */</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> If <code>epkg update</code> takes too long, you can:<br /> <br /> <code>cd /etc/portage && git pull && cd /var/db/repos/gentoo && git pull && cd /var/db/repos/argent-ws && git pull && git pull && git submodule update --init --recursive --depth=1<br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.<br /> <br /> === Post kernel recompilation ===<br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=35 Known Issues 2025-09-20T19:07:01Z

<p>Stefan: /* EPKG Update takes a long time */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.<br /> <br /> Or if you mistakenly destroyed your repositories in trying to fix this issue above, you can simply reset everything via:<br /> <br /> <code>avasile --usermode</code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=34 Known Issues 2025-09-20T19:01:38Z

<p>Stefan: epkg: update</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code><br /> <br /> == EPKG Update takes a long time ==<br /> <br /> <code> epkg update </code><br /> <br /> Takes a long time because it depends on git to do anything.<br /> <br /> Practically it runs a deep-run through git history of the repo and optimizes based on space.<br /> <br /> But since we've got plenty of space nowadays, all you have to do is just:<br /> <br /> <code> cd /etc/portage && git pull </code><br /> <br /> <code> cd /var/db/repos/gentoo && git pull </code><br /> <br /> <code> cd /var/db/repos/argent-ws && git pull && git submodule update --init --recursive --depth=1 </code><br /> <br /> As a workaround. Most probably we'll change how EPKG behaves in updating.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=33 EPKG Package Manager 2025-06-18T12:14:15Z

<p>Stefan: corrected the compile-preserved in the right spot</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.<br /> <br /> === Post kernel recompilation ===<br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=32 EPKG Package Manager 2025-06-18T12:13:06Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> === Post kernel recompilation ===<br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.<br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=31 EPKG Package Manager 2025-06-18T12:11:12Z

<p>Stefan: corrected spaces</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code><br /> <br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <br /> <code>epkg module-rebuid</code><br /> <br /> Or automated:<br /> <br /> <code>epkg automodule-rebuild</code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=30 EPKG Package Manager 2025-06-18T12:10:33Z

<p>Stefan: added module-rebuild</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code><br /> <br /> If you are on development mode, after the reinstallation and upgrading of all kernels, you must use:<br /> <code>epkg module-rebuid</code><br /> Or automated:<br /> <code>epkg automodule-rebuild</code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=29 EPKG Package Manager 2025-04-15T19:21:08Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> == If you get "preserved-rebuilds" warning ==<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=28 EPKG Package Manager 2025-04-15T15:50:32Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> = If you get "preserved-rebuilds" warning =<br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=27 EPKG Package Manager 2025-04-15T15:47:47Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved </code><br /> <br /> Compile-preserved knows what packages it needs to recompile in order to relink properly, it's the base foundation of a stable OS, compared to other distros that don't really care what they link against when they upload packages.</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=26 EPKG Package Manager 2025-04-15T15:39:45Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code><br /> <br /> In order to compile the preserved-rebuild dependencies (that failed to compile for you):<br /> <br /> <code>epkg compile-preserved <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autocompile-preserved <package> </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=25 EPKG Package Manager 2025-04-14T10:11:46Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>epkg compile <package> </code><br /> <br /> <code>epkg autocompile <package> </code><br /> <br /> or<br /> <br /> <code>epkg recompile <package> </code><br /> <br /> <code>epkg autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=24 EPKG Package Manager 2025-04-13T13:24:52Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you are a developer, and want to start developing things with easy maintenance ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>avasile compile <package> </code><br /> <br /> <code>avasile autocompile <package> </code><br /> <br /> or<br /> <br /> <code>avasile recompile <package> </code><br /> <br /> <code>avasile autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=23 EPKG Package Manager 2025-04-13T12:53:27Z

<p>Stefan: </p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> First of all, the holy '''epkg --help'''.<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code><br /> <br /> == To upgrade also development & build packages ==<br /> <br /> <code>epkg upgrade-full </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade-full </code><br /> <br /> <br /> === Package Administration ===<br /> <br /> Argent comes with some Gentoo sets that you need to remove if you want KDE removed.<br /> <br /> Normally KDE Plasma can't be removed from Argent installation by a normal user - '''and this is the right way, it's like removing Windows 11 or MacOS UI'''.<br /> <br /> But in order to remove this protection, you have to have some Gentoo knowledge, and understanding what you are doing.<br /> <br /> So, basically you will have:<br /> <br /> <code>emerge --deselect plasma-workspace plasma-tools</code><br /> <br /> Then, you can remove Plasma, and install something else.<br /> <br /> == If you want to start developing things ==<br /> <br /> You have to switch on development mode using <code>avasile --help</code> like this:<br /> <br /> <code>avasile --devmode </code><br /> <br /> It's not a big issue, this will let you compile some things that you do not have, and versions that our precompiled repository do not have yet.<br /> <br /> Normally a linux advanced user won't feel any difference between the normal user mode and devmode.<br /> <br /> But essentially, the devmode will start installing '''build dependencies''', and those dependencies are only used '''to compile or build programs'''.<br /> <br /> In this mode you can start using epkg to compile things, like this:<br /> <br /> <code>avasile compile <package> </code><br /> <br /> <code>avasile autocompile <package> </code><br /> <br /> or<br /> <br /> <code>avasile recompile <package> </code><br /> <br /> <code>avasile autorecompile <package> </code><br /> <br /> Difference between them is intuitive, as well as non-verbose (compile) versus verbose (recompile).<br /> <br /> == Compilation management ==<br /> <br /> If you want to recompile every package that's based on a given package:<br /> <br /> <code>epkg recompile-depend <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autorecompile-depend <package> </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=22 Main Page 2025-04-13T12:39:10Z

<p>Stefan: /* Documentation */</p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based (systemd) distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT<br /> <br /> == Documentation ==<br /> <br /> * [[Documentation|Documentation]]<br /> * [[Known Issues|Known Issues]]<br /> * [[EPKG Package Manager]] (How to install programs)</div>

Stefan https://wiki.argentlinux.io/index.php?title=EPKG_Package_Manager&diff=21 EPKG Package Manager 2025-04-13T12:38:07Z

<p>Stefan: EPKG instruction manual</p> <hr /> <div>=== Epkg Package Manager ===<br /> <br /> == To install packages ==<br /> <br /> <code>epkg install <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoinstall <package> </code><br /> <br /> == To remove packages ==<br /> <br /> <code>epkg remove <package> </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoremove <package> </code><br /> <br /> == To update ==<br /> <br /> <code>epkg update </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupdate </code><br /> <br /> == To upgrade ==<br /> <br /> <code>epkg upgrade </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoupgrade </code><br /> <br /> == To clean after upgrade/install ==<br /> <br /> <code>epkg clean </code><br /> <br /> No confirmation:<br /> <br /> <code>epkg autoclean </code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=20 Main Page 2025-04-13T12:34:06Z

<p>Stefan: /* Documentation */</p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based (systemd) distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT<br /> <br /> == Documentation ==<br /> <br /> * [[Documentation|Documentation]]<br /> * [[Known Issues|Known Issues]]<br /> * [[EPKG Package Manager]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=19 Main Page 2025-04-13T12:33:40Z

<p>Stefan: /* Documentation */</p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based (systemd) distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT<br /> <br /> == Documentation ==<br /> <br /> * [[Documentation|Documentation]]<br /> * [[Known Issues|Known Issues]]<br /> * EPKG Package Manager</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=18 Known Issues 2025-03-17T20:06:18Z

<p>Stefan: </p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''your user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=17 Known Issues 2025-03-17T20:06:06Z

<p>Stefan: </p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as '''simple user''' (not root!) in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=16 Known Issues 2025-03-14T14:34:08Z

<p>Stefan: /* Pipewire: No sound after installation */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as simple user in Konsole terminal:<br /> <br /> <code>systemctl --user disable --now pulseaudio.socket pulseaudio.service</code><br /> <br /> <code>systemctl --user enable --now pipewire-pulse.socket wireplumber.service</code><br /> <br /> <code>systemctl --user enable --now pipewire.service</code></div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=15 Known Issues 2025-03-14T14:32:41Z

<p>Stefan: /* Pipewire: No sound after installation */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> Run these commands as simple user:<br /> <br /> systemctl --user disable --now pulseaudio.socket pulseaudio.service<br /> <br /> systemctl --user enable --now pipewire-pulse.socket wireplumber.service<br /> <br /> systemctl --user enable --now pipewire.service</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=14 Known Issues 2025-03-13T23:41:01Z

<p>Stefan: /* No sound after installation */</p> <hr /> <div>=== Known issues ===<br /> == Pipewire: No sound after installation ==<br /> <br /> systemctl --user disable --now pulseaudio.socket pulseaudio.service<br /> <br /> systemctl --user enable --now pipewire-pulse.socket wireplumber.service<br /> <br /> systemctl --user enable --now pipewire.service</div>

Stefan https://wiki.argentlinux.io/index.php?title=Documentation&diff=13 Documentation 2025-03-13T23:17:47Z

<p>Stefan: </p> <hr /> <div>= Table of contents =<br /> <br /> *[[Installation]]<br /> <br /> *[[System administration]]<br /> <br /> *[[Packages]]<br /> <br /> *[[Troubleshoot]]<br /> <br /> *[[Known Issues]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=12 Main Page 2025-03-13T23:17:24Z

<p>Stefan: </p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based (systemd) distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT<br /> <br /> == Documentation ==<br /> <br /> * [[Documentation|Documentation]]<br /> * [[Known Issues|Known Issues]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=11 Known Issues 2025-03-13T23:16:53Z

<p>Stefan: </p> <hr /> <div>=== Known issues ===<br /> == No sound after installation ==<br /> <br /> systemctl --user disable --now pulseaudio.socket pulseaudio.service<br /> <br /> systemctl --user enable --now pipewire-pulse.socket wireplumber.service<br /> <br /> systemctl --user enable --now pipewire.service</div>

Stefan https://wiki.argentlinux.io/index.php?title=Known_Issues&diff=10 Known Issues 2025-03-13T23:16:39Z

<p>Stefan: Create Known issues page</p> <hr /> <div>=== Known issues ===<br /> == No sound after installation ==<br /> <br /> systemctl --user disable --now pulseaudio.socket pulseaudio.service<br /> systemctl --user enable --now pipewire-pulse.socket wireplumber.service<br /> systemctl --user enable --now pipewire.service</div>

Stefan https://wiki.argentlinux.io/index.php?title=Documentation&diff=9 Documentation 2025-03-13T23:11:49Z

<p>Stefan: </p> <hr /> <div>= Table of contents =<br /> <br /> *[[Installation]]<br /> <br /> *[[System administration]]<br /> <br /> *[[Packages]]<br /> <br /> *[[Troubleshoot]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Documentation&diff=8 Documentation 2025-03-12T15:59:08Z

<p>Stefan: Created page with "= Table of contents = *Installation *System administration *Packages"</p> <hr /> <div>= Table of contents =<br /> <br /> *[[Installation]]<br /> <br /> *[[System administration]]<br /> <br /> *[[Packages]]</div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=7 Main Page 2025-03-12T14:38:53Z

<p>Stefan: /* Welcome to the Argent Linux Wiki! */</p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based (systemd) distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT</div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=6 Main Page 2025-03-12T14:25:05Z

<p>Stefan: </p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based systemd distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues<br /> * Discord: https://discord.gg/hpmt5KU4yT</div>

Stefan https://wiki.argentlinux.io/index.php?title=Main_Page&diff=5 Main Page 2025-03-12T14:14:58Z

<p>Stefan: </p> <hr /> <div>== Welcome to the Argent Linux Wiki! ==<br /> Argent Linux is a Gentoo-based systemd distribution for Workstation and Servers usage.<br /> <br /> == Official links ==<br /> * Download link: https://iso.argentlinux.io<br /> * Home page: https:///argentlinux.io<br /> * Wiki: https://wiki.argentlinux.io<br /> * Bug report: https://github.com/Rogentos/argent-ws/issues</div>

Stefan