android-src-vendor (5-0ubuntu1) trusty; urgency=medium
* Adding back hwcompositor for grouper as it's now compatible with
MIR
-- Ricardo Salveti de Araujo Tue, 14
Jan 2014 22:40:23 -0200
** Changed in: android-src-vendor (Ubuntu)
Status: Triaged => Fix Released
--
You received
This bug was fixed in the package mir - 0.1.2+14.04.20131128.1-0ubuntu1
---
mir (0.1.2+14.04.20131128.1-0ubuntu1) trusty; urgency=low
[ Kevin Gunn ]
* New upstream release 0.1.2
- graphics: android: improve interface for mga::DisplayDevice so its
just concerned with rend
** Branch linked: lp:ubuntu/trusty-proposed/mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 when
using the hwcomp
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 whe
Adding bug task to android-src-vendor so we can add hwcomposer.tegra3.so
back once latest mir is available in the archive.
** Changed in: libhybris (Ubuntu)
Status: Triaged => Invalid
** Also affects: android-src-vendor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: a
** Changed in: mir
Status: Fix Committed => Fix Released
** Changed in: libhybris (Ubuntu)
Status: Confirmed => Triaged
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Status: New => Triaged
** Changed in: mir (Ubuntu)
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 when
u
I assume "FB composition" is not desirable, and slower... ?
** Changed in: mir
Milestone: None => 0.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSE
for the reports about 'my nexus 7 works'
In mir, we first try to load the HWC display mechanism, and then, if we
can't load HWC, we load an alternative display mechanism (FB)
We saw that the HWC was segfaulting, so we removed hwcomposer.tegra3.so from
the build. This forced FB composition.
A
the issue was that the hwcomposer was relying on HWC_GEOMETRY_CHANGED
flag to do some initialization of its internal data structures
(including some pthread mutexes). Mir was not setting this flag leaving
those mutexes uninitialized. When hwc tried to lock the uninitialized
mutexes, we would segfa
After a bit of more investigation, this actually seems to be a bug in
the way Mir is using the hwcomposer interface (not using the 2 layers,
and also with a different init/flags set).
The crash happens because it tries to use a pthread_mutex that is not
initialized. From our current investigation
Assigned to kdub as he's currently investigating the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 when
usin
OK, but why reopen for Mir? What needs fixing in Mir?
** Changed in: mir
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with S
Marking as valid still as it happens when using the android hwcomposper.
** Changed in: mir
Status: Invalid => Confirmed
** Changed in: libhybris (Ubuntu)
Status: Fix Released => Confirmed
** Description changed:
- Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7
Seems to be fixed in:
libhybris (0.1.0+git20130606+c5d897a-0ubuntu33) saucy; urgency=low
** Changed in: mir
Status: Confirmed => Invalid
** Changed in: libhybris (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
B
Update: unity appears to no-longer crash on startup when using Mir on my
Nexus 7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1
** Summary changed:
- Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7
+ Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 when using
the hwcomposer (tegra3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Ok, the other unity8 related crash was because we didn't had the
permissions set right. Will be pushing a change to lxc-android-config to
get that fixed.
Also uploading a new android package without the hwcomposer for grouper,
until we're able to ignore it from Mir itself (could use getprop to
che
** Changed in: mir
Importance: Low => Medium
** Changed in: libhybris (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SI
Seems to be related with the hwcomposer, as after removing
/system/lib/hw/hwcomposer.tegra3.so I'm able to start mir_demo and run a
few examples.
Unity8 is crashing still it seems, still debugging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I did a quick check, and noticed that it crashes in
my_pthread_mutex_lock, a hybris hook for the original
pthread_mutex_lock.
The problem is that the mutex used (__mutex) contains an anddress that's
not part of the mapped memory region for the process, causing a segfault
when we try to access the
Yes, old Nexus 7 (Tegra 3).
** Changed in: mir
Status: New => Confirmed
** Changed in: mir
Importance: Undecided => Low
** Changed in: libhybris (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I should note that is old Nexus hardware (i.e. tegra3).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7
To manage noti
Thanks for the suggestion, Kevin. Unfortunately this doesn't seem to
help. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libhybris (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
old nexus 7 (nvidia hardware) or new nexus 7 (qcom hardware)?
it might be that the hwc isn't working for the nexus 7. You can try to
mv /system/lib/hw/hwcomposer.* out of that directory, which will force
mir into a backup composition mode.
--
You received this bug notification because you are a
26 matches
Mail list logo
