[Kernel-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Sorry it took so long to get to this, but I was finally able to test on my phone with OTA-8. The pairing worked as expected. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "hcidump of a pairing attempt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4643207/+files/hcidump-hr.log -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Here's the syslog snippet from when I tried pairing using bluetoothctl ** Attachment added: "syslog part containing pairing attempt using bluetoothctl" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4641441/+files/syslog-snippet-bluetoothctl -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "ubuntu-system-settings log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640868/+files/application-legacy-ubuntu-system-settings-.log -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Still didn't work for me. ** Attachment added: "syslog part containing pairing attempt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640867/+files/syslog-snippet -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1560094] Re: Starting bluez service is denied
** Branch linked: lp:~ssweeny/bluez/snappy-interface -- 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/1560094 Title: Starting bluez service is denied Status in bluez package in Ubuntu: In Progress Bug description: If snappy core is updated in the background (on Raspberry Pi 2), and then bluez installed, starting the service is failing. Denials: [ 45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0 [ 46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0 [ 46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2 If trying to start bluetootctl: [ 582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0 [bluetooth]# ubuntu@localhost:~$ snappy list NameDate Version Developer bluez5 2016-02-04 5.37-2-armhf canonical canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-03-08 16.04.0-15.armhf canonical ubuntu@localhost:~$ ubuntu@localhost:~$ snappy info release: core/rolling architecture: armhf frameworks: bluez5.canonical apps: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
I tried to pair today using bluetoothctl but all I got back was Failed to pair: org.bluez.Error.AuthenticationRejected and the same "failed" message on the radio display. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Unfortunately the latest rc-proposed image does not fix the problem. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
It is intentional, as the bq-aquaris channel includes things like the HERE AGPS service. My BT keyboard, mouse, and headset all work so it's something to do with the HFP changes that came with bluez5 I have to assume, since before the switch I could pair with the car just fine. -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
** Attachment added: "system-settings log showing some potentially interesting errors" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4586975/+files/application-legacy-ubuntu-system-settings-.log ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1552410] [NEW] Cannot pair mako with 2014 Subaru Forester
Public bug reported: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1552410/+attachment/4586974/+files/syslog -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1550857] [NEW] BUG: Bad page map in process dbus pte:01000000 pmd:7a1cf067
Public bug reported: Kernel OOPSed while browsing the web and downloading a large file. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-7-generic 4.4.0-7.22 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ssweeny3652 F pulseaudio /dev/snd/controlC1: ssweeny3652 F pulseaudio /dev/snd/controlC0: ssweeny3652 F pulseaudio /dev/snd/seq:timidity 1210 F timidity Date: Sat Feb 27 01:21:32 2016 Failure: oops HibernationDevice: RESUME=UUID=80bfcb92-70b6-4781-9e21-7c24149e0449 InstallationDate: Installed on 2011-07-08 (1695 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: System manufacturer P5K-E ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=e610b8df-32fe-4598-ac60-3d7d2f02fa93 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: BUG: Bad page map in process dbus pte:0100 pmd:7a1cf067 UpgradeStatus: Upgraded to xenial on 2016-02-22 (5 days ago) dmi.bios.date: 12/10/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/10/2007:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops kernel-oops xenial -- 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/1550857 Title: BUG: Bad page map in process dbus pte:0100 pmd:7a1cf067 Status in linux package in Ubuntu: Confirmed Bug description: Kernel OOPSed while browsing the web and downloading a large file. ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-7-generic 4.4.0-7.22 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ssweeny3652 F pulseaudio /dev/snd/controlC1: ssweeny3652 F pulseaudio /dev/snd/controlC0: ssweeny3652 F pulseaudio /dev/snd/seq:timidity 1210 F timidity Date: Sat Feb 27 01:21:32 2016 Failure: oops HibernationDevice: RESUME=UUID=80bfcb92-70b6-4781-9e21-7c24149e0449 InstallationDate: Installed on 2011-07-08 (1695 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: System manufacturer P5K-E ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=e610b8df-32fe-4598-ac60-3d7d2f02fa93 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: BUG: Bad page map in process dbus pte:0100 pmd:7a1cf067 UpgradeStatus: Upgraded to xenial on 2016-02-22 (5 days ago) dmi.bios.date: 12/10/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/10/2007:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550857/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1280304] Re: [System76, Inc. Lemur UltraThin] late resume failure
Sorry it took so long, but I reproduced the bug with the upstream kernel. ** Tags added: kernel-bug-exists-upstream -- 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/1280304 Title: [System76, Inc. Lemur UltraThin] late resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Suspend no longer works on my laptop running Trusty. It will just blank the screen for a few seconds then come back up to the unlock prompt. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ssweeny 21867 F pulseaudio Date: Fri Feb 14 08:57:40 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=5abbcc52-f627-41eb-956f-3f811627ebed InstallationDate: Installed on 2010-10-11 (1221 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) InterpreterPath: /usr/bin/python3.3 MachineType: System76, Inc. Lemur UltraThin ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=552496e2-92cc-4e0f-87c0-322edc0cb632 ro quiet splash pcie_aspm=force vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System76, Inc. Lemur UltraThin] late resume failure UpgradeStatus: Upgraded to trusty on 2013-12-15 (61 days ago) UserGroups: dmi.bios.date: 11/11/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur UltraThin dmi.board.vendor: System76, Inc. dmi.board.version: lemu2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: lemu2 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd11/11/2010:svnSystem76,Inc.:pnLemurUltraThin:pvrlemu2:rvnSystem76,Inc.:rnLemurUltraThin:rvrlemu2:cvnSystem76,Inc.:ct10:cvrlemu2: dmi.product.name: Lemur UltraThin dmi.product.version: lemu2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1280304/+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 1280304] [NEW] [System76, Inc. Lemur UltraThin] late resume failure
Public bug reported: Suspend no longer works on my laptop running Trusty. It will just blank the screen for a few seconds then come back up to the unlock prompt. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ssweeny 21867 F pulseaudio Date: Fri Feb 14 08:57:40 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=5abbcc52-f627-41eb-956f-3f811627ebed InstallationDate: Installed on 2010-10-11 (1221 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) InterpreterPath: /usr/bin/python3.3 MachineType: System76, Inc. Lemur UltraThin ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=552496e2-92cc-4e0f-87c0-322edc0cb632 ro quiet splash pcie_aspm=force vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System76, Inc. Lemur UltraThin] late resume failure UpgradeStatus: Upgraded to trusty on 2013-12-15 (61 days ago) UserGroups: dmi.bios.date: 11/11/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur UltraThin dmi.board.vendor: System76, Inc. dmi.board.version: lemu2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: lemu2 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd11/11/2010:svnSystem76,Inc.:pnLemurUltraThin:pvrlemu2:rvnSystem76,Inc.:rnLemurUltraThin:rvrlemu2:cvnSystem76,Inc.:ct10:cvrlemu2: dmi.product.name: Lemur UltraThin dmi.product.version: lemu2 dmi.sys.vendor: System76, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume resume-late-hang suspend trusty -- 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/1280304 Title: [System76, Inc. Lemur UltraThin] late resume failure Status in “linux” package in Ubuntu: New Bug description: Suspend no longer works on my laptop running Trusty. It will just blank the screen for a few seconds then come back up to the unlock prompt. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-8-generic 3.13.0-8.28 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ssweeny 21867 F pulseaudio Date: Fri Feb 14 08:57:40 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=5abbcc52-f627-41eb-956f-3f811627ebed InstallationDate: Installed on 2010-10-11 (1221 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) InterpreterPath: /usr/bin/python3.3 MachineType: System76, Inc. Lemur UltraThin ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=552496e2-92cc-4e0f-87c0-322edc0cb632 ro quiet splash pcie_aspm=force vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-8-generic N/A linux-backports-modules-3.13.0-8-generic N/A linux-firmware1.124 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System76, Inc. Lemur UltraThin] late resume failure UpgradeStatus: Upgraded to trusty on 2013-12-15 (61 days ago)
