Bug 114033 - Crash in: libgobject-2.0.so.0.5000.3
Summary: Crash in: libgobject-2.0.so.0.5000.3
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.4.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-24 18:09 UTC by Howard Johnson
Modified: 2019-10-19 02:44 UTC (History)
4 users (show)

See Also:
Crash report or crash signature: ["libgobject-2.0.so.0.5000.3"]


Attachments
Snapshot of help about, but of a slightly newer version than originally reported (42.06 KB, image/png)
2018-03-21 19:49 UTC, Howard Johnson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Howard Johnson 2017-11-24 18:09:59 UTC
This bug was filed from the crash reporting server and is br-fe533d7c-4d85-4e92-98ff-b0acbc756ee7.
=========================================

A random crash, but I have seen this a bunch of times now.  

I think it might occur when moving the focus from one Form editing dialog to another, especially if I click before the screen is fully redrawn.  But I can't be sure.

Sometimes this just crashes LO, but not my cinnamon window manager.  Other times, like this time, it also crashes cinnamon.  

I have not seen it also crash linux.

Not sure what other information I can provide that would help with this.


Recovery notes:

I was able to restart with:

* Ctrl-Alt-F2 to get to TTY2, then login to home, 
* then issue 'pkill cinnamon' to restart cinnamon.  
* Then once cinnamon restarted the LO windows were still dead.  
* So I had to click the upper right "X" of a LO window,  wait a bit, then click Force quit.  
* Then restart LO.  

* Then as is often the case when I then try to restart LO this also fails and have to again click the upper right "X" of a LO window,  wait a bit, then click Force quit.  
* Then restart LO again.  This time it uses the older backup of my Base and starts correctly, but loosing my edits.

linux 9.3
Comment 1 Xavier Van Wijmeersch 2017-11-25 10:30:57 UTC
I think its more a OS based error and so, maybe not a LO bug

Anyone ???
Comment 2 Kevin Suo 2017-11-27 04:24:31 UTC
Set OS to Linux
Comment 3 Alex Thurgood 2017-11-27 09:42:39 UTC
So this is on Debian Stretch ? Perhaps Réné might have an idea ?

@Howard : is this the distro provided version, or a version you have downloaded from TDF ?
Comment 4 Buovjaga 2017-11-27 10:39:31 UTC
I asked Caolán and he said (regarding the trace): "not enough there for me to hazard a guess. If the Window Manager is crashing too then there's definitely a bug outside of LibreOffice even if there's also a bug inside LibreOffice"
Comment 5 Howard Johnson 2017-11-27 16:13:02 UTC
@Alex, It's a downloaded version.  Debian repository is at 1:5.2.7-1 (5.2.7).  This is about the third or forth version I think I have downloaded.  

Ever since starting to use LO it has proved unstable no matter which version I use.  At first I had too many other fires to fight so have not reported this until now.

Only recently has it been crashing cinnamon in addition to just the normal crashing.  But I could be wrong about that as it has crashed so many times in the past two years that I just sort of got used to it.  I even wrote and now use AnnotatedBackups [https://github.com/TopView/AnnotatedBackups/wiki] to deal with these frequent freezes.

We might just have to wait to see if others also have this issue or if it's just me.
Comment 6 Howard Johnson 2017-12-01 17:31:31 UTC
1) This morning I had two LibreOffice Base windows open that were just sitting there doing nothing.  I was busy working on something else in Firefox, when LibreOffice just out of the blue crashed, like on it's own, without any mouse or keyboard input from me!  (This time it didn't take down the windows manager, just itself.)

2) Yesterday LibreOffice crashed my windows manager so badly that cinnamon lost all and had to do a full, fresh restart (rather than the normal restart where it keeps alive all of the programs and windows that were open before the crash).
Comment 7 Howard Johnson 2017-12-01 17:32:20 UTC
I don't think this is a bug in the windows manager.  

The reason: I run lots of software other than LibreOffice and I *never* see any of it crash my window manager.  

Rather, I find that LibreOffice (at least LO Base) is chock full of bugs, as I have reported many here, and I think what is most likely is that LibreOffice Base is crashing the windows manager.

(I don't say this with any joy.  I wish it weren't so, and I am helpless at the moment to fix LO.  All I can do this day is report what I am seeing in hopes that it moves the process forward.)
Comment 8 Julien Nabet 2018-01-25 09:28:47 UTC
(In reply to Howard Johnson from comment #5)
> @Alex, It's a downloaded version.  Debian repository is at 1:5.2.7-1
> (5.2.7).  This is about the third or forth version I think I have
> downloaded.  
I think it might be the pb. Linux versions on TDF are more for package maintainers.
I use Debian testing and LO package is 5.4.4.2

Rene: thought you might be interested in this one. Indeed, when you download a package from tdf, is there a lot of work (I think about dependencies) to upload it on SID (or perhaps in experimental first?) or do you think it's safe to use TDF packages directly on one's distrib?
Comment 9 Xisco Faulí 2018-03-21 16:54:01 UTC
Dear Howard,
Could you please paste the info from Help - about LibreOffice ?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' once the information has been provided
Comment 10 Howard Johnson 2018-03-21 19:47:06 UTC
(In reply to Xisco Faulí from comment #9)
> Dear Howard,
> Could you please paste the info from Help - about LibreOffice ?
> 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the information has been provided

Xisco, Sorry, but I don't have that version installed anymore. 

I had to roll back and forward to test another bug, and in the process lost the whole LO business and had to reload LO from scratch.  ... So much has changed in 4 months since this was reported.

I will attach snapshot of the 5.4.4.2 I have currently installed if that might help.

I have been working to transition to 6x, but not fully there yet.  ...

More recently, LO has been more stable for me.  I think I have only seen one such crash in the past month, but I also have not been doing as much development on LO of late. 

So perhaps something has been fixed somewhere.  I'll keep you posted.  Thank you.
Comment 11 Howard Johnson 2018-03-21 19:49:19 UTC
Created attachment 140799 [details]
Snapshot of help about, but of a slightly newer version than originally reported

See comment 10
Comment 12 Buovjaga 2018-03-21 19:53:25 UTC
(In reply to Howard Johnson from comment #11)
> Created attachment 140799 [details]
> Snapshot of help about, but of a slightly newer version than originally
> reported

Thanks. Btw. you can just select the text with your mouse and copy, so no need to fiddle with screenshots :)
Comment 13 mattia.b89 2019-01-27 10:42:23 UTC
can't replicate the bug
Comment 14 Xisco Faulí 2019-03-21 12:21:33 UTC
Hello Howard,
LibreOffice 6.2.2.2 is going to be released today, could you please try again
with this version to see if the problem has been resolved meanwhile? Thanks in
advance
Comment 15 QA Administrators 2019-09-18 02:55:07 UTC Comment hidden (obsolete)
Comment 16 QA Administrators 2019-10-19 02:43:56 UTC
Dear Howard Johnson,

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