Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Printing problems with SO5.1

0 views
Skip to first unread message

bgda...@my-deja.com

unread,
Aug 30, 1999, 3:00:00 AM8/30/99
to
On my Debian (glibc2.1) system, whenever I try to print a file, it puts
up a dialog saying "Printing page X/Y". X increases until X==Y, then SO
hangs. I am trying to print to a .ps file, but this file does not get
created. When it hangs, if the window is obscured by another, SO does
not redraw that area and just leaves it black. The only way I can get
rid of it is "killall -9 soffice.bin". What do I have to do to get it
to print?

-Ben


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Trey Nolen

unread,
Sep 4, 1999, 3:00:00 AM9/4/99
to


I am having a similar problem and I am also running Debian with
glibc2.1. My printer is on a Novell network and I use "nprint -N -" to
print. That prints from stdin with no banner. I can print fine in
Netscape, Adobe Acrobat, etc. I can also make a .prn file by printing to
file and then manually nprint it, and it works. I am trying to print to
an HP5 and it hangs up like you describe if I try to print directly. I
could print fine with Star Office 5.0 before I switched to glibc2.1.
Sorry this doesn't offer any help....but maybe if they see more than one
person is having the trouble, someone will answer.

Trey

bgda...@my-deja.com

unread,
Sep 8, 1999, 3:00:00 AM9/8/99
to
In article <7qev7a$dic$1...@nnrp1.deja.com>,

bgda...@my-deja.com wrote:
> On my Debian (glibc2.1) system, whenever I try to print a file, it
puts
> up a dialog saying "Printing page X/Y". X increases until X==Y, then
SO
> hangs. I am trying to print to a .ps file, but this file does not get
> created. When it hangs, if the window is obscured by another, SO does
> not redraw that area and just leaves it black. The only way I can get
> rid of it is "killall -9 soffice.bin". What do I have to do to get it
> to print?
>

Addendum: I can print simple documents. The document that caused the
problem above made use of graphics and equations. Hope this helps
someone locate the bug.

0 new messages