[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cannot print from StarOffice



-----BEGIN PGP SIGNED MESSAGE-----

On Sat, 4 Sep 1999, Dirk Eddelbuettel wrote:

> 
>   Dirk> I am at wit's end here -- I have a `network' installation of
>   Dirk> StarOffice 5.1 here at home for use by myself and my wife. It works
>   Dirk> fine, but just won't print. I even re-downloaded 5.1 again, and
>   Dirk> reinstalled, but no luck.  The machine is current potato with lpd and
>   Dirk> magicfilter installed and working.

Ditto here. Also, SO5.1 used to work and print fine with an older version
of potato.

>   Julio> It seems that some StarOffice functionalities hang when running over
>   Julio> potato with libc6 2.1. It does work fine with slink (libc6 2.0.7)
>   Julio> indeed.
> 
> Yes, that's like it. Whenever it attempts to print, it hangs and starts
> several soffice.bin processes which I have to kill hard (kill -9, sometime
> even xkill). 

After i kill it using the pulldown menu in WindowMaker, ps ax still
shows three SO-related threads:
 4075 ?        D      0:05 /usr/local/staroffice51/bin/soffice.bin        
 4090 ?        Z      0:00 [soffice.bin <defunct>]
 4113 ?        S      0:00 /usr/local/staroffice51/bin/soffice.bin        

Note number 4090 is zombied. Combining this with the following facts:
 * SO uses a system(3) call for printing (which was a problem when trying
   to trick 5.01 into working, since just adjusting LD_LIBRARY_PATH to
   point to glibc 2.0.7 killed sh, so no printing),
 * SO probably uses threads, although i don't know how to be sure of this
   with no source. I don't see it forking all those processes... i do see
   a clone(2) call in the strace, which is suggestive.
 * Bug #43549 (http://www.debian.org/Bugs/db/43/43549.html)

> So then it's now me but rather glibc and staroffice?  

glibc, yeah... Guess that's why glibc 2.1.2 is still in prerelease.


- -- 
  finger for PGP public key.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBN9Ha9L7M/9WKZLW5AQEaFQP/RgJye6fQNZPzJkn2EPJFYatbjm8ULVsj
7bVa+0EFW4+W6udiJv5fbGEWnP2FYjy3+3x3zfnejoeqk/3aD77DwANX4FXmc+tm
SOOeNzqNcP7YCaceYiWNSizEZgTwgeBgN/zAFdDFFZpvpRnHHlA0XtjYO+mWlGX8
/4Ty0ChwXQQ=
=uoAp
-----END PGP SIGNATURE-----


Reply to: