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 756106 - "activate-link" signal not sent when GtkLabel in embedded in plug which is embedded in a socket
"activate-link" signal not sent when GtkLabel in embedded in plug which is em...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkLabel
unspecified
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-10-06 06:22 UTC by Ali
Modified: 2018-04-15 00:29 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A small program to illustrate the bug (10.00 KB, application/gzip)
2015-10-06 06:22 UTC, Ali 		Details

Description Ali 2015-10-06 06:22:12 UTC 
Created attachment 312703 [details]
A small program to illustrate the bug

Consider the following situation, program A that creates a socket and pass it through the command line to a program B, which uses it to plug itself in the socket of A. 

The problem is that B has a GtkLabel set with a link markup. When clicking the link the signal "activate-link" is never emitted. 

I have tested it on Gtk3 version 3.16.7 and on Gtk2 version 2.24.28. Code attached with a Makefile that compiles code for gtk2 and gtk3 (socket-window-gtk2/3 will launch plug-gtk2/3). 

I flagged the bug severity as "Major" since it affects the functionality of the interface that I'm writing.
Comment 1 Matthias Clasen 2018-02-10 05:22:51 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:29:06 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new