Bug 146111 - CRASH when working with cell borders and click user defined box
Summary: CRASH when working with cell borders and click user defined box
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-08 04:32 UTC by James
Modified: 2022-07-22 03:44 UTC (History)
2 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 James 2021-12-08 04:32:35 UTC
Description:
I had set cell borders for one row too many in my document and went into the menu again to reset them. I didn't see an immediate option for removing and setting the borders like excell has to give a side/bottom border change so I clicked on the user defined borders option box in the middle of the window and it crashed the program. 

Steps to Reproduce:
First, my program version is 7.2.4 which is not in your window above^
Second, I went back and tried it again with the same crash result.

1.set a group of cells to full borders around each cell.
2.go back into format cells with bordered cells still selected and click any cell line in the "user defined" cell borders image. 
3.watch it crash

Actual Results:
Program crashes. everything else running on computer is fine, but the libre calc file just disappears and when you go to reopen it from it's folder you have to recover it.

Expected Results:
wanted to be able to set borders manually using the user selection tool.


Reproducible: Always


User Profile Reset: No



Additional Info:
I was not sure what to put in the hardware box above, I am not a computer genius. I am using a ROG gaming laptop and in the device manager settings tab I found something labelled processors and it said: AMD RYZEN 7 3750H with Radeon Vega Mobile GFX. I don't know if that is what hardware box above was looking for but maybe that helps.
Comment 1 Rainer Bielefeld Retired 2021-12-08 07:53:49 UTC
NOT reproducible with Installation of Version 7.2.3.2 (x64) / LibreOffice 
Build  d166454616c1632304285822f9c83ce2e660fd92; CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI: de-DE; Calc: threaded;  My normal User Profile

@reporter:
Please try with a fresh new User Profile (Close LibO, rename your User Profile, detailed info at <https://wiki.documentfoundation.org/UserProfile#Resolving_corruption>
Comment 2 raal 2021-12-22 16:26:56 UTC
No crash Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 40487d9c81c69c4e5ee1621e53c8162ae33c80b2
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

Please try with a fresh new User Profile.
Comment 3 QA Administrators 2022-06-21 03:30:15 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-07-22 03:44:41 UTC
Dear James,

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