Issue 110185 - Crash when printing on non-default printer (probably related to post-it notes)
Summary: Crash when printing on non-default printer (probably related to post-it notes)
Status: CLOSED DUPLICATE of issue 93818
Alias: None
Product: Writer
Classification: Application
Component: printing (show other issues)
Version: OOO320m13
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: max.odendahl
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 12:13 UTC by mux2005
Modified: 2010-06-21 10:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Backtrace of crash (7.54 KB, text/plain)
2010-03-17 12:14 UTC, mux2005 		no flags Details
Valgrind log of crash run (224.83 KB, text/plain)
2010-03-17 12:14 UTC, mux2005 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mux2005 2010-03-17 12:13:36 UTC 
When attempting to print the document ba.odt from issue #96281 on a non-default
printer (i.e. in the print dialog I choose a different printer in the drop-down
box) OOo crashes. The crash is reproducible every time but requires that the
sticky notes sidebar is visible. If it is turned off in Options, the crash does
not occur. So it appears to be yet another bug introduced with the oh-so-pretty
sticky notes. I see the crash under Linux with OOo 3.0.1 and above. I will
attach a backtrace and valgrind run from 3.2.1 m13. I could not reproduce the
crash under Windows.
Comment 1 mux2005 2010-03-17 12:14:08 UTC 
Created attachment 68388 [details]
Backtrace of crash
Comment 2 mux2005 2010-03-17 12:14:47 UTC 
Created attachment 68389 [details]
Valgrind log of crash run
Comment 3 h.ilter 2010-03-26 16:20:13 UTC 
@mod: Please check for duplicate, thanks.
Comment 4 max.odendahl 2010-03-26 16:36:16 UTC 
I guess this is a dup of issue 93818, fixed long time ago, but printerpullpages
did not make it into 3.2

mux: can you test your scenario with latest developer snapshot and close the
issue if it is indeed a dup
Comment 5 mux2005 2010-04-01 15:09:38 UTC 
@mod: Which one do you want me to test? 320_m14 or 300_m74?
Comment 6 max.odendahl 2010-04-01 15:27:40 UTC 
m74
Comment 7 max.odendahl 2010-06-21 10:12:07 UTC 
.

*** This issue has been marked as a duplicate of 93818 ***
Comment 8 max.odendahl 2010-06-21 10:12:53 UTC 
closing