Description of problem: When using a chat program like mattermost I noticed that notifications arrive at random times and not when they should. I managed to reproduce this with solely notify-send Version-Release number of selected component (if applicable): GNOME Shell 44.rc How reproducible: Always Steps to Reproduce: 1. Run `notify-send Test` to verify that notifications work. Wait for the notification to disappear 2. Run `notify-send Test1 && notify-send Test2` (sic) and observe that only "Test1" is shown. Wait for Test1 to disappear 3. Run `notify-send Test3`. Now Test2 (sic) shows up and Test3 does not show
> 2. Run `notify-send Test1 && notify-send Test2` (sic) and observe that only "Test1" is shown. Wait for Test1 to disappear On my system, Test2 appears immediately, and Test1 is just silently skipped (but it's still visible in a list if you display the calendar+notification top panel). This: $ notify-send Test1 && notify-send Test2 && notify-send Test3 makes me skip Test1, show Test2, and after Test2 disappears, show Test3 immediately. I have: gnome-shell-44~rc-2.fc38.x86_64 By the way, please use the upstream to report these non-Fedora-specific issues, the maintainers are much more responsive there: https://gitlab.gnome.org/GNOME/gnome-shell/
Proposed as a Blocker for 38-final by Fedora user apollo13 using the blocker tracking app because: I think this bug should be considered as a release blocker. Notifications are imo a pretty important aspect of getting notified (reminded) of certain things. Opening the message history (is it called so?) does not seem to be a good workaround since that requires you to know that you missed a notification in the first place (unless you are opening it more often because you know of this bug).
Discussed during the 2023-04-03 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as it was agreed this is just too much of a corner case to constitute a violation of the panel or update notification criteria. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-04-03/f38-blocker-review.2023-04-03-16.01.txt
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Still an issue in Fedora 40.
Because we already have an upstream report, this doesn't seem like a Fedora-specific issue, and there's nothing particular that can be done downstream in Fedora, I'll close this bug as UPSTREAM, and let's follow it there: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6529