** Also affects: arale
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Milestone: 11 => 12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Still happening
current build number: 322
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening the camera for the first
Same here. On my arale rc-proposed 315 image, I install Authenticator,
run it, click the camera icon, grant it permission, and get a reboot. I
got it twice in a row, then it worked the third time... (that time I
was plugged into adb, so maybe that makes a difference?) Same kernel
stack trace as
Not sure if it helps, but I encountered this using a slightly different
sequence of steps in bug 1569660: Install uTorch, run it, then try to
grant it permission to access camera-service. I get a kernel panic
every time, and am never able to grant access. This was with arale rc-
proposed 304.
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtdeclarative-opensource-src (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
best to fix in the kernel
** Changed in: canonical-devices-system-image
Assignee: kevin gunn (kgunn72) => Yuan-Chen Cheng (ycheng-twn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title
** Also affects: qtdeclarative-opensource-src (Ubuntu)
Importance: Undecided
Status: New
** Changed in: trust-store
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
@Cemil: Thanks for the investigation. With Cemil's findings, I'm marking
the bug as invalid for trust-store, marking Qt (Quick) as affected
instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155181
As the last step to isolate the issue, I've created a trivial GL-based
TPP and was NOT able to repro after trying many times. I assume at this
point that the Qt QuickSceneGraph Renderer the actual TPP uses is doing
something funny.
I am off the next couple of days and if anyone wants to try the TP
** Changed in: mir (Ubuntu)
Assignee: Cemil Azizoglu (cemil-azizoglu) => (unassigned)
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Changed in: mir
Status: New => Incomplete
** Changed in: mir
Status: Incomplete => Invalid
--
You received this bug notification
I 've tested with a trivial TPP (one that doesn't use Qt, that only
connects to and disconnects from U8) and wasn't able to repro the issue.
Thanks to Thomas for his help. As I said before, the camera driver is a
bit flakey - I get errors like
[ 933.537054] [mt-i2c]ERROR,454: id=0,addr: 50, trans
Also, Alberto told me that he saw this issue on N4 while doing some
unrelated release testing, though he couldn't repro it later after
trying 20 times or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I (with tvoss' help) created some tools to recreate the scenario in a
more controlled setup (e.g. no Qt). I have tested the trusted prompt
feature at the mir level, as well as the unity8 level, with Camera app
and with other apps. I haven't been able to repro the issue after
thousands of iterations
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening the camera for the first time leads to reboot
To manage notifications about this bug go to:
h
** Also affects: mir
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/1551811
Title:
Opening the camera for the first time leads to reboot
To manage notific
@Simon, thanks for the clear steps.
I see that the panic is caused by the 'trust-prompt' executable's quick
scene graph renderer (QSGRenderThread) thread. It happens in the Camera
app too, but easier to repro using the Telegram app.
Updating the description with a quicker method to repro.
** Des
** Also affects: trust-store
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/1551811
Title:
Opening the camera for the first time leads to reboot
To manage
** Changed in: mir (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: mir (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening t
Updated the descriptions with the steps I used to reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551811
Title:
Opening the camera for the first time leads to reboot
To manage notifi
Just reproduce the crash again. Still caused by the same kernel panic as
mentioned in comment 7.
** Description changed:
Test case.
- Flash the phone.
- Open Telegram app.
- Fill the account details.
- Add a contact (if needed).
- Select a contact to send a message.
- Tap on the cli
@Kevin: I've seen it only on arale so far and also Dave says that is the
only device he saw this so far on. So suspecting an issue on the device
side is valid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
@Cemil: Also that the syslog's don't show the actual crash I've seen is
likely because this is a kernel panic and syslog might not get the
kernel output before the device is rebooted. Use something like
$ cat /proc/last_kmsg
on the next boot to get the kernel side output only which is stored in
m
I took a look and was able to repro on Arale with the latest rc-proposed
but it's difficult.
In my instance of the crash, I did not see the PVR kernel logs reported
by Simon in comment #7. (Also, I don't see them in the logs attached by
Dave and Victor). How were they obtained?
>From the logs I o
adding mir b/c that looks like a gpu kernel panic - might be the driver
itself, so we might be limited or have to look for a workaround.
@reporters - does anyone know if this behavior is identical or exists on
other HW/gpu's ? e.g. mako, frieza, krillin? if not, can someone test?
** Also affects:
it's very possible the PVR spew is a red-herring. so let's consider
incomplete for the gfx side of things until someone has more to add
** Changed in: mir (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
25 matches
Mail list logo
