Bug 135281 - EDITING: Calc crashed after pasting data (CTRL+V) into PyCharm previously copied (CTRL+C) from a Calc sheet
Summary: EDITING: Calc crashed after pasting data (CTRL+V) into PyCharm previously cop...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.5.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2020-07-29 13:07 UTC by conrad_heimbold
Modified: 2021-06-11 03:50 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description conrad_heimbold 2020-07-29 13:07:35 UTC
Description:
See "Steps to Reproduce". 

Somehow, I wasn't able to get a gdb stacktrace/backtrace. I have all the necessary gdb debugsymbols installed but I don't know what to do on the gdb commandline. The gdb commandline disappears after running: 
$ gdb --pid=$(pidof soffice.bin) 
(gdb) c
Could you help me with this? Thank you! 
When I choose "Beenden erzwingen" (Force quit) in Calc, the process gets killed of course; so gdb cannot get any stacktrace/backtrace. 

Steps to Reproduce:
1. Open PyCharm, create a new python file. 
2. Open Libreoffice Calc. 
3. Write something into a cell. 
4. Copy the data from that cell (CTRL+C). 
5. Paste the data into your python file in PyCharm (CTRL+V). 

Actual Results:
6. Result: Calc freezes/crashes and becomes unresponsive. 

Expected Results:
6. The data gets pasted into PyCharm, Calc continues. 


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 6.4.5.2
Build ID: 6.4.5.2-2.fc32
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3; 
Locale: de-DE (de_DE.UTF-8); UI-Language: en-US
Calc: threaded
Comment 1 Julien Nabet 2020-07-29 14:15:50 UTC
Here's a link to help about retrieving a bt.
Comment 2 conrad_heimbold 2020-08-14 22:23:35 UTC
I can't see any link. Can you send the link again?
Comment 3 Julien Nabet 2020-08-15 07:03:08 UTC
(In reply to conrad_heimbold from comment #2)
> I can't see any link. Can you send the link again?

Sorry for the missing link, here it is:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Comment 4 Xisco Faulí 2020-11-11 19:17:10 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2021-05-11 03:51:59 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-06-11 03:50:39 UTC
Dear conrad_heimbold,

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