microsoft / microsoft/wslg

Strange XFCE panel behavior

Open
#41 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
11.9k
Forks
429
PR merge metrics
No merged PRs in 30d

Description

Environment

Windows build number: 21364.1
Your Distribution version: Arch (up to date)
Your WSLg version: 1.0.17.1

Steps to reproduce

When I was using x410 I had set up an xfce4 panel to house all my commonly used GUI apps. I have a script that launches xfce4 panel.

xfce4-panel --sm-client-disable --disable-wm-check &> /dev/null

If I unlock an existing panel and attempt to drag it to a new position on the screen it does not move, though the "drag" icon appears properly.

WSL logs:

weston.log

Expected behavior

I expect the xfce panel to retain its position on launch and be able to be moved when unlocked.

Actual behavior

The panel still appears when launched but its position seems to change every launch and when unlocked and I cannot drag it to a new position.

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the reported xfce4-panel --sm-client-disable --disable-wm-check command and inspect weston.log for panel positioning or input-handling clues. Compare the panel's launch position and unlocked drag behavior against the expected behavior described in the issue; done means the panel retains its position and can be moved when unlocked.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.