[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
@AceLan, In the comment #32 you were saying: "removed the beta bluez, and install stable bluez" It looks like you removed bluez that was from 22/beta track (bluez (22/beta) 5.64-3), and then installed one from 20/stable track (bluez 5.53-7 334 20/stable). You wrote that with that revision of bluez snap "power cycle the machine, and then advinfo works". Can you please confirm that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
@Daniel, The same Ubuntu Core image works as expected on the Thinkpad E15 and x86 Mac. Why would the lack of "some extra privileges" impact how it runs on the Dell system, but not Thinkpad and Mac? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775816] Re: Hang at the 3rd cycle when running S4 stress script on Ubuntu core system.
This bug is a duplicate of private bug https://bugs.launchpad.net/plano/+bug/1776129. We agreed with Jack_Le to track its resolution in #1776129. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775816 Title: Hang at the 3rd cycle when running S4 stress script on Ubuntu core system. Status in linux package in Ubuntu: Incomplete Bug description: Image info: Caracalla 16.04-1.35 rev 49/ Caracalla-kernel 4.4.0-2019.20-1 Rev 84/ Core 16-2.32.8 Rev 4650 System info: Ubuntu core Description of the issue: Hang at the 3rd cycle when running S4 stress script. Expected result: Enter S4 and wake up successfully when running S4 stress script. Actual result: Hang at the 3rd cycle, and Green LED always ON. Isolation: Manual type “rtcwake -s 120 -m disk” in the terminal, then at the third cycle input the command, the SUT hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
Krilin, r140, BT headset: Rocketfish RF-MAB2 On the first attempt, I was not able to connect to BT headset, which always connected and worked reliably with previous releases. I was able to connect after I rebooted the phone and power cycled BT headset. I tried about 5 more times power-cycling BT headset after that and it did connect reliably every time. It did not cause phone to reboot while BT headset was power cycled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in “bluez” package in Ubuntu: New Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: warn Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): device state change: failed - disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: info (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3-0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593]MAGNETIC mag_context_obj ok---hwm_obj-early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=771 x-info=http://www.rsyslog.com;] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=785 x-info=http://www.rsyslog.com;] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1387949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
