Using the LO-Viewer in "Testing" mode on latest Lineage to create a new odt results in a semi blank screen. Control bar and buttons are visible and useable, but it is impossible to see entered text. Even zooming in and out does not result in the smalest visible portion of the entered text. Tried to enter arround 20 lines of text and even copied in the summary of the Wikipedia article of "Goethe's Faust" using "Hacker's Keyboard" (as the native way did not work, either) resulted in a blank page - documented as screenshot and available on request. Sorry for not attaching it here, but I'm on mobile and logged in using my private mail and your attachment disclaimer puzzeled me about public availability of that mail address. Kind Regards, uso
Needs comment? Of what sort? Still does not work. Similar claims on Google PlayStore. If no one asks questions and I even not have the posibility to enter the viewer version, what should I comment to help the devs?!
it should be fixed in master now Info from ESC meeting: + Android viewer + Issue when opening any document? (Xisco) + Should be fixed (Cloph) Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Dear uso, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
I'm unable to fetch the APK from the provided source (no build available). Hence no test possible. Regards, uso
(In reply to uso from comment #4) > I'm unable to fetch the APK from the provided source (no build available). There's currently some hardware issue with the machine creating the Android daily builds... Will hopefully be available again sometime soon.
https://dev-builds.libreoffice.org/daily/master/current.html now offers a daily build for Android again. Can you please retest?
Created attachment 161692 [details] Landing page/main screen
Created attachment 161693 [details] Document edit window Lading page/main screen is visible and usable, creating a document works. But editing is not possible. No controls, no input possible.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to uso from comment #8) > Lading page/main screen is visible and usable, creating a document works. > But editing is not possible. No controls, no input possible. Editing requires the experimental editing mode to be enabled, both during the build and in the app's settings. A quick look at the build log, e.g. [1], suggests that it's not enabled (it does "assembleStrippedUIDebug", not "assembleStrippedUIEditingDebug"). I've quickly tested editing a while ago in a custom build (and TDF daily builds had that enabled as well) and that was generally working on my LineageOS (yet, the "experimental" label is justified...). [1] https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&full-log=1591510202.28103
I've asked cloph on IRC; he said: "Changed the bot's autogen to enable experimental mode, so next builds should have it enabled again." -> Could you please try again with a daily build from tomorrow or later?
(In reply to Michael Weghorn from comment #11) > I've asked cloph on IRC; he said: "Changed the bot's autogen to enable > experimental mode, so next builds should have it enabled again." > > -> Could you please try again with a daily build from tomorrow or later? Sure, I'll test again.
(In reply to Michael Weghorn from comment #11) > I've asked cloph on IRC; he said: "Changed the bot's autogen to enable > experimental mode, so next builds should have it enabled again." > > -> Could you please try again with a daily build from tomorrow or later? Tested with todays build. Editing works after enabling the experimental mode. Thanks!
Thanks for testing.