Bug 100457 - Crash: The viewer doesn't start
Summary: Crash: The viewer doesn't start
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: ARM Android
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-17 14:42 UTC by lorenzo.morin
Modified: 2017-05-31 10:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Hardware info (105.99 KB, image/png)
2016-06-17 14:43 UTC, lorenzo.morin
Details
crash logcat (12.13 KB, text/plain)
2016-06-22 13:47 UTC, definesinsanity
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lorenzo.morin 2016-06-17 14:42:43 UTC
The app crashes at start on:

Huawei ALE-L21

Version:5.2.0.0.Alpha0+/f6at4ce
Comment 1 lorenzo.morin 2016-06-17 14:43:14 UTC
Created attachment 125707 [details]
Hardware info
Comment 2 steve 2016-06-20 08:11:24 UTC
From what I can tell, this bug has not been confirmed. Correct me if I am wrong. Back to Unconfirmed for now.
Comment 3 lorenzo.morin 2016-06-20 12:55:33 UTC
The app crashes also after deleting data file, tell me if you need more info.
Comment 4 definesinsanity 2016-06-22 13:47:32 UTC
Created attachment 125833 [details]
crash logcat
Comment 5 definesinsanity 2016-06-22 13:50:51 UTC
Happening to me on 5.3.0.0.alpha0+/e505ab7/android Master/Nightly downloaded on June 22/16.

The above logcat is on a Nexus 6 running 6.0.1
There are a couple of selinux denials in the log, which seems odd.
Comment 6 definesinsanity 2016-06-22 13:52:25 UTC
Note that mmcblk0p42 is the userdata partition.
Comment 7 Robinson Tryon (qubit) 2016-08-04 18:29:10 UTC
TESTING on Android 5.1.1 with 5.3.0.0.alpha0+/f2da3173f8:
  tinderbox: tree: MASTER; pull time 2016-08-04 00:59:32

(In reply to definesinsanity from comment #5)
> Happening to me on 5.3.0.0.alpha0+/e505ab7/android Master/Nightly downloaded
> on June 22/16.
> 
> The above logcat is on a Nexus 6 running 6.0.1

I don't currently have a device running Android 6. Looks like Lorenzo's on Android 5.0.1, so either it's not a v6-only bug or these crashes are unrelated.

Lorenzo/DefineInsanity: Can either of you still reproduce a crash with today's build?

Status -> NEEDINFO
Comment 8 definesinsanity 2016-10-24 14:47:57 UTC
(In reply to Robinson Tryon (qubit) from comment #7)
> TESTING on Android 5.1.1 with 5.3.0.0.alpha0+/f2da3173f8:
>   tinderbox: tree: MASTER; pull time 2016-08-04 00:59:32
> 
> (In reply to definesinsanity from comment #5)
> > Happening to me on 5.3.0.0.alpha0+/e505ab7/android Master/Nightly downloaded
> > on June 22/16.
> > 
> > The above logcat is on a Nexus 6 running 6.0.1
> 
> I don't currently have a device running Android 6. Looks like Lorenzo's on
> Android 5.0.1, so either it's not a v6-only bug or these crashes are
> unrelated.
> 
> Lorenzo/DefineInsanity: Can either of you still reproduce a crash with
> today's build?
> 
> Status -> NEEDINFO

Currently nightly, same phone, updated to Android 7.0, same problem.
Open LO, select odt file, starts to open, shows partial rendering of first page of document, then displays "LibreOffice Viewer has stopped", and back to file browser activity.
Comment 9 QA Administrators 2017-05-02 11:36:29 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2017-05-31 10:45:45 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-20170531