Bug 119105 - Crash in: libc-2.17.so with a VNC session
Summary: Crash in: libc-2.17.so with a VNC session
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-05 10:33 UTC by martijn
Modified: 2019-10-11 02:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["libc-2.17.so"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description martijn 2018-08-05 10:33:11 UTC
This bug was filed from the crash reporting server and is br-19c14fe6-0e0b-4653-84a0-22c34487f775.
=========================================
Immediate and consistent crash when trying to open Impress through "File" menu => "New presentation". This is when using LibreOffice remotely over a VNC session.

Downgrading back from 6.0.6 to 6.0.4 fixes the problem (I skipped 6.0.5).
Comment 1 raal 2018-08-05 11:34:01 UTC
Please paste here information fro Help-> About.
Comment 2 martijn 2018-08-05 12:04:42 UTC Comment hidden (obsolete)
Comment 3 martijn 2018-08-05 12:07:00 UTC
Sorry, please discard the previous comment. Here is the CORRECT information from Help -> About:

Versie: 6.0.6.2
Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU-threads: 8; Besturingssysteem: Linux 3.10; UI-render: standaard; VCL: gtk2; 
Locale: nl-NL (nl_NL.UTF-8); Calc: group
Comment 4 Xisco Faulí 2018-08-06 10:19:09 UTC
To be certain the reported issue is not related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 5 martijn 2018-08-06 15:49:27 UTC
Resetting the user profile makes no difference, neither does deleting it altogether and having a fresh one generated. Here is a crash report generated with a completely fresh profile: https://crashreport.libreoffice.org/stats/crash_details/431f122e-7a56-49ba-be0c-569fb084a11b
Comment 6 Xisco Faulí 2019-03-13 18:54:39 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 QA Administrators 2019-09-10 08:45:47 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-10-11 02:38:28 UTC
Dear martijn,

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