Ubuntu
unity8 package

Unity8 wont start on Mir when screen is blanked

Bug #1235000 reported by Loïc Minier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mir (Ubuntu)
New
Undecided
Unassigned
unity8 (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Hi,

Unity8 starts more slowly on Mir than on SF, and apparently slowly enough that the idle time kicks in.

Problem is that Unity 8 can't start with blank screen on Mir; I get this in a loop:
QOpenGLShader::link: "--From Fragment Shader:
--From Vertex Shader:
Link was successful.
"

** (process:4016): CRITICAL **: Unable to get session bus: Error calling StartServiceByName for com.canonical.hud: Timeout was reached
__pthread_gettid -2
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): Could not unblank display
ofono/ofono/account0 initialized
__pthread_gettid -2
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): Could not unblank display

Thanks,

Revision history for this message
Michał Sawicz (saviq) wrote :

Another point is that IIRC it stalls on startup in that case instead of exiting with an error code.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Confirmed with build 80.
Possible duplicate of bug 1188504.

TEST CASE:
1. Boot a Mako
2. During boot, when the google logo is displayed, turn display off with a short press on the power button
3. Wait until boot finished

ACTUAL RESULT:
unity8 fails to start and the following message is printed to ~/.cache/upstart/unity8.log:
"""
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): Could not unblank display
"""

Changed in unity8 (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Gema Gomez (gema)
tags: added: avengers qa-touch rls-s-incoming
Revision history for this message
Kevin DuBois (kdub) wrote :

when I had this build on
root@ubuntu-phablet:/# system-image-cli -i
current build number: 82
device name: mako
channel: devel-proposed
last update: 2013-10-05 00:46:03
version version: 82
version ubuntu: 20131004.1
version device: 20131003.2

i couldn't get mir to start with older revisions of mir that were known-working. Suspect something's amiss in the build that's causing the drivers to go haywire, but haven't pinpointed it yet

Revision history for this message
Kevin DuBois (kdub) wrote :

this appears to prevent the error from happening:

# touch /userdata/.writable_image
# reboot

probably some firmware, device file, or driver that is needed has been made inaccessible in the image

Revision history for this message
Michał Sawicz (saviq) wrote :

Are you sure writable image helped for you? I doubt it's the case for anyone else - the only "fix" is to toggle the display with the power button and start then.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1188504, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Kevin DuBois (kdub) wrote :

apologies for the confusion, i could not reproduce the fix i proposed in the earlier comment. I probably was just not controlling for the blank state carefully enough

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.