Limit Notification-Popups

[GammaSQ]

The problem you're addressing (if any)

I recently edited my policies to disallow previously open ports. A VM was still using those ports. The result was that my whole screen was immediately flooded by notifications of port-access being blocked. This happened quickly enough, that it was hard to even hit certain buttons under notifications.

The solution you'd like

Some limit on notifications. This might be limiting notifications to a screen area, a maximum number, a (screen-size-dependent) maximum frequency, or similar.

(Personally, having a "notification area" I could easily reposition when I need more visibility would be awesome.)

In my particular case, just binning identical notifications would have worked, but I can easily imagine a scenario where lots of different notifications pop up.

The value to a user, and who that user might be

not / not as easily being overwhelmed by notifications.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

[marmarek]

That's up to the notification daemon, but I'm not sure if the one in XFCE supports such configuration. The one in KDE does.

But also, you can use deny notify=no in the policy instead of just deny to avoid notifications about specific calls.

[GammaSQ]

I've looked through the XFCE-options and there is no (obvious?) limit. (not entirely true: apparently it only ever fills one screen)

Not sure if policy-notifications are the only thing that might overwhelm the screen. I know there are some non-disappearing notifications which can have a similar effect. Anyway, deny notify=no would only help in my particular case, there should be a way to handle sudden, unexpected notification-floods.

[3hhh]

This is an upstream XFCE bug / feature request imho.

If you don't like the XFCE behaviour, you are free to switch to the KDE notification daemon or e.g. use independent notification daemons such as dunst.

[github-actions]

This issue has been closed as an "upstream issue." This means that the issue pertains to software that does not belong to the Qubes OS Project and that we do not develop or control. We suggest that you file this issue in the appropriate project's issue tracker instead. For more information, see Why don't you fix upstream bugs that affect Qubes OS?

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "upstream issue" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.