Open brandonskiser opened 3 months ago
Thank you for reporting this. We definitely shoudn't panic here so this bug is very valid. However, the solution would involve erroring out or ignoring the non-compliant message (sender header field is supposed to be a unique name and it must start with a :
according to the spec).
When trying to listen for IBus messages on the
"org.freedesktop.IBus.InputContext"
interface, zbus panics because a message is being passed with a sender that isn't a unique name. A sender with something like"org.freedesktop.IBus.InputContext"
is being passed instead, which causes a panic.Here is some code for reference that causes the panic - running this and then focusing out of the terminal causes the panic.
Here is a resulting stack trace