From: gnome-perl (bugzilla.gnome.org) <bug...@bu...> - 2006-05-20 21:00:19
|
Do not reply to this via email (we are currently unable to handle email responses and they get discarded). You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=3D342444 gnome-perl | Gnome2::Print | Ver: unspecified ------- Comment #6 from muppet 2006-05-20 21:00 UTC ------- The most common reason for the "method signal_connect not found" on some = widget deriving from Glib::Object has been the combination of gtk+ >=3D 2.8 and = Gtk2 < 1.120. In gtk+ 2.8, the ancestry to GtkObject (from which all GtkWidgets derive)= was altered to add GInitiallyUnowned between GObject and GtkObject. This cha= nge broke all nontrivial Gtk2-Perl scripts, because GInitiallyUnowned was unk= nown to the Glib module, and resulted in Glib::Object not being added to the widget's @ISA. There is a workaround, but the real fix is to upgrade to = >=3D 1.120. Could you please check that: - running the script manually still triggers the problem. after buildin= g, do=20 cd Gnome2-Perl-0.951/ && perl -Mblib ./t/04.GnomePrintDialog.t - Please add these lines to 04.GnomePrintDialog.t and paste the output: ok( $dialog =3D Gnome2::Print::Dialog->new($job, "Test", 0) ); +use Data::Dumper; +print Dumper($dialog); +print Dumper(\@Gnome2::Print::Dialog::ISA); +print Dumper(\@Gtk2::Object::ISA); +print "Gtk2::VERSION $Gtk2::VERSION\n"; +print "Glib::VERSION $Glib::VERSION\n"; + $dialog->signal_connect(response =3D> sub { ok( $_[1] =3D=3D 1 ); For me, the output is homie:~/cvs/gtk2-perl-xs/GnomePrint2$ perl -Mblib t/04.GnomePrintDialog.t= =20 1..4 WARNING **: IPP request failed with status 1030 at t/04.GnomePrintDialog.= t line 24. ok 1 $VAR1 =3D bless( {}, 'Gnome2::Print::Dialog' ); $VAR1 =3D [ 'Gtk2::Dialog', 'Gtk2::Atk::Implementor' ]; $VAR1 =3D [ 'Glib::Object::_Unregistered::GInitiallyUnowned' ]; Gtk2::VERSION 1.120 Glib::VERSION 1.120 ok 2 ok 3 ok 4 --=20 Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |