Bug 105546 - Crash in: SalAbort(rtl::OUString const &,bool)
Summary: Crash in: SalAbort(rtl::OUString const &,bool)
Status: RESOLVED DUPLICATE of bug 105015
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-26 15:26 UTC by amersdorfer
Modified: 2017-01-26 18:29 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SalAbort(rtl::OUString const &,bool)"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description amersdorfer 2017-01-26 15:26:31 UTC 
This bug was filed from the crash reporting server and is br-87114cd7-d028-4dbe-9ff5-93244c55910e.
=========================================

Tested with fresh profile.

Crash can always be reproduced.

When opening the Print-Menu (STRG+P), Calc/Writer crashes immediately, as soon as one specific printer is selected, the local USB Laserjet 1020.
If the document is completely empty, changing the printer does not crash LO and an empty page is printed successfully.
As soon as one character is entered (no matter which font), or e.g. one cell in Calc is colored, selecting the Laserjet 1020 in the print-menu crashes LO. If the Laserjet was already selected, the crash happens without even seeing the print-menu.

If the Laserjet is the default-printer, right-clicking a document in explorer and printing does nothing, but soffice.exe and soffice.bin remain in the task-manager, with soffice.bin using 25% cpu until manually removed.

Printing via "Direct print" button also results in a crash, if the Laserjet is the target.

None of these crashes happened with 5.1.6
Comment 1 Xisco Faulí 2017-01-26 18:29:06 UTC 
This is a duplicate of 105015.
Please update your LibreOffice version to 5.2.5.1 which has been released
today.

*** This bug has been marked as a duplicate of bug 105015 ***