After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 775626 - Clicking on Terminal notifications does nothing
Clicking on Terminal notifications does nothing
Status: RESOLVED DUPLICATE of bug 731101
Product: gnome-shell
Classification: Core
Component: message-tray
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-12-05 11:48 UTC by Alexandre Franke
Modified: 2016-12-08 10:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexandre Franke 2016-12-05 11:48:37 UTC 
Since I upgraded to F25 / GNOME 3.22, clicking on the notifications that appear when a job in the terminal is done does not bring up the terminal anymore.
Comment 1 Florian Müllner 2016-12-07 13:57:36 UTC 
Is there anything in the logs? The shell simply calls a D-Bus method when the notification is clicked (org.freedesktop.Application.Activate() by default, or org.freedesktop.Application.ActivateAction() when the app specified a default action). If that doesn't work as expected, it's more likely an issue in the app's implementation of those methods than the calls themselves (in particular if it's an issue with a particular app rather than any notification).
Comment 2 Allan Day 2016-12-08 10:22:35 UTC 
I've noticed this happening on Wayland; doesn't seem to be an issue on X11 though. Is that true for you, Alexandre?

It might be the same issue as bug 731101.
Comment 3 Debarshi Ray 2016-12-08 10:30:37 UTC 
(In reply to Allan Day from comment #2)
> I've noticed this happening on Wayland; doesn't seem to be an issue on X11
> though. Is that true for you, Alexandre?

Yes, works on X but not on Wayland.
Comment 4 Alexandre Franke 2016-12-08 10:45:03 UTC 
Yes. This indeed seems to be a duplicate of 731101. I'm surprised it's a GTK+ bug and not a GNOME Shell one, but fair enough.

*** This bug has been marked as a duplicate of bug 731101 ***