https://bugs.documentfoundation.org/show_bug.cgi?id=147822

robert_hartm...@gmx.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #10 from robert_hartm...@gmx.net ---

(In reply to Timur from comment #8)
> Multiple problems here while rule is: One issue per bug. 

Well, it depends on definition, of the word "problem".
I have one problem : 
I cannot save the single choice radiobuttons for interaction with excel-users.

But if you say, hey there are multiple reasons for your problem,
then you are right. But for me, all reasons have to be fixed to 
solve that one problem.

As a programmer I do not like to force users to splitt their observations about
reasons into multiple user reports, because for the user it is only one
problem, one issue.

To be fair, technical different reasons could fixed seperate, but the user
issue remains until all reasons have a solution.  

> 1. as for crash, I don't repro, and it may be about NextCloud specifix 
> conf - bug only makes sense if reproducible so please write steps to
> reproduce, otherwise your crash report will be of use in statistics 
> if some crash happens in new versions.

The steps where clear:
a) Open LO
b) create two radio option buttons 
c) link their data with a cell
d) put them in a group , that is set "group name" value
f) store the file as XLS-File into a Cryptomator vault (cryptomator.org)
   living on a Nextcloud storage.
g) crash while saving.

Even if the crash is hard to reproduce, the crash reporting service had 
captured the crash, so there is an up to now uncovered problem. 
I could not find this signature with searching on bugreporting website. 
And I didn't find your linked bug reports via website.


> 2. repro save as XLS wrong and as XLSX differently wrong,
> when reopened both in LO and MSO 
> - but it seems like a duplicate of bug 136397.

Yes, the bug 136397 from 2020-09-02 handles XLSX - but if it is technical the
same reason, I do not know, but I think so. 


(In reply to Timur from comment #9)
> There's also Bug 79542 for XLS 

Yes, the bug 79542 from 2014-06-02 handles XLS - but if it is technical the
same reason, I do not know, but I think so.

Perhaps the stack trace of crash gives information about where grouping or
choosing-logic get lost.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to