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

Bug#202309: openoffice.org: hangs when trying to print or when modifying the printer settings



Package: openoffice.org
Version: 1.0.3-2
Severity: important
Tags: upstream

I'm running Debian/unstable with OO version 1.0.3-2 and unfortunately
OOwriter hangs every time I try to print. OO can't even refresh the
screen and I have to kill it. I'm running on a Dell Latitude laptop with
a ATI Rage Mobility P/M AGP video card. I'm running CUPS version
1.1.19final-1; printing works just fine in all other applications both
inside my Gnome desktop and in terminal mode.

OO hangs no matter which printer I select (I have several defined),
including the PDF converter and the "print to file"
options. Even worst, it hangs when I try to edit something in the print
settings dialogs. There is one exception: if I select the "generic
printer" that comes configured by default with OO then everything is OK;
this generic printer becomes then my CUPS default printer so CUPS
doesn't seem to be the problem here.

Also, OO seems to go idle when is hung since it doesn't
use any CPU cycles at all. It just sits there doing nothing. In fact, I
believe it sigfaults (see below)

I have access to other PC's running OO but I don't see the problem
there. I can think of just two things particular to my laptop:

1. I'm using CUPS for printing. However, the fact that OO hangs even
when printing to a file tells me that this doesn't matter.

2. My laptop has lots of fonts installed including truetype fonts
that I carried over from some windows servers and the fonts from the
msttcorefonts package version 1.1.2.

For what is worth, I run strace to see what OO is doing when the
hangs occurs. I attach the output at the end. The lines you'll see there
is what strace shows just before I click the OK button in the print
menu. It seems that OO segfaults but is not killed immediately.
I tried running strace -f to follow the child processes but I get into
an endless gettimeofday() - poll() loop that prevents me from going any
further.

My only work around at this moment is to use the "generic printer" but I
can't use any other printer or the PDF output or the "print to file" options
which are the worst important to me.

strace output
=============

sched_yield()                           = 0
write(6, "\2\3\4\0\230\2`\2\0@\0\0\20\0`\2\36\0\4\0\20\0`\2\0\0\0"...,
32) = 32
gettimeofday({1058808448, 286765}, NULL) = 0
select(7, [4 6], NULL, [6], {0, 311490}) = 1 (in [4], left {0, 320000})
gettimeofday({1058808448, 287302}, NULL) = 0
read(4, "\0", 4)                        = 1
read(4, 0xbfffe00c, 4)                  = -1 EAGAIN (Resource
temporarily unavailable)
gettimeofday({1058808448, 287455}, NULL) = 0
select(7, [4 6], NULL, [6], {0, 310800}) = 1 (in [6], left {0, 190000})
gettimeofday({1058808448, 425894}, NULL) = 0
select(7, [6], NULL, [], {0, 0})        = 1 (in [6], left {0, 0})
ioctl(6, FIONREAD, [32])                = 0
read(6, "\5\1\0C\221\241\364\0009\0\0\0\230\2`\2\0\0\0\0004\2`\002"...,
32) = 32times({tms_utime=932, tms_stime=58, tms_cutime=9, tms_cstime=6})
= 1609570
write(6, "\33\3\2\0\0\0\0\0\33@\2\0\0\0\0\0", 16) = 16
write(5, "\0", 1)                       = 1
times({tms_utime=932, tms_stime=58, tms_cutime=9, tms_cstime=6}) =
1609570
gettimeofday({1058808448, 426756}, NULL) = 0
write(5, "\0", 1)                       = 1
write(5, "\0", 1)                       = 1
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigprocmask(SIG_SETMASK, NULL, ~[KILL STOP], 8) = 0
rt_sigsuspend(~[KILL STOP RTMIN]


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pcard0ze 2.4.20 #1 Mon Apr 21 10:33:47 EDT 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set)

Versions of packages openoffice.org depends on:
ii  openoffice.org-bin            1.0.3-2    OpenOffice.org office suite binary
ii  openoffice.org-debian-files   1.0.3-2+1  Debian specific parts of OpenOffic
ii  openoffice.org-l10n-en        1.0.3-2    English (US) language package for 

-- no debconf information




Reply to: