Re: fribidi error with abiword on F11

[Globe Trotter]

> > > fribidi-0.19.2-1.fc11
> > > contains libfribidi.so.0 with the symbol

you
> refer to.
> > Clearly this is installed. But yum provides
>
> */libfribidi0*
>
> libfribidi.so.0 == libfribidi0*
>
> Since when?

But that was my point! The responder indicated it was. So,
 how does one get around the missing symbol, as in:

abiword: symbol lookup error: /usr/lib/libabiword-2.6.so:
 undefined symbol: fribidi_get_type

Best,
 T
>

fribidi error with abiword on F11

[Michael Schwendt]

On Tue, 29 Sep 2009 16:49:59 -0700 (PDT), Globe wrote:
> > > > fribidi-0.19.2-1.fc11
> > > > contains libfribidi.so.0 with the symbol
>
> you
> > refer to.
> > > Clearly this is installed. But yum provides
> >
> > */libfribidi0*
> >
> > libfribidi.so.0 == libfribidi0*
> >
> > Since when?
>
> But that was my point!

Uh? libfribidi.so.0 (which the libraries internal name) is included
within package "fribidi". Wherever you've found something on the
web that points to something called "libfribidi0", that isn't
applicable to Fedora. There may be other Linux distributions that
put the library into a package called "libfribidi0", but not Fedora.

$ repoquery --whatprovides libfribidi.so.0  
fribidi-0:0.19.2-1.fc11.i586

$ rpm --query --provides fribidi|grep so
libfribidi.so.0

$ objdump -T /usr/lib/libfribidi.so.0|grep get_type
007e79d0 g    DF .text  00000023  Base        fribidi_get_type_internal
007e7a00 g    DF .text  00000023  Base        fribidi_get_type
> The responder indicated it was. So,
>  how does one get around the missing symbol, as in:
>
> abiword: symbol lookup error: /usr/lib/libabiword-2.6.so:
>  undefined symbol: fribidi_get_type

1) Can you show that your "fribidi" package isn't damaged?
Run: rpm -V fribidi

2) Can you show that the libfribidi.so.0 library is found and
linked with /usr/lib/libabiword-2.6.so?
Run: ldd -r /usr/lib/libabiword-2.6.so|grep frib

fribidi error with abiword on F11

[Globe Trotter]

Hi,

Thanks very much for your detailed help and instructions!!
> $ repoquery --whatprovides libfribidi.so.0  
> fribidi-0:0.19.2-1.fc11.i586

# repoquery --whatprovides libfribidi.so.0 
fribidi-0:0.19.2-1.fc11.i586
> $ rpm --query --provides fribidi|grep so
> libfribidi.so.0

# rpm --query --provides fribidi|grep so
libfribidi.so.0
> $ objdump -T /usr/lib/libfribidi.so.0|grep get_type
> 007e79d0 g    DF .text  00000023 
> Base        fribidi_get_type_internal
> 007e7a00 g    DF .text  00000023 
> Base        fribidi_get_type

# objdump -T /usr/lib/libfribidi.so.0|grep get_type
06d179d0 g DF .text 00000023 Base fribidi_get_type_internal
06d17a00 g DF .text 00000023 Base fribidi_get_type
> Can you show that your "fribidi" package isn't damaged?
>
> Run: rpm -V fribidi

As root, I get nothing, as user I get:

$ rpm -V fribidi
prelink: /usr/bin/fribidi: at least one of file's dependencies has changed since prelinking
S.?......    /usr/bin/fribidi
> Can you show that the libfribidi.so.0 library is found
>
> and
> linked with /usr/lib/libabiword-2.6.so?
> Run: ldd -r /usr/lib/libabiword-2.6.so|grep frib

ldd -r /usr/lib/libabiword-2.6.so|grep frib
    libfribidi.so.0 => /usr/local/lib/libfribidi.so.0 (0x00502000)
undefined symbol: fribidi_get_type	(/usr/lib/libabiword-2.6.so)

As root, things are fine and I get:

ldd -r /usr/lib/libabiword-2.6.so|grep frib
        libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x06d14000)

Not as user, though. How do I track this?

Best,
T

fribidi error with abiword on F11

[Sam Sharpe]

2009/9/30 Globe Trotter :
> > Can you show that the libfribidi.so.0 library is found
> >
> > and
> > linked with /usr/lib/libabiword-2.6.so?
> > Run: ldd -r /usr/lib/libabiword-2.6.so|grep frib
>
> ldd -r /usr/lib/libabiword-2.6.so|grep frib
>        libfribidi.so.0 => /usr/local/lib/libfribidi.so.0 (0x00502000)
> undefined symbol: fribidi_get_type      (/usr/lib/libabiword-2.6.so)
>
> As root, things are fine and I get:
>
> ldd -r /usr/lib/libabiword-2.6.so|grep frib
>        libfribidi.so.0 => /usr/lib/libfribidi.so.0 (0x06d14000)
>
> Not as user, though. How do I track this?

Mmmmm.... that's interesting. As root it's resolving to a library in
/usr/lib but as the user it's resolving to a library in /usr/local/lib
(why do you have fribidi libraries in /usr/local/lib?)

What's the output of this command as root and as the user?
# echo $LD_LIBRARY_PATH

fribidi error with abiword on F11

[Globe Trotter]

--- On Wed, 9/30/09, Sharpe, Sam J  wrote:
> From: Sharpe, Sam J 
> Subject: Re: fribidi error with abiword on F11
> To: "Community assistance, encouragement, and advice for using Fedora." 
> Date: Wednesday, September 30, 2009, 2:56 PM
> 2009/9/30 Globe Trotter :
> > > Can you show that the libfribidi.so.0 library
>
> is found
> > > and
> > > linked with /usr/lib/libabiword-2.6.so?
> > > Run: ldd -r /usr/lib/libabiword-2.6.so|grep frib
> >
> > ldd -r /usr/lib/libabiword-2.6.so|grep frib
> >        libfribidi.so.0 =>
>
> /usr/local/lib/libfribidi.so.0 (0x00502000)
> > undefined symbol: fribidi_get_type
>
> (/usr/lib/libabiword-2.6.so)
> > As root, things are fine and I get:
> >
> > ldd -r /usr/lib/libabiword-2.6.so|grep frib
> >        libfribidi.so.0 =>
>
> /usr/lib/libfribidi.so.0 (0x06d14000)
> > Not as user, though. How do I track this?
>
> Mmmmm.... that's interesting. As root it's resolving to a
> library in
> /usr/lib but as the user it's resolving to a library in
> /usr/local/lib
> (why do you have fribidi libraries in /usr/local/lib?)
>
> What's the output of this command as root and as the user?
> # echo $LD_LIBRARY_PATH

Aha! Here we go:

As root:

# echo $LD_LIBRARY_PATH

(nothing)

As user:

$ echo $LD_LIBRARY_PATH
/usr/local/lib

Clearly some setting somewhere which got set: wonder where.It happened after a installing the printer and the associated hp* rpms, btw.

Best wishes,
T

fribidi error with abiword on F11

[Sam Sharpe]

2009/9/30 Globe Trotter :
> > From: Sharpe, Sam J 
> > Mmmmm.... that's interesting. As root it's resolving to a
> > library in
> > /usr/lib but as the user it's resolving to a library in
> > /usr/local/lib
> > (why do you have fribidi libraries in /usr/local/lib?)
> >
> > What's the output of this command as root and as the user?
> > # echo $LD_LIBRARY_PATH
>
> Aha! Here we go:
>
> As root:
>
> # echo $LD_LIBRARY_PATH
>
> (nothing)
>
> As user:
>
> $ echo $LD_LIBRARY_PATH
> /usr/local/lib
> Clearly some setting somewhere which got set: wonder where.It happened after a installing the printer and the associated hp* rpms, btw.

Check out .profile, .bash_profile and .bashrc in your home directory.
If it's not set there, it'll be in /etc/profile or /etc/bashrc

fribidi error with abiword on F11

[Michael Schwendt]

On Wed, 30 Sep 2009 14:47:43 -0700 (PDT), Globe wrote:
> > /usr/local/lib/libfribidi.so.0 (0x00502000)
> > > undefined symbol: fribidi_get_type
> $ echo $LD_LIBRARY_PATH
> /usr/local/lib
>
> Clearly some setting somewhere which got set: wonder where.It happened after a installing the printer and the associated hp* rpms, btw.

What hp* rpms in particular? And it doesn't explain why you installed
an incompatible fribidi lib into /usr/local. If you don't need that
library for anything else, you could simply delete any traces of it
below /usr/local

fribidi error with abiword on F11

[Globe Trotter]

--- On Thu, 10/1/09, Michael Schwendt  wrote:
> From: Michael Schwendt 
> Subject: Re: fribidi error with abiword on F11
> To: [e-mail]
> Date: Thursday, October 1, 2009, 2:35 AM
> On Wed, 30 Sep 2009 14:47:43 -0700
> (PDT), Globe wrote:
> > > /usr/local/lib/libfribidi.so.0 (0x00502000)
> > > > undefined symbol: fribidi_get_type
> > $ echo $LD_LIBRARY_PATH
> > /usr/local/lib
> >
> > Clearly some setting somewhere which got set: wonder
>
> where.It happened after a installing the printer and the
> associated hp* rpms, btw.
> >
>
> What hp* rpms in particular? And it doesn't explain why you
> installed
> an incompatible fribidi lib into /usr/local. If you don't
> need that
> library for anything else, you could simply delete any
> traces of it
> below /usr/local

Thanks very much! The fribidi was from an old installation from the ancient days over two years ago when I hadn-installed and used fvwm. I got rid of them and things work. It still does not explain why installing the hp* rpms (hpic, hplip, hpijs, hping3 and dependencies) made this problem show up. I also installed the .ppd for my JetDirect printer by hand since it would not show up otherwise as a network discovered printer.

Best wishes,
T