This bug was fixed in the package mir - 0.5.0+14.10.20140722-0ubuntu1
---------------
mir (0.5.0+14.10.20140722-0ubuntu1) utopic; urgency=medium
[ Kevin Gunn ]
* Fixed: [regression] Mir fails to start on Nexus 5 / Nexus 10 (LP: #1345533)
-- Ubuntu daily release <ps-jenk...@lists.canonical.com> Tue, 22 Jul 2014
02:17:22 +0000
** Changed in: mir (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1345533
Title:
[regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it
fails to turn vsync signal on
Status in Mir:
Fix Committed
Status in Mir 0.5 series:
Fix Committed
Status in “mir” package in Ubuntu:
Fix Released
Bug description:
Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
(hammerhead), as it fails to turn the vsync signal on.
This is what I get from logcat:
D/libEGL ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
I/qdutils ( 3038): Right Split=0
D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could
not be opened : No such file or directory
I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
I/qdhwcomposer( 3038): MDP version: 500
I/Adreno-EGL( 3038): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build:
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
I/Adreno-EGL( 3038): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build:
I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
I/qdhwcomposer( 3038): hwc_registerProcs
I/qdhwcomposer( 3038): Initializing UEVENT Thread
I/qdhwcomposer( 3038): Initializing VSYNC Thread
I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from
/sys/class/graphics/fb0/vsync_event
I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from
/sys/class/graphics/fb1/vsync_event
D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0,
enable=1 : Operation not supported
W/libEGL ( 3038): eglTerminate() called w/ 1 objects remaining
E/libEGL ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
I/ServiceManager( 913): service 'display.qservice' died
The vsync control failed message was always there, and Mir 0.4 worked
fine with it still.
System compositor log:
root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
ERROR:
/build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75):
Throw in function virtual void
mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
Dynamic exception type:
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: error turning vsync signal on. rc = ffffffa1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1345533/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
