Description: The program freezes when pasting text into the "File name:" field in the "Microsoft Print to PDF" printer. Steps to Reproduce: 1. Copy text from withing the document to be used in/as the file name. 2. Open the "Print" dialog. 3. Select "Microsoft Print to PDF" as the printer and click "OK". 4. Paste the copied text into the "File name:" field. 5. Freeze. Actual Results: The application froze. Expected Results: Save the file as a PDF on my desktop. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 6.2.7.1 (x64) Build ID: 23edc44b61b830b7d749943e020e96f5a7df63bf CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL After copying the text inside of LibreOffice Write document I followed the steps in another program, IrfanView, and it worked as expected. GL Report: Renderer: AMD Radeon HD 7700 Series Vendor: ATI Technologies Inc. Memory: 1024 MB Version: 4.6.13559 Core Profile Forward-Compatible Context 26.20.12001.7006 Shading language version: 4.60
Created attachment 154161 [details] File used when the bug was encountered The first two words from the document, "Understanding Broilers", were copied and pasted into the "File name:" field of the "Microsoft Print to PDF" dialog when the bug was encountered.
reproducible, even with AOO 4.1.5
On Win10 with master sources updated today, I don't reproduce this. However, it creates a PDF named "Understanding Broilers" containing just "Understanding Broilers" (!!).
I can confirm with Version: 6.4.0.0.beta1 (x64) Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920 CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: CL Additional information. A. Simpler procedure to produce, using an empty / new / minimal document. For example: 1. Open New Document. 2. Write "abcd" on the first line, then select and copy (Ctrl-C) 3. Open "Print" dialog. 4. Select "Microsoft Print to PDF" as the printer and click "OK". 5. Paste (Ctrl-V) into the File name field in the "Save Print Output As" window. Actual result: Freeze (i.e., cannot cancel or close the "Save Print Output As" window, cannot access other document windows). B. According to Microsoft's Task Manager, both soffice.exe and soffice.bin are running, but LO is not responsive. C. If Ctrl-V has nothing in its buffer to paste (i.e., is "empty"), then no freeze when using Ctrl-V D. No problem to write manually into the Field name and print the document (to PDF).
On Win10 with master sources updated today, I could reproduce this. I noticed we had the same pb with "Microsoft XPS Document Writer".
Mike: noticing https://cgit.freedesktop.org/libreoffice/core/commit/?id=84be3e396cae16a975c7c7f5b892e6b615b73356, thought you might have some idea here?
Created attachment 157317 [details] bts on windbg Here are all the bts retrieved on Windbg on Win10 with master sources updated today. Steps to retrieve them: - launch LO from cygwin term - launch Windbg and attach LO process + "g" - reproduce the freeze with sdc.blanco's comment - Ctrl-c one (2 times if needed) on Cygwin => Windbg allows to launch the following command: ~*k All bts display on Command window but you can't copy paste bts from Windbg since clipboard is locked for all apps in Windows. solution: in Windbg, menu Edit, Write Window Text to File...
Let's increase a bit importance since clipboard problem seems to have larger impact than printing.
Dear bitcat70, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
works for me Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: bb29b12a9e367d181a5d9d962d466df41e093e0c CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL
*** Bug 149998 has been marked as a duplicate of this bug. ***
Not reproducible for me. Considering sdc (comment 10) can't reproduce either, going to mark this report as WORKSFORME. Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Still repro. However, in bug 149998 comment 1 Stuart said "happens with other applications as well. Word 2019 for example". So it might be notourbug. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c0c8cffd3541e3cd616c96791b04e7ebf2b2ed03 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Reproduced with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5dac0fe157a5c35824cab2c27e391ff7a0d1d421 CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded While debugging with "Visual Studio 2022", I pressed pause button when freeze happened. Using "Enable Just My Code" option, I get this message: Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code) When not using the above option, I get this stack trace: ntdll.dll!NtWaitForSingleObject() KernelBase.dll!WaitForSingleObjectEx() nvwgf2umx.dll!...() nvwgf2umx.dll!...() kernel32.dll!BaseThreadInitThunk() ntdll.dll!RtlUserThreadStart() During the period of the freeze, copy/paste does not work in any application. Note that I don't face freeze when doing the same thing in MS Office Word, copy text from Word and pasting that in the print dialog.
Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/07dfeffae8cba808dbad85dfed9b6a693a1f9543 tdf#127547 Freeze in Microsoft Print to PDF dialog It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Thanks to Julien for providing a useful stacktrace, and to Hossein for testing the patch
(In reply to Noel Grandin from comment #16) > Thanks to Julien for providing a useful stacktrace, and to Hossein for > testing the patch No pb, if providing a bt or a Valgrind trace may help don't hesitate to ask! :-)
Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/98a35222bdc0b4dcf146c40248799addd2fbf510 tdf#127547 Freeze in Microsoft Print to PDF dialog It will be available in 7.6.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.