Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 757181[details]
reproducer
Description of problem:
When running the attached script the notification hides after roughly five seconds (which is default, right?). Using Ctrl-C (and obtained time measurement) I can clearly see that the script runs more than 5s and less than 12s even after the notifications hides.
From looking at gnome-shell/us/js/notificationDaemon.js it seems to me that the timeout parameter is on line 412 assigned to ndata object, but I cannot find anywhere in the rest of gnome-shell that this parameter would be used (the code of messageTray.js is so convoluted, that I am not sure I haven't lost it somewhere though).
Version-Release number of selected component (if applicable):
libnotify-0.7.5-5.el7.x86_64
gnome-shell-3.8.2-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.run the attached script
2.
3.
Actual results:
notification hides after roughly 5s
Expected results:
it should hide exactly (more or less) after 12s
Additional info:
I also see https://bugzilla.gnome.org/show_bug.cgi?id=658189, but that's against notification-daemon, which is now dead, AFAIK. Is it that the problem just got transferred with rewrite of notification-daemon into Javascript?
Created attachment 757181 [details] reproducer Description of problem: When running the attached script the notification hides after roughly five seconds (which is default, right?). Using Ctrl-C (and obtained time measurement) I can clearly see that the script runs more than 5s and less than 12s even after the notifications hides. From looking at gnome-shell/us/js/notificationDaemon.js it seems to me that the timeout parameter is on line 412 assigned to ndata object, but I cannot find anywhere in the rest of gnome-shell that this parameter would be used (the code of messageTray.js is so convoluted, that I am not sure I haven't lost it somewhere though). Version-Release number of selected component (if applicable): libnotify-0.7.5-5.el7.x86_64 gnome-shell-3.8.2-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.run the attached script 2. 3. Actual results: notification hides after roughly 5s Expected results: it should hide exactly (more or less) after 12s Additional info: