Bug 156588

Summary: Changing language crashes LO (Not Responding)
Product: LibreOffice Reporter: Peter Wilkins <wilkins.peter>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: buzea.bogdan, ilmari.lauhakangas, miguelangelrv, serval2412
Priority: medium    
Version: 7.5.4.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=156535
https://bugs.documentfoundation.org/show_bug.cgi?id=155939
Whiteboard:
Crash report or crash signature: Regression By:

Description Peter Wilkins 2023-08-03 00:50:25 UTC
Description:
Recently, LO crashes (Not Responding) whenever I try to change language, per:
> Tools > Language > For All Text > English (Canada)
This does not happen for all documents, but I am unable to share documents where this happens.  I am trying to create a sanitized document where this happens that I can share. So, this appears to be related to something contained in the document - but this problems occurs regularly.

Steps to Reproduce:
1. Open document
2. Select text
3. > Tools > Language > For All Text > English (Canada)

Actual Results:
Kaboom! (Not Responding)

Expected Results:
It should have changed the language and allowed me to continue editing


Reproducible: Always


User Profile Reset: No

Additional Info:
I am trying to create a dummy document (no confidential info) which exhibits this problem - so far without success, but I am working on it.
Comment 1 m_a_riosv 2023-08-03 00:56:18 UTC
Please test in safe mode, Menu/Help/Restart in Safe Mode
Comment 2 Julien Nabet 2023-08-03 06:38:49 UTC
I don't think it'll help a lot but please upgrade to LO 7.5.5 so at least we'll know if it's still relevant in the last LO version.
Comment 3 Stéphane Guillou (stragu) 2023-08-03 08:02:23 UTC
(In reply to Julien Nabet from comment #2)
> I don't think it'll help a lot but please upgrade to LO 7.5.5 so at least
> we'll know if it's still relevant in the last LO version.

I think it might actually solve it, it's likely a duplicate of bug 155939.
Marking as such, but please let us know if you can still reproduce in 7.5.5, Peter.
Thanks!

*** This bug has been marked as a duplicate of bug 155939 ***
Comment 4 Peter Wilkins 2023-09-05 00:28:44 UTC
It only happens for some documents and I have never been able to identify what might trigger it.  I am currently on v7.5.5.2 and - so far - I have not experienced this problem recently.  I believe (but not totally sure) that I last experienced this problem after upgrading to v7.5.5.2.  However, it does seem to be the same bug as described in bug 155939.  I will check back if the problem resurfaces.
Comment 5 Julien Nabet 2023-09-05 12:23:36 UTC
(In reply to Peter Wilkins from comment #4)
> It only happens for some documents and I have never been able to identify
> what might trigger it.  I am currently on v7.5.5.2 and - so far - I have not
> experienced this problem recently.  I believe (but not totally sure) that I
> last experienced this problem after upgrading to v7.5.5.2.  However, it does
> seem to be the same bug as described in bug 155939.  I will check back if
> the problem resurfaces.

Perhaps I wrongly understood what you meant but If you experienced this after having upgrading to v7.5.5.2, it can't be the same as tdf#155939 since this last one has been fixed (and verified) for 7.5.5.2.
Comment 6 Buovjaga 2023-09-21 16:17:50 UTC
Any problem recently? Should we close as duplicate for good?
Comment 7 Stéphane Guillou (stragu) 2024-03-04 05:27:37 UTC
No response, let's go back to duplicate.
Peter, if you can still reproduce in a recent version, please provide a sample file and set back to "unconfirmed"
Thank you!

*** This bug has been marked as a duplicate of bug 155939 ***