Issue 71417 - Batch printing broken in 2.2, WinXP
Summary: Batch printing broken in 2.2, WinXP
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: 71421
  Show dependency tree
Reported: 2006-11-10 14:45 UTC by sb56637
Modified: 2013-08-07 15:31 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description sb56637 2006-11-10 14:45:04 UTC
Hi, I often print multiple OOo files to my printer (WinXP SP2) by dragging the
documents from Explorer to the print queue.  This no longer works on 2.0.4.  It
did work well with 2.0.3.  I experienced the issue while trying to print a bunch
of *odg files, so I immediately downgraded to 2.0.3.  So I don't know if this
just affects all files types, or just *odg.  I have verified that this problem
happens every time, with any printer I try.  I also tried printing multiple text
files to the same printer, which works fine, so I know it's not a Windows print
spooler problem.  

What happens is it starts to print one of the files (appears to be the file that
is alphabetically last) and then no more files appear in the queue, and a bunch
of left over soffice.exe and soffice.bin processes asre left hanging in the
process tree.

Thanks for your help!
Comment 1 thorsten.martens 2006-11-15 13:02:18 UTC
TM->>>>><HI: please have a look. Seems to be more a printing-issue than a
framework problem to me. Thanks
Comment 2 thorsten.martens 2006-11-16 10:37:53 UTC
Comment 3 sb56637 2007-03-01 20:13:26 UTC
Any way this bug can be confirmed?  I, for one, can confirm it.
Comment 4 kpalagin 2007-05-10 12:03:02 UTC
Works fine here with 2.3m209 on WinXP using local printer (dropping to printer 
icon in Printers folder).
Resolving as worksforme.

please check version 2.2, also specify if file, folder and printer names  
contain national chars.
Comment 5 sb56637 2007-07-07 19:49:18 UTC
Using OpenOffice 2.2 on Win XP SP2, this is STILL broken.  It prints one
document, then no more get added to the queue, and leaves a bunch of soffice
processes hanging.
Comment 6 sb56637 2007-07-07 19:50:54 UTC
Comment 7 sb56637 2007-07-07 19:54:00 UTC
Is there any way this issue could be confirmed?  Thanks!
Comment 8 sb56637 2007-07-07 20:11:02 UTC
I have moved the files to the directory C:\test  and the filenames do not
contain spaces or special chars.  Still broken.
Comment 9 Olaf Felka 2007-07-07 20:32:02 UTC
Comment 10 Olaf Felka 2007-07-07 21:59:19 UTC
Please don't change the version entry. If nobody has fixed this problem it is
logical that it is still in the current version.. We want to know in which
version it has been found.
Comment 11 h.ilter 2007-07-09 10:52:11 UTC
Comment 12 philipp.lohmann 2007-07-09 10:59:29 UTC
pl->cd: Is this a framework or application issue ?
Comment 13 carsten.driesner 2007-07-23 10:23:49 UTC
cd: Must be checked if this is a pipe communication, command line processing
problem. Otherwise this issue i related to the real printing code.
Comment 14 sb56637 2007-08-21 19:15:41 UTC
If this helps any, I just found out something...  If I manually launch
OpenOffice before trying to batch print in the manner I described, it works.  It
only hangs as I described if I do not have any soffice processes running before
dragging'n'dropping the files onto the print queue.
Comment 15 sb56637 2007-10-11 23:16:01 UTC
Well, this just keeps getting better.  I upgraded to 2.3.0, and now batch
printing is completely broken.  In fact, I can't even print a single file from
the Windows Explorer / Printer Queue interface.
Comment 16 Mathias_Bauer 2007-12-04 16:19:08 UTC
according to release status meeting -> target 3.x
Comment 17 billp 2010-07-23 16:24:23 UTC
I have the same problem with ODT files in OOo 3.2.1 on Vista. If the
Quickstarter is disabled and OOo is not running before trying to print multiple
files from Windows Explorer, only one file is actually printed. Multiple
instances of soffice.bin and soffice.exe processes will then remain running and
must be manually stopped before OOo can be opened.