Bug 115616 - Crash in: framework::ToolBarManager::UpdateControllers()
Summary: Crash in: framework::ToolBarManager::UpdateControllers()
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-10 16:47 UTC by Oliver Heard
Modified: 2018-10-09 11:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["framework::ToolBarManager::UpdateControllers()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Heard 2018-02-10 16:47:28 UTC
This bug was filed from the crash reporting server and is br-1a9ea404-e30e-4dff-afe8-2ff64c9c261d.
=========================================

This occurred when I was customising the Standard toolbar in Customise -> Toolbars. I was going through deselecting most of the icons from top to bottom and I /think/ my finger slipped on my touch pad when the crash happened. It might have been when I deselected something though.

Interestingly even though Writer crashed it saved the changes (the other icons I had deselected) before I'd pressed "OK" (I didn't get the chance to). I don't know if that's a bug too but I'm glad it did that, suits me!

I've set the arch and OS fields for this bug to those that I'm using, I don't know if it's limited to those though.
Comment 1 Xisco Faulí 2018-02-12 19:10:44 UTC Comment hidden (obsolete)
Comment 2 Oliver Heard 2018-02-13 00:42:56 UTC
It's a tough one because I'm not sure what actually triggered the crash due to the (possible) touch pad slippage. Therefore reproducing it intentionally is unlikely.

I'd hoped the crash dump would have enough info for those familiar with the code base to see any immediate problems.

Having gone back in and finished customising the toolbars it hasn't crashed again.

I'll change the status back to UNCONFIRMED in case you guys want to do anything more with it but if it does ever happen again (I still need to customise a few other programs) I'll return with more details.

In the meantime I don't see any harm in it being set to RESOLVED for bookkeeping purposes if that suits you.
Comment 3 Xisco Faulí 2018-02-14 10:00:53 UTC
@Muhammet, do you know why this might be crashing ?
Comment 4 Muhammet Kara 2018-02-19 13:56:13 UTC
(In reply to Oliver Heard from comment #0)
> This bug was filed from the crash reporting server and is
> br-1a9ea404-e30e-4dff-afe8-2ff64c9c261d.
> =========================================
> 
> This occurred when I was customising the Standard toolbar in Customise ->
> Toolbars. I was going through deselecting most of the icons from top to
> bottom and I /think/ my finger slipped on my touch pad when the crash
> happened. It might have been when I deselected something though.
> 
> Interestingly even though Writer crashed it saved the changes (the other
> icons I had deselected) before I'd pressed "OK" (I didn't get the chance
> to). I don't know if that's a bug too but I'm glad it did that, suits me!

That's the known (and wrong) behavior, and it was decided to be changed, but not done so far.

> 
> I've set the arch and OS fields for this bug to those that I'm using, I
> don't know if it's limited to those though.


(In reply to Xisco Faulí from comment #3)
> @Muhammet, do you know why this might be crashing ?

Didn't ring a bell at first sight, and I couldn't reproduce it with latest master on Linux.

Version: 6.1.0.0.alpha0+
Build ID: 7d4584a18fac7f37ed0f7b3b26e6e1a9d65da26f
CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 5 Xisco Faulí 2018-02-19 14:33:47 UTC
Thanks Muhammet,
Putting to NEEDINFO until steps to reproduce the issue are provided
Comment 6 QA Administrators 2018-09-03 14:50:14 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2018-10-09 11:31:23 UTC
Dear Bug Submitter,

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-20181009