gnome-shell issueshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues2024-03-28T15:28:26Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6059GNOME shell freeze with Nautilus "Sushi" (spacebar) preview triggering a GNOM...2024-03-28T15:28:26ZHubert FiguièreGNOME shell freeze with Nautilus "Sushi" (spacebar) preview triggering a GNOME Software notification
### Affected version
Fedora Silverblue 36
42.3.1-1.fc36
### Bug summary
GNOME Shell freeze for a while (several minutes on a Core i7 machine) and then keep an unclosable notification.
![image](/uploads/77bd9dfd400421822c89582611866...
### Affected version
Fedora Silverblue 36
42.3.1-1.fc36
### Bug summary
GNOME Shell freeze for a while (several minutes on a Core i7 machine) and then keep an unclosable notification.
![image](/uploads/77bd9dfd400421822c89582611866452/image.png)
### Steps to reproduce
1. Open nautilus.
2. Select a `.odt` file (LibreOffice)
3. Press "space".
### What happened
GNOME Shell freeze for a while then display the notification above that can't be closed. See screenshot above. Not that it appeared in the top left corner, then moved in the top middle where it is supposed to be.
With `journalctl -r` I got the following (note the timestamps):
```
Nov 06 23:21:47 rocinante systemd-journald[722]: [π‘] Suppressed 10859 messages from user@1000.service
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
[... supresssed a few hundreds of of these ...]
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: The offending signal was handle-method-call on GjsDBusImplementation 0x560cf6fead20.
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
[...]
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying>
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:08 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
[...]
Nov 06 23:21:08 rocinante gnome-shell[1792]: The offending signal was handle-method-call on GjsDBusImplementation 0x560cf6fead20.
Nov 06 23:21:08 rocinante gnome-shell[1792]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying>
Nov 06 23:21:08 rocinante gnome-shell[1792]: The offending signal was handle-method-call on GjsDBusImplementation 0x560cf6fead20.
Nov 06 23:21:08 rocinante gnome-shell[1792]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying>
[... suppressed 15 thousands log lines ...]
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b371b0 I resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387 (996662cdba0 @ 34)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:769 (38bb3ef56510 @ 148)
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: #6 7ffdf7b371b0 I resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387 (996662cdba0 @ 34)
Nov 06 23:21:05 rocinante gnome-shell[1792]: The offending signal was notification-added on Gjs_ui_notificationDaemon_GtkNotificationDaemonAppSource 0x560d0e>
Nov 06 23:21:05 rocinante gnome-shell[1792]: #5 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante systemd-journald[722]: [π‘] Suppressed 183377 messages from user@1000.service
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:763 (38bb3ef56510 @ 30)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:758 (38bb3ef564c0 @ 272)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:695 (38bb3ef561f0 @ 22)
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: #6 7ffdf7b371b0 I resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387 (996662cdba0 @ 34)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #5 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:763 (38bb3ef56510 @ 30)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:758 (38bb3ef564c0 @ 272)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:695 (38bb3ef561f0 @ 22)
[...]
Nov 06 23:21:05 rocinante gnome-shell[1792]: The offending signal was notification-added on Gjs_ui_notificationDaemon_GtkNotificationDaemonAppSource 0x560d0e>
Nov 06 23:21:05 rocinante gnome-shell[1792]: #5 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante systemd-journald[722]: [π‘] Suppressed 183377 messages from user@1000.service
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:763 (38bb3ef56510 @ 30)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:758 (38bb3ef564c0 @ 272)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:695 (38bb3ef561f0 @ 22)
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: #6 7ffdf7b371b0 I resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387 (996662cdba0 @ 34)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #5 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:763 (38bb3ef56510 @ 30)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:758 (38bb3ef564c0 @ 272)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:695 (38bb3ef561f0 @ 22)
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: #5 7ffdf7b371b0 I resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387 (996662cdba0 @ 34)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #4 7ffdf7b37160 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354 (996662cda60 @ 945)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #3 7ffdf7b37050 I resource:///org/gnome/shell/ui/notificationDaemon.js:761 (1c00583b6f10 @ 580)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #2 7ffdf7b36fe0 I resource:///org/gnome/shell/ui/notificationDaemon.js:640 (1c00583b6b00 @ 197)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #1 7ffdf7b36f70 I resource:///org/gnome/shell/ui/messageTray.js:763 (38bb3ef56510 @ 30)
Nov 06 23:21:05 rocinante gnome-shell[1792]: #0 7ffdf7b36f30 I resource:///org/gnome/shell/ui/messageTray.js:756 (38bb3ef564c0 @ 257)
Nov 06 23:21:05 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:21:05 rocinante gnome-shell[1792]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying>
Nov 06 23:21:05 rocinante systemd-journald[722]: [π‘] Suppressed 236282 messages from user@1000.service
```
I lost where it started
If I try to close the notification mentioned above, I get this messages in journalctl:
```
Nov 06 23:26:49 rocinante gnome-shell[1792]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x560d183a8940), has been already disposed >
Nov 06 23:26:49 rocinante gnome-shell[1792]: #3 560d0e5ef0d8 i self-hosted:1178 (996662b0a10 @ 454)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #2 560d0e5ef1a0 i resource:///org/gnome/shell/ui/messageList.js:393 (38bb3ef5cec0 @ 22)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #1 560d0e5ef230 i resource:///org/gnome/shell/ui/calendar.js:754 (38bb3ef5ba10 @ 64)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #0 560d0e5ef2b8 i resource:///org/gnome/shell/ui/messageTray.js:494 (38bb3ef55a10 @ 84)
Nov 06 23:26:49 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:26:49 rocinante gnome-shell[1792]: #3 560d0e5ef0d8 i self-hosted:1178 (996662b0a10 @ 454)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #2 560d0e5ef1a0 i resource:///org/gnome/shell/ui/messageList.js:393 (38bb3ef5cec0 @ 22)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #1 560d0e5ef230 i resource:///org/gnome/shell/ui/calendar.js:754 (38bb3ef5ba10 @ 64)
Nov 06 23:26:49 rocinante gnome-shell[1792]: #0 560d0e5ef2b8 i resource:///org/gnome/shell/ui/messageTray.js:493 (38bb3ef55a10 @ 69)
Nov 06 23:26:49 rocinante gnome-shell[1792]: == Stack trace for context 0x560cf668b630 ==
Nov 06 23:26:49 rocinante gnome-shell[1792]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x560d183a8940), has been already disposed >
```
### What did you expect to happen
Either nothing, or a preview.
### Relevant logs, screenshots, screencasts etc.
See above.
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/753Inconsistent ellipsizing vs expandable line height behavior for notifications2024-03-27T06:39:44ZPhilip Gotophilip.goto@gmail.comInconsistent ellipsizing vs expandable line height behavior for notificationsI recently tried to use notifications including their buttons/actions in an app, and I was surprised at the unnatural behavior of them. I think there are a lot of things that could be improved regarding notifications. Here are two potent...I recently tried to use notifications including their buttons/actions in an app, and I was surprised at the unnatural behavior of them. I think there are a lot of things that could be improved regarding notifications. Here are two potential improvements that come to mind, which are inspired by Android/Windows notification system.
- When a notification moves from a peek/popup to the notification tray, it becomes fixed in height. This means the text is cut off and the actions disappear. I don't see any reason to do this, and I think they should be expanded in the tray so you are still able to fully read and interact with the notification might you have missed it in the first few seconds of showing.
- Some parts of the notification only appear on hovering it, like the dismiss icon and the actions in peek mode. This means you don't know you can interact with a notification until you hover it and also means they become frustratingly unusable on a touchscreen-enabled device. Always displaying these actions and the dismiss icon would fix both these issues and have very little drawback IMO.
The images below should illustrate my points a bit.
![notify_peek_nohover](/uploads/411201002adca76a441e867fb032b7e6/notify_peek_nohover.png)
*Peeking notification, unclear this notification has actions*
![notify_peek_hover](/uploads/b114d0992d65359266a29a976dfedffa/notify_peek_hover.png)
*Hovering the peeking notification, this looks fine*
![notify_tray](/uploads/4265a74cda29ef4170478a1eb42affa1/notify_tray.png)
*Hovering the notification in the tray, actions are unusable and full text unreadable*https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4831Pictures in notification centre does not have correct aspect ratio2024-03-26T21:55:18ZCrist YePictures in notification centre does not have correct aspect ratio<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
-->
3.36.8 on Ubuntu 20.04.3 LTS (X11)
### Bug summary
The aspect ratio is wrong for pictures in notifications. It's just ugly.
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
Open https://www.youtube.com/watch?v=saDmN2f3HI0 with Firefox. A notification will be shown for the music playing. The URL of the picture can be obtained from
```
navigator.mediaSession.metadata.artwork[0].src
"https://i.ytimg.com/vi/saDmN2f3HI0/hqdefault.jpg?sqp=-oaymwEβ¦4IARUAAIhCGAFwAcABBg==&rs=AOn4CLCr72fHXKiKW_YZqML-sHC685QmMw"
```
<!--
1. Step one
2. Step two
3. ...
-->
### What happened
The picture's aspect ratio is not respected:
![image](/uploads/7e6653f1284d4037fc2b1f5b640a17d8/image.png)
<!--
What did GNOME Shell do that was unexpected?
-->
### What did you expect to happen
The picture should preserve its aspect ratio instead of being stretched to 1:1
<!--
What did you expect GNOME Shell to do?
-->
### Relevant logs, screenshots, screencasts etc.
(see above)
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7303Notifications with long, elided titles need tooltips2024-03-26T21:20:41ZFederico Mena QuinteroNotifications with long, elided titles need tooltips![notif](/uploads/d848de69b21636bdff1b7d4c3ac51f03/notif.jpg)
E.g. the "Kingston DataTraveler 3.0 can..." above - it says "can be removed" but there's no way to read the extra text. Could we have a tooltip there?![notif](/uploads/d848de69b21636bdff1b7d4c3ac51f03/notif.jpg)
E.g. the "Kingston DataTraveler 3.0 can..." above - it says "can be removed" but there's no way to read the extra text. Could we have a tooltip there?https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/358"<Application> is ready" middleman notifications2024-03-26T17:12:49ZBrian Zwahr"<Application> is ready" middleman notificationsSometimes when I get a notification, for instance if I get an email and Evolution notifies me, when I click on the notification, it opens a second "Evolution is ready" notification. I have to click on that second notification to actually...Sometimes when I get a notification, for instance if I get an email and Evolution notifies me, when I click on the notification, it opens a second "Evolution is ready" notification. I have to click on that second notification to actually get to the application/content. This also happens with Firefox notifications and others.
Why does this happen? I'm assuming there's a reason for the "<Application> is ready" middleman notifications, but I can't figure out what that reason would be.
Someone mentioned that those are supposed to happen when the program is closed, in which case the program opens behind your current window then lets you know that it is open and ready to use. However:
1) This is happening to me with programs that are already open.
2) If I'm clicking on a notification, I don't want whatever action it takes to be in the background. I want to be taken directly to that content or program.
The only other thought I had was maybe this was happening with programs that are open by hidden with Super-h. That is not the case, though, as Firefox and Evolution aren't hidden when they produce this behavior.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7477Notification on opening links in Firefox is not activatable and can't be clos...2024-03-17T15:35:43Zdarkblaze69Notification on opening links in Firefox is not activatable and can't be closed with X* OS: Arch Linux
* GNOME 46.rc
* mutter 46.rc at a66b4c3da9
* gnome-shell 46.rc at 05c44b546
Notification on opening links in Firefox is not activatable and can't be closed with X. On clicking the notification the error is logged:
```
...* OS: Arch Linux
* GNOME 46.rc
* mutter 46.rc at a66b4c3da9
* gnome-shell 46.rc at 05c44b546
Notification on opening links in Firefox is not activatable and can't be closed with X. On clicking the notification the error is logged:
```
Mar 12 18:20:29 gnome-shell[239115]: JS ERROR: TypeError: this.notification is null
vfunc_clicked@resource:///org/gnome/shell/ui/calendar.js:812:9
@resource:///org/gnome/shell/ui/init.js:21:20
```
Steps to reproduce:
1. Open Firefox
2. Open a terminal in foreground
3. Emulate opening a link from an app by running in terminal `xdg-open https://anysite.com`
4. Notification will appear, it can't be closed by X or clicked to activate the browser.
![Screencast_from_2024-03-12_18-18-13](/uploads/2d2b06e2ea2c353d0255abb2fd2f106a/Screencast_from_2024-03-12_18-18-13.webm)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7463Empty notification banner2024-03-13T11:39:37ZJulian Sparberjulian@sparber.netEmpty notification banner<!--
Please read https://gitlab.gnome.org/GNOME/gnome-shell/-/tree/main#reporting-bugs
first to ensure that you create a clear and specific issue.
-->
### Affected version
nested GNOME Shell build from [main](https://gitlab.gnome.org/GN...<!--
Please read https://gitlab.gnome.org/GNOME/gnome-shell/-/tree/main#reporting-bugs
first to ensure that you create a clear and specific issue.
-->
### Affected version
nested GNOME Shell build from [main](https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/4a81099ff2babd8ffbd61fcff703f0a97e77b4ae) in toolbox using Wayland
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://release.gnome.org/calendar/
for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
Some times notifications don't show any content.
![image](/uploads/0817d12d6ac6078ed77dd17cccf52393/image.png)
### Steps to reproduce
1. Make an app show more then 3 (or maybe a few more) notifications
2. See empty notification banner like in the screenshot
### What happened
The banner doesn't show anything other then the title.
### What did you expect to happen
That the banner shows the content of the notification
### Relevant logs, screenshots, screencasts etc.
<details><summary>Click to expand the log </summary>
```
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to connect to any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a7a0 b resource:///org/gnome/shell/misc/signalTracker.js:233 (3fb5ec886100 @ 204)
#1 7ffde6d1a8e0 b resource:///org/gnome/shell/misc/signalTracker.js:239 (2bf1399aa420 @ 513)
#2 7ffde6d1a9d0 b resource:///org/gnome/shell/ui/environment.js:246 (94ca7771bf0 @ 126)
#3 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:780 (32728433d420 @ 132)
#4 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#5 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#6 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#7 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#8 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#9 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to connect to any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a7a0 b resource:///org/gnome/shell/misc/signalTracker.js:233 (3fb5ec886100 @ 204)
#1 7ffde6d1a8e0 b resource:///org/gnome/shell/misc/signalTracker.js:239 (2bf1399aa420 @ 513)
#2 7ffde6d1a9d0 b resource:///org/gnome/shell/ui/environment.js:246 (94ca7771bf0 @ 126)
#3 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:780 (32728433d420 @ 132)
#4 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#5 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#6 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#7 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#8 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#9 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to connect to any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a7a0 b resource:///org/gnome/shell/misc/signalTracker.js:233 (3fb5ec886100 @ 204)
#1 7ffde6d1a8e0 b resource:///org/gnome/shell/misc/signalTracker.js:239 (2bf1399aa420 @ 513)
#2 7ffde6d1a9d0 b resource:///org/gnome/shell/ui/environment.js:246 (94ca7771bf0 @ 126)
#3 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:780 (32728433d420 @ 132)
#4 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#5 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#6 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#7 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#8 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#9 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to connect to any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a710 b resource:///org/gnome/shell/misc/signalTracker.js:89 (3272843f6330 @ 54)
#1 7ffde6d1a7e0 b resource:///org/gnome/shell/misc/signalTracker.js:60 (3272843eae20 @ 73)
#2 7ffde6d1a8e0 b resource:///org/gnome/shell/misc/signalTracker.js:244 (2bf1399aa420 @ 609)
#3 7ffde6d1a9d0 b resource:///org/gnome/shell/ui/environment.js:246 (94ca7771bf0 @ 126)
#4 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:780 (32728433d420 @ 132)
#5 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#6 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#7 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#8 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#9 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#10 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:789 (32728433d420 @ 177)
#1 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#2 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#3 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#4 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#5 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#6 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Wrapper for GObject 0x564c97dd0d40 was disposed, cannot get property title
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:792 (32728433d420 @ 222)
#1 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#2 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#3 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#4 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#5 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#6 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Wrapper for GObject 0x564c97dd0d40 was disposed, cannot get property body
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:795 (32728433d420 @ 267)
#1 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#2 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#3 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#4 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#5 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#6 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Wrapper for GObject 0x564c97dd0d40 was disposed, cannot get property use-body-markup
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:798 (32728433d420 @ 312)
#1 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#2 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#3 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#4 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#5 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#6 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Wrapper for GObject 0x564c97dd0d40 was disposed, cannot get property datetime
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1aaf0 b resource:///org/gnome/shell/ui/calendar.js:801 (32728433d420 @ 357)
#1 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1105 (327284334b50 @ 205)
#2 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#3 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#4 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#5 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#6 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:20 pika gnome-shell[2307]: Wrapper for GObject 0x564c97dd0d40 was disposed, cannot get property gicon
mars 06 14:23:20 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a6f0 b resource:///org/gnome/gjs/modules/core/_common.js:38 (3fb5ec89d7e0 @ 70)
#1 564c9722fba0 i resource:///org/gnome/shell/ui/messageTray.js:1136 (327284334ba0 @ 18)
#2 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1116 (327284334b50 @ 382)
#3 7ffde6d1b5a0 b resource:///org/gnome/shell/ui/messageTray.js:1059 (327284334a60 @ 563)
#4 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1239 (327284334d80 @ 54)
#5 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#6 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#7 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:24 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a110 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:702 (3fb5ec89d240 @ 25)
#1 7ffde6d1a1d0 b resource:///org/gnome/shell/misc/signalTracker.js:127 (94ca77219c0 @ 21)
#2 7ffde6d1a2a0 b resource:///org/gnome/shell/misc/signalTracker.js:172 (94ca77411a0 @ 35)
#3 7ffde6d1a3a0 b self-hosted:203 (3fb5ec897ab0 @ 245)
#4 7ffde6d1a460 b resource:///org/gnome/shell/misc/signalTracker.js:171 (94ca773fce0 @ 135)
#5 7ffde6d1a510 b resource:///org/gnome/shell/misc/signalTracker.js:123 (94ca7721470 @ 17)
#6 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1254 (327284334dd0 @ 181)
#7 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1238 (327284334d80 @ 38)
#8 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#9 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#10 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:24 pika gnome-shell[2307]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
mars 06 14:23:24 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a110 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:702 (3fb5ec89d240 @ 25)
#1 7ffde6d1a1d0 b resource:///org/gnome/shell/misc/signalTracker.js:127 (94ca77219c0 @ 21)
#2 7ffde6d1a2a0 b resource:///org/gnome/shell/misc/signalTracker.js:172 (94ca77411a0 @ 35)
#3 7ffde6d1a3a0 b self-hosted:203 (3fb5ec897ab0 @ 245)
#4 7ffde6d1a460 b resource:///org/gnome/shell/misc/signalTracker.js:171 (94ca773fce0 @ 135)
#5 7ffde6d1a510 b resource:///org/gnome/shell/misc/signalTracker.js:123 (94ca7721470 @ 17)
#6 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1254 (327284334dd0 @ 181)
#7 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1238 (327284334d80 @ 38)
#8 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#9 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#10 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:24 pika gnome-shell[2307]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
mars 06 14:23:24 pika gnome-shell[2307]: Object .Gjs_ui_notificationDaemon_GtkNotificationDaemonNotification (0x564c97dd0d40), has been already disposed β impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
== Stack trace for context 0x564c97169640 ==
#0 7ffde6d1a110 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:702 (3fb5ec89d240 @ 25)
#1 7ffde6d1a1d0 b resource:///org/gnome/shell/misc/signalTracker.js:127 (94ca77219c0 @ 21)
#2 7ffde6d1a2a0 b resource:///org/gnome/shell/misc/signalTracker.js:172 (94ca77411a0 @ 35)
#3 7ffde6d1a3a0 b self-hosted:203 (3fb5ec897ab0 @ 245)
#4 7ffde6d1a460 b resource:///org/gnome/shell/misc/signalTracker.js:171 (94ca773fce0 @ 135)
#5 7ffde6d1a510 b resource:///org/gnome/shell/misc/signalTracker.js:123 (94ca7721470 @ 17)
#6 564c9722fae8 i resource:///org/gnome/shell/ui/messageTray.js:1254 (327284334dd0 @ 181)
#7 564c9722fa68 i resource:///org/gnome/shell/ui/messageTray.js:1238 (327284334d80 @ 38)
#8 7ffde6d1c010 b resource:///org/gnome/shell/ui/environment.js:67 (32728436e920 @ 98)
#9 7ffde6d1c0c0 b resource:///org/gnome/shell/ui/environment.js:154 (94ca7735510 @ 14)
#10 564c9722f9d8 i resource:///org/gnome/shell/ui/init.js:21 (3fb5ec870bf0 @ 48)
mars 06 14:23:24 pika gnome-shell[2307]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
```
</details>
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/32Notifications should show action buttons when only touch devices are present2024-03-04T15:33:44ZChristian HergertNotifications should show action buttons when only touch devices are presentIf you have a `GNotification` to display and it has actions associated with it, there is no way to activate the actions unless you have a mouse to hover over the notification.
As you can imagine, this is problematic on tablet-like devic...If you have a `GNotification` to display and it has actions associated with it, there is no way to activate the actions unless you have a mouse to hover over the notification.
As you can imagine, this is problematic on tablet-like devices.
(This is currently an issue for me with https://gitlab.gnome.org/chergert/deviced where we need to be able accept an incoming controller connection from a notification on a tablet.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7099Replacing notification does remove buttons2024-03-03T01:44:55ZJulian Sparberjulian@sparber.netReplacing notification does remove buttons<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version (see https://wiki.gnome.org/Schedule for currently supported versions)
* Does this issue appear in XOrg and/or Wayland
* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
- GNOME 44 (Fedora 38) and `main` (Fedora 39) without any extensions
- Wayland
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. Send a notification to GNOME Shell via FDO API (see command below)
2. Send second notification replacing the notification of step one to GNOME Shell via FDO API (see command below)
3. Hover notification to show buttons of the banner. You will notice that there aren't any
Use the following command to send the notification.
Replace `REPLACE_ID` with `0` for the first call and with the return value from the first call for the second notification.
```
gdbus call --session --dest org.freedesktop.Notifications \
--object-path /org/freedesktop/Notifications \
--method org.freedesktop.Notifications.Notify \
app_name \
REPLACE_ID \
app_icon \
"Message" "Body" \
"['0', 'app.something']" \
"{}" \
1
```
### What happened
GNOME Shell doesn't display any buttons in the notification banner when hovered after a notification got replaced
### What did you expect to happen
GNOME Shell should display buttons in the notification banner when hovered even when a notification got replaced
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
![Screencast_from_2023-10-13_18-16-17](/uploads/b00ba832201df5ca109d062f8256d814/Screencast_from_2023-10-13_18-16-17.webm)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7409ActivateAction calls from clicking on notifications always provide an invalid...2024-02-28T13:48:32ZMikkel HansenActivateAction calls from clicking on notifications always provide an invalid desktop-startup-id<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Software Information:
- **Distro:** Fedora Linux 39.202...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Software Information:
- **Distro:** Fedora Linux 39.20240216.0 (Silverblue)
- **Arch:** 64-bit
- **GNOME-version:** 45.4
- **Window System:** Wayland
- **Kernel Version:** Linux 6.7.4-200.fc39.x86_64
- **mutter:** 45.4
- **gnome-shell:** 45.4
- **xdg-desktop-portal:** 1.18.2
- **xdg-desktop-portal-gnome:** 45.1
- **Fractal:** 6
- **Gtk used by fractal:** 4.12.4 (Wayland backend)
### Bug summary
When you click on a notification in shell, an `ActivateAction` call is made to the application of origin.
However the whilst the action is correctly activated, the application can't raise it's window as the `desktop-startup-id` provided by the dbus call is always `"_TIME0"`.
### Steps to reproduce
1. Open Fractal from flathub
2. Wait for a notification to appear
3. Start monitoring the session bus using bustle
4. Click on notification in the notification tray
5. Fractal does not present itself
6. The `ActivateAction` call sent to Fractal reads:
```
("show-room", [<("f73f8cad-7f2c-4419-b657-1085d6960f74", "!RfXaBjokqHAbzZrgHz:matrix.org")>], {"desktop-startup-id": <"_TIME0">})
```
### What happened
The `desktop-startup-id` sent along with the `ActivateAction` dbus call is always `"_TIME0"`.
I believe this has a hand in: https://gitlab.gnome.org/GNOME/gtk/-/issues/5239
### What did you expect to happen
Provide a `desktop-startup-id` or `activation-token` that can be used to present an application's window.
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1050Notifications shown for an online account (Nextcloud) on every resume2024-02-23T15:16:04ZAllan DayNotifications shown for an online account (Nextcloud) on every resumeEvery time my machine resumes from suspend, I get a notification for my cloud.gnome.org account. This is obviously pretty annoying, since it's just unnecessary noise. To make the situation worse, the notifications are mostly blank, and t...Every time my machine resumes from suspend, I get a notification for my cloud.gnome.org account. This is obviously pretty annoying, since it's just unnecessary noise. To make the situation worse, the notifications are mostly blank, and they persist in the notification list, so it ends up being swamped by them.
They look like this:
![image](/uploads/76c005d89f60b0199735850d4192dc31/image.png)
We probably shouldn't show these notifications at all.GNOME 42https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2134Notification bubble: large icons look weird2024-02-14T15:22:01ZTobias BernardNotification bubble: large icons look weirdThe CSS rework makes the icon on notifications larger, which looks pretty odd, primarly because
- the icon draws a lot of attention, even though it doesn't carry much/any information in most cases
- we use symbolics here, which are spec...The CSS rework makes the icon on notifications larger, which looks pretty odd, primarly because
- the icon draws a lot of attention, even though it doesn't carry much/any information in most cases
- we use symbolics here, which are specifically designed for 16 and don't always look good larger
- if we use a larger size, we might as well use non-symbolics icons
![image](/uploads/6cac8be4583cf1a9a54d38f6237a856f/image.png)
That said, the current layout with the icon in the upper left and whitespace below was better in this sense, but worse in that the whitespace on the left made it look a bit off-balance.
![image](/uploads/820cd08b3f029ee67f68a7df46b7e099/image.png)
I think we should either
1. keep the larger icon but switch to non-symbolic icons
2. keep the symbolic but make it 16px again
If we go with 2 I'd also maybe change the layout to avoid the whitespace on the left below the icon, e.g. like so (obviously with cleaned-up spacing):
![image](/uploads/1ac3e3ca48c2a6bcd3dcf29ea362dbe7/image.png)
cc @snwh @jimmachttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7302Notification for removed media gets obsolete easily2024-02-09T13:13:07ZFederico Mena QuinteroNotification for removed media gets obsolete easily![notif](/uploads/d62c4d94a3b4ef7d81114ec1e1e50c9a/notif.jpg)
"Device can be removed"... from "4 weeks ago" - I already did that! :smiley:
Can we remove those notifications when the media is actually removed?![notif](/uploads/d62c4d94a3b4ef7d81114ec1e1e50c9a/notif.jpg)
"Device can be removed"... from "4 weeks ago" - I already did that! :smiley:
Can we remove those notifications when the media is actually removed?https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3330Ability to set Do Not Disturb mode for a set amount of time, and/or automatic...2024-01-31T18:35:01ZJeff FortinAbility to set Do Not Disturb mode for a set amount of time, and/or automatically based on times of the dayThis is kind of the spiritual follow-up to @BrainBlasted's issue #239 (in which @aday was also commenting quite a bit). It's nice that we have a DnD mode toggle in GNOME Shell now, unfortunately the fact that it gets toggled "until you t...This is kind of the spiritual follow-up to @BrainBlasted's issue #239 (in which @aday was also commenting quite a bit). It's nice that we have a DnD mode toggle in GNOME Shell now, unfortunately the fact that it gets toggled "until you toggle it off" does not match my workflow, or rather, my total lack of awareness about having toggled it on. I _know_ that I'll forget to toggle it off some hours later, and therefore I have a mental block on using it at all because I don't trust myself to turn it back on.
To compensate my human weaknesses, I would like two features, to cater for two types of scenarios:
1. Ability to turn it on for a set amount of time (either by setting "Turn on Do Not Disturb until [enter hh:mm here, with various syntaxes supported, taking 17h for example: 17, 17:00, 17h, 1700, etc.] ", or by also offering time presets). But I do think that allowing the user to just set the end time directly is easier both from a technical implementation and from a UI design perspective, than offering a gazillion presets like 15, 30, 45, 60, 90, 120 mins etc. This is the "I don't want distractions while I'm working" usecase/scenario.
2. Ability for it to turn itself on and off at set times of the day (phones in particular have had the ability to turn off notifications from evening to morning). This is the "I want to sleep or not to look at work" usecase/scenario.
Even if I only had feature no.1, that would already be a significant improvement for me to be able to make use of the feature, so I consider it more important. Feature no.2 is also extremely attractive to me, but still "icing on the cake" and I can live longer without it if I have feature no1.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7248RFE: Visually highlight Do Not Disturb mode in top-panel2024-01-31T18:27:25ZPete GoodallRFE: Visually highlight Do Not Disturb mode in top-panel<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
When I enable Do Not Distrub mode I get an icon next to the cl...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
When I enable Do Not Distrub mode I get an icon next to the clock - which is great - but because it is the same colour as the clock text I don't often notice it. Therefore, I enable DnD during a meeting, forget it is enabled, and realise a few hours later that I'm not getting any notifications. It would catch my attention more if it was another colour.
### How would you like it to work
It would catch my attention more if it was another colour. I would suggest red, but I know that can be problematic for people that are colour blind. That being said, I _think_ that even those with colour blindness could differentiate between black and another colour (though I'm not an A11y expert).
### Relevant links, screenshots, screencasts etc.
Nothing more right now, but please let me know if you need more info.
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7153Light style: notifications and calendar/clock/weather cards should be lighter2024-01-09T17:57:42ZCassidy James BlaedeLight style: notifications and calendar/clock/weather cards should be lighterNotification bubbles and the cards with calendar events, world clocks, and the weather in the menu feel like they should be lighter than the background behind them instead of darker than the background. I think the current style is the s...Notification bubbles and the cards with calendar events, world clocks, and the weather in the menu feel like they should be lighter than the background behind them instead of darker than the background. I think the current style is the same as buttons which in the dark style are always lighter than the background, so this has been inverted; but in the light style, we'd typically keep these elements lighter than their background.
Light | Dark
----- | ----
![Screenshot_from_2023-10-31_15-11-54](/uploads/f3d18aa74f5918fc08da799e6137d3b9/Screenshot_from_2023-10-31_15-11-54.png) | ![Screenshot_from_2023-10-31_15-23-42](/uploads/cafd3a598683f1e07f1995a4cf939e80/Screenshot_from_2023-10-31_15-23-42.png)
For reference, below is Adwaita's styling for regular **buttons** and **cards**. This might require adding something like a class `.card` or `.raised` to these elements to distinguish them from other interactive widgets, but that's up to whoever implements it, I guess. :)
Light | Dark
----- | ----
![Adwaita buttons in light style](/uploads/5fef6b2db5b475b3015015566c48af51/Screenshot_from_2023-10-31_15-20-20.png) | ![Adwaita buttons in dark style](/uploads/09dc10cec8e9daffd7520350b591df67/Screenshot_from_2023-10-31_15-22-43.png)
![Adwaita cards in light style](/uploads/27cb1d9d15150ae83699a155c9c494b5/Screenshot_from_2023-10-31_15-20-27.png) | ![Adwaita cards in dark style](/uploads/7141cf7dd1e8cdc09aa38ae90332512b/Screenshot_from_2023-10-31_15-22-38.png)Sam Hewittsnwh@gnome.orgSam Hewittsnwh@gnome.orghttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/102message-tray: new messages moving older ones down can result in possible misc...2023-10-19T01:18:01ZXavier Johnsonmessage-tray: new messages moving older ones down can result in possible misclicksBecause the message-tray places newer notifications above older ones, any existing messages get pushed down when a new one appears. This can result in accidentally clicking on the wrong message. The below video shows a contrived example ...Because the message-tray places newer notifications above older ones, any existing messages get pushed down when a new one appears. This can result in accidentally clicking on the wrong message. The below video shows a contrived example of this happening:
![message-tray-order](/uploads/a994cd042ac8abc0d08679ee644ab06c/message-tray-order.ogv)
If new messages were placed at the bottom of the list, existing messages would stay where they are, and this scenario would never happen. Unless it violates other UX principles of Gnome Shell, placing new messages at the bottom should be considered, or at least an option to sort them that way should be provided.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6650Simple selecting date will destroy the UI of the calendar2023-04-30T13:56:41ZAayush ShresthaSimple selecting date will destroy the UI of the calendarWe have an issue while clicking any date in calendar after clicking it destroy the UI of the calendar. Where as it should shows the events of that selected date
![Screenshot_from_2023-04-30_10-15-23](/uploads/92f5b9d1c44814ed83eef450e9d4...We have an issue while clicking any date in calendar after clicking it destroy the UI of the calendar. Where as it should shows the events of that selected date
![Screenshot_from_2023-04-30_10-15-23](/uploads/92f5b9d1c44814ed83eef450e9d49245/Screenshot_from_2023-04-30_10-15-23.png)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2890Allow expanding notifications to show full text2023-02-01T07:21:57ZLyubomirAllow expanding notifications to show full text<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
Currently notifications that just came can be hovered to show f...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Feature summary
Currently notifications that just came can be hovered to show full text. Once a notification is gone to the Popup notifications list that is shown on click of clock, the whole content cannot be seen anymore. I propose to allow that.
<!--
Describe what you would like to be able to do with GNOME Shell
that you currently cannot do.
-->
### How would you like it to work
Once you open the notifications list by clicking the clock in the top bar, each notification should show its full text content either on hover or by default.
<!--
If you can think of a way GNOME Shell might be able to do this,
let us know here.
-->
### Relevant links, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation,
code, mockups or a similar feature in another desktop environments,
please provide them here.
-->
Here is the difference:
The whole text that is available on hover of new notification:
![2020-06-09_18-21](/uploads/c6b36cb3cb7b18cc1563e576ff78446f/2020-06-09_18-21.png)
The collapsed text with ellipsis that cannot be expanded in any way once it gets to the notifications list:
![fxGpTsT_-_Imgur](/uploads/fa02ae8c9a24f46d9d3de444bbaa8b61/fxGpTsT_-_Imgur.png)
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1552Crash on startup if saved notifications are corrupt2023-01-20T04:22:22ZWill ThompsonCrash on startup if saved notifications are corruptAn Endless OS system was found in the wild with a malformed `.local/share/gnome-shell/notifications`. When deserialized in Python, after passing `trusted=True` to `g_variant_new_from_bytes()`, the first element of the first struct in the...An Endless OS system was found in the wild with a malformed `.local/share/gnome-shell/notifications`. When deserialized in Python, after passing `trusted=True` to `g_variant_new_from_bytes()`, the first element of the first struct in the array looks like this:
In [41]: _38.get_child_value(0).get_child_value(0)
Out[41]: GLib.Variant('s',
'\Uffffffff\Uffffffff\Uffffffff\Uffffffff\Uffffffff')
When deserialised in GJS, we get:
gjs> v.get_child_value(0).get_child_value(0)
[object variant of type "s"]
gjs> v.get_child_value(0).get_child_value(0).get_string()
typein:43:1 malformed UTF-8 character sequence at offset 0
@typein:43:1
@<stdin>:1:34
This causes Shell to crash on startup:
```
Aug 28 14:32:39 endless gnome-shell[7879]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
_unpack_variant@resource:///org/gnome/gjs/modules/overrides/GLib.js:207:9
_unpack_variant@resource:///org/gnome/gjs/modules/overrides/GLib.js:247:12
_unpack_variant@resource:///org/gnome/gjs/modules/overrides/GLib.js:247:12
_init/this.Variant.prototype.deep_unpack@resource:///org/gnome/gjs/modules/overrides/GLib.js:285:9
_loadNotifications@resource:///org/gnome/shell/ui/notificationDaemon.js:762:27
GtkNotificationDaemon@resource:///org/gnome/shell/ui/notificationDaemon.js:733:9
NotificationDaemon@resource:///org/gnome/shell/ui/notificationDaemon.js:833:39
_initializeUI@resource:///org/gnome/shell/ui/main.js:205:26
start@resource:///org/gnome/shell/ui/main.js:143:5
@<main>:1:31
```
Here is the offending [.local/share/gnome-shell/notifications](/uploads/fda014d76c69311eda7d0223f1289790/notifications) file. `hexdump -C`:
```
00000000 b0 8d a8 b7 cc 55 00 00 b0 a5 17 b7 cc 55 00 00 |.....U.......U..|
00000010 75 73 00 00 00 00 00 00 6e 61 75 74 69 6c 75 73 |us......nautilus|
00000020 2d 6d 6f 75 6e 74 2d 6f 70 65 72 61 74 69 6f 6e |-mount-operation|
00000030 2d 30 78 35 35 64 66 38 36 33 35 38 65 33 30 00 |-0x55df86358e30.|
00000040 74 69 74 6c 65 00 00 00 4a 65 74 46 6c 61 73 68 |title...JetFlash|
00000050 20 54 72 61 6e 73 63 65 6e 64 20 34 47 42 20 63 | Transcend 4GB c|
00000060 61 6e 20 62 65 20 73 61 66 65 6c 79 20 75 6e 70 |an be safely unp|
00000070 6c 75 67 67 65 64 00 00 73 06 00 00 00 00 00 00 |lugged..s.......|
00000080 62 6f 64 79 00 00 00 00 44 65 76 69 63 65 20 63 |body....Device c|
00000090 61 6e 20 62 65 20 72 65 6d 6f 76 65 64 2e 00 00 |an be removed...|
000000a0 73 05 00 00 00 00 00 00 69 63 6f 6e 00 00 00 00 |s.......icon....|
000000b0 74 68 65 6d 65 64 00 00 6d 65 64 69 61 2d 72 65 |themed..media-re|
000000c0 6d 6f 76 61 62 6c 65 2d 73 79 6d 62 6f 6c 69 63 |movable-symbolic|
000000d0 00 19 00 61 73 07 00 28 73 76 29 05 00 00 00 00 |...as..(sv).....|
000000e0 70 72 69 6f 72 69 74 79 00 00 00 00 00 00 00 00 |priority........|
000000f0 6e 6f 72 6d 61 6c 00 00 73 09 00 00 00 00 00 00 |normal..s.......|
00000100 74 69 6d 65 73 74 61 6d 70 00 00 00 00 00 00 00 |timestamp.......|
00000110 23 78 ff 5c 00 00 00 00 00 78 0a 3a 62 9c ba db |#x.\.....x.:b...|
00000120 00 61 7b 73 76 7d 28 00 6e 61 75 74 69 6c 75 73 |.a{sv}(.nautilus|
00000130 2d 6d 6f 75 6e 74 2d 6f 70 65 72 61 74 69 6f 6e |-mount-operation|
00000140 2d 30 78 35 35 65 30 65 31 34 64 35 34 35 30 00 |-0x55e0e14d5450.|
00000150 74 69 74 6c 65 00 00 00 55 53 42 20 44 69 73 6b |title...USB Disk|
00000160 20 63 61 6e 20 62 65 20 73 61 66 65 6c 79 20 75 | can be safely u|
00000170 6e 70 6c 75 67 67 65 64 00 00 73 06 00 00 00 00 |nplugged..s.....|
00000180 62 6f 64 79 00 00 00 00 44 65 76 69 63 65 20 63 |body....Device c|
00000190 61 6e 20 62 65 20 72 65 6d 6f 76 65 64 2e 00 00 |an be removed...|
000001a0 73 05 00 00 00 00 00 00 69 63 6f 6e 00 00 00 00 |s.......icon....|
000001b0 74 68 65 6d 65 64 00 00 6d 65 64 69 61 2d 72 65 |themed..media-re|
000001c0 6d 6f 76 61 62 6c 65 2d 73 79 6d 62 6f 6c 69 63 |movable-symbolic|
000001d0 00 19 00 61 73 07 00 28 73 76 29 05 00 00 00 00 |...as..(sv).....|
000001e0 70 72 69 6f 72 69 74 79 00 00 00 00 00 00 00 00 |priority........|
000001f0 6e 6f 72 6d 61 6c 00 00 73 09 00 00 00 00 00 00 |normal..s.......|
00000200 74 69 6d 65 73 74 61 6d 70 00 00 00 00 00 00 00 |timestamp.......|
00000210 8e 2f 02 5d 00 00 00 00 00 78 0a 2c 52 8c aa cb |./.].....x.,R...|
00000220 00 61 7b 73 76 7d 28 10 01 0f 02 13 00 2d 02 |.a{sv}(......-.|
0000022f
```Will ThompsonWill Thompson