[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** 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 Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in arale: New Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/arale/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 comment #7 when it did happen though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** 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 Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: Invalid Status in mir package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
@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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: Invalid Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 TPP is in silo 80 (https://requests.ci-train.ubuntu.com/#/ticket/1187). Please use the packages with the '15.04.20160330-0ubuntu1' tag as 'citrain device upgrade' picks up the older versions, probably because not all 'arch'es built successfully the last time. At this time, I'll remove myself and Mir from the bug, as I am not familiar with the QSG. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: Invalid Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** 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 because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: Invalid Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: New Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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, transfer error [ 933.537093] [mt-i2c]ERROR,460: I2C_ACKERR or of the following sort, [ 1006.938770] inv_mpu: error to reset fifo [ 1007.055090] inv_mpu: error in header parsing=3c00 but the camera preview still seems to work, though the startup delay varies slightly due to these. This seems to indicate Qt Quick Scenegraph Renderer is doing something bogus. I guess we could also try a TPP which sets up EGL only to glClear the surface to be 100% sure. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: New Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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. It involves running the camera unconfined like so : phablet@ubuntu-phablet:/usr/share/click/preinstalled/com.ubuntu.camera/current$ ./camera-app --desktop_file_hint=dialer-app and then running the following in a script doing thousands of iterations : mir_demo_client_prompt_helper_provider.bin -p -m /run/user/32011/mir_socket_trusted -- --desktop_file_hint=dialer-app mir_demo_client_prompt_helper_provider.bin sets up a trust session and forks a gl app (simulating the dialog box) that renders 20 frames and exits (so it could be run automatically. This setup didn't yield any panic or crash. One thing I haven't tried is using trivial code (no Qt) as the actual TPP - this way the timing that TPP cutting in right before Camera starts to render can be recreated. Whereas the above case requires the Camera app to have been launched and rendering already. This involves modifying the lp:trust-store code that I'm not familiar with, but with some help, am willing to give it a try. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: New Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** Tags added: regression-proposed -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: New Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** Also affects: mir Importance: Undecided Status: New -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Mir: New Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
@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. ** 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging-app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment - #7. To verify it was really the kernel panic run + #7. + + You can reset the trust db entry for the camera app using : + $rm -rf ~/.local/share/CameraService + $restart cameraservice-trust-stored + + Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): + ps H -eo 'pid tid cmd:250 comm' + + To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. You can reset the trust db entry for the camera app using : $rm -rf ~/.local/share/CameraService $restart cameraservice-trust-stored Run the following to get the command line for all threads so you can match the pid from the kmsg later (see below): ps H -eo 'pid tid cmd:250 comm' To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** Also affects: trust-store Importance: Undecided Status: New -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in trust-store: New Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
** 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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging-app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en + + -- + + Same happens with the following steps: + + 1. Flash device (arale) with + + $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- + proposed/meizu.en --recovery-image + --bootstrap + + 2. Wait until flash process is done + 3. Go through first-start wizard + 4. Pass tutorial + 5. Directly launch camera-app, approve trust-prompt + + Repeat 1-5 multiple times and you will see a frozen device after step 5. + You can verify it happened due to a kernel panic mentioned in comment + #7. To verify it was really the kernel panic run + + $ sudo cat /proc/last_kmsg + + once the device has rebooted. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: Incomplete Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
Updated the descriptions with the steps I used to reproduce this. -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: Incomplete Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en -- Same happens with the following steps: 1. Flash device (arale) with $ ubuntu-device-flash touch --device arale --channel ubuntu/rc- proposed/meizu.en --recovery-image --bootstrap 2. Wait until flash process is done 3. Go through first-start wizard 4. Pass tutorial 5. Directly launch camera-app, approve trust-prompt Repeat 1-5 multiple times and you will see a frozen device after step 5. You can verify it happened due to a kernel panic mentioned in comment #7. To verify it was really the kernel panic run $ sudo cat /proc/last_kmsg once the device has rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
@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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: Incomplete Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
@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 memory and remembered from last boot (not if you turn the device off). -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: Incomplete Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => Critical ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Cemil Azizoglu (cemil-azizoglu) ** Changed in: canonical-devices-system-image Assignee: (unassigned) => kevin gunn (kgunn72) ** Changed in: canonical-devices-system-image Milestone: ww08-2016 => 11 -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 obtained, I saw a couple of lines spewed out by the PVR kernel side : ./logs/logs:Mar 17 17:51:36 ubuntu-phablet kernel: [ 688.646227] PVR_K:(Error): 104: RGXGetDeviceHealthStatus: KCCB for DM2 has not progressed (ROFF=10 WOFF=11) [0, ] ./logs/logs:Mar 17 20:55:38 ubuntu-phablet kernel: [ 2670.497641] PVR_K:(Error): 105: RGXGetDeviceHealthStatus: KCCB for DM0 has not progressed (ROFF=1 WOFF=2) [0, ] but not when the crash happened. So I don't think they are related. I did notice a constant stream of the following messages, but they seem to happen even when the camera is seemingly working normally. And sometimes, they don't happen. ... ./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [7.331986] [mt-i2c]ERROR,454: id=0,addr: 10, transfer error ./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [7.363560] [mt-i2c]ERROR,454: id=0,addr: 10, transfer error ./logs/logs:Mar 17 21:04:59 ubuntu-phablet kernel: [7.363701] [mt-i2c]ERROR,454: id=0,addr: 10, transfer error ... I can investigate the GL (PVR) driver side of things more if I someone can tell me how/when PVRSRV related logs appear and how to collect them? -- 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/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: New Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot
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 Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1551811 Title: Opening the camera for the first time leads to reboot Status in camera-app: New Status in Canonical System Image: Confirmed Status in Telegram app: Invalid Status in mir package in Ubuntu: Incomplete Bug description: 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 clip to attach a photo. - Select the camera. Expected result. - After accepting the permission dialog, camera app allows to take a picture. Actual result. - After accepting the permission dialog, phone reboots. I'm not sure whether this is a problem with Telegram or with the camera. However, I couldn't reproduce the problem using the messaging- app. And once the permission dialog is accepted, the reboot is gone. com.ubuntu.telegram_2.0.8.0_armhf.click current build number: 259 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1551811/+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
