Bug 73498

Summary: CRASH: Fatal Python error: Py_Initialize: can't initialize sys standard streams via Tools Customize Events causes a crash when clicking on the "macro" button
Product: LibreOffice Reporter: pierre-yves samyn <pierre-yves.samyn>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: michael.stahl, serval2412
Priority: high    
Version: 4.3.0.0.alpha0+ Master   
Hardware: Other   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Screenshot tools customize crash
Windbg_ToolsCustomizeEventsMacro.txt

Description pierre-yves samyn 2014-01-11 11:59:27 UTC 
Created attachment 91857 [details]
Screenshot tools customize crash

Hello

Platform : windows 7/64 Version: 4.3.0.0.alpha0+
Build ID: ae8e579515fff84cbef1ccc2da78fa769fb079ec
TinderBox: Win-x86@39, Branch:master, Time: 2014-01-10_11:16:31

Steps to reproduce:

1. Start LibreOffice
2. Tools> Customize> Events tab 
3. Click the Macro button

the system shows "LibreOfficeDev has stopped working"
("LibreOfficeDev a cessé de fonctionner" in french)
See attached screenshot

Windbg !analyze -v produces nothing but two lines before there is an error:
Fatal Python error: Py_Initialize: can't initialize sys standard streams

See attached Windbg_ToolsCustomizeEventsMacro.txt

Regards
Pierre-Yves
Comment 1 pierre-yves samyn 2014-01-11 12:01:00 UTC 
Created attachment 91858 [details]
Windbg_ToolsCustomizeEventsMacro.txt
Comment 2 Julien Nabet 2014-01-12 08:35:49 UTC 
I put it at New since there's a bt.

Michael: could it be related to Python 3.3.3 upgrade?
Comment 3 Julien Nabet 2015-04-07 21:15:06 UTC 
On pc Debian x86-64 with master sources updated today, I don't reproduce this.

On Win8 with no JRE+LO 4.3.6, I don't reproduce this. I must recognize I thought it would hang after the warning about the fact there was no JRE but finally, LO opened Macro selection dialog.

Pierre-Yves: Could you give a new try with a recent LO version (4.3.6 or 4.4.2) + a brand new profile if needed?
Comment 4 pierre-yves samyn 2015-04-08 06:57:40 UTC 
Hi Julien 

Thank's for testing

I can not reproduce the bug on windows 7 pro & Version: 4.4.1.1
Build ID: b5ac74bf8683a92078a2bc8aff97d4b436af63cb
Locale : fr_FR

I will try also with 4.4.2

Regards
Pierre-Yves
Comment 5 Julien Nabet 2015-04-08 21:11:32 UTC 
I put it as WFM but don't hesitate to reopen this tracker if you can reproduce it on 4.4.2.
In this case it would be a regression but with just a range of 1 minor version (kindda of pre bibisect! :-))
Comment 6 pierre-yves samyn 2015-04-09 06:28:08 UTC 
(In reply to Julien Nabet from comment #5)
> I put it as WFM but don't hesitate to reopen this tracker if you can
> reproduce it on 4.4.2.
> In this case it would be a regression but with just a range of 1 minor
> version (kindda of pre bibisect! :-))


No crash with Version: 4.4.2.2
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Locale: fr_FR

WFM too :)

Regards
Pierre-Yves