https://bugs.kde.org/show_bug.cgi?id=420248

Dennis Schridde <devuran...@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDSINFO                   |REPORTED
         Resolution|WAITINGFORINFO              |---

--- Comment #2 from Dennis Schridde <devuran...@gmx.net> ---
(In reply to David Edmundson from comment #1)
> From your sway session can you run
> 
> qdbus org.kde.kglobalaccel
> 
> and report back
> 
> 1) what it shows
> 2) if it replies immediately or after 30s

❯ time qdbus org.kde.kglobalaccel
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.

________________________________________________________
Executed in   24.92 secs   fish           external
   usr time    8.75 millis  456.00 micros    8.29 millis
   sys time    0.11 millis  106.00 micros    0.00 millis

> it's an interesting case:
>  - kglobalaccell won't work on X
>  - on kwin waland it'll be registered by our compositor
> 
> on sway, I would expect that we:
> start kglobalaccel, exit, reply with an error immediately, but I'm not sure.

❯ pgrep kglobalaccel

Returns no results / non-zero exit status, i.e. there is no process with that
name.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to