Qtile start errors and odd behavior

gangliaghost · 24 May 2023 15:32

Updated using garuda-update yesterday, booting today caused an issue where qtile either isn't loading or is partially loading? On SDDM, I log in and a bar at the bottom appears. Login dialog box is still there, DE doesn't load or anything, but I'm able to make windows using M-r. My super + Q key doesn't close processes though.

Anyway, I checked that nvidia drivers are the usual ones, not changed. I replaced the ~/.xinitrc with the default from /etc/X11/xinit/xinitrc. When using ctrl + alt + F2 term, I tried running startx, which promptly shuts itself off with no errors. I have garuda-inxi output plus the qtile start outputs.

Restoring snapshots all the way to earlier this week resulted in same behaviors, almost like the snapshots didn't change anything. I don't really know how to interpret the Qtile start error, since I'm newer to linux. Would appreciate some assistance.

`garuda-inxi` output: 

System:
  Kernel: 6.3.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=fec35a8a-ac27-428a-ab15-ff89bcf15665 rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: Qtile v: 0.22.1 wm: LG3D vt: 1 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK MAX (MS-7C02) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 3.F1
    date: 07/05/2022
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 2942 high: 3855 min/max: 2200/4950 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3599 2: 2200
    3: 2200 4: 3700 5: 3855 6: 2800 7: 3700 8: 2200 9: 2875 10: 3700 11: 3700
    12: 2200 13: 3700 14: 2200 15: 2200 16: 3700 17: 3700 18: 3700 19: 2200
    20: 2200 21: 2200 22: 2200 23: 3700 24: 2200 bogomips: 177599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2060] vendor: Micro-Star MSI
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
    link-max: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 25:00.0
    chip-ID: 10de:1e89 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: nvidia gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 95 s-size: 1198x389mm (47.17x15.31")
    s-diag: 1260mm (49.59")
  Monitor-1: DP-0 pos: bottom-l res: 1920x1080 hz: 60 dpi: 96
    size: 510x287mm (20.08x11.3") diag: 585mm (23.04") modes: N/A
  Monitor-2: DP-4 pos: primary,top-right res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 685mm (26.97") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce RTX
    2060/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 4 link-max: lanes: 16
    bus-ID: 25:00.1 chip-ID: 10de:10f8 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 27:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech G733 Gaming Headset
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-9:4 chip-ID: 046d:0ab5 class-ID: 0300
  API: ALSA v: k6.3.3-zen1-1-zen status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 1.21 TiB (44.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDS100T3X0C-00SJG0 size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 111110WD temp: 39.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 24.97 GiB (2.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 24.97 GiB (2.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 24.97 GiB (2.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 24.97 GiB (2.7%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.27 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 37.1 C mobo: N/A gpu: nvidia temp: 34 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30%
Info:
  Processes: 352 Uptime: 23m wakeups: 0 Memory: available: 31.27 GiB
  used: 2.15 GiB (6.9%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 Packages: pm: pacman pkgs: 1321
  libs: 459 tools: pamac,paru Shell: fish v: 3.6.1 default: Bash v: 5.1.16
  running-in: alacritty inxi: 3.3.27
Garuda (2.6.16-1):
  System install date:     2023-04-25
  Last full system update: 2023-05-23
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:


`qtile start`

Traceback (most recent call last):
  File "/usr/bin/qtile", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/main.py", line 66, in main
    options.func(options)
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/start.py", line 88, in start
    q = make_qtile(options)
        ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/start.py", line 51, in make_qtile
    kore = libqtile.backend.get_core(options.backend)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/backend/__init__.py", line 15, in get_core
    return importlib.import_module(f"libqtile.backend.{backend}.core").Core(*args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/backend/x11/core.py", line 104, in __init__
    raise ExistingWMException(existing_wmname)
libqtile.backend.x11.core.ExistingWMException: LG3D

gangliaghost · 24 May 2023 16:15

Alternative to fixing whatever these errors are, is it possible to reinstall qtile without reinstalling garuda? I think my google searches are messed up because I can't seem to find any good info on if or how to do that.

filo · 24 May 2023 16:43

I'm not a qtile user, so just trying to guess here...
Have you checked in the qtile GitHub issue list, e g. this one?

github.com/qtile/qtile

some errors after update

opened 08:44PM - 03 May 23 UTC

smjt2000

bug

### The issue: so finally Arch updated the python to 3.11 and I have many probl…ems now. yesterday I fully upgraded my system. today when I tried to login Qtile, It didn't start. so I logged in to Gnome and after a while I found that python updated. and now I logged in to Qtile. but my config file didn't load and I'm using the default config. I executed `python ~/.config/qtile/config.py` and I got this Error. ``` Traceback (most recent call last): File "/home/smjt2000/.config/qtile/config.py", line 1, in <module> from modules.keys import keys, mod File "/home/smjt2000/.config/qtile/modules/keys.py", line 1, in <module> from libqtile.lazy import lazy File "/usr/lib/python3.11/site-packages/libqtile/lazy.py", line 24, in <module> from libqtile.command.client import InteractiveCommandClient File "/usr/lib/python3.11/site-packages/libqtile/command/__init__.py", line 28, in <module> from libqtile.lazy import LazyCommandInterface ImportError: cannot import name 'LazyCommandInterface' from partially initialized module 'libqtile.lazy' (most likely due to a circular import) (/usr/lib/python3.11/site-packages/libqtile/lazy.py) ``` what should I do? ### Required: - [X] I have searched past issues to see if this bug has already been reported.

gangliaghost · 24 May 2023 17:06

Realized the QTile start error is incorrect, because I'm technically trying to launch from inside qtile. When I exit and try from tty, it says something about no display manager. I'm having an awful time trying to save the command output to a txt file.

Also looking at the github page you recommended, filo. I can try to do the key edit if I can figure out which file is the main issue. They're also talking about downgrades to some of the dependencies, but I'm having a hard time figuring out how to do that. I try sudo pacman -S python-cairocffi=1.4.0-3 and get a target not found error.

gangliaghost · 24 May 2023 17:13

Okay! Now that I know stdout and stderr are different, I have the error message from tty! Also tried reinstalling qtile and python dependencies from pacman with sudo pacman -S qtile and etc, nothing fixed.

File: output.txt
qtile start
Traceback (most recent call last):
  File "/usr/bin/qtile", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/main.py", line 66, in main
    options.func(options)
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/start.py", line 88, in start
    q = make_qtile(options)
        ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/scripts/start.py", line 51, in make_qtile
    kore = libqtile.backend.get_core(options.backend)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/backend/__init__.py", line 15, in get_core
    return importlib.import_module(f"libqtile.backend.{backend}.core").Core(*args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/libqtile/backend/x11/core.py", line 82, in __init__
    raise QtileError("No DISPLAY set")
libqtile.utils.QtileError: No DISPLAY set

gangliaghost · 24 May 2023 17:43

Update: Might be a python/pip issue? Tried rebuilding qtile with pip using pip install qtile --upgrade --force-reinstall, received this note at end of the output. Will try opening issue in github, I think, since it seems to not be garuda itself.

It looks like your cairocffi was not built with xcffib support.  To fix this:

        - Ensure a recent xcffib is installed (pip install 'xcffib>=0.5.0')
        - The pip cache is cleared (remove ~/.cache/pip, if it exists)
        - Reinstall cairocffi, either:

            pip install --no-deps --ignore-installed cairocffi

          or

            pip uninstall cairocffi && pip install cairocffi

      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for qtile
ERROR: Could not build wheels for qtile, which is required to install pyproject.toml-based projects

gangliaghost · 24 May 2023 18:07

github issue that's the same as mine opened, here. Linking for posterity.

github.com/qtile/qtile

Build error building wheel for qtile did not run successfully

opened 05:12AM - 14 May 23 UTC

Ehiffi

unconfirmed

### The issue: Was trying to install latest dev version of qtile from git, an…d running ```shell pip install .``` ended with ```python Defaulting to user installation because normal site-packages is not writeable Processing /home/ehiffi/git/qtile Installing build dependencies ... done Getting requirements to build wheel ... done Installing backend dependencies ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: cffi>=1.1.0 in /usr/lib/python3.11/site-packages (from qtile==0.22.2.dev185+g4ecf1bde) (1.15.1) Requirement already satisfied: cairocffi[xcb]>=0.9.0 in /home/ehiffi/.local/lib/python3.11/site-packages (from qtile==0.22.2.dev185+g4ecf1bde) (1.5.1) Requirement already satisfied: xcffib>=0.10.1 in /home/ehiffi/.local/lib/python3.11/site-packages (from qtile==0.22.2.dev185+g4ecf1bde) (1.3.0) Requirement already satisfied: pycparser in /usr/lib/python3.11/site-packages (from cffi>=1.1.0->qtile==0.22.2.dev185+g4ecf1bde) (2.21) Building wheels for collected packages: qtile Building wheel for qtile (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for qtile (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [45 lines of output] Failed to find pywlroots. Wayland backend libinput configuration will be unavailable. running bdist_wheel running build running build_py file libqtile/_ffi_pango.py (for module libqtile._ffi_pango) not found file libqtile/backend/x11/_ffi_xcursors.py (for module libqtile.backend.x11._ffi_xcursors) not found running egg_info writing qtile.egg-info/PKG-INFO writing dependency_links to qtile.egg-info/dependency_links.txt writing entry points to qtile.egg-info/entry_points.txt writing requirements to qtile.egg-info/requires.txt writing top-level names to qtile.egg-info/top_level.txt reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'libqtile/_ffi*.py' warning: no previously-included files found matching 'libqtile/backend/x11/_ffi*.py' no previously-included directories found matching 'rpm' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE' writing manifest file 'qtile.egg-info/SOURCES.txt' file libqtile/_ffi_pango.py (for module libqtile._ffi_pango) not found file libqtile/backend/x11/_ffi_xcursors.py (for module libqtile.backend.x11._ffi_xcursors) not found generating cffi module 'build/lib.linux-x86_64-cpython-311/libqtile/_ffi_pango.py' already up-to-date generating cffi module 'build/lib.linux-x86_64-cpython-311/libqtile/backend/x11/_ffi_xcursors.py' already up-to-date running build_ext generating cffi module 'build/temp.linux-x86_64-cpython-311/libqtile.widget._pulse_audio.c' already up-to-date installing to build/bdist.linux-x86_64/wheel running install It looks like your cairocffi was not built with xcffib support. To fix this: - Ensure a recent xcffib is installed (pip install 'xcffib>=0.5.0') - The pip cache is cleared (remove ~/.cache/pip, if it exists) - Reinstall cairocffi, either: pip install --no-deps --ignore-installed cairocffi or pip uninstall cairocffi && pip install cairocffi [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for qtile Failed to build qtile ERROR: Could not build wheels for qtile, which is required to install pyproject.toml-based projects ``` The thing is I have all it needs for it to build! ```shell pip install pywlroots Defaulting to user installation because normal site-packages is not writeable Requirement already satisfied: pywlroots in /usr/lib/python3.11/site-packages (0.15.24) Requirement already satisfied: cffi>=1.12.0 in /usr/lib/python3.11/site-packages (from pywlroots) (1.15.1) Requirement already satisfied: pywayland>=0.4.14 in /usr/lib/python3.11/site-packages (from pywlroots) (0.4.15) Requirement already satisfied: xkbcommon>=0.2 in /usr/lib/python3.11/site-packages (from pywlroots) (0.8) Requirement already satisfied: pycparser in /usr/lib/python3.11/site-packages (from cffi>=1.12.0->pywlroots) (2.21) ``` I work with wayland and its not the actual reason why I want to build qtile! The whole reason is this ```shell qtile start -b wayland Traceback (most recent call last): File "/home/ehiffi/.local/bin/qtile", line 5, in <module> from libqtile.scripts.main import main ModuleNotFoundError: No module named 'libqtile' ``` And all that happened after i tried to update my system! I run Artix Linux with OpenRC. Any help would help ### Required: - [X] I have searched past issues to see if this bug has already been reported.

system · 7 June 2023 18:07

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.