uNav

Is blank screen bug supposed to be fixed?

Asked by Michele Giacomoli

HI Marcos,
since a pair (at least) of OTAs and some uNav versions I'm experiencing uNav's map view always getting blank after around 30Km of navigation. I saw two bugs that should address this problem, #1559428 that now seems to be fixed and #1559428 marked as invalid. I wonder if now, with latest stable updates (OTA 10.1 + uNav 0.59), this bug is considered as fixed, if anyone else is experiencing this problem, or if it should be fixed with a future OTA.

Thanks in advance

Question information

Language:
English Edit question
Status:
Solved
For:
uNav Edit question
Assignee:
No assignee Edit question
Solved by:
costales
Solved:
Last query:
Last reply:
Revision history for this message
costales (costales) said : 		#1

We fixed a white map returning from menus.
But uNav has that white map issue yet, it's from the system. It should
appears when you return from another app to uNav and oxide kills the map :(
This is the bug, please, if you can report in it, thanks in advance!
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1375215
Thank you for your feedback!

Revision history for this message
Michele Giacomoli (michele-giacomoli) said : 		#2

Hi, actually the screen goes blank while navigating to a destination, not returning from another app, just keeping uNav in the foreground with the screen always on. Do you think it's always the same bug? Should I fill a new bug?

Revision history for this message
costales (costales) said : 		#3

Could you attach the log? Use logviewer and upload to ubuntu pastebin :)

<email address hidden> wrote:
> Question #293126 on uNav changed:
> https://answers.launchpad.net/unav/+question/293126
>
> Status: Answered => Open
>
> Michele Giacomoli is still having a problem:
> Hi, actually the screen goes blank while navigating to a destination,
> not returning from another app, just keeping uNav in the foreground with
> the screen always on. Do you think it's always the same bug? Should I
> fill a new bug?
>
> --
> You received this question notification because you are an answer
> contact for uNav.

Revision history for this message
Michele Giacomoli (michele-giacomoli) said : 		#4

http://paste.ubuntu.com/16200745/
Here is the content of ~/.cache/upstart/application-click-navigator.costales_navigator_0.59.log.1.gz, the last related log I found
If you need more info or this log is wrong let me know

Revision history for this message
costales (costales) said : 		#5

Hola Iris.
Ya estáde camino.El número de seguimiento es el 9378940.
Publiqué la review en planet.ubuntu.com y en breve en ubuntu-españa.org.
Muchísimas gracias por el préstamo.
Costales

<email address hidden> wrote:
> Question #293126 on uNav changed:
> https://answers.launchpad.net/unav/+question/293126
>
> Status: Answered => Open
>
> Michele Giacomoli is still having a problem:
> http://paste.ubuntu.com/16200745/
> Here is the content of ~/.cache/upstart/application-click-navigator.costales_navigator_0.59.log.1.gz, the last related log I found
> If you need more info or this log is wrong let me know
>
> --
> You received this question notification because you are an answer
> contact for uNav.

--
Sent Using Firefox OS

Revision history for this message
Best costales (costales) said : 		#6

Yes, oxide killed the webview:

file:///opt/click.ubuntu.com/navigator.costales/0.59/qml/Main.qml:103:
TypeError: Type error
ubuntumirclient: Attempted to deliver an event to a non-existent
window, ignoring.

A hug!

Revision history for this message
Michele Giacomoli (michele-giacomoli) said : 		#7

Thanks costales, that solved my question.