GtkBuilder will not connect properly the activate-link signal to a GtkLinkButton

Bug #925676 reported by Natalia Bidart
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pygobject
Fix Released
Medium
pygobject (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

If you execute the sample python script attached, you'll notice that even though the 'activate-link' signal is connected to a callback in the XML passed to the builder, the default gtk_show_uri is executed the same.

Please note that the on_activate_link handler is returning True as the documentation requires if you don't want that the default gtk_show_uri is called.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libgtk-3-0 3.3.10-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Thu Feb 2 16:39:16 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Natalia Bidart (nataliabidart) wrote :
Revision history for this message
Natalia Bidart (nataliabidart) wrote :
summary: - GtkBuilder will not connect the activate-link signal to a GtkLinkButton
+ GtkBuilder will not connect properly the activate-link signal to a
+ GtkLinkButton
description: updated
Changed in gtk+3.0 (Ubuntu):
assignee: nobody → Canonical Desktop Experience Team (canonical-dx-team)
assignee: Canonical Desktop Experience Team (canonical-dx-team) → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Sebastien Bacher (seb128) wrote :
affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
importance: Undecided → High
status: New → Fix Committed
affects: ubuntu → pygobject (Ubuntu)
Changed in pygobject (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → Martin Pitt (pitti)
Changed in pygobject:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pygobject - 3.1.0-2

---------------
pygobject (3.1.0-2) unstable; urgency=low

  * Add glib_2.30.patch: Partially revert commit ee62df4 to drop the usage of
    g_value_*_schar. This was introduced in glib 2.31 only. (Closes: #659184)
  * Add 00git_pygspawn_error_check.patch: Fix crash in pygspawn() when the
    argv or envp arguments are not proper sequences. Backported from upstream
    git head.
  * Add 00git_gtkbuilder-signals.patch: Fix GtkBuilder signal connection
    'after' logic. Backported from upstream git head. (LP: #925676)
 -- Martin Pitt <email address hidden> Thu, 09 Feb 2012 07:01:44 +0100

Changed in pygobject (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.