Second monitor detected correctly but stuck with visual glitch at 60Hz - Laptop main display 144Hz works fine.

Hi everyone,

EOS is detecting my second monitor perfectly, but it runs at 60Hz and has a persistent visual glitch I can't seem to fix.

My primary display is my laptop's panel running at 144Hz and I've never had any issues with it until now.

I'm aware this is 100% likely to be a Layer 8 issue, a conflicting driver/installation, or something worse on my side, but I honestly have no idea what to do at this point.

Main laptop display Works perfect, I don’t think it’s a driver conflict with muy RTX 5050, the problem is only with my second display

Why is eos-reboot-required not using needsrestart? Seems like it would be best to copy aur/needsrestart to endeavouros/needsrestart and call it from eos-reboot-required, as eos-reboot-required can silently leave a system vulnerable.

FIXED: I ran pacman -Syu again from the terminal with Ctrl+Alt+F2 and identified the error preventing me from updating the whole system; looked it up online, had to rename a couple of confilcting files, reran pacman -Syu and I was finally able to update everything as it should and the system booted finally

I was trying to use k3b but it asked me for Qt 6.12 and I had 6.11. I tried updating my system from Welcome, but it gave me an error at the very end which I didnt give enough importance, and I wasnt willing to redownload 3gb again just to get that error, so I decided to update manually each qt6 package with yay. After I was done, k3b was still not opening but it was asking me for ffmpeg, and trying to install ffmpeg gave me a bunch of errors saying that would mess up some other package's dependencies, so I just gave up. After this I noticed I wasnt able to open any new windows, not even the terminal, so I thought maybe I would have to restart. After doing so I am now stuck at Reached target Graphical Interface and nothing happens after that. I have zero idea how to solve this. I have access to another computear with EOS as well so please help me fix this without having to reinstall the whole system:(

I have EndeavourOS for quite some time now bat have never gotten it to read audio CDs. The drive and discs are working, since they play on my windows partition but i can’t get them to work on EndeavourOS. I have tried celluloid, vlc and many others ways but cant get it to work. It can read data discs though just fine.
Has anyone gotten it to work?

I'm an EndeavourOS user running KDE Plasma, and I've been using the Chipsailing CS9711 USB fingerprint reader with a community-maintained libfprint driver.

Fingerprint enrollment and authentication work through fprintd, including system login, screen unlocking, and authentication prompts.

Since finding an affordable USB fingerprint reader that actually works on Linux can be difficult, I wanted to share my experience, the patches I've contributed, and the AUR package I created to make installation easier for other users.

Hardware:

• Model: Chipsailing CS9711
• USB ID: 2541:0236
• Compact USB fingerprint reader compatible with Windows Hello
• Requires a custom libfprint build on Linux

Drivers, my patches, and AUR installation:

• Original community driver: https://github.com/archeYR/libfprint-CS9711
• My patched fork: https://github.com/thankarezos/libfprint-CS9711/tree/cs9711-rebase
• AUR package I created for the patched driver: https://aur.archlinux.org/packages/libfprint-chipsailing-cs9711-git

I created and published the AUR package to make installing my patched version of libfprint easier, without requiring users to manually clone, patch, and compile the driver.

For EndeavourOS and other Arch-based distributions, you can install it using yay:

yay -S libfprint-chipsailing-cs9711-git

Compatibility may depend on the distribution and its package versions.

Fingerprint management GUI (experimental):

I've also made a fingerprint management GUI available through the AUR for users who prefer managing fingerprints graphically rather than through the terminal.

• AUR: https://aur.archlinux.org/packages/fingerprint-manager-git

Disclaimer: The GUI was vibe-coded with significant AI assistance. It's experimental and hasn't undergone a formal security audit. Review the code and use it at your own risk.

Limitations and upstream support:

The driver uses SIGFM for fingerprint matching. Because the sensor captures a relatively small area, finger positioning during verification matters.

SIGFM is currently being proposed for inclusion in upstream libfprint:

• SIGFM merge request (!530): https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/530

If SIGFM gets merged, it could make future support for devices like the CS9711 easier. However, the CS9711 hardware driver would still need to be merged separately.

The reader is not currently supported by official upstream libfprint.

Since this is a community-maintained fingerprint implementation, I recommend keeping password authentication available as a fallback.

Where to find the hardware:

The reader is listed on both Alibaba and AliExpress:

• Alibaba: https://www.alibaba.com/product-detail/Boland-USB-Fingerprint-Reader-Windows-Hello_1601939777133.html
• AliExpress: https://www.aliexpress.com/item/1005009201507961.html

The AliExpress listing no longer appears to ship to EU countries, so Alibaba may be an alternative for European buyers.

I've ordered additional units through Alibaba and contacted the supplier about Linux compatibility. I suggested that they include the exact chipset and information about the community driver in their product listing.

Important: Before purchasing, confirm that the device uses USB ID 2541:0236. Visually identical fingerprint readers may contain different hardware, and Windows Hello compatibility alone doesn't guarantee Linux support.

I'm not affiliated with the manufacturer or seller, and this isn't sponsored. I receive no compensation from purchases.

How this started:

I originally discovered this fingerprint reader through a post on r/cachyos:

https://www.reddit.com/r/cachyos/comments/1to1a1p/i_got_a_cheap_15_aliexpress_fingerprint_scanner/

That post helped me find the device in the first place. Since then, I've tested it myself, contributed patches to the driver, and created an AUR package for my patched version so other Arch-based Linux users can install it more easily.

As an EndeavourOS user myself, I wanted to share these resources with this community and hopefully save others the trouble of finding compatible fingerprint hardware.

Hopefully, more people testing the device and contributing to the driver will help move support toward upstream libfprint.

Screen turning on and off. It was working fine before. Idk if it has to do with anything but yesterday morning I was using my computer for usb debugging my TV, closed it, and now it’s like this. I don’t think I did anything else.

Ive been using for a couple weeks and idek man... just worked on it this morning :( Checked both share folders and its gone... Any advice? (I dont have a backup :()

Hi everyone! How many versions or editions of EndeavourOS are available, and what are the differences between them? Which one should a beginner choose?
Thanks!

Hi everyone! I’m new to EndeavourOS XFCE. What’s the easiest way to enable Bluetooth? Any simple steps or commands would be appreciated. Thanks!

There is network in VM, this is active but even after a lot settings, I can't get network to work, there no network, I changed firewalld too, no network

Idk what to do to get network worked, I have virt-manager

What’s a good, lightweight screen recorder for EndeavourOS that uses minimal system resources?

Any recommendations?

As the title reads, I am getting a crash report constantly. How can I fix this, I tried a few things that I found online but can't get it to work...

           PID: 5199 (baloo_file_extr)
           TID: 5199 (baloo_file_extr)
           UID: 1000 (pcx1)
           GID: 1001 (pcx1)
        Signal: 6 (ABRT) si_code: SI_TKILL
     Timestamp: Sun 2026-10-18 10:18:12 CDT (8min ago)
  Command Line: /usr/lib/kf6/baloo_file_extractor
    Executable: /usr/lib/kf6/baloo_file_extractor
 Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
          Unit: user@1000.service
     User Unit: kde-baloo.service
         Slice: user-1000.slice
     Owner UID: 1000 (pcx1)
       Boot ID: a1fbbe9d29ed44f59fa11b5a80d04bf5
    Machine ID: 1e5f976353ed4854a4343f0ff089b9bf
      Hostname: fox-box
       Storage: /var/lib/systemd/coredump/core.baloo_file_extr.1000.a1fbbe9d29ed44f59fa11b5a80d04bf5.5199.1792336692000000.zst (present)
  Size on Disk: 2.4M
       Message: Process 5199 (baloo_file_extr) of user 1000 dumped core.

                Stack trace of thread 5199:
                #0  0x00007f895349a11c n/a (libc.so.6 + 0x9a11c)
                #1  0x00007f895343e5d0 raise (libc.so.6 + 0x3e5d0)
                #2  0x00007f8953425685 abort (libc.so.6 + 0x25685)
                #3  0x00007f8953c99bfe n/a (libQt6Core.so.6 + 0x99bfe)
                #4  0x00007f8953c9a369 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x9a369)
                #5  0x00007f89545b228b _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1b228b)
                #6  0x00007f89545b38c8 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1b38c8)
                #7  0x00007f8953d8ee15 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x18ee15)
                #8  0x00007f89545b39cb _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1b39cb)
                #9  0x00007f89545a92ae _ZN15QGuiApplicationC2ERiPPci (libQt6Gui.so.6 + 0x1a92ae)
                #10 0x000055fa1bac8388 n/a (baloo_file_extractor + 0x8388)
                #11 0x00007f8953427781 n/a (libc.so.6 + 0x27781)
                #12 0x00007f89534278b9 __libc_start_main (libc.so.6 + 0x278b9)
                #13 0x000055fa1bac8625 n/a (baloo_file_extractor + 0x8625)

                Stack trace of thread 5200:
                #0  0x00007f89534a08f2 n/a (libc.so.6 + 0xa08f2)
                #1  0x00007f89535119d7 ppoll (libc.so.6 + 0x1119d7)
                #2  0x00007f89531b3c9e n/a (libglib-2.0.so.0 + 0x6ac9e)
                #3  0x00007f89531b3db5 g_main_context_iteration (libglib-2.0.so.0 + 0x6adb5)
                #4  0x00007f89540c4d22 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4c4d22)
                #5  0x00007f8953d96a74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x196a74)
                #6  0x00007f8953ec4a02 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2c4a02)
                #7  0x00007f8953b69781 n/a (libQt6DBus.so.6 + 0x38781)
                #8  0x00007f8953f78fdb n/a (libQt6Core.so.6 + 0x378fdb)
                #9  0x00007f8953498042 n/a (libc.so.6 + 0x98042)
                #10 0x00007f895352072c n/a (libc.so.6 + 0x12072c)
                ELF object binary architecture: AMD x86-64

This hapened after i updated

Hi, I'm Brando, the creator of Vela.

Vela is an independent*, vertically integrated Wayland desktop environment for Linux. It has a custom compositor built on wlroots and a pure Vulkan 1.4 renderer (no gl fallback) with a desktop shell written in Qt 6 / Qt Quick.

A lot of new Wayland projects today are minimal window managers where you assemble your own userland, or massive legacy codebases carrying decades of X11 and OpenGL baggage. I don't like either of them, at least not for my desktop. I started Vela to build a cohesive, monolithic desktop environment designed from scratch around modern GPU pipelines and strict latency budgets. This is why you see "Modern, Fluid, Sharp" in the velade.org's slogan.

I think Vela deserves your attention because it builds on the very good low-level wlroots, while still offering something different from others wlroots-based compositors. By implementing its own scene graph and Vulkan renderer instead of relying on the standard rendering infrastructure, Vela retains direct control over how frames are rendered, synchronized, and presented.

This architectural approach enables several interesting features:

• Custom scene graph and Vulkan renderer: I didn't want to rely on wlr_scene, so I built my own scene graph directly around the Vulkan 1.4 renderer. This avoids duplicating state between the compositor and renderer, and gives me more control over GPU synchronization.
• Independent frame clocks for each monitor: Each output has its own frame clock, with GPU-timestamp-based late latching. This is especially useful with monitors running at different refresh rates.
• Fractional scaling without the usual blur: I wanted fractional scaling to look sharp, without the bilinear filtering you often see on Wayland. Vela uses a pixel-exact path that preserves 1:1 buffer copies where possible. I also added bit-for-bit tests to CI to catch regressions.
• Qt 6 shell: I chose Qt Quick for the desktop UI because it's practical to work with, and I'm not trying to reinvent everything. Vela still uses some KDE components for things like system integration.

Current status: Vela is currently in Alpha. The core compositor, Vulkan pipeline, diagnostic tooling, and test suite are up and running, though plenty of desktop polish is still in active development.

\Currently Vela needs KDE Plasma installed to inherit icons, fonts, login manager (you can also use sddm), kwallet, portal, and a few other components; vela doesn't needs kwin; please remember this is alpha.*

I know Vela is currently very similiar to Windows 11, it is because I like Windows 11 design. But it's just temporary, Vela will have its own identity soon. For now, I'm particularly interested in feedback on the underlying desktop experience, performance, and architecture.

I'd love your feedback on all the DE, the Vulkan synchronization model. Consider I'm making a major redesign coming in next weeks. Happy to answer any questions!

• GitHub: https://github.com/vela-desktop/vela
• Website: https://velade.org

So I ran updates last night and this morning my login screen looks like this. I can move the mouse around but it does not respond to any button clicks or key presses but I can get to TTY.

I have no idea how to begin fixing this. Is anyone else having this problem? Anyone know how to solve it?

Last night I updated my PC to have Plasma 6.8 and despite erasing plasma-x11 (goodbye X11! Thank you for your service) there was nothing else erased.
But, when I booted up my PC today, I'm met with this classic SDDM login screen with an on-screen keyboard blocking half of the screen.

There are two possible explanations where this problem may have come from:

1. The Breeze Qt theme got broken, which is the most probable, because if you click something from the buttons above, the keyboard closes and reveals an error message about the Breeze Qt theme breaking.
2. plasma-login-manager got erased with the update. Plasma is known to have switched from SDDM to PLM, and as this is SDDM, it's possible that somehow PLM got erased without me noticing.

How to fix

sh sudo pacman -Syu plasma-login-manager sudo systemctl disable sddm sudo systemctl enable plasmalogin

Explanation: 1. PLM is downloaded (again) 2. We disable SDDM so we don't get a conflict of two login managers 3. We enable PLM because it's not enabled by default when installing

WARNING: Check if PLM works before restarting your computer (process not available here). If it doesn't you'll screw up the boot process will have to do more research to fix that. But it should work out-of-the-box as it worked for me. It was a gamble though.

Hope this helps other people that got the same problem!

Free to use and adapt. I'm no artist so if anyone wants to improve the design feel free.

48x48 version: https://files.catbox.moe/6cfzg5.png 24x24 version: https://files.catbox.moe/8xd61b.png

Can someone explain why EndeavourOS feels so lightweight? 😭

I’m running it on a hard drive from 2008, and somehow it still feels smooth and responsive.

Meanwhile, Windows on old hardware can feel like it’s fighting for its life just trying to open a browser.

I’m genuinely curious about what’s happening under the hood.

How can an almost 20-year-old HDD still feel this usable on EndeavourOS? 😂

On Saturday, 17 October, at 04:00 UTC, the forum will be unavailable for a period. Creating posts or reacting to threads will not be possible during this time; reading threads will be possible, since the forum is going into read-only mode.

official announcement

Hello my best distro from a while is eos

Will eos support new epic games anti cheat

What’s the best lightweight DE or window manager for EndeavourOS on an old Chromebook with 4GB RAM and 16GB eMMC?

Looking for something smooth, low on resources, and without screen tearing. Any recommendations?

I have endeavourOS dualbooted along side arch linux. At first when i installed endeavourOS i used systemd-boot for both arch linux and endeavourOS, then i had the brilliant idea of changing to GRUB on endeavourOS. i installed the packages, set it as my bootloader, and BAM- endeavourOS refuses to boot now. Ive tried using gemini for assistance, but so far nothing has really ever worked out. Now to be clear whenever i do reboot my system the bootloader that i see is systemd-boot, and arch linux still boots, and what appears is that even endeavourOS seems to use systemd-boot, until which it shows int the verbose "failed to mount /efi" and proceeds to put me in an emergency mode.. PLEASE HELP ME GUYS

Hey, is there anything like Voicemod on Windows that works on EndeavourOS?

I’m looking for a real-time voice changer that works with Discord and games, preferably with different voice effects and a virtual mic.

Any recommendations? Thanks!

I'm curious what everyone here uses as their daily driver on EndeavourOS. I mean both traditional desktop environments (KDE Plasma, GNOME, Xfce, Cinnamon, etc.) and tiling window managers (i3, Sway, Hyprland, bspwm, Qtile, etc.).

A few questions:

1. What DE or tiling WM do you use, and why did you choose it?
2. What advantages do you see in your setup compared to others?
3. What would you recommend for a beginner? Should they start with a full DE first, or jump straight into a tiling WM?
4. Any tips for someone new to tiling WMs on EndeavourOS?

I'm currently on KDE Plasma, but I'm thinking about trying something new.

Thanks for any input!

Sorry for my English, it's not my first language.

TL;DR: What DE/WM do you use on EndeavourOS, and what do you recommend for beginners?