Bug 104991 - "unknown SEH exception" when trying to print on HP LaserJet 1000 series
Summary: "unknown SEH exception" when trying to print on HP LaserJet 1000 series
Status: RESOLVED DUPLICATE of bug 104952
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
5.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-29 21:34 UTC by arielmazatlan
Modified: 2017-01-04 13:28 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
"unknown SEH exception" when trying to print (99.68 KB, text/plain)
2016-12-29 21:34 UTC, arielmazatlan 		Details
View All 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 arielmazatlan 2016-12-29 21:34:10 UTC 
Created attachment 130021 [details]
"unknown SEH exception" when trying to print

As suggested by @Buovjaga , in https://bugs.documentfoundation.org/show_bug.cgi?id=94830#c6 I'm opening this new report with my problem.

I'm attaching a back trace file.

The problem most of the time occurs when opening the print dialog, but doesn't happen all the time. I haven't tried printing thought, and I'm not so sure anymore, but seem to have something to do with an specific printer being present in the system.

I was able to use LibreOffice 4.7.2 with no problem, but LibreOfice 5.2.4 and 5.3 Beta 2 has it.

I'm using Windows XP, and the printer I was referring to is a very old one, a HP LaserJet 1000 series. 

Thank you.
Comment 1 Julien Nabet 2016-12-30 11:25:31 UTC 
Mariosv/Buovjaga: there are now 3 bugtrackers about printing crash, wonder if:
1) They could be the same problem
2) Above all, if we could increase to highest priority since:
- it's a crash
- it's a regression
- it's a common use case
(but it seems only on Windows)
Comment 2 Buovjaga 2016-12-30 15:58:29 UTC 
Hard to say without backtraces. Unfortunately, the trace from Ariel was not successful (nothing produced by analyze) :(
Comment 3 Timur 2016-12-30 16:28:14 UTC 
(In reply to Buovjaga from comment #2)
> Hard to say without backtraces. Unfortunately, the trace from Ariel was not
> successful (nothing produced by analyze) :(
In that case, I'd go with "kb" that prints stack trace and "~* kp" to dump the whole stack.
Comment 4 arielmazatlan 2016-12-31 17:01:36 UTC 
I'll be making a new back track today following the additional procedures shown in https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump

Thank you all for your help. I'll report back as soon I get the chance.
Comment 5 arielmazatlan 2016-12-31 20:12:29 UTC 
I tried using ProcDump as descrived in https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump but I get trhe following error while trying to run ProcDump:

The procedure entry point CxxFrameHandler3 could not be located in the dynamic link library msvcrt.dll

Any help? The artitle says something about using a "LibreOffice debug build" but I'm using 5.2.4 that I downloaded from the libreoffice website, could that be it?
Comment 6 Buovjaga 2016-12-31 20:26:54 UTC 
(In reply to arielmazatlan from comment #5)
> Any help? The artitle says something about using a "LibreOffice debug build"
> but I'm using 5.2.4 that I downloaded from the libreoffice website, could
> that be it?

Here is a debug build: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/
It installs in parallel and will not mess up your stable installation.
Comment 7 arielmazatlan 2016-12-31 21:05:43 UTC 
Thanks a lot C:, I won't be able to report back until Monday though.
Comment 8 Julien Nabet 2017-01-04 13:28:23 UTC 

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