Arch Linux on Reddit

Firstly, I want to mention, I know that as a beginner I have chosen a difficult distro to try and run, but I have my heart set on Arch. I don't mind the extra effort. Additionally, as a beginner, I don't think I'll get every term 100% correct. Please bear with me. So I cannot get Arch to install on my computer. I have gotten it to work in a virtual machine, so I have gotten to the "archinstall" part in the terminal. My issue is just before this. I select the usb to dual boot from, then the first "install arch" option, then before the install finishes I get hit with errors. I'm not sure how I could give a log from the install screen, but the most common error I get is: "watchdog: CPU11: Watchdog detected hard LOCKUP on cpu 11" The CPU number always seems to change as well. I have tried adding things to the install by pressing e before choosing the Arch install option, and adding things like: nomodeset nouveau.modeset=0 module_blacklist=btusb or maxcpus=1 or modprobe.blacklist=nouveau I have tried so many things, like different USBs, different arch ISO's, updating my BIOS, disabling things in the BIOS. Nothing seems to work. I have an NVIDIA card, and a Ryzen 7800X3D. Maybe these are causing issues? If anyone has any ideas and needs more info from me, I'm happy to provide anything. I appreciate the help! submitted by /u/MrFerrot12 [link] [comments]

I installed a fresh ARCH Linux with Hyprland but whenever I tried to watch a video the pc fans start being loud and after serval minutes the hole system crashes. these are my pc parts CPU: i5 4460 RAM: 4GB DDR3 1600Mhz GPU: Radeon R9 270X -/How I can fix it submitted by /u/PaperElite [link] [comments]

submitted by /u/Odd-Werewolf-006 [link] [comments]

I installed Davinci Resolve and realized it was quite laggy and eventually got a warning saying that my GPU memory is full. When checking, davinci is using my integrated intel graphics rather than my NVIDIA 3080 and I do not have an option to switch and use the 3080. I couldnt find anything on google to fix the problem nor could I find anything on the wiki page about that. The closest I could find is section 3.11 but I'm having difficulties understanding it fully... Though, I dont think is my problem as the computer uses my main GPU (The 3080) at all times except for when I open Davinci Resolve. submitted by /u/Maybe_A_Zombie [link] [comments]

i was having problem with Bluetooth and saw that my up time is more than 24h i decided to update my system and then rebooted it, but then when i try to open kitty it opens for like 0.5 sec and then closes itself, and when i tried to open konsole it worked submitted by /u/NV_editz [link] [comments]

Basically the title. Audacity 4 was released a few weeks ago but it is not in the repos yet. I am wondering if the drastic changes may have created some block related to dependencies or something like it that is delaying the update in the repos. (I know I can use the AUR, that's what I've been doing actually, but I am curious about the reason it is not in the repos yet.) submitted by /u/Money_Alarm291 [link] [comments]

So I was unable to download npm through worldwide mirror as I kept getting 404 from the mirrors. So I updated the mirrorlist to the servers of my country. I did it with rankmirrors. Now my packages are getting downloaded by a server named after some person. I wanted to ask it if safe compared to the worldwide mirror. Or was this not the right solution? submitted by /u/ResponsibilityBig343 [link] [comments]

Hi, fresh Arch install with Archinstall and Hyprland profile. The desktop loads, but Super+Q, Super+R, etc. don't open a terminal or launcher. I've checked that Kitty and Wofi are installed. Hyprland shows the desktop, but shortcuts don't launch applications. What could cause this on Arch with Hyprland 0.57? Anyone know what to check first? submitted by /u/artii829 [link] [comments]

I installed Hyprland on Arch Linux and then put the Serpantinum shell on top of it. I can open apps from the bars, but the desktop itself is completely empty — I don’t see any applications or icons. However, the apps do work after they are successfully launched. I tried rebooting through Konsole, and even though the screen was blank, the computer rebooted correctly. P.S. I also have a fully working KDE Plasma 6 desktop that works perfectly, so I can safely run commands from there. How can I fix the issue of seeing nothing on the desktop? submitted by /u/kario038 [link] [comments]

I used archinstall for installing my arch system but i do plan on installing it by myself in summer break submitted by /u/Outside-Wrap-6447 [link] [comments]

So in my previous post people seemed to agree that the issue was: package maintainer time being in short supply. So I've come up with a follow-up plan: What if we copied/adapated parts of Alpine abuild auto-splits. BUT limited it to non-functional aspects only (and biggest wastes): -docs and -lang These two hold little functionality (in terms of size vs features lost), and with about 100 lines in makepkg should be possible to fully automate. I've done some attempts in a repo. And wrote a small article about it (mostly a summary of the last post). Before proposing this more officially, I wanted to ask the community what are their thoughts on this? submitted by /u/Responsible-Sky-1336 [link] [comments]

I investigated a strange ToDesk problem on my Arch Linux machine: GNOME's screen-sharing permission dialog would appear for a fraction of a second and disappear before I could click anything. Sometimes the remote side showed a black screen, and sometimes the connection failed and retried. For additional context on the problem, see this Reddit discussion. If you read Chinese, you can also find the original write-up here. The useful discovery was that ToDesk 4.9.8.1 already had a functioning Wayland/PipeWire capture path. Its logs showed it automatically clicking the portal's Share button through AT-SPI, the Linux accessibility interface. Disabling the accessibility bridge specifically for the GNOME portal backend prevents that automatic click and lets me approve sharing manually. This is a workaround for that permission-dialog behavior on my setup. I also found session creation errors, which need to be treated separately. Successful capture does not establish that every remote-control feature works on Wayland. My environment Component Version Distribution Arch Linux, x86_64 Desktop/session GNOME 51.1, Wayland Mutter 51.1-1 xdg-desktop-portal 1.22.1-2 xdg-desktop-portal-gnome 51.0-1 PipeWire 1.6.10 ToDesk AUR todesk-bin 4.9.8.1-1 For comparison, Sunlogin 16.6.0.32198 on the same machine left the permission dialog open for manual approval. Why I looked beyond the “Xorg ONLY” warning The AUR package prints this during installation: Todesk Remote Control doesn't support Wayland, Xorg ONLY! Initially, that seemed to explain the failure. But inspecting the installed binary suggested there was more to it: strings -a /opt/todesk/bin/ToDesk | grep -iE 'wayland|pipewire|portal' Among the strings were: CScreenCapturerWayland WaylandPortalHelper::RequestScreenCapture WaylandSecureUiController ldd /opt/todesk/bin/ToDesk also showed a dependency on libpipewire-0.3.so.0. Symbols and dependencies alone would not prove working capture, but the runtime logs under ~/.local/share/todesk/Logs/ went further: [screencap][wayland] selecting PipeWire capturer PipeWire stream connected successfully [screencap][wayland][frame-diag] screen=530 ... callbacks=... consumed=... [zrtc] PublishCallback onSuccess stream label:desktop-stream These are excerpts, with some fields omitted. Together with advancing frame counters, they show successful capture and desktop-stream publication during the investigation. That made “no Wayland capture support at all” an inadequate explanation. What was making the permission dialog disappear? The ToDesk logs explicitly recorded portal automation: [screencap][wayland] starting AT-SPI portal automation ... [screencap][wayland] AT-SPI portal application found window_count=1 ... [screencap][wayland] portal screen already selected ... [screencap][wayland] portal confirmation attempt=1, accepted=true, role=button, action=click [screencap][wayland] portal dialog closed after confirmation attempt In one sample, the click was logged at 12:56:53.109 and the closed dialog at 12:56:53.364: a 255 ms interval. The whole sequence from starting automation to closing the dialog took about 360 ms. So the brief flash was consistent with ToDesk finding the dialog through AT-SPI and confirming it automatically. It was not, by itself, evidence that GNOME could not provide a capture stream. The workaround: keep the dialog available for manual approval The GNOME portal backend uses GTK. Setting GTK_A11Y=none for that backend stops it exposing its UI through the accessibility bridge, which blocks the automatic interaction described above. Run these commands as your normal desktop user, without sudo, in the GNOME session. Restarting the backend can interrupt existing screen-sharing sessions. If no-a11y.conf already exists, inspect it before replacing it. mkdir -p ~/.config/systemd/user/xdg-desktop-portal-gnome.service.d cat > ~/.config/systemd/user/xdg-desktop-portal-gnome.service.d/no-a11y.conf <<'EOF' [Service] Environment=GTK_A11Y=none EOF systemctl --user daemon-reload systemctl --user restart xdg-desktop-portal-gnome.service To check the service configuration and the running process: systemctl --user is-active xdg-desktop-portal-gnome.service systemctl --user show xdg-desktop-portal-gnome.service -p Environment pid=$(systemctl --user show xdg-desktop-portal-gnome.service -p MainPID --value) tr '\0' '\n' < "/proc/$pid/environ" | grep -Fx 'GTK_A11Y=none' The service should be active, and the process environment should contain GTK_A11Y=none. Then start a fresh ToDesk connection, select the monitor, and click Share yourself. The intended result is that the dialog stays available for manual confirmation. Confirm promptly, because ToDesk has a timeout while waiting for the portal response. For a successful capture session, look for PipeWire stream connected successfully and advancing frame counters after approval. In the new connection's logs, there should no longer be a successful automatic click on that dialog. This setting affects the accessibility bridge of the GNOME portal process, rather than changing accessibility settings for every application. It does, however, prevent screen readers such as Orca from accessing that process's UI through the bridge. If you rely on that access, this workaround is unsuitable. To undo it, remove the file created above and restart the backend: rm ~/.config/systemd/user/xdg-desktop-portal-gnome.service.d/no-a11y.conf systemctl --user daemon-reload systemctl --user restart xdg-desktop-portal-gnome.service The separate issue: session creation failures During failed connections, the GNOME portal journal also contained: Failed to start session: GDBus.Error:org.freedesktop.DBus.Error.Failed: Session creation inhibited There were also errors closing an old GNOME screencast session because its object path no longer existed. To watch for new errors: journalctl --user -u xdg-desktop-portal-gnome.service -f Those messages point to a problem during session startup or cleanup. An old session overlapping a reconnect is one possible explanation, but these logs do not establish whether the cause is in ToDesk, Mutter, or their interaction. Disabling AT-SPI access does not guarantee a fix for this failure. If it persists, try closing and reopening ToDesk. Restarting its system service is another troubleshooting step, but it disconnects existing remote sessions: sudo systemctl restart todeskd.service What the AUR history adds I checked the packaging repository rather than relying only on the installation message: The “Xorg ONLY” warning was introduced on February 9, 2021, for ToDesk 1.2.4d, in commit b095cb5. It is a fixed output string, not a capability test. The November 1, 2026 update to 4.9.8.1, commit 4d59901, retained that warning while adding packaging for /opt/todesk/lib and fallback handling for libraries including libpipewire-0.3.so.0. The installation script at that commit only creates fallback links when a system copy of the library is not found. A missing link in /opt/todesk/bin/ is therefore not automatically an installation fault; check ldd to see what is actually resolved. The PKGBUILD at that commit still downloads 4.8.5.1 for AArch64, despite the package version being 4.9.8.1-1. My findings about the newer binary should not be assumed to apply to ARM64. The AUR repository contains packaging scripts, not ToDesk's capture or accessibility implementation. It provides useful version and dependency context; the evidence for automatic confirmation comes from ToDesk's runtime logs. I have only investigated this workaround on GNOME Wayland with the versions above. KDE and Hyprland use different portal backends, so changing the service name alone would not make this GTK setting applicable. If anyone has investigated the Session creation inhibited failure on a similar setup, I would be interested in comparing logs. But everything is working fine now, and I can use ToDesk for remote access without any issues. I've also found that the Reddit community is incredibly friendly and helpful! submitted by /u/Material-Sherbet9132 [link] [comments]

I'm using Arch Linux in China, and I've run into an issue with ToDesk on Wayland. When I use Sunlogin Remote Control, everything works fine. It correctly brings up the screen-sharing permission prompt when a remote session starts. However, ToDesk behaves differently. The screen-sharing authorization prompt only flashes on the screen for a split second and then disappears, making it impossible to grant permission. Has anyone else experienced this issue or found a workaround? Having to switch from Wayland to X11 every time I want to use ToDesk would be really inconvenient. Is there a way to get it working properly on Wayland? submitted by /u/Material-Sherbet9132 [link] [comments]

Does anyone know why the veracrypt package still isn't flagged out of date? https://veracrypt.jp/en/Downloads.html https://archlinux.org/packages/extra/x86_64/veracrypt/ I'm concerned since 1.26.30 fixes vulnerabilities and it has already been over a week. It also took many months to update to 1.26.29. submitted by /u/captain150 [link] [comments]

When I try to sleep, one of two things happens, either it just turns back on, or the screen turns off while the power button stays on, and the computer won't take any inputs and must be force shut down. I'm on a Thinkpad T14. I was probably very vague so if you want more information let me know, and if you want logs let me know too. Thanks for your help. submitted by /u/Acrobatic-Tower7252 [link] [comments]

I still remember that many years ago there used to be fancy scripts to pick the fastest mirrors, then replaced by the reflector package to sort by age, country, speed etc. Nowadays it seems like the CDN powered by mirror.pkgbuild.com can be a set-and-forget option which works really well, especially in a strange time in need of timely updates, where lots of high CVEs are being found by AI and getting patched? Server = https://fastly.mirror.pkgbuild.com/$repo/os/$arch Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch submitted by /u/etherealshatter [link] [comments]

Some months back I choose arch linux as I thought it's one of the most popular distros out there, thus it will stay on the market for a very long time. But recently I started doubting that choice - when new critical CVEs show up for linux, I can't manage to find any sort of statement/guidance from the maintainers, the arch forums has very low traffic, the amazing wiki's home page was last edited almost 2 years ago... I started thinking - is this distro even being maintained by anyone anymore? Is there any place to find any messages (especially around CVEs) from maintainers? submitted by /u/ojek [link] [comments]

I was playing a game on Steam earlier today (The First Descendant) after trying to shutdown the game KDE Plasma crashes on me and becomes unresponsive. I try to reboot but nothing works in KDE, I switch to a different tty and do a reboot via (systemctl reboot). Now my system hangs at a black screen and when reaching "starting graphical interface" in the boot process. I tried to boot with the single kernel parameter and that goes into rescue mode for some reason? I thought that adding single as a boot parameter would just bypass the graphical boot part and let me reach a tty. Because right now I just get black screen and I can't switch tty or anything. I have done no updates of my machine today. I am running KDE Plasma 6 on Wayland with AMD 9060 RX card. To me it seems like my KDE session is borked but I can't get it to boot SDDM. Any ideas what to do here? submitted by /u/afettouhi [link] [comments]

I'm dual-booting Arch Linux and Windows on an Acer Nitro V15 ANV15-41 (Insyde UEFI, BIOS v1.52). My Arch UKI is at \EFI\Linux\arch-linux.efi on the ESP. Booting normally sometimes gives Failed to mount /sysroot, and one failed boot showed a corrupted kernel command line. However, the UKI's embedded command line is correct. I created a clean UEFI entry using efibootmgr. Booting it via BootNext successfully launched Arch, with BootCurrent: 0005. But when I put that entry first in BootOrder, the laptop boots straight into Windows instead. The entry also doesn't appear in the F12 boot menu. I also selected arch-linux.efi through the BIOS's Select an UEFI file as trusted for executing option. Any ideas why BootNext works but normal boot order doesn't? Is this an Acer/Insyde firmware quirk, and would GRUB help? submitted by /u/MarketIndependent143 [link] [comments]

After updating from openexr-3.5.3-1 to openexr-3.5.3-2 my system became completely unusable, reverting to openexr-3.5.3-1 solved it. So be aware. There's already a bug report on the package https://gitlab.archlinux.org/archlinux/packaging/packages/openexr/-/work_items/22 submitted by /u/bargu [link] [comments]

submitted by /u/penguinux [link] [comments]

submitted by /u/AfternoonBusy4770 [link] [comments]

I am just curious what do you think? submitted by /u/Entheon94 [link] [comments]

Basically the question. I have SynthV and Vocaloid both installed in Bottles (vocal synths for anyone unfamiliar with them), and I'd like to be able to use Japanese input with them (via skk). I have previously been able to get SKK to work with Bottles apps in Fedora before but that was in Gnome, and I can't remember now if that was via ibus or fcitx. Also worth noting that this is the Flatpak version of Bottles, same as in Fedora. Based on the research, I needed to set GTK_IM_MODULE=fcitx5, QT_IM_MODULE=fcitx5, and XMODIFIERS=@im=fcitx5. I set those overrides for Bottles but I still can't get it to work. As a test, I also set those variables for the Flatpak version of MuseScore 4 which still uses Xwayland and it does work there, so my guess is something to do with Wine maybe? IDK. Side note, the actual Bottles app (the native GTK Linux app to manage each bottle) does work with the IME, but it's also using Wayland I'm pretty sure... Technically I think using Wayland to render the apps in Wine allows the IME to work, but there's so multiple other rendering issues that it just doesn't work out in the end (gotta thank Windows for considering popup menus to each be individual windows lol...). Finally worth noting if it helps at all that my system is in en-us UTF-8 and the primary input is a standard en-US keyboard. I have CJK fonts installed in the Vocaloid bottle, and on my system but not in the SynthV bottle (didn't make a difference though). The bottles all also use the system language (en-US). submitted by /u/FaultWinter3377 [link] [comments]

First read the Arch Linux FAQ from the wiki Code of conduct How do I ask a proper question? Smart Questions XYProblem Please follow the standard list when giving a problem report. What AUR helper should I use? There are no recommended AUR helpers. Please read over the wiki entry on AUR helpers. If you have a question, please search the subreddit for previous questions. If your AUR helper breaks know how to use makepkg manually. I need help with $derivativeDistribution Use the appropriate support channel for your distribution. Arch is DIY distribution and we expect you to guide us through your system when providing support. Using an installer defeats this expectation. Why was the beginners guide removed? It carried a lot of maintenance on the wiki admin as it duplicated a lot of information, and everyone wanted their addition included. It was scrapped for a compact model that largely referenced the main wiki pages. Why Arch Linux? Arch compared to other distributions Follow the wiki. Random videos are unsupported. <plug>Consider getting involved in Arch Linux!</plug> submitted by /u/Foxboron [link] [comments]