You are not logged in.

#1 2025-05-11 08:32:27

lurenmax
Member
Registered: 2025-05-11
Posts: 2

Application (Most chromium) unclickable when debugging a python app

When I try to debug an python app named moss ( https://github.com/RedTTGMoss/moss-desktop.git ), which uses CEF4pygame and cefpython3, all chromium app will be unclickable.

I use vscode and debugpy to debug moss, and this is my first time debugging a chromium related program.

Clickable Application:

  • Firefox

  • Dolphin

  • kde UI, including the frame around any app

  • Konsole

Unclickable:

  • All chromium based windows (Draw.io, vscode, electron, etc.)

However, unclickable applications can accept keyboard inputs.

> inxi -xxx -S
System:
  Host: archlaptop Kernel: 6.12.26-1-lts arch: x86_64 bits: 64 compiler: gcc
    v: 15.1.1 clocksource: hpet
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_wayland vt: 1 dm:
    1: LightDM v: 1.32.0 note: stopped 2: SDDM Distro: Arch Linux

No any error log.

Any help will be appreciate.

Offline

#2 2025-05-11 08:38:16

lurenmax
Member
Registered: 2025-05-11
Posts: 2

Re: Application (Most chromium) unclickable when debugging a python app

When debugging, `xev` can focus but shows no mouse events.

>xinput list          
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
⎡ Virtual core pointer                          id=2     [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4     [slave  pointer  (2)]
⎜   ↳ xwayland-pointer:10                       id=6     [slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:10              id=7     [slave  pointer  (2)]
⎜   ↳ xwayland-pointer-gestures:10              id=8     [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3     [master keyboard (2)]
    ↳ Virtual core XTEST keyboard   

Normal:

_NET_WM_USER_TIME(CARDINAL) = 352122653
_VARIABLE_REFRESH(CARDINAL) = 1
_NET_WM_ICON(CARDINAL) = 
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 6, 6, 42, 6
_NET_FRAME_EXTENTS(CARDINAL) = 6, 6, 42, 6
_NET_WM_DESKTOP(CARDINAL) = 0
_KDE_NET_WM_ACTIVITIES(STRING) = "cf93b889-6abb-4796-9de7-cca8f2f9ada8"
WM_STATE(WM_STATE):
                window state: Normal
                icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_FOCUSED
XdndAware(ATOM) = BITMAP
_NET_WM_NAME(UTF8_STRING) = "RedTTG Moss"
WM_NAME(UTF-8) = "RedTTG Moss"
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 351099162
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
_NET_WM_BYPASS_COMPOSITOR(CARDINAL) = 1
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_PID(CARDINAL) = 1699055
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLASS(STRING) = "moss.py", "moss.py"
WM_HINTS(WM_HINTS):
                Client accepts input or input focus: True
                window id # of group leader: 0xa2bc325f
WM_NORMAL_HINTS(WM_SIZE_HINTS):
                user specified location: 942, 350
WM_CLIENT_MACHINE(STRING) = "archlaptop"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x1, 0x0, 0x0

When debuging:

> xprop      
xprop: error: Can't grab the mouse.

Last edited by lurenmax (2025-05-11 08:41:09)

Offline

Board footer

Powered by FluxBB

OSZAR »