Bug 155102 - Writer crashes when opening sidebar
Summary: Writer crashes when opening sidebar
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-01 10:06 UTC by ab1985
Modified: 2023-12-04 03:18 UTC (History)
4 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 ab1985 2023-05-01 10:06:59 UTC
Description:
When I want to open the sidebar to change text format in Writer LibreOffice crashes.
At first it crashed immediately when trying to open the sidebar. Now I can open the sidebar but as soon as I want to change to formatting patterns LibreOffice crashes.
This is very annoying since I need the option to quickly change text format for my profession.

Steps to Reproduce:
1.Open Writer
2.Open sidebar
3.Change to tab "formatting patterns"

Actual Results:
LibreOffice crashes.

Expected Results:
Not crashing but letting me choose formatting patterns.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: StartModule
[Information guessed from browser]
OS: Linux (Ubuntu 22.04.2 LTS)
OS is 64bit: yes
Comment 1 Julien Nabet 2023-05-01 11:11:10 UTC
Sidebar has different entries:
- Properties
- Styles
- Gallery
- Navigator
- Page
- Style Inspector
- Manage Changes
- Accessibility Check

where is "formatting patterns"?
Comment 2 Telesto 2023-05-01 19:26:44 UTC
First guess: profile corruption.
https://wiki.documentfoundation.org/UserProfile#Resolving_corruption
Comment 3 ab1985 2023-05-02 17:51:20 UTC
(In reply to Julien Nabet from comment #1)
> Sidebar has different entries:
> - Properties
> - Styles
> - Gallery
> - Navigator
> - Page
> - Style Inspector
> - Manage Changes
> - Accessibility Check
> 
> where is "formatting patterns"?

Translation problem here. The second entry "Styles" is called "Formatvorlagen" in German. This translates to formatting patterns.
Comment 4 ab1985 2023-05-02 17:52:09 UTC
(In reply to Telesto from comment #2)
> First guess: profile corruption.
> https://wiki.documentfoundation.org/UserProfile#Resolving_corruption

Will try that and let you know if it solves the problem.
Comment 5 QA Administrators 2023-05-03 03:18:38 UTC Comment hidden (obsolete)
Comment 6 Stéphane Guillou (stragu) 2023-05-03 13:02:30 UTC
Can't confirm either on Ubuntu 20.04 with:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: fb3a6b82b55a298eabf8f431f1451dc826642acd
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Nor in:

Version: 7.5.3.1 (X86_64) / LibreOffice Community
Build ID: d29ee673721b12c92b3de9b9663473211414f0db
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Let us know how you go with a profile reset, and if you do reproduce, please share the information copied from Help > About LibreOffice.

I changed the hardware field from 32 to 64 bit given the info in your description.

Thank you!
Comment 7 ab1985 2023-05-06 11:32:33 UTC
(In reply to Stéphane Guillou (stragu) from comment #6)
> Can't confirm either on Ubuntu 20.04 with:
> 
> Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
> Build ID: fb3a6b82b55a298eabf8f431f1451dc826642acd
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
> Locale: en-AU (en_AU.UTF-8); UI: en-US
> Calc: threaded
> 
> Nor in:
> 
> Version: 7.5.3.1 (X86_64) / LibreOffice Community
> Build ID: d29ee673721b12c92b3de9b9663473211414f0db
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
> Locale: en-AU (en_AU.UTF-8); UI: en-US
> Calc: threaded
> 
> Let us know how you go with a profile reset, and if you do reproduce, please
> share the information copied from Help > About LibreOffice.
> 
> I changed the hardware field from 32 to 64 bit given the info in your
> description.
> 
> Thank you!


Update: The problem seems to have solved itself. I've just opened Writer and tried to reproduce the problem but nothing happened.
So before I do something with the user profile, I just try to go on. If the problem reoccurs, I'll try to reset the user profile.
Will keep you updated!
Comment 8 QA Administrators 2023-05-06 12:51:31 UTC Comment hidden (obsolete)
Comment 9 Dieter 2023-05-06 13:32:05 UTC
(In reply to ab1985 from comment #7)
> Update: The problem seems to have solved itself. I've just opened Writer and
> tried to reproduce the problem but nothing happened.
> So before I do something with the user profile, I just try to go on. If the
> problem reoccurs, I'll try to reset the user profile.
> Will keep you updated!

Good to read. So let's change status to NEEDINFO for the moment. Please let us know, if it happens again.
Comment 10 QA Administrators 2023-11-03 03:15:40 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2023-12-04 03:18:19 UTC
Dear ab1985,

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