Bug 77448 – Scribus-1.2.1 fail to start -- libscriptplugin.so.0.0.0: undefined symbol: PyUnicodeUCS2_SetDefaultEncoding

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Chin Yee 2005-01-10 18:01:05 UTC]

Just upgraded to Scribus-1.2.1 and it fail to start with the following console messages:- 

~ $ scribus
QScimInputContextGlobal ()
Loading IMEngine module: socket ...
    Loading IMEngine Factory 0 ... : OK
    Loading IMEngine Factory 1 ... : OK
    Loading IMEngine Factory 2 ... : OK
socket IMEngine module is successfully loaded.
reloading global config...
ScimInputContextPlugin()
QMultiInputContext::changeInputMethod(): index=0, slave=xim
QMultiInputContext::changeInputMethod(): index=0, slave=xim
QMultiInputContext::changeInputMethod(): index=0, slave=xim
scribus: symbol lookup error: /usr/lib/scribus/plugins/libscriptplugin.so.0.0.0: undefined symbol: PyUnicodeUCS2_SetDefaultEncoding

Downgrading to scribus-1.2 and the application startup normally.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Hanno Böck 2005-01-11 06:04:35 UTC]

Seems like a problem with your python-installation.
Can you try running revdep-rebuild? This should fix it.
If not, please provide some more information (emerge info-output, your installed python-version).

[Comment 2 Chin Yee 2005-01-11 07:01:41 UTC]

I did run revdep-rebuild before reporting the bug, but it report nothing to rebuild. I also re-emerge python and scribus but to no avail.

~ $ emerge info
Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r3 i686)
=================================================================
System uname: 2.6.10-gentoo-r3 i686 AMD Athlon(tm) XP processor 1800+
Gentoo Base System version 1.6.8
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Aug 19 2004, 10:52:02)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3
sys-devel/binutils:  2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r2
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-pipe -march=athlon-xp -mmmx -m3dnow -msse -mfpmath=sse,387 -momit-leaf-frame-pointer -O2 -ffast-math -fomit-frame-pointer         
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-pipe -march=athlon-xp -mmmx -m3dnow -msse -mfpmath=sse,387 -momit-leaf-frame-pointer -O2 -ffast-math -fomit-frame-pointer         -fvisibility-inlines-hidden"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms userpriv"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
LDFLAGS="-Wl,-O1"
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 3dnow 3dnowex X aalib acl acpi alsa apm arts avi berkdb cdr cjk crypt cups divx4linux encode esd exif faad fam ffmpeg flac foomaticdb fortran gdbm gif gpm gs gtk2 imagemagick imlib imlib2 immqt ipv6 java jpeg junit kde lcms libwww mad mikmod mmx mng motif moznocompose moznoirc moznomail mozsvg mpeg mpeg4 ncurses nls no_wxgtk1 nptl nptlonly nvidia oggvorbis opengl oss pam pdflib perl png postgres ppds python qt quicktime readline real scanner sdl slang spell sse ssl svg svga tcltk tcpd tidy tiff timidity truetype unicode usb wmf xine xml2 xmms xprint xv zlib"

[Comment 3 Chin Yee 2005-01-14 06:57:55 UTC]

I think I've found the solution to the problem. Scribus-1.2.1 requires python to be build with ucs2 support. So I added the ucs2 USE flag and re-emerge python and now scribus launch without any problem.

I think the ebuild need to be modified to reflect this dependency.

[Comment 4 Hanno Böck 2005-01-16 03:23:08 UTC]

I don't have the ucs2-useflag set and scribus runs fine for me. So this cannot be the problem.
Maybe you've build scribus while python was built with ucs2 and then re-merged it without?

[Comment 5 Chin Yee 2005-01-16 08:31:31 UTC]

When I remove the ucs2 flag and re-emerge python and scribus-1.2.1 in sequence, it failed with the captioned error message.

[Comment 6 Santtu Pajukanta 2005-04-05 00:01:59 UTC]

I don't think "USE=ucs2 emerge python" is a good solution. Quoting from the Python ebuild:

        # super-secret switch. don't use this unless you know what you're
        # doing. enabling UCS2 support will break your existing python
        # modules
        use ucs2 \ ...

For the record, I'm getting the same error message (scribus: symbol lookup error: /usr/lib/scribus/plugins/libscriptplugin.so.0.0.0: undefined symbol: PyUnicodeUCS2_SetDefaultEncoding).

[Comment 7 Hanno Böck 2005-06-05 18:13:17 UTC]

Is this still an issue for anyone? I failed to reproduce it. If you used the 
ucs2-useflag, I can't help you, because that's unsupported stuff. 

[Comment 8 Chin Yee 2005-06-10 21:49:42 UTC]

Prior to python-2.4 I had to emerge python with the ucs2 flag or else I'll get 
the captioned error. 
 
With python-2.4.1 which only hit the portage tree a few days ago, I no longer 
need the ucs2 use flag. The problem just went away. 

[Comment 9 Hanno Böck 2005-06-13 05:40:38 UTC]

So it's fixed.