Description: LibreOffice crash when opening properties for samsung CLX-3175N. It prints if directly given "OK". There is no problem with other programs. There is no problem with other printers I am using, even for samsung C-460 or clx-3300. Actual Results: Open print file and try the properties box Expected Results: LibreOffice crash. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Would it be possible you give a try to last stable LO version 5.2.2? If you still reproduce this, could you retrieve a backtrace (see https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg)?
This also happens to me with an HP Photosmart C4500 series as well as the Nitro PDF printer when using both Writer and Calc (Version: 5.3.2.2 (x64) Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1) on Windows 10 (x64). I open the Print dialog, select the printer and click the Properties button. This opens up another dialog box where the tab names are missing. When I click on a tab (or two or three), the application crashes. Every time. I was also unable to retrieve a valid backtrace: When WinDbg is running and attached to soffice.bin, LibreOffice Calc freezes completely. I have to stop and close WinDbg, then Calc crashes. When WinDbg is running and attached to soffice.exe or scalc.exe, I open the Print dialog in Calc, select the printer and click the Properties button. This opens up another dialog box where the tab names are missing. When I click on a tab (or two or three), the application crashes and WinDbg doesn't record anything. (Remains set to "int 3".)
Since I don't have more questions for the moment and someone else confirmed, let 's put this one to NEW.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I have this problem with Libre Office 6.1.5.2. When I try to open Properties on my Samsung ML-2550 printer Libre Office crashes. This problem first appeared with Libre Office 5. I also have the same problem with Pale Moon and Firefox when trying to print web pages.
(In reply to omnes from comment #5) > I have this problem with Libre Office 6.1.5.2. >... > I also have the same problem with Pale Moon and Firefox when trying to print > web pages. If you got also this pb with Pale Moon and Firefox, it doesn't seem a LO specific problem. Anyway, you can retrieve a backtrace by following this link: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Could you try this: - check you got last updates of your printer/scan driver - upgrade to LO 6.4.3 - rename your LO profile (see https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile) ?
Dear aafskerr, 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
Dear aafskerr, 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