Description: crashreport.libreoffice.org/stats/crash_details/3675c59a-29e6-409d-a816-95966355fcc6 It seems to be a problem of printer properties dialogue window (network printer Minolta C220) and windows 10. At least even opening printer properties from inside Windows Control Panel also doesn't work. Anyway, LibreOffice shouldn't be impressed that much by that fawlty printer properties dialogue window. Steps to Reproduce: 1. Open menu "Datei", "Drucken..." (probably "File", "Print..." in english 2. Window "Drucken" (probably "Print" appears, on the left is a preview, on the right at the top there is a list of printers. Choose "\\....local\MINOLTA C220..." 3. Under the list of printers, press button "Eigenschaften..." (probably "properties") [Btw.: Under Windows, one can also 1. open "Einstellungen", "Drucker & Scanner" (probably "Preferences", "Printers & Scanners") 2. Choose "MINOLTA C220", press button "Verwalten" (probably "Manage") 3. Choose "Druckereigenschaften" (probably "printer properties") 4. Under tab "Allgemein" (probably "General") choose button "Einstellungen..." (probably "Preferences") 5. The Manage-window silently closes, no preferences-windows appears] Actual Results: Upon pressing the button "Eigenschaften..." as described under "Steps to Reproduce", LibreOffice crashes. Expected Results: There should be an error message like e.g. "Sorry, but the printer properties dialogue yielded unexpected results. We tried hard, but it seems not possible to use printer properties." Reproducible: Always User Profile Reset: No Additional Info: Version: 6.1.6.3 (x64) Build-ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: threaded I don't know weather OpenGL is enabled, hence I left the Question unticked
The weather is too hot, probably the reason why I didn't write "whether"
Could you give a try to LO 6.2.6 or brand new 6.3.0 if you still reproduce the crash?
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
6.2.6.2 (as downloaded about an hour before) looks the same. Rf. crashreport.libreoffice.org/stats/crash_details/6310b87c-2f74-48d6-b410-302c2006ba42
(In reply to Peter from comment #4) > 6.2.6.2 (as downloaded about an hour before) looks the same. Rf. > crashreport.libreoffice.org/stats/crash_details/6310b87c-2f74-48d6-b410- > 302c2006ba42 Version: 6.2.6.2 (x64) Build-ID: 684e730861356e74889dfe6dbddd3562aae2e6ad CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
I just noticed this part of initial comment: "At least even opening printer properties from inside Windows Control Panel also doesn't work". So without talking about LO, you can't see printer properties on Windows. Could you try to uninstall then reinstall driver by using last version from here: https://www.konicaminolta.eu/eu-en/support/download-centre ? Indeed, it must work at least on Windows, if not it's not worth trying on LO.
(In reply to Julien Nabet from comment #6) > So without talking about LO, you can't see printer properties on Windows. It depends. There are some apps. that can open it: Outlook, MS Word and AtmelStudio (based on MS VisualStudio) are able to open it, my colleague uses Adobe Reader successfully. Other programs don't (e.g. Notepad++, SumatraPDF, Control Panel). It seems, with the exceptions of Control Panel and Adobe, that Windows stuff are able, other stuff aren't. I don't expect LO to give me a working printer requester if that is faulty. I just thought about a (fateful) dependency on the well behaving of third party software. After all, only thanks to the well working document recovery this issue isn't critical. Regrettably, the printer driver is not under my responsibility. We are in contact with our IT department.
there are a number of issues with Windows, 10 printing, mostly caused by their updates. please write your exact Win10 version and build.
Dear Peter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Could you try this: - check you got last updates of your Minolta printer driver - upgrade to LO 6.4.3 - rename your LO profile (see https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile) ?
Dear Peter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp