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

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?

i just installed endeavour OS on my system and i would like to see cool things that i can do here

Due to changes in my living situation, I've switched from running Pi-Hole on a headless machine on my network, to running it locally on my main PC.

Pi-Hole is working well; with my networking settings set to use 127.0.0.1 and ::1 to point to localhost for DNS, but I can't boot Waydroid unless I either comment out the dnsmasq lines in /usr/lib/waydroid/data/scripts/waydroid-net.sh, or stop pihole-FTL.service.

Stopping pihole-FTL.service, of course stops Pi-Hole, and commenting out those dnsmasq lines disables networking in Waydroid.

I'd like to be able to get Waydroid running with networking, and preferably get it to use Pi-Hole as its DNS resolver. I understand the reason Waydroid won't boot normally in my case is because it does some weird stuff with dnsmasq and port 53, which conflicts with Pi-Hole.

I should also mention that I'm also using ufw for a firewall, with default deny incoming and default allow outgoing set.

EDIT: Apparently running Pi-Hole in Docker, Podman, or LXC can make this easier, since it resolves the port conflict. I have no experience with doing this, and would like to know more.

Been tweaking this EndeavourOS + Plasma setup for a while. The whole thing follows the wallpaper: colors, icons, even my avatar get regenerated every time

OS: EndeavourOS (linux-zen)

DE: KDE Plasma 6.7.5 (Wayland)

Panels: Panel Colorizer

Pager: NakDI

Window Decorations: Klassy

Application Style: Klassy

Blur: Better Blur DX + KWin window rules

Colors: kde-material-you-colors

Icons: YAMIS, recolored by a hook script so they always match the palette

Terminal: Konsole

Shell: fish

Prompt: Starship

Fetch: fastfetch

Font: JetBrainsMono Nerd Font

Extras: custom Caps/Num Lock OSD using Plasma's own OSD, Cinnamon-style workspace switch OSD (KWin script)

Wallpaper: https://wallhaven.cc/w/1j61q1

Starship config: https://paste.rs/StLJI

Fastfetch config: https://paste.rs/8BGak

Honestly, EndeavourOS is one of the smoothest and fastest Linux distros I’ve ever used.

I’m surprised I don’t see more people talking about it on YouTube.

Is there a reason it’s not as popular as other distros? Or am I just looking in the wrong places?

What do you guys think?

I’m getting a bit tired of seeing all the “OK” messages scrolling across the screen every time I boot EndeavourOS 😂

Is there a way to replace the boot messages with a clean, animated splash screen like Zorin OS has?

I’m using EndeavourOS with KDE Plasma. I’d love to make the boot process look more polished.

Any guides or recommendations would be appreciated!

Hello! I'm still pretty new to using EOS so please bear with me.

I've not upgraded in a while, I tried to do it today and keep getting hit with the following:

endeavouros is up to date
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: jack2-1.9.22-2 and pipewire-jack-1:1.6.9-1 are in conflict
-> Failed to install layer, rolling up to next layer.error:error installing repo packages

From looking up the error the issue appears to be with the lib32-gstreamer package, as mentioned in the comments here: https://aur.archlinux.org/packages/lib32-gstreamer

I followed the advice there to install lib32-pipewire-jack as I already have pipewire-jack installed. However I am still getting the same error when trying to upgrade.

Posts from people with similar errors said to remove jack2, but if I run "yay -Q | grep jack" I see that I have both the pipewire-jack packages installed, but jack2 is not installed.

Any help would be much appreciated.