-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
notifications regression: NotificationClosed emitted with wrong type #118
Labels
bug
Something isn't working
Comments
The-Compiler
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
May 2, 2022
The-Compiler
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
May 2, 2022
See BuddiesOfBudgie/budgie-desktop#118 (cherry picked from commit a2f7786)
EbonJaeger
added a commit
that referenced
this issue
May 2, 2022
Ref #118 Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
2 tasks
I neglected to realize that enum values are |
JoshStrobl
pushed a commit
that referenced
this issue
May 3, 2022
Ref #118 Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
twigleingrid
pushed a commit
to twigleingrid/qutebrowser
that referenced
this issue
May 13, 2022
serebit
pushed a commit
that referenced
this issue
Jun 11, 2022
Ref #118 Signed-off-by: Evan Maddock <maddock.evan@vivaldi.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When a notification is closed,
NotificationClosed
is emitted withuint32, int32
as arguments (id, reason) while the specification mandates uint32 for both.Budgie version
budgie-desktop 10.6.1
This seems to be a recent regression: On a fresh Solus 4.3 install I can't reproduce, only after a full update.
Operating system
Solus 4.3
Steps to reproduce the issue
dbus-monitor interface=org.freedesktop.Notifications
notify-send foo
in another terminalActual result
Expected result
uint32 2
for both argumentsAdditional information
This currently causes qutebrowser to crash when a notification is closed - will add a workaround there too.
The text was updated successfully, but these errors were encountered: