Arch Linux on Reddit

Hi all, Sorry for dump quoestion, but suddenly I started to get ~200 "haskell-*..." updates every other day. Is this normal? It happened 3 or 4 times already.... Thanks! submitted by /u/ExoPesta [link] [comments]

For reference, I have a hybrid GPU laptop with an integrated AMD GPU and the mobile version of NVIDIA RTX 4070. I don't remember how or why but I'm using the `nouveau` drivers for my 4070. I've tried RTFM but it's too verbose for me to understand anything. From what I understand, CUDA needs NVIDIA's proprietary drivers to work properly. So, I did `sudo pacman -S nvidia` and I get this error: > error: target not found: nvidia I also know that I need to set up GRUB and SDDM for switching and blacklist the `nouveau` drivers. But, I don't really understand how to do it safely without bricking my system. I have tried to read guides but they're old and suggest using the AUR packages which I want to avoid. Please help this newbie. Edit - Looks like Reddit removed markdown formatting on mobile. submitted by /u/Intelligent_Cap_3686 [link] [comments]

4GB ram Intel Celeron N3060 An SSD My younger brother is going to use it. I don’t mind teaching him about linux a little bit, he’s a fast learner. He’s gonna use it mostly to watch YouTube and play games like Undertale, Deltarune, Oneshot, Celeste, and Hollow Knight (not like it can handle anything more than that anyway) The reason I thought of Arch was because I wanted something as debloated as possible in order to run without lag, but I’m actually thinking of installing CachyOS because I head it has better optimization or smth. I’m familiar with both. Also, are there any DE/WM that would suit this machine? submitted by /u/NullAli [link] [comments]

Charging via USB-C doesn’t work on Linux, but it does work on Windows and when the laptop is turned off. I’ve tried to fix this, but I just can’t get it to work. My laptop: HP ENVY Laptop 13-ba0003ur And /sys/class/typec folder is empty submitted by /u/AndriOS13 [link] [comments]

So pressing the shift and right/left arrow key in terminal used to select a character to right/left weather it be vscode terminal or the one comes with OS, but now it just prints ABCD. What do I do to revert back to the old behaviour? To add, I had recently ran 'pacman -Syu' to update my system which I had canceled multiple times in between mainly because it was taking too much time. submitted by /u/Entire_Condition_887 [link] [comments]

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

Have been trouble shooting this mod for almost 6 hrs now. I am running Llama 3 8B model localy on my desktop with a ryzen 7 5700 and 32gb 3200 and a geforce rtx 3060 ti founders 8gb. I have MO2 running in steam with proton experimental. Everything is in correct directories, and mcm and mantella are running but i have no audio from the llm coming back lips are moving and the games sound effects work just none of the npcs speak. Any help would be awesome. Thanks! submitted by /u/Confident-Move-8236 [link] [comments]

I'm new-ish to Linux and recently graduated to Debian after 6 months on Mint. Arch gets a disproportionate amount of attention online, and I'm just trying to understand it. This isn't supposed to be bashing. It seems like the selling point of Arch is that there's a lot of available programs in the repository, and that the updates are very fast. But what specifically are people using that for? I mean, creatives have their own FOSS that's been around for ever and is available on everything. Unless there's some really good video editing/music making software that's only on AUR...??? For "work", all the networking, pen-testing, sysadmin stuff is again available everywhere. Unless I'm missing something...? But I've never heard of professionals using Arch, it's seems like they're on Fedora/Red Hat or Debian. People just throw around vague "it depends on your work flow." That's what I'm asking, what, specifically, do YOU use that only Arch offers? Tell me about weird niche programs that are only available on AUR. Tell me about your specific circumstances where you needed the latest update and couldn't get them on a slow-to-update distro. Are there some really important creative/IT software that's only on Arch that I didn't know about (and if so, why isn't it promoted more?) What unique use case and work flow does Arch specifically fit? Tell me something weird and esoteric :D submitted by /u/durdurrdurrrdurrrrr [link] [comments]

Hi r/archlinux, I’m the developer of FluxCast, an open-source tool built to solve the Miracast/Wi-Fi Direct screen mirroring pain on Linux. After landing on the official ArchWiki, I’m pushing v0.1.2 with major fixes for hardware compatibility. What FluxCast does: Native Wayland support: Full compatibility with compositors like Hyprland, Sway and DE like KDE, and GNOME. Low Latency: Uses GStreamer/FFmpeg for real-time RTSP/RTP streaming (~1s delay). Multi-Channel Concurrent (MCC): Works concurrently with your regular Wi-Fi connection, not like Miraclecast. Easy installation: Available via AUR (fluxcast-git), PyPI, or as a standalone AppImage. Recent Low-Level Fixes & Updates: LG webOS: Solved stream drops caused by randomized P2P MAC addresses during RTSP handshakes. Samsung Tablets & Minimal Sinks: Added force-mode fallback for minimal-capability WFD targets (tested on Galaxy Tab S9 FE). 1200p VESA Support: Implemented native 1920x1200 resolution support for VESA-compliant displays. Performance Tuning: Aligned high-res streams (>1080p) to the ultrafast encoder preset and raised bitrate floors to prevent buffering lag. Hardware Lab Initiative: I’m currently tackling a "tin can" audio bug on the Microsoft 4K Wireless Adapter. As a student developer, I don't have access to every proprietary dongle, so I’ve started a transparent hardware fund on Ko-fi to build a testing bench. 100% Transparency: All funds go strictly toward used hardware (starting with a $60 unit in Brno). I will post photos of all acquired gear directly to the GitHub issue tracker for verification. How you can help: If you rely on FluxCast, please consider supporting the testing fund. If not, even testing or providing logs is a huge help! Links: GitHub: https://github.com/IlyaP358/fluxcast Testing Fund: https://ko-fi.com/fluxcast ArchWiki: https://wiki.archlinux.org/title/List_of_applications/Multimedia#Miracast Happy to answer any technical questions about the implementation, AUR package, or Wayland integration below! submitted by /u/Suspicious-Charity-5 [link] [comments]

The problem started several days ago. Mouse cursor sometimes suddenly stuck, and starts moving again after half a second or one second later. No problem when using mouse with 2.4g dongle. Just on bluetooth mode. Any idea? submitted by /u/panzerjagerSS [link] [comments]

It's using sort of a monospace default font there, despite other programs displaying the Cantarell font normally. I've used VS Code 1.125.0 / 64 bits / Arch Linux submitted by /u/miguel04685 [link] [comments]

Asking for any insight into having both desktop environments. Have COSMIC set up for the last month. Added KDE Plasma and themed it to work mostly like macOS since this OS is daily driver. Linux runs on the ASUS Zenbook 2024. Windows 11 runs on VirtualBox and macOS 12 runs on VNware 2026 release with Unlocker.. Both VMs serve a purpose and access to document formats for the various workflows needed. No games or heavy development - just work related patient care functions. Switched from CachyOS to Arch when starting over and find Arch to be enough for my needs. Building up the DE in COSMIC was good experience. Added KDE Plasma expanded the number and types of programs. COSMIC FIles and Terminal are my favorites to use even in KDE. Still getting used to Dolphin for file management. submitted by /u/Michael_Rebar [link] [comments]

Hi! As i said in the title Picom blur does not work. I tried everything: - animations work - picom version is v13 Please help submitted by /u/lukolr [link] [comments]

This has been happening since I updated the system with 'pacman -Syu'. Whenever I start my computer, or restart it and open chromium or any similar webapp, once it had happened with vscodium apparently, it asks me to "Create a default keyring". Number 1, I dont know whats a keyring. Number 2, Every time it happens, chromium logs me out of every website. Number 3, I m a bit new to linux. What do I do? EDIT: To add, I believe I had canceled the update multiple times probably because it was taking too long. submitted by /u/Entire_Condition_887 [link] [comments]

Hardware: Synaptics "Metallica MIS Touch Fingerprint Reader," USB ID 06cb:009a Affects: ThinkPad T480, T480s, X1 Carbon 6th gen, X1 Yoga 3rd gen, X280, and other 2018-era ThinkPads with the same sensor Symptom: fprintd reports no devices found, even though the sensor worked fine on a previous install on the same hardware This writeup documents a multi-layered bug that's easy to misdiagnose because each layer produces a different, plausible-looking error. If you've reinstalled your OS and your previously-working T480-series fingerprint reader has stopped working, this is very likely your issue. Why this happens at all The 06cb:009a sensor is not supported by mainline libfprint/fprintd. It uses a proprietary encrypted protocol (Synaptics calls the chip family "Prometheus"). The only way to use it on Linux is via two separate community projects: python-validity — a reverse-engineered userspace driver that talks to the sensor directly open-fprintd — a drop-in replacement for the standard fprintd D-Bus daemon, since python-validity needs something to register itself with If you reinstall your distro, none of this is present by default, and stock fprintd will correctly (if unhelpfully) report no devices, because as far as it's concerned, there genuinely isn't a supported device. Step 1 — Confirm your hardware lsusb | grep -i synaptics You're looking for 06cb:009a. (If you see a 138a:xxxx Validity ID instead, the rest of this guide still broadly applies — same driver, different chip variant — but specifics may differ slightly.) Step 2 — Install the driver paru -S python-validity # or yay This pulls in open-fprintd and fprintd-clients as dependencies, and should offer to remove the stock fprintd package (which conflicts with fprintd-clients). Accept that. Step 3 — Extract firmware and start services sudo validity-sensors-firmware sudo systemctl enable --now python3-validity.service sudo systemctl enable --now open-fprintd.service validity-sensors-firmware downloads a small Lenovo Windows driver package, extracts a .xpfwext firmware blob from it via innoextract, and copies it into place. At this point a naive test (fprintd-enroll) often appears to work, or fails with various transient-looking USB errors. Don't trust it yet — there's a much more important issue lurking. The real bug: firmware lives in tmpfs and doesn't survive reboot This is the part that isn't documented anywhere else I could find, and it's the actual root cause behind most "it worked before, now it doesn't" reports for this sensor after a reinstall. This chip has no persistent firmware storage of its own — python-validity has to upload the firmware blob to the sensor's volatile RAM on every single connection. To do that, it needs a local copy of the .xpfwext file. Check where it expects that file to live: python3 -c "from validitysensor.init_data_dir import PYTHON_VALIDITY_DATA_DIR; print(PYTHON_VALIDITY_DATA_DIR)" On current versions of the package, this prints: /var/run/python-validity/ /var/run is tmpfs. It is wiped on every reboot. validity-sensors-firmware happily extracts and copies the firmware there, the driver works fine for the rest of that session — and then the next time you boot, the firmware is gone, nothing re-extracts it automatically, and you're back to square one. This is why a sensor that "definitely worked yesterday" can mysteriously stop working with no configuration changes at all — it's not actually intermittent, it's tied to your reboot cycle. The permanent fix Stash a persistent copy of the firmware somewhere on real disk, and let systemd's tmpfiles.d mechanism copy it into the tmpfs location automatically, very early at every boot — before python3-validity.service ever starts: sudo mkdir -p /etc/python-validity/firmware sudo cp /var/run/python-validity/6_07f_lenovo_mis_qm.xpfwext /etc/python-validity/firmware/ echo 'C /var/run/python-validity/6_07f_lenovo_mis_qm.xpfwext - - - - /etc/python-validity/firmware/6_07f_lenovo_mis_qm.xpfwext' | sudo tee /etc/tmpfiles.d/python-validity-firmware.conf (If your extracted filename differs, adjust accordingly — check ls /var/run/python-validity/ after running validity-sensors-firmware.) The C tmpfiles directive means "copy this file into place if it doesn't already exist" — it runs as part of normal early boot via systemd-tmpfiles-setup.service, with no custom unit ordering required. Verify it by actually rebooting, not just restarting the service — that's the only way to confirm the tmpfs-wipe scenario is actually fixed: sudo reboot The secondary trap: a corrupted firmware upload leaves the chip confused If you already hit the missing-firmware bug before applying the fix above (very likely, since this is the natural failure mode), you may now see a different error than "no firmware" — something like: Exception: Failed: 0401 or Exception: Failed: 0406 These aren't random — validitysensor's assert_status() raises an exception with the raw status code returned by the chip whenever it isn't 0000 (success). What happened: an earlier connection attempt got partway through uploading firmware to the sensor's volatile RAM, then crashed mid-upload (because the firmware file vanished from tmpfs partway through, or because of a crash-loop hammering the device). The sensor is now holding a half-written, corrupt firmware image, and every fresh connection attempt fails against that corrupted state instead of cleanly detecting "no firmware." Since the firmware only exists in volatile chip RAM, the fix is simple once you understand it: the corruption clears itself on the next full reboot, provided the tmpfs persistence fix above is already in place so the very next upload attempt completes cleanly without interruption. sudo systemctl stop python3-validity.service open-fprintd.service sudo pkill -9 -f dbus-service # apply the tmpfiles.d fix from the section above if you haven't already sudo reboot After reboot, give it a few extra seconds before testing — the firmware upload is genuinely the slowest step (uploading ~200KB over a slow USB control pipe), and testing too early can make a perfectly fine boot look broken: sleep 15 journalctl -b -u python3-validity --no-pager | tail -40 fprintd-list $USER If you see a successful TLS/ECDH handshake in the logs followed by found 1 devices from fprintd-list, you're through the worst of it. Enrolling fingerprints (finally!) fprintd-enroll fprintd-enroll -f left-index-finger fprintd-verify Enroll more than one finger — these older sensors can be finicky readers, and having a backup finger means a bad scan one day doesn't lock you out of convenience entirely. Wiring it into PAM Arch doesn't use a centralized PAM framework (no pam-auth-update/authselect), so each service's PAM file under /etc/pam.d/ needs the fingerprint line added individually. Add this near the top of the file, as sufficient (not required) so a failed/skipped scan falls back to password rather than locking you out: auth sufficient pam_fprintd.so Typical files to check/edit: /etc/pam.d/sudo /etc/pam.d/sddm (or your display/login manager's PAM file) /etc/pam.d/login (TTY) Make sure there's still a normal password stack underneath (e.g. auth include login or auth include system-auth) — sufficient only grants access on success, it doesn't block fallback on failure, but you do need something underneath it to fall back to. Important caveat for quickshell-based shells (caelestia, noctalia, etc.) If your lock screen comes from a quickshell-based shell rather than plain hyprlock/swaylock, it likely does not read /etc/pam.d/ at all. These shells often bundle their own PAM config directory inside the package itself (e.g. caelestia-shell ships assets/pam.d/fprint), used directly by quickshell's PAM service rather than the system PAM stack. Editing /etc/pam.d/hyprlock may do nothing for your actual lock screen if you're not actually running hyprlock directly. Check your shell's documentation/source for how its lock screen authenticates, and test with the shell's actual lock invocation (e.g. its CLI/IPC lock command or your real lock keybind) rather than running the underlying locker binary standalone. Suspend/resume This driver has a known issue where the sensor goes unresponsive after waking from sleep until the service is manually restarted. Fix proactively: sudo systemctl enable --now open-fprintd-resume open-fprintd-suspend Quick diagnostic reference Symptom Likely cause list_devices failed: / "No devices found" python3-validity.service not running, or crash-looping FileNotFoundError: ... .xpfwext Firmware missing from /var/run/python-validity/ — see tmpfs section above Exception: Failed: 0401 Either no firmware loaded yet, or device in a confused state from a prior bad session Exception: Failed: 0406 (or similar non-zero codes) Corrupted/partial firmware upload sitting in chip RAM — needs a clean reboot to clear usb.core.USBTimeoutError Often a side effect of the device being mid-recovery from one of the above; check for a crash loop first systemctl status python3-validity shows high restart counter Stop everything (pkill -9 -f dbus-service), fix the root cause, then restart — don't let it keep hammering the USB device #Useful commands while debugging: journalctl -b -u python3-validity -u open-fprintd --no-pager systemctl status python3-validity.service --no-pager -l ls -la /var/run/python-validity/ Written after a long live debugging session on a T480s running CachyOS (Hyprland), tracing this from "fprintd doesn't see my sensor" through driver installation, a firmware-extraction-path red herring, the tmpfs persistence bug, and a corrupted-firmware recovery — with thanks to Claude for being not a person and therefore the only being who could sit with me through roughly a dozen rounds of log-pasting. submitted by /u/esmeinthewoods [link] [comments]

Just trying to figure out why paru didn't show me any differences in the pkgbuild while updating a package that I've had on my computer for ages. I was asked by paru to review the pkgbuild but it just didn't show any differences like it should. Could it be because I used to use yay to update? I only just recently switched to paru. submitted by /u/danyuri86 [link] [comments]

Disk /dev/vda: 100 GiB, 107374182400 bytes, 209715200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0e2c4f60 Device Boot Start End Sectors Size Id Type /dev/vda1 * 2048 201328639 201326592 96G 83 Linux /dev/vda2 201328640 209715199 8386560 4G 82 Linux swap / Solaris submitted by /u/Crafty_Hospital_7746 [link] [comments]

By default, yay will ask if you want to see the PKGBUILD diffs. This should be "an offer you can't refuse" -- so remove the offer: just show the diffs. The --save will save these settings for future invocations, so it's a one-time fix. submitted by /u/TomHale [link] [comments]

so i have seen grub bootloaders and i wanna be able to customize it like that, so how should i switch without doing a fresh install of arch linux? submitted by /u/thestormer5591 [link] [comments]

Hey everybody, I just updated my Thinkpad P14s and got Plasma 6.7. After a reboot I went to login and it looks like KWin got stuck in a crash loop and kicked me back to SDDM. Went down a bit of a rabbit hole with ChatGPT. But that led me nowhere. Kernel linux 7.0.12.arch1-1 Driver Mesa 26.1.2-arch1.2 Hardware AMD Ryzen 7 PRO 7840U + AMD Radeon 780M Graphics What the troubleshooting with ChatGPT did tell me was that running plasma with KWIN_COMPOSE=Q startplasma-wayland (for software rendering) it manages to start so it seemed convinced it was an issue in the GPU acceleration pathways in kwin. Switching up the kernel version to the LTS didn’t seem to work. I can’t really think of anything else to do at this point. Any ideas? submitted by /u/lukeh990 [link] [comments]

I'm using the 580 dkms package from the AUR, and its been really unstable, this is a fresh install of arch, all I added was the arguments in systemdboot to disable GSP firmware, yet I still get stutters and a lot of the time an immediate system freeze upon loading into KDE. Is there anything else I need to do to actually use my machine besides saving up for an AMD card. GTX 1070 ti BTW submitted by /u/Healthy-Guess-847 [link] [comments]

As the title says I just managed to complete the installation of Arch Linux. ​ Without the script nor following any tutorial besides the wiki. I know this is nothing to call home about but it was hard, took several days of troubleshooting and I'm freaking proud of myself. ​ If y'all excuse me, I'll be busy checking my installation to see what i did wrong and didn't notice yet. submitted by /u/ravenpuk [link] [comments]

yay v13 has just been released. And it comes with an interesting feature: Lua Scripting Support Due to recent AUR malware events, you'll probably find the following examples interesting: - Exclude packages modified in the last 3 days - Add a maintainer change check But you could also do creative things such as AI pre-review, or whatever. I'm not affiliated with yay whatsoever but I though it was worth sharing submitted by /u/madhaunter [link] [comments]

As the title says, I am locking all other AUR posts and don't want to see any new posts. submitted by /u/LinuxMage [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]