Bug 100605

Summary: Crash when copy-pasting in watch inspector during Basic editing (gtk3 and not easily reproduceable)
Product: LibreOffice Reporter: Julien Nabet <serval2412>
Component: BASICAssignee: Caolán McNamara <caolan.mcnamara>
Status: CLOSED FIXED    
Severity: normal CC: ilmari.lauhakangas
Priority: medium Keywords: haveBacktrace
Version: 5.3.0.0.alpha0+   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 103182    
Attachments: console bt logs

Description Julien Nabet 2016-06-25 17:11:37 UTC 
Created attachment 125902 [details]
console bt logs

On pc Debian x86-64 with master sources updated today, I had a crash when try to to copy-paste a variable in watch inspect.

Steps to reproduce (not sure because I can't reproduce this easily):
1) Retrieve the file here 
https://bugs.documentfoundation.org/attachment.cgi?id=114772
2) Open the file
3) Menu Tools/Macros/Organize Macros/LO Basic
4) Edit Bug90600.ods/Standard/LibFilter
5) Double click on a variable to watch it
6) Type F8 to begin to debug TodaysWeekday

=> crash
I'm not sure after step 4), sorry :-(
Comment 1 Buovjaga 2016-07-02 18:28:41 UTC 
No crash. I watched variable oDBR and stepped with F8 dozens of times.

Julien: if you think your console logs qualify for it, set the keyword haveBacktrace

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: ef47ce2397d4ed453fe01d994d13a13f442ec3bb
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on July 2nd 2016
Comment 2 Julien Nabet 2016-07-02 18:52:10 UTC 
(In reply to Buovjaga from comment #1)
> No crash. I watched variable oDBR and stepped with F8 dozens of times.
> 
> Julien: if you think your console logs qualify for it, set the keyword
> haveBacktrace
>... 


Thank you for testing! You're right indeed, let's put haveBacktrace but let unconfirmed (since I'm the only one to have this)
Comment 3 Caolán McNamara 2016-10-18 11:25:57 UTC 
This was filed on the 26th of June. Since then I fixed rhbz#1352965, rhbz#1351369 and rhbz#1350478 and rhbz#1362451 which are all gtk3 related cut and paste problems.

I'm not sure that this one is the same problem as those, but I think its likely enough that I'll call this fixed. But if anyone can get this to crash with this backtrace again, then definitely reopen. Trying myself here it all seems to work ok
Comment 4 Julien Nabet 2016-10-18 17:17:16 UTC 
Indeed, I don't reproduce this, thank you! :-)