Bugzilla Bug 74579

The last version of galculator available on Portage is 1.2.3. The last version
is 1.2.4. I tested renaming the ebuild and it worked. Please update.

I can confirm, I just renamed the ebuild and sci-calculators/galculator-1.2.4
is working fine here on ~x86.

Was assigned to wrong herd...

bumped in tree

Don't know what you guys did with this ebuild, but it suddenly no longer works
after doing an emerge -avuD world.

(galculator:21983): libglade-WARNING **: could not find signal handler
'on_dec_activate'.
<snip>
(galculator:22079): libglade-WARNING **: could not find signal handler
'on_mplus_button_clicked'.

(galculator:22079): libglade-CRITICAL **: glade_xml_get_widget: assertion `self
!= NULL' failed
Segmentation fault


(Yes libglade was also updated ... So i guess I'll post this bug there aswell?)
I'll try a reboot (sounds pathetic I know) to maybe remove an old version from
memory maybe.

Reopening bug on account of comment #4.

a new bug should have been opened for this, not reopened since this bug was
about a version bump.

are you having issues with the bump vanquirius? 

or did you reopen purely b/c of comment 4?

Can node repost with whether ~ galculator build works for him after his reboot?

I reopened the bug solely on account of comment #4.
node, please open a new bug next time, it is easier for us to track.

I experienced the same problem in 'glurp' after upgrading libglade and other
packages.  I found a fix for glurp (Bug 91482) and I assume the galculator fix
should be similar - Just make sure that '-export-dynamic' is being passed to
the linker.

If I have time I may write a patch/new ebuild for this.

Created an attachment (id=58068) [details]
Patch against galculator-1.2.4 which adds '-export-dynamic' to the linker

This patch is for use with the galculator-1.2.4-r1.ebuild also attached to this
bug.  It should go in sci-calculators/galculator/files/

Created an attachment (id=58069) [details]
New ebuild which uses the export-dynamic.patch

This ebuild requires the patch also attached to this bug.

This fix works for me.  Galculator can work again.

I have also submitted my patch to galculator-general@lists.sourceforge.net

I have no problems running the version bumped galculator.  What version is
libglade for you?  Are you running anything else unstable?  Have you tried
re-merging the package after you upgraded the libglade / other things ?  As
always, please provide your emerge info.

As you can see from the following 'emerge info' I am running ~x86 with latest
GCC and everything.  My libglade version is 2.5.1.  I did try downgrading
libglade to both 2.4.2 and 2.4.0 with no change in galculator's behaviour.  I
also tried an earlier compiler (gcc-3.3.5) also with no effect.

I'm not sure which package (of the many I recently upgraded with 'emerge -uD
world') would have been the cause, but I expected either libglade or gcc.  By
adding the '-export-dynamic' flag to the linker with my patch, the problem went
away.

emerge info:

Portage 2.0.51.21 (default-linux/x86/2005.0, gcc-3.4.3-20050110,
glibc-2.3.5-r0,                           2.6.11-gentoo-r1 i686)
=================================================================
System uname: 2.6.11-gentoo-r1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.11
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.3
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r8
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.11
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share                          /config /usr/kde/3.4/shutdown
/usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/                         
mozilla/defaults/pref /usr/share/config /var /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.binarycompass.org ftp://cs.ubishops.ca/pub/gentoo
                          ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/
ftp://gentoo.risq.qc.ca/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac alsa apache2 apm avi berkdb bitmap-fonts cdr cjk crypt cups curl
                          eds emboss encode esd fam flac foomaticdb fortran gd
gdbm gif gimpprint gnome gp                          m gstreamer gtk gtk2
imagemagick imap imlib java jpeg kde ldap libg++ libwww mad                    
      mikmod mmx mmx2 motif mozilla mp3 mpeg mysql ncurses nls nptl ogg
oggvorbis ope                          ngl oss pam pdflib perl php png python
qt quicktime readline real samba sasl sdl                           spell sse
ssl svga tcltk tcpd threads tiff truetype truetype-fonts type1-fonts           
               vorbis xml2 xprint xv zlib userland_GNU kernel_linux libc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

what version of pkgconfig are you using ? If it's 0.17 then go back to 0.15 and
try rebuild libglade/galculator with that.

pkg-config --version returns:
0.15.0

Recieved email from Simon Floery (via
galculator-general@lists.sourceforge.net):

> Thanks a lot for your contribution! From time to time this problem
> arose in the past but no user, who encountered it, was able to track it down.
> I asked someone who recently reported this problem to try your patch and
> everything works fine now.
>
> I'll update the build process and kick out a new release of galculator ASAP.

The fix I submitted shouldn't affect the basic gentoo ebuild, so the next
version bump should get this fixed.

great, thanks for contacting upstream.  i'll keep an eye out for the new
release upstream, if you see it first, please post here.

okay, heres *hopefully* a good fix for both galculator and glurp.  foser did
some research and found a good thread that describes the problem more in
detail:
http://mail.gnome.org/archives/desktop-devel-list/2005-January/msg00037.html

foser made good comments and suggested this patch.

Jim, if you could test this patch against galculator, that would be great. 
Please post back with the results.

Created an attachment (id=58273) [details]
galculator gmodule patch

This patch also works perfectly, no complaints here.

okay, a new bug was filed today for the new version of galculator, so i will be
testing / committing that shortly.  Also, in the new version it looks like they
incorporated your patch, but I think that the one I previously attached is a
better way of doing it.  Either way, with the new version, the patch should not
be needed.  Thanks for testing!

I think either solution is valid.  It's now up to the software developer to
include the '-export-dynamic' in cases like this, so whether they do it by
explicitly asking pkg-config to provide 'gmodule-2.0' instead of
'gmodule-no-export-2.0' (your patch), or by explicitly specifying
'-export-dynamic' in their own LDFLAGS (my patch), the right thing happens.

committed 1.2.5