[Bug 54461] New: MS Excel 2007 Printing Fails
https://bugs.winehq.org/show_bug.cgi?id=54461 Bug ID: 54461 Summary: MS Excel 2007 Printing Fails Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skycap1501(a)gmail.com Distribution: --- I am running Linux Mint 21.1 with WINE stable version 8.0 with MS Office 2007 installed. The MS Excel software fails to queue a print job when attempting to print an Excel spreadsheet. However, if I roll back to WINE stable version 7.0.1, then printing works. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Severity|major |minor --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- Please run a regression test: https://wiki.winehq.org/Regression_Testing -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 MaranBr <maranbr(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maranbr(a)outlook.com --- Comment #2 from MaranBr <maranbr(a)outlook.com> --- There seems to be an issue where Wine is erroneously leaving the printer port blank in the course of code execution, so the printer fails and prints nothing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 --- Comment #3 from skycap1501(a)gmail.com --- (In reply to MaranBr from comment #2)
There seems to be an issue where Wine is erroneously leaving the printer port blank in the course of code execution, so the printer fails and prints nothing.
Curiously, the MS Word 2007 software successfully queues a print job. Also, the MS Office 2007 SP3 patch has also been applied. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 --- Comment #4 from MaranBr <maranbr(a)outlook.com> --- Created attachment 74019 --> https://bugs.winehq.org/attachment.cgi?id=74019 Printer log Log of printer processor -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 --- Comment #5 from MaranBr <maranbr(a)outlook.com> ---
From what I was investigating, at some point in the execution of the code, some variables needed by the print processor become blank:
Port DocName OutputFile Datatype Causing this situation: 0374:trace:winspool:StartDocPrinterW (00000003, 1, 0021F008 {L"", L"", (null)}) 0374:trace:localspl:fpStartDocPrinter (01532730 1 0021F008 {pDocName = L"", pOutputFile = L"", pDatatype = (null)}) 0374:trace:localspl:fpScheduleJob need to schedule job 1 filename L"C:\\windows\\system32\\spool\\PRINTERS\\00001.SPL" to port L"" 0374:trace:winprint:OpenPrintProcessor L", Port", 0021DF54 0374:trace:winspool:OpenPrinter2W (L", Port",0021DECC,00000000,00000000) 0374:trace:localspl:fpOpenPrinter (L", Port", 01532B74, 00000000) 0374:trace:localspl:monitor_load_by_port (L"") The process is completed, but nothing is printed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 --- Comment #6 from skycap1501(a)gmail.com --- Will this problem be fixed in a future stable branch update? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 Eugene Savelov <savelov(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |savelov(a)gmail.com --- Comment #7 from Eugene Savelov <savelov(a)gmail.com> --- duplicate of https://bugs.winehq.org/show_bug.cgi?id=54379 the fix is committed to master already -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 --- Comment #8 from Eugene Savelov <savelov(a)gmail.com> --- can you check if it is resolved in wine 8.3 please? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC| |infyquest(a)gmail.com --- Comment #9 from Vijay Kamuju <infyquest(a)gmail.com> --- As reported seems to be duplicate of #54379 *** This bug has been marked as a duplicate of bug 54379 *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54461 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing DUPLICATE. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla