Skip to content

workspace switch returns "Success" but does not actually dispatch to Hyprland #7

Description

@bivanoid

Description

Running axctl workspace switch <id> returns Success, but Hyprland's active workspace never actually changes. The command appears to be accepted by axctl but is not forwarded to the compositor.

Environment

  • axctl version: v0.0.19
  • Compositor: Hyprland
  • Installed via: Ambxst (binary at /usr/local/bin/axctl)
  • OS: Arch Linux

Steps to Reproduce

  1. Confirm current workspace:
   hyprctl activeworkspace
   # workspace ID 5 (5) on monitor eDP-1
  1. Run axctl switch command:
   axctl workspace switch 2
   # Success
  1. Check Hyprland's actual state again:
   hyprctl activeworkspace
   # still workspace ID 5 (5) on monitor eDP-1 — unchanged
  1. Check axctl's own reported state:
   axctl workspace active
   # still reports id "5", not "2"

Expected Behavior

axctl workspace switch 2 should cause Hyprland to actually switch to workspace 2, and hyprctl activeworkspace / axctl workspace active should both reflect that change.

Actual Behavior

  • Command returns Success with no real effect.
  • Hyprland's active workspace does not change.
  • axctl workspace active continues to report the old workspace, confirming the switch never happened.

Additional Notes

As a sanity check, dispatching directly via Hyprland bypasses the issue entirely and works correctly:

hyprctl dispatch workspace 5
# ok — this actually switches

This confirms Hyprland itself and the compositor config are functioning normally; the issue is isolated to axctl's workspace switch command not forwarding the dispatch.

Also confirmed there is only one axctl daemon and one axctl subscribe process running (pgrep -a axctl), so this isn't caused by a stale/duplicate daemon.

Daemon logs

(please paste any relevant axctl daemon stdout/stderr output here, if available)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions