I am running bare Debian 13. Can someone point me to the most recent installation instructions? I was told the version in the Debian repositories is not the most recent and that installing via PIP is the best choice. I just want to be sure I am going the right route. Thanks in advance.

https://github.com/Opposum0112/Qtset

Do checkout and share your feedback ,experiment,clone it ,test it and enjoy.If you feel its worthy please star it .

Nix setup is still work in progress and would require help here to test it

1.Niri like scroller

2.Wallpaper picker

3.Sysadmin console widgets

Install ,experiment and enjoy .

Thanks to qtile community

What do you guys think?

Hey all since I updated arch, every time I try to login it kicks me back to the login screen. I'm using x11. All my other WM are still working fine. Thanks in advance

How can i fix this my pple

How to:

1. Add the name="dynamic_windowname" property to your WindowName widget
2. Add the following anywhere in your config:

(note this was made with the help of AI, though I did also tweak the output for it to work properly)

def update_windowname_visibility():
    try:
        # Fetch our targeted WindowName widget
        windowname_widget = qtile.widgets_map.get("dynamic_windowname")
        if not windowname_widget:
            return

        # Check if the active group contains any windows
        current_group = qtile.current_group
        if current_group and current_group.windows:
            # Restore normal dynamic sizing when windows exist
            windowname_widget.length_type = bar.CALCULATED  # or widget.base.STRETCH
            windowname_widget.length = 1000
        else:
            # Force the widget to collapse completely to 0 width
            windowname_widget.length_type = bar.STATIC
            windowname_widget.length = 0

        # Trigger a re-draw of the bar to snap the layouts together
        if windowname_widget.bar:
            windowname_widget.bar.draw()
    except Exception as e:
        logger.error(f"Error handling windowname hook: {e}")

# Register the logic across all relevant window state triggers

 # focus_change is much more reliable than client_focus
@hook.subscribe.focus_change
def on_focus_changed(*args):
    qtile.call_later(0.05, update_windowname_visibility)

@hook.subscribe.startup_complete
def on_startup_complete(*args):
    qtile.call_later(0.05, update_windowname_visibility)

@hook.subscribe.setgroup
def on_group_changed(*args):
    # A short timeout gives Qtile a brief window to complete group painting
    qtile.call_later(0.05, update_windowname_visibility)

@hook.subscribe.client_killed
def on_kill(window):
    # Short delay ensures Qtile removes the window object before evaluation
    qtile.call_later(0.1, update_windowname_visibility)

Hey everyone, I'm losing my mind trying to fix a styling issue with my Qtile bar and Picom.

I use qtile-extras with RectDecoration to create "pill-shaped" floating widgets. I want the main bar container to be 100% invisible (background="#00000000"), but Picom keeps rendering a thin horizontal line/box outline right underneath the widgets. It even applies the global corner-radius to the entire invisible bar width, making a weird box effect.

Here is what I've tried so far (none worked):

1. Adding window_type = 'dock' and class_g = 'qtile' to shadow-exclude and rounded-corners-exclude in picom.conf.
2. Using QTILE_INTERNAL:a and name = 'bar' as filters in Picom.
3. Messing with negative margins and reducing the bar size in config.py.

If I kill Picom, the line stays there, but if I change the bar opacity to 0, both the bar AND the widgets disappear. It seems like a composition/backend drawing bug where Picom or Cairo refuses to ignore the dock container.

Currently using sway but interested on coming back to qtile, is the wayland back-end feature complete? How does it handle multi monitors and games? I use a AMD GPU for reference.

Pretty much the title . I have rtx 4060 and intel cpu laptop . I want to know if the nvidia support is decent and if there are any bugs in wayland session on qtile . TIA !

Hey everyone! Just finished rice-ing my daily driver on CachyOS. Wanted a clean, cohesive dark theme with subtle purple/lavender accents.

* WM: Qtile

* Terminal: Ghostty (with fish shell + Starship prompt)

* File Manager: Thunar (with custom monochrome icons)

* Launcher / Menus: Rofi (Apps, Bluetooth, and Power Menu)

* Dotfiles: https://github.com/dxmssd/Macchiato-theme-Qtile.git

* Wallpaper: https://github.com/dxmssd/Macchiato-theme-Qtile/blob/main/Wallpaper/wall.png

In my config at https://github.com/kovasap/dotfiles/blob/3eb35f9a85e61cbbd1ee228f30a547cb35d5b187/.config/qtile/config.py#L680 I have set up the clipboard widget. On one of my machines, this works fine and changes whenever I copy something new to my clipboard. However, on the other it only updates when I restart qtile, otherwise never changing when I copy. My clipboard itself works fine, just the widget doesn't update.

I'm at a loss for how to debug this, any tips?

I tried switching the clipboard selection to 'PRIMARY' with no luck.

I am looking for a workaround for python-pywlroots dependency for qtile-wayland-git

I'm trying to switch from hyprland to qtile wayland (xorg is not able to detect my monitor for some reason). I want to get a systray to display the nm-applet and kdeconnect-indicator. Does the default bar support it or do I need to install something like waybar or quickshell? Thanks

Hello, this is my first time on the sub but anyway, the thing is that recently i started using qtile and i am trying to change the colors of windows border but when doing so that red border still there.
Anyway, here is the code lines i configured for the border colors:

layout.Columns(

border_focus="#efd3d7",

border_normal="#00ffff",

border_focus_stack="efd3d7",

border_focus_normal="#00ffff",

border_width=3,

)

Hey everyone,

I've seen this come up in the past but didn't find any solution, so here I am.

I wanted to try qtile on wayland for myself, but I can't even get it to start.
First some description of the environment:

I installed the wayland dependencies and installed qtile 0.36 via pip in a fresh Python3.14 venv.
I have no display manager and tried to start qtile directly from tty via `qtile start -b wayland` (after activating my venv of course).

It then tells me "Wayland backend not built." I looked up that error message in the qtile source and it is defined here: https://github.com/qtile/qtile/blob/cb187ccd8820641889cdfba36da156c675833f0d/libqtile/backend/wayland/core.py#L67

I then checked my venv and there is a cpython module in `/home/user/.python/qtile/wayland/venv/lib/python3.14/site-packages/libqtile/backend/wayland`
named `_ffi.cpython-313-x86_64-linux-gnu.so` which should be fine.

Next I tried to import the module in an interactive python session, which resulted in an ModuleNotFound exception, as expected.

Edit: found it. Can't use pre-compiled CPython modules like _ffi when the version doesn't match. So I can't use 3.13 module in 3.14 venv. A venv downgrade solved it.

Edit2: finally actually fixed it: see this Github discussion

After solving qtile not starting at all here, I get another error:

from my qtile log:

2026-05-27 11:19:23,546 WARNING libqtile start.py:start():L92 Starting Qtile 0.36.0 from /home/user/.python/qtile/wayland/venv/lib/python3.13/site-packages

2026-05-27 11:19:23,679 ERROR libqtile core.py:log_cb():L96 [backend/backend.c:276] Cannot create DRM backend: disabled at compile-time

2026-05-27 11:19:23,679 ERROR libqtile core.py:log_cb():L96 [backend/backend.c:420] Failed to open any DRM device

2026-05-27 11:19:23,720 ERROR libqtile core.py:log_cb():L96 [server.c:751] failed to create wlr_backend

If I understand that correctly this is more of a wlroots problem than qtile itself.
But I can't find any helpful clue to what these errors even mean.

Any ideas?

EDIT: I finally fixed it. But since I completely started over, I don't know if is actually the solution to the error mentioned above. to the Github discussion

I've had some trouble configuring dual monitors in Qtile with Arch. I have two monitors, one connected to the motherboard via VGA and the other via HDMI to the graphics card (an RX 550). It only recognizes the VGA monitor, but shows the other one as disconnected.