Bug 146989 - Crash when opening Printer Settings ("EXCEPTION_ACCESS_VIOLATION_READ" in ssp2mu.dll)
Summary: Crash when opening Printer Settings ("EXCEPTION_ACCESS_VIOLATION_READ" in ssp...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Printer-Settings Crash
  Show dependency treegraph
 
Reported: 2022-01-25 18:34 UTC by muesliflyer
Modified: 2024-06-09 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["ssp2mu.dll"]


Attachments
printer settings dialog (10.60 KB, image/png)
2022-01-25 18:34 UTC, muesliflyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description muesliflyer 2022-01-25 18:34:39 UTC
Created attachment 177786 [details]
printer settings dialog

This bug was filed from the crash reporting server and is br-f4f89c82-51ca-42d7-99bf-fc526d956cd9.
=========================================

My Windows default printer is a network printer connected to a Raspberry Pi (with CUPS 1.7.5 as a raw printer device):

\\http://raspberrypi:631\Canon_MP550_raw

Another printer with same problem:

\\raspberrypi\SKG-Laser-2 (Samsung ML-1640)

Steps to reproduce:

Open empty.ods (an empty LO spreadsheet)

File -> printer settings

Push printer settings button in the printer settings dialog to the right of the printer name.

LO crashes

A second execution of the above procedure produces this crash report:
https://crashreport.libreoffice.org/stats/crash_details/0b11307d-407b-4b8d-9b20-2415a6436cd5
Comment 1 Stéphane Guillou (stragu) 2023-04-28 22:55:01 UTC
Thank you for the report.
Could you please test again with a currently-supported version of LibreOffice, 7.4 or 7.5, to see if the issue persists?
Comment 2 QA Administrators 2023-10-26 03:14:55 UTC Comment hidden (obsolete)
Comment 3 muesliflyer 2023-10-29 16:13:51 UTC
I reproduced the bug with

LibreOffice 7.5.7.1

https://crashreport.libreoffice.org/stats/crash_details/1a8e1292-1a03-4458-94e4-35ca1d5fb4e8
Comment 4 QA Administrators 2023-10-30 03:13:18 UTC Comment hidden (obsolete)
Comment 5 Stéphane Guillou (stragu) 2023-11-10 12:32:11 UTC
Cloph on IRC chased down this Firefox report, crashing when opening printer settings: https://bugzilla.mozilla.org/show_bug.cgi?id=1547379

See in particular this comment with the same DLL in the crash signature: https://bugzilla.mozilla.org/show_bug.cgi?id=1547379#c5
and this comment about updating drivers: https://bugzilla.mozilla.org/show_bug.cgi?id=1547379#c8

Please try updating your printer drivers and report back if you still experience the issue.
Ultimately, it doesn't look like something we'd have to fix on our end, but more of a driver or Windows issue.
Comment 6 QA Administrators 2024-05-09 03:16:40 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2024-06-09 03:15:00 UTC
Dear muesliflyer,

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