*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
Going back to the reporter Uranicus' original description, he says he
noticed the issue at "January, 10th at approx. 13:30 h".
And his unit8.log.3.gz contains:
[1452429068.248925] <ERROR> mircommon: Caught exception at Mir/EGL driver
boundary (in queueBuffer):
/build/mir-4B0JBP/mir-0.18.0+15.04.20151216.1/src/client/buffer_stream.cpp(169):
Throw in function virtual MirWaitHandle*
{anonymous}::ExchangeSemantics::submit(const std::function<void()>&,
mir::geometry::Size, MirPixelFormat, int)
Dynamic exception type:
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: disconnected: no new buffers
whose time stamp translates to:
$ env TZ='Europe/Paris' date -d @1452429068
Sun Jan 10 13:31:08 CET 2016
Assuming Uranicus is in Western Europe, that must be the error. So this
bug becomes a duplicate of bug 1506358, which has the added bonus of
almost having a nice reproducible test case (needs work still).
** This bug has been marked a duplicate of bug 1506358
libmirclient gives up and exits prematurely with "std::exception::what:
disconnected: no new buffers" via ExchangeSemantics::submit()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
Status in Canonical System Image:
Confirmed
Status in Mir:
New
Status in mir package in Ubuntu:
Confirmed
Status in unity-system-compositor package in Ubuntu:
Confirmed
Bug description:
My system:
current build number: 225
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-01-09 06:52:53
version version: 225
version ubuntu: 20160109
version device: 20151216-378d4f3
version custom: 20151111--36-46-vivid
What happened:
Someone called me and I wanted to take the call on the phone (nothing
attached to the phone). The screen was locked and I pressed the power button to
unlock the screen. The phone did not react on any pushed buttons. The phone
continued ringing but I was not able to do anything with the phone during this
time.
During the next minute the phone was blocked. After this period a
"restart" followed.
"Restart":
The restart was not a real reset. The phone screen was black. Then approx. 1
- 2 minutes after the call was gone, the screen went on again and the ubuntu
logo with the dots appeared (same screen when you start the phone but without
the "bq"-screen).
I did not need to enter the PIN code of the SIM card. The phone was
again fully operational.
This happened on January, 10th at approx. 13:30 h. I have attached the
sys.log for your review and hopefully for tracing back the issue to
the root cause.
Matthias
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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
