On Monday 13 March 2006 17:17, Andy Pepperdine wrote: [..] > In my case, I use A4 sheets in a HP laserjet printer with Suse 10.0 either > on a desktop machine with the printer attached to its parallel port, or > from a laptop across a network through CUPS on the desktop. Same printer > connected the same way in both cases. If I print an old document, > everything works fine from either machine. If I print a new text document > from the laptop it is also OK. > > But when I print a _new_document_ from the desktop it reverts to US letter, > and then only after several seconds of cpu bound thinking by both cupsd and > soffice.bin. After that the two seem to loop together for ever. Only by > closing OOo completely does it come out of it. (I used top to see what was > using cpu.) None of the log files seem to show any problems. > > At first I thought it must be cups or something, but no other application > shows anything like these symptoms; so I'm moving towards thinking it is > the way OOo interrogates cups to get printer information. > > Has anyone else seen anything similar?
This is now solved. Explicitly selecting the driver when setting up the printer, rather than taking Suse's default for that printer, has cured this strange behaviour. Not OOo at all. -- Andy Pepperdine --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
