** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - follo
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage
** Changed in: canonical-devices-system-image
Milestone: ww04-2016 => 9.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "resta
** No longer affects: mir/0.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this bug go
Uranicus:
You did a great job with your detailed bug report. There's nothing to
improve. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in
Dear developers!
Thanks for the great work done to fix this issue!
Seeing that this bug (maybe also the reporting of it?) has caused some
troubles I would appreciate a feedback what needs to be improved in the
future bug reporting to get directly to the point where you can fix it.
If there is som
** Changed in: unity-system-compositor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followe
** Changed in: canonical-devices-system-image
Status: Confirmed => 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/1532607
Title:
Phone not usable while a call comes in - followed
** Changed in: mir/0.19
Status: Fix Committed => Fix Released
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
** Changed in: mir (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To man
** Changed in: mir (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To m
** Branch unlinked: lp:mir/0.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this bug go
** Changed in: mir/0.19
Status: New => Fix Committed
** Changed in: mir/0.20
Status: New => 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/1532607
Title:
Phone not usable
I'm happy to let this become another confused bug and it get closed. We
have plenty of those and it's an unavoidable consequence of Launchpad's
awesome openness. Managing popular bugs is often like herding cats.
There is however still absolute proof here that the original reporter
hit bug 1506358
just following up, very good anecdotal evidence testing from pat who
consistently could repro this bug that the mir0.19.2 branch corrects
this issue. Silo under test now. thanks for everyone's help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I reproduced this again with an incoming text on mx4, and we checked
the stack trace in http://pastebin.ubuntu.com/15009225/
Using silo 64 I am unable to trigger the symptom
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Branch linked: lp:mir/0.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this bug go t
@Daniel,
The OP also reports a "restart", whose description match what would
happen if USC restarts... so we are going by our suspicion that it's
related to the failure to start the compositor threads. The error logs
in unity8 (USC's client) are irrelevant in that case.
--
You received this bug
Don't yet claim any fix committed. It was only mentioned in the 0.19.2
changelog and I suspect that's incorrect.
** Changed in: mir/0.19
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Changed in: mir/0.19
Status: New => Fix Committed
** Changed in: mir/0.19
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usabl
** Changed in: mir
Milestone: None => 0.19.2
** Also affects: mir/0.20
Importance: Critical
Status: New
** Also affects: mir/0.19
Importance: Undecided
Status: New
** Changed in: mir/0.20
Milestone: 0.19.2 => 0.20.0
** Changed in: mir/0.19
Milestone: None => 0.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this bug go to:
https://bugs.launchpad.net/c
I don't think treating this separately to bug 1506358 will be helpful.
Firstly, there is proof in comment #40 that the original reporter hit
bug 1506358 at 13:31:08 on 10 January. Assuming Uranicus is 1 hour ahead
of UTC...
Secondly, if you look in bug 1506358 you'll find I mentioned that when
it
I've got a similar issue and is definitely related to the proximity
sensor: when the telephone app is down but there's a call active and I
want to tap the green stripe to go back to the call the screen starts to
blink and the phone ceased to respond until it perform a "fake reboot"
(no pin needed)
deduplicating for the moment, discussing with alf not convinced we
should dupe quite yet
** This bug is no longer a duplicate of bug 1506358
libmirclient gives up and exits prematurely with "std::exception::what:
disconnected: no new buffers" via ExchangeSemantics::submit()
--
You received t
*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
unity-system-compositor.log is not from the original reporter of the
bug. So likely a separate issue.
As always, we should ignore "me too"'s on the bug and focus on what the
original reporter has provided.
*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
The core problem here is that USC crashes with "Compositor thread failed
to start" (see unity-system-compositor.log.old), not that libmirclient
throws (because the server crashed, in this case). I think thi
*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
Oops, my memory failed me. We don't use SIGHUP there. Instead
mir_buffer_stream_api.cpp simply catches, logs and then ignores all
exceptions. That's probably worse.
--
You received this bug notification be
*** This bug is a duplicate of bug 1506358 ***
https://bugs.launchpad.net/bugs/1506358
BTW, you won't get a crash report either. Because although it starts out
as a serious-sounding C++ exception, libmirclient converts that into a
SIGHUP for consumption by C clients. And SIGHUP's default actio
*** 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] mircommon: Caught except
I'm using nexus 4. After installing OTA 9 my phone rebooted for
installation but after successful installation. It just keeps on a a
reboot loop shows ubuntu dotted booting logo then reboots again. So,
I've to use volume up + power button to turn on and from the recovery
menu i did 'wipe cache'. On
Don't know if the bug I experienced is related directly to this bug, but I had
a couple of situations that when I tried to call someone the phone just hangs,
no dial tone, just hangs.
Other time I have closed the dialler and the call stayed active and I couldn't
close the call when I have rea
I also noticed a few things after the crash,
- the first being the proximity sensor which now behaves like the phone
is in a call and blanks the screen when your hands reach the top of the
phone during normal usage.
- Second being the call which is dropped is not recorded/listed in the
dialer app
On the E4.5 the phone came back on its own after about a min, on the MX4
it did not recover and I did a hard power cycle. There is also no crash
file on the MX4.
Seems quite random when it will happen. I got it on the second call,
then not again after 10 calls
--
You received this bug notificat
** Attachment added: "unity-system-compositor.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4566098/+files/unity-system-compositor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "unity-system-compositor.log.old"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4566097/+files/unity-system-compositor.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Reproduced on MX4 running rc-proposed r242
I am also touching the screen prior to picking it up and allowing the screen to
come on, which may help trigger it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
To add to the steps, the screen was off, phone was face down to engage the
proximity sensor.
When the call came in I touched the screen before lifting it, but not sure that
was necessary as it hasn't reproduced again.
The device was plugged into usb the entire time o not suspended.
--
You rec
** Attachment added: "unity-system-compositor.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4566095/+files/unity-system-compositor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Attachment added: "unity-system-compositor.log.old"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4566094/+files/unity-system-compositor.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I managed to reproduce it once on E4.5 running ota 9
I made 6 calls and on the 6th it failed as described, kept ringing and u-s-c
crashed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
** Attachment added: "_usr_sbin_unity-system-compositor.0.crash"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4566093/+files/_usr_sbin_unity-system-compositor.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Until the moment I did not have this bug, at least with phone calls,
because I have those reboots when I receive SMS. In OTA-8.5, the phone
was great, no reboots, everything worked as expected. My phone is the
E4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
i have exactly the same problem and sometimes during a call the phone will just
reset back to the ubuntu loading screen and cut the call and has once had the
phone call still running but usually just cuts the call
its been doing that for over a month id say maybe 2-3 months?
--
You received thi
also happens sometimes when I'm in a call and briefly turn the screen on
to check the time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - follo
OK, we've made a point release of mir 0.19.1 and unity-system-compositor 0.4.1
which are now in the stable overlay.
Which means will be built into the next image and available on the rc-proposed
channel.
Also, this should make it into the OTA9.5 release.
If you update and know you are on these po
The exceptions in comment #6 is bug 1506358, where the client dies
unexpectedly but the server keeps running (and remember Unity8 is a
client as well as a server).
If that's the only issue then this is a duplicate of that. But it may
not be the only issue.
--
You received this bug notification b
We're needing more data on this bug, and we're going to eventually land
the MP's to improve some reporting.
But this bug is critical, and we'd like to get information as soon as possible.
_Only_ if you are willing to risk not getting autoupdates (and have to flash
your phone in future) - you can
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-system-compositor (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/1532
Agreed, this is the behaviour I'd expect lp:1528384 to exhibit. Occum's
razor suggests we don't needlessly look for another explanation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Comment #7 & #13 in this bug claiming "no crash files" would seem to suggest
they're different, but sometimes people miss them.
And I do agree the description from Olivier sure sounds the same as this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
>From the comment of Olivier on bug 1528384 could it be the due to the
same crash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "
After re-reading this thread it sounds like
a) a bug specifically in the proximity sensor/blanking logic...like in some
situation it's getting locked to blank
b) it sounds like as part of this, u-s-c (possibly unity8) is restarting as a
result
--
You received this bug notification because you a
lightdm / u-s-c logs
** Attachment added: "lightdm.zip"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+attachment/4553659/+files/lightdm.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** No longer affects: qtmir (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by "restart"
To manage notifications about this b
The logs in comment #6 are a normal reaction that unity8 would have if
USC crashed. So I'd guess from what's gathered here that we should be
looking for USC logs instead of unity8 ones.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir (Ubuntu)
Importance: Undecided => Critical
** Changed in: qtmir (Ubuntu)
Importance: Undecided => Critical
** Also affects: unity-system-compositor (Ubuntu)
Importance: Undecided
Status: New
** Changed in
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => ww04-2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a call comes in - followed by
Forgot log files
syslog text:
Jan 20 10:51:58 ubuntu-phablet kernel: [ 6749.701233]init: lightdm main process
(1678) terminated with status 1
Jan 20 10:51:58 ubuntu-phablet kernel: [ 6749.701292]init: lightdm main process
ended, respawning
** Attachment added: "unity8.log.1"
https://bugs.l
I have seen a similar symptom twice in the past 4 days In both cases a
new SMS followed an exchange of SMS's within the previous minute. I hear
the notification, phone is in pocket so proximity will be enabled, take
phone out and it stays black, pressing power does not turn on the
screen, then the
Same issue with my BQ E5
- Phone rings
- I take it up from the pocket or table
- Black screen and not waking up if I press the power button.
- Keeps ringing
- The screen wakes up 1-3 minuts after and is again usable.
- No recent or missed call are registeret
Build number: 229
--
You received th
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtmir (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/1532607
Title:
Phon
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (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/1532607
Title:
Phone
@kevin gunn
To be honest, I can not guarantee what the screen was when I wanted to take the
incoming call. Since the phone was in my pocket I might have pushed something,
may the screen be on or off. When I had the phone in my hand the screen was
black (this is what I meant with "screen locked")
@Uranicus
>From your original report, can I ask when you described this...
>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.
** Also affects: mir
Importance: Undecided
Status: New
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
@Jean-Baptiste:
I have checked the directory /var/crash/. There is no file from this
time interval.
Uranicus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532607
Title:
Phone not usable while a c
Thanks for the logs. /var/log/syslog, /home/phablet/.cache/upstart and
/var/crash are usually good place to start gathering information.
>From syslog lightdm restarted
Jan 10 13:31:17 ubuntu-phablet kernel: [62846.465084]init: lightdm main process
(1966) terminated with status 1
Jan 10 13:31:17
68 matches
Mail list logo