Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upnotify-send parameter --expire-time broken in Qubes #1297
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 8, 2015
Member
Check description of --expire-time parameter - the timeout is in
miliseconds, not seconds. It probably works on your another system,
because notification daemon running there doesn't support this feature
at all. Just curious - what notification daemon you have there?
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Check description of Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Oct 8, 2015
Member
https://packages.debian.org/stretch/libnotify4, I think.
Right. My mistake. Not a bug. Closing.
|
https://packages.debian.org/stretch/libnotify4, I think. Right. My mistake. Not a bug. Closing. |
adrelanos commentedOct 8, 2015
How to reproduce:
notify-send --expire-time 20 test aExpected result:
Show up as on a comparable Debian jessie system.
Actual result:
The passive popup is just showing for a second.
Additional information:
When dropping the
--expire-time 20parameter, it works normal.