[Kernel-packages] [Bug 1628968] ProcModules.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751089/+files/ProcModules.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

[Kernel-packages] [Bug 1628968] CurrentDmesg.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751083/+files/CurrentDmesg.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 

[Kernel-packages] [Bug 1628968] UdevDb.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1628968/+attachment/4751090/+files/UdevDb.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio 

[Kernel-packages] [Bug 1628968] JournalErrors.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751084/+files/JournalErrors.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: 

[Kernel-packages] [Bug 1628968] ProcCpuinfo.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1628968/+attachment/4751086/+files/ProcCpuinfo.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 

[Kernel-packages] [Bug 1628968] [NEW] powerpc 4.8.0-17 fails to boot on PowerMac G5

[Mathieu Trudel-Lapierre]

Public bug reported:

Not much else to say. The system fails to complete booting, it gets
stuck somewhere before network comes up; with errors in syslog about
missing symbols for some modules (see
http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount (err 
0)
Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 0)
Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
--- 
ApportVersion: 2.20.3-0ubuntu7
Architecture: powerpc
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
InstallationDate: Installed on 2016-09-28 (1 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
IwConfig:
 lono wireless extensions.
 
 enP1p5s4f1  no wireless extensions.
 
 enP1p5s4f0  no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-powerpc64-smp N/A
 linux-backports-modules-4.4.0-21-powerpc64-smp  N/A
 linux-firmware  1.161
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags:  yakkety
Uname: Linux 4.4.0-21-powerpc64-smp ppc64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner 

[Kernel-packages] [Bug 1628968] CRDA.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1628968/+attachment/4751082/+files/CRDA.txt

-- 
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/1628968

Title:
  powerpc 4.8.0-17 fails to boot on PowerMac G5

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Not much else to say. The system fails to complete booting, it gets
  stuck somewhere before network comes up; with errors in syslog about
  missing symbols for some modules (see
  http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:

  Sep 28 12:49:55 fujin kernel: [4.698092] uninorth_agp: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.715284] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.731545] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759718] drm: Unknown symbol ence_release 
(err 0)
  Sep 28 12:49:55 fujin kernel: [4.759781] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.777863] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.798476] drm: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.815248] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.826136] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.846026] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.862106] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.882364] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [4.898322] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.914094] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [4.930108] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [5.396683] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [7.609956] autofs4: Unknown symbol 
cache_dir_open (err 0)
  Sep 28 12:49:55 fujin kernel: [7.610137] autofs4: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [9.989854] parport: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.405448] shpchp: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   16.684111] ata_generic: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.826081] rack_meter: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.953962] i2c_algo_bit: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   16.977975] pps_core: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.010110] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.022857] soundcore: Unknown symbol mcount 
(err 0)
  Sep 28 12:49:55 fujin kernel: [   17.034422] firewire_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.049942] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.070474] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.085972] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.102451] windfarm_core: Unknown symbol 
mcount (err 0)
  Sep 28 12:49:55 fujin kernel: [   17.118814] uio: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.813073] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   17.820183] hid: Unknown symbol mcount (err 
0)
  Sep 28 12:49:55 fujin kernel: [   19.022406] bluetooth: Unknown symbol mcount 
(err 0)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=8c8a4ee6-57e4-4d02-9196-6c4620ee5883
  InstallationDate: Installed on 2016-09-28 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enP1p5s4f1  no wireless extensions.
   
   enP1p5s4f0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: root=UUID=fd6c3ae7-7de7-416e-8bed-b4513658ee6d ro quiet 
splash verbose
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio 

[Kernel-packages] [Bug 1627875] Re: Yakkety server Beta install fails in a virtual client with UEFI bios

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1624096 ***
https://bugs.launchpad.net/bugs/1624096

** This bug has been marked a duplicate of bug 1624096
   yakkety: backport (or rebase to) fix eliminating a double-close in shim

-- 
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/1627875

Title:
  Yakkety server Beta install fails in a virtual client with UEFI bios

Status in Ubuntu Manual Tests:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  Using Virt-manager the Beta2 ISO fails to boot when a UEFI BIOS is
  selected. 4GB RAM, 8 CPUs. Nothing appears on the console after the
  Tiancore splash screen.

  Here is an image of what it hangs at:
  http://img.ctrlv.in/img/16/09/27/57e9aae61a86d.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1627875/+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 1627875] Re: Yakkety server Beta install fails in a virtual client with UEFI bios

[Mathieu Trudel-Lapierre]

This is bug 1624096.

-- 
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/1627875

Title:
  Yakkety server Beta install fails in a virtual client with UEFI bios

Status in Ubuntu Manual Tests:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  Using Virt-manager the Beta2 ISO fails to boot when a UEFI BIOS is
  selected. 4GB RAM, 8 CPUs. Nothing appears on the console after the
  Tiancore splash screen.

  Here is an image of what it hangs at:
  http://img.ctrlv.in/img/16/09/27/57e9aae61a86d.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1627875/+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 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

Verification-successful for shim-signed on precise --- all that is
required is there: the update-secureboot-policy script does what it
should and is run as expected.

However, it looks like MokManager.efi (which isn't something coming from
shim-signed) isn't installed on the system under /boot/efi/EFI/ubuntu.
This isn't a regression since it does not appear that it was ever
automatically installed. Still, this breaks the workflow of toggling
shim validation, so it must be fixed ASAP.

** Tags removed: verification-needed
** Tags added: verification-done-precise

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Released
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Invalid
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Wily:
  Fix Released
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Released
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

efivar for trusty ended up not being needed.

** Changed in: efivar (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Released
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Released
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Wily:
  Fix Released
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Released
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom 

[Kernel-packages] [Bug 1278522] Re: asus n750jv cannot install with secure boot enabled

[Mathieu Trudel-Lapierre]

Given that the solution presented here on the same kind of system was to
set:

nomodeset acpi_osi=

It sounds a lot more like an issue in the kernel. Disabling Secure Boot
should not impact the system if it reaches the point of the boot splash
(the purple screen with the Ubuntu logo in the center, or with Ubuntu
text). Reassigning to 'linux'.

Marat, did this solution help you at all?

** Package changed: shim (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1278522

Title:
  asus n750jv cannot install with secure boot enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot install ubuntu 13.10 with secure boot enabled and fast boot
  disabled and UEFI mode on asus n750jv with windows 8 preinstalled.
  Hungs on a purple start screen with an ubuntu word. Ubuntu installed
  well after disabling secure boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: shim 0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 10 21:48:34 2014
  Dependencies:
   
  InstallationDate: Installed on 2014-02-10 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1278522/+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 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

Verification done for XENIAL: grub2-signed, dkms, shim-signed all found
to be working as expected. Test cases pass. As previously discussed, the
grub2-signed update is not especially useful in itself and does need to
drop the calls to mokutil, but will need a further SRU to remove calling
update-secureboot-policy later.

** Tags added: verification-done-wily

** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

Verification-done for TRUSTY: efivar, mokutil, dkms, shim-signed all
found to be working at expected. Test cases pass.

** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

Verification-done for WILY: mokutil, dkms, shim-signed all found to be
working as expected. Test cases pass.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Wily:
  Fix Committed
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Description changed:

  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.
  
  [Impact]
  All our users booting in UEFI; on all supported releases.
  
  [Test cases]
- 
+ 
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0
  
  Test cases here are separated by the components that need to be changed:
+ 
+ = mokutil =
+ 
+ Adding a MOK key:
+ 1) Install system
+ 2) Run 'mokutil --import ' to import a signing certificate.
+ 3) On reboot; validate MOK prompts for new MOK key to add.
+ 
+ Toggling Secure Boot state:
+ 1) Install system
+ 2) mokutil --enable-validationormokutil --disable-validation
+ 3) Validate that on reboot MOK prompts to change Secure Boot state.
+ 
+ Listing keys:
+ 1) mokutil --list-enrolled
+ -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.
+ 
+ 
+ = efivar =
+ 
+ libefivar0 gets tested via the use of mokutil. Since it is a library
+ with no directly usable binaries; we rely on mokutil / sbsigntool /
+ efibootmgr to do testing.
+ 
+ 1) Run efibootmgr -v ; verify it lists BootEntries.
+ 2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.
+ 
+ 
+ = shim-signed =
+ 
+ 1) Install system; upgrade to new packages
+ 1b) Verify /proc/sys/kernel/secure_boot shows 1.
+ 1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
+ 2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
+ 3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
+ 4) Reboot; follow MOK steps to disable Secure Boot.
+ 4b) Verify /proc/sys/kernel/secure_boot shows 1.
+ 4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
+ 5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
+ 6) Reboot; follow MOK steps to re-enable Secure Boot.
+ 6b) Verify /proc/sys/kernel/secure_boot shows 1.
+ 6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
+ 
  
  = grub2 =
  
  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)
  
  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.
  
+ 
  = dkms =
  
  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.
  
  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.
+ 
  
  = shim =
  
  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.
  
  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.
  
- 
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
  - (dkms, on new shim) prompting unnecessarily if validation is already 
disabled
  - (grub) not prompting on upgrade ...
  - (grub) not prompting on upgrade across releases if validation is disabled; 
without the applied SRU on original release.
  - (grub, on new shim) prompting unecessarily ...
  - (shim) failing to boot on some firmware that doesn't correctly follow 
specification
  - (shim) 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

precise:
- verified efivar & sbsigntool
- verified mokutil

Verification passes for these SRUs.

** Tags added: verification-done-precise

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Committed
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  Fix Committed
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  In Progress
Status in dkms source package in Trusty:
  New
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  In Progress
Status in dkms source package in Wily:
  New
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  In Progress
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.

  
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Changed in: shim-signed (Ubuntu Wily)
   Status: New => In Progress

** Changed in: shim-signed (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: shim-signed (Ubuntu Precise)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Committed
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  Fix Committed
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  In Progress
Status in dkms source package in Trusty:
  New
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  In Progress
Status in dkms source package in Wily:
  New
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  In Progress
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Committed
Status in grub2-signed source package in Xenial:
  Fix Committed
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Also affects: efibootmgr (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: efibootmgr (Ubuntu)
   Status: New => Fix Released

** Changed in: efibootmgr (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: efibootmgr (Ubuntu Wily)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efibootmgr source package in Trusty:
  New
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in grub2-signed source package in Xenial:
  New
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Changed in: shim-signed (Ubuntu)
   Importance: Undecided => High

** Changed in: shim-signed (Ubuntu)
   Status: New => Fix Released

** Changed in: shim-signed (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in grub2-signed source package in Xenial:
  New
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.

  
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
  - (dkms, on new shim) prompting unnecessari

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Also affects: shim-signed (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  New
Status in dkms source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efivar source package in Trusty:
  Fix Committed
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  Fix Committed
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  Fix Committed
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in grub2-signed source package in Xenial:
  New
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.

  
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
  - (dkms, on new shim) prompting unnecessarily if validation is already 
disabled
  - (grub) not prompting on upgrade ...
  - (grub) not prompting on upgrade across releases if validation is disabled; 
without the applied SRU on original release.
  - (grub, on new shim) 

[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Mathieu Trudel-Lapierre]

This doesn't really depend on any extra steps -- I've just uploaded
grub2 and grub2-signed to xenial-proposed queue, so as soon as it's
reviewed by a member of the SRU team it will be available in proposed.

>From there, we'll need people to test this carefully to make sure
nothing is broken and that it's fulfilling its intended purposed (ie.
fixing the issue), after that we'll be able to make it available to the
general public in -updates.

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu)
   Status: New => Fix Released

** Changed in: grub2-signed (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: grub2-signed (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: grub2-signed (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: grub2-signed (Ubuntu)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1527727

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  New

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+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 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...

[Mathieu Trudel-Lapierre]

Uploaded to yakkety:

grub2 (2.02~beta2-36ubuntu5) yakkety; urgency=medium

  * debian/patches/zpool_full_device_name.patch: Signal to zpool that
it should emit full names of constituent devices.

** Changed in: grub2 (Ubuntu)
   Status: In Progress => Fix Released

** Description changed:

+ [Impact]
+ Installs over ZFS where a ZFS disk is expected to be used as a root device.
+ 
+ [Test case]
+ - Run update-grub on a system with a ZFS root filesystem.
+ 
+ [Regression Potential]
+ Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.
+ 
+ ---
+ 
  update-grub runs /usr/sbin/grub-probe
  
  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.
  
  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.
  
  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".
  
  It then tests the existence of the path name of the device. it fails.
  
  grub-probe then returns  something like
  
  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev/ata-
  ST31000333AS_-part1'.
  
  The actual path is of course /dev/disk/by-id/ST31000333AS_-part1
  
  It can prepend smarter than "/dev" or it can understand ZFS natively, to
  fix the problem.

** Also affects: grub2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: zfs-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: grub2 (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: grub2 (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: grub2 (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1527727

Title:
  grub-probe for zfs assumes all devices prefix with /dev, ignoring
  /dev/disk/...

Status in grub:
  Unknown
Status in grub2 package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  New

Bug description:
  [Impact]
  Installs over ZFS where a ZFS disk is expected to be used as a root device.

  [Test case]
  - Run update-grub on a system with a ZFS root filesystem.

  [Regression Potential]
  Installs relying on the current broken behavior to avoid listing other 
operating systems in grub menu may find that new entries are added.

  ---

  update-grub runs /usr/sbin/grub-probe

  Without libzfslinux support compiled in, /usr/sbin/grub-probe runs
  ["zpool", "status", poolname] to find out ZFS info.

  zpool responds with device names as used at (I think!) pool creation
  time. Often, this is /dev/disk/by-id/... names, without the path.

  grub-probe then parses the output, and takes the names of devices, and
  if they do not start with a "/", it prepends "/dev/".

  It then tests the existence of the path name of the device. it fails.

  grub-probe then returns  something like

  /usr/sbin/grub-probe: error: failed to get canonical path of `/dev
  /ata-ST31000333AS_-part1'.

  The actual path is of course /dev/disk/by-
  id/ST31000333AS_-part1

  It can prepend smarter than "/dev" or it can understand ZFS natively,
  to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub/+bug/1527727/+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 1507505] Re: NVME partition names incorrect; should be nvme0p1, not nvme0n1

[Mathieu Trudel-Lapierre]

No, it's not that simple.

The kernel and anything is free to use the naming policy it wants, but
that's not the problem here. p* is still used in nvme, but there is a
numbering before that for the device ID -- nvme0n1 points to a "drive",
nvme0n1p1 points to a partition. This issue is in grub-installer, it's
just that I don't have NVMe drives to play with to figure it out.

Could someone seeing this issue please run the installer but just before
that, modify grub-installer to add "set -x" near the top so we can see
which part of grub-installer does the parsing wrong?

Reassigning to grub-installer since we don't need to bug the kernel team
for this...

** Package changed: linux (Ubuntu) => grub-installer (Ubuntu)

** Changed in: grub-installer (Ubuntu)
   Importance: Undecided => High

** Changed in: grub-installer (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: grub-installer (Ubuntu)
     Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

-- 
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/1507505

Title:
  NVME partition names incorrect; should be nvme0p1, not nvme0n1

Status in grub-installer:
  New
Status in Linux:
  Unknown
Status in grub-installer package in Ubuntu:
  Triaged

Bug description:
  On T460s, I tried to install the wily daily build,  it could detect
  the nvme partition, at the end of installation, it prompt ' Unable to
  install GRUB in /dev/nvme'

  Oct 19 16:47:01 ubuntu grub-installer: info: Installing grub on '/dev/nvme'
  Oct 19 16:47:01 ubuntu grub-installer: info: grub-install does not support 
--no-floppy
  Oct 19 16:47:01 ubuntu grub-installer: info: Running chroot /target 
grub-install  --force "/dev/nvme"
  Oct 19 16:47:01 ubuntu grub-installer: Installing for i386-pc platform.
  Oct 19 16:47:02 ubuntu grub-installer: grub-install: error: cannot find a 
GRUB drive for /dev/nvme.  Check your device.map.
  Oct 19 16:47:02 ubuntu grub-installer: error: Running 'grub-install  --force 
"/dev/nvme"' failed.
  Oct 19 16:48:30 ubuntu systemd[1]: Started Session c2 of user ubuntu.

  Why it install to /dev/nvme, while not the /dev/nvme0n1?

  $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme
  Installing for i386-pc platform
  grub-install: error: cannot find a GRUB drive for /dev/nvme.  Check your 
device.map.

  $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0
  Installing for i386-pc platform
  grub-install: error: attempt to read or write outside of disk 
`hostdisk/dev/nvme0'.

  $ sudo grub-install --boot-directory /target/boot/grub /dev/nvme0n1
  Installing for i386-pc platform
  Inatalltion finished. No error reported.

  But even it's no error reported, I still cant' find any grub after
  reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/grub-installer/+bug/1507505/+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 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

** Also affects: efivar (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: mokutil (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: efivar (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: mokutil (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: efivar (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: mokutil (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: efivar (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: mokutil (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: efivar (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: mokutil (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: efivar (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: efivar (Ubuntu Wily)
   Status: New => Fix Released

** Changed in: efivar (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: efivar (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: dkms (Ubuntu Xenial)
   Status: New => Fix Released

** No longer affects: dkms (Ubuntu Yakkety)

** No longer affects: efivar (Ubuntu Yakkety)

** No longer affects: grub2 (Ubuntu Yakkety)

** No longer affects: grub2-signed (Ubuntu Yakkety)

** No longer affects: mokutil (Ubuntu Yakkety)

** No longer affects: shim (Ubuntu Yakkety)

** Changed in: mokutil (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: mokutil (Ubuntu)
   Status: New => Fix Released

** Changed in: dkms (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in dkms source package in Precise:
  New
Status in efivar source package in Precise:
  New
Status in grub2 source package in Precise:
  New
Status in grub2-signed source package in Precise:
  New
Status in mokutil source package in Precise:
  New
Status in shim source package in Precise:
  New
Status in dkms source package in Trusty:
  New
Status in efivar source package in Trusty:
  New
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in mokutil source package in Trusty:
  New
Status in shim source package in Trusty:
  New
Status in dkms source package in Wily:
  New
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  New
Status in grub2-signed source package in Wily:
  New
Status in mokutil source package in Wily:
  New
Status in shim source package in Wily:
  New
Status in dkms source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  New
Status in 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

That should have read, any version of mokutil below 0.3.0-0ubuntu3~ will
not work correctly with lts kernels on the LTS releases.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  New
Status in efivar package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.

  
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
  - (dkms, on new shim) prompting unnecessarily if validation is already 
disabled
  - (grub) not prompting on upgrade ...
  - (grub) not prompting on upgrade across releases if validation is disabled; 
without the applied SRU on original release.
  - (grub, on new shim) prompting unecessarily ...
  - (shim) failing to boot on some firmware that doesn't correctly follow 
specification
  - (shim) failing to load a properly-signed grub
  - (shim) accepting to load a badly-signed grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1574727/+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 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

This also needs a mokutil update, as the version in >=14.04 will not
work correctly with *-lts* kernels.

** Also affects: mokutil (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim validation.

  = dkms =

  Prompting for dkms on install:
  1) Install r8168-dkms
  2) Verify that you're asked to disable shim validation, and walked through 
the process via debconf prompts.

  Prompting for dkms on upgrade
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
  2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
  3) Validate that dkms prompts you to disable shim validation.

  = shim =

  Booting:
  -> Validate that it allows booting grubx64.efi signed with the old key.
  -> Validate that it allows booting grubx64.efi signed with the new key.

  Validation toggle:
  0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
  If MokSBStateRT is preset:
  1) sudo mokutil --enable-validation && sudo reboot
  2) Validate that Mok asks you if you want to enable validation
  Otherwise:
  1) sudo mokutil --disable-validation && sudo reboot
  2) Validate that Mok asks you if you want to disable validation
  Finally:
  3) Complete the process to toggle validation state, reboot, and verify 
whether MokSBStateRT is present.
  4) Run mokutil again to toggle validation back to its former state.

  
  [Regression Potential]
  Issues to watch out for:
  - (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
  - (dkms, on new shim) prompting unnecessarily if validation is already 
disabled
  - (grub) not prompting on upgrade ...
  - (grub) not prompting on upgrade across releases if validation is disabled; 
without the applied SRU on original release.
  - (grub, on new shim) prompting unecessarily ...
  - (shim) failing to boot on some firmware that doesn't correctly follow 
specification
  - (shim) failing to load a properly-signed grub
  - (shim) accepting to load a badly-signed grub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1574727/+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 1574727] [NEW] [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

Public bug reported:

[Rationale]
Secure Boot is good. We want to be able to validate that as much as possible of 
the boot process happens with signed binaries; from our shim (the part that is 
loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded 
modules.

[Impact]
All our users booting in UEFI; on all supported releases.

[Test cases]


Test cases here are separated by the components that need to be changed:

= grub2 =

Booting signed kernels:
1) Try to boot a custom kernel
2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

Prompting on upgrade:
0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
3) Validate that grub2 prompts you to disable shim validation.

= dkms =

Prompting for dkms on install:
1) Install r8168-dkms
2) Verify that you're asked to disable shim validation, and walked through the 
process via debconf prompts.

Prompting for dkms on upgrade
0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && reboot'
2) Upgrade to the new dkms package (you may need to download the updated 
package beforehand)
3) Validate that dkms prompts you to disable shim validation.

= shim =

Booting:
-> Validate that it allows booting grubx64.efi signed with the old key.
-> Validate that it allows booting grubx64.efi signed with the new key.

Validation toggle:
0) Boot the system; verify if /sys/firmware/efi/efivars/MokSBStateRT-* is 
present;
If MokSBStateRT is preset:
1) sudo mokutil --enable-validation && sudo reboot
2) Validate that Mok asks you if you want to enable validation
Otherwise:
1) sudo mokutil --disable-validation && sudo reboot
2) Validate that Mok asks you if you want to disable validation
Finally:
3) Complete the process to toggle validation state, reboot, and verify whether 
MokSBStateRT is present.
4) Run mokutil again to toggle validation back to its former state.


[Regression Potential]
Issues to watch out for:
- (dkms) not prompting on upgrade of a dkms package/dkms itself if validation 
is currently enabled (provided debconf does not have dkms/disable_secureboot 
seen and set to false)
- (dkms, on new shim) prompting unnecessarily if validation is already disabled
- (grub) not prompting on upgrade ...
- (grub) not prompting on upgrade across releases if validation is disabled; 
without the applied SRU on original release.
- (grub, on new shim) prompting unecessarily ...
- (shim) failing to boot on some firmware that doesn't correctly follow 
specification
- (shim) failing to load a properly-signed grub
- (shim) accepting to load a badly-signed grub

** Affects: dkms (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: shim (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: grub2 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: shim (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1574727

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  

  Test cases here are separated by the components that need to be
  changed:

  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by grub (you should see an error 
message about the signature)

  Prompting on upgrade:
  0) On a system that runs a dkms module (such as r8168-dkms, rtl8812au-dkms, 
ndiswrapper-dkms, bbswitch-dkms, etc.)
  1) Make sure that validation is enabled and reboot: 'sudo mokutil 
--enable-validation && sudo reboot'
  2) Upgrade to the new grub2 package (you may need to download the updated 
package beforehand)
  3) Validate that grub2 prompts you to disable shim 

[Kernel-packages] [Bug 1569484] Re: Auto Ethernet connection profile appears. Wifi does not work anymore.

[Mathieu Trudel-Lapierre]

There isn't much here to indicate anything is wrong with
NetworkManager's handling of the wireless interface. This looks rather
like a kernel issue, or at least the driver being confused by the device
renaming done by udev rules/systemd.

Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: brcmf_c_preinit_dcmds: 
Firmware version = wl0: Oct 22 2015 06:16:26 version 7.35.180.119 (r594535) 
FWID 01-e791c176
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: brcmf_cfg80211_reg_notifier: 
not a ISO3166 code
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: brcmfmac :3a:00.0 wlp58s0: 
renamed from wlan0
[...]
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: IPv6: ADDRCONF(NETDEV_UP): 
wlp58s0: link is not ready
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: brcmf_add_if: ERROR: 
netdev:wlp58s0 already exists
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: brcmf_add_if: ignore IF event
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel: IPv6: ADDRCONF(NETDEV_UP): 
wlp58s0: link is not ready

Since we have errors from the kernel, I'm reassigning this to the linux
package.

** Package changed: network-manager-applet (Ubuntu) => linux (Ubuntu)

-- 
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/1569484

Title:
  Auto Ethernet connection profile appears. Wifi does not work anymore.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran sudo apt-get upgrade && sudo apt-get dist-upgrade. Some
  installation have done and Auto Ethernet profile emerged in internet
  settings. After those installations I could not connect to internet.
  My laptop is Dell xps 13 9350.

  I used my TP-LINK wireless adapter to be able to send you this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 12 20:18:04 2016
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-10 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e98417061b  proto static  metric 600
   169.254.0.0/16 dev wlxc4e98417061b  scope link  metric 1000
   192.168.1.0/24 dev wlxc4e98417061b  proto kernel  scope link  src 
192.168.1.63  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH
   berkaywifi 1  3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  802-11-wireless  
1460481455  Sal 12 Nis 2016 20:17:35 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxc4e98417061b  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1
   berkaywifi 2  6afc325f-3765-4687-b4dd-47c17a93f185  802-11-wireless  
1460480549  Sal 12 Nis 2016 20:02:29 EEST  yes  0 
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH
   wlxc4e98417061b  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  berkaywifi 1  
3f5048a4-32e9-4ca5-ad31-f615ca2bc0e9  
/org/freedesktop/NetworkManager/ActiveConnection/1
   wlp58s0  ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
   lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  ---- 
   --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569484/+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 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels

[Mathieu Trudel-Lapierre]

AFAICT systemtap works well in xenial with the latest version:

systemtap (2.9-2ubuntu2) xenial; urgency=medium

  * d/p/0001-Fix-PR9497-by-updating-the-runtime-to-handle-linux-4.patch:
Fix stap compilation after kernel 4.4 commit 7523e4dc50. (LP: #1557673)

** Changed in: systemtap (Ubuntu Xenial)
   Status: Confirmed => Fix Released

-- 
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/1545330

Title:
  [wily][regression] systemtap script compilation broken by new kernels

Status in linux package in Ubuntu:
  Fix Released
Status in systemtap package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in systemtap source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Released
Status in systemtap source package in Xenial:
  Fix Released
Status in systemtap package in Fedora:
  Unknown

Bug description:
  The following errors appear when compiling any systemtap script:

  In file included from include/linux/mutex.h:15:0,
   from 
/tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25:
  include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’ 
undeclared here (not in a function)
    .raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \
    ^
  include/linux/spinlock_types.h:79:15: note: in expansion of macro 
‘__RAW_SPIN_LOCK_INITIALIZER’
    { { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } }
     ^
  include/linux/spinlock_types.h:82:16: note: in expansion of macro 
‘__SPIN_LOCK_INITIALIZER’
    (spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname)
  ^
  include/linux/mutex.h:111:18: note: in expansion of macro 
‘__SPIN_LOCK_UNLOCKED’
     , .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \
    ^
  include/linux/mutex.h:117:27: note: in expansion of macro 
‘__MUTEX_INITIALIZER’
    struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)

  Upstream fix:
  
https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+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 1558438] Re: "Disable secure boot" workflow is broken

[Mathieu Trudel-Lapierre]

dkms would be affected the same way, they both use the same code.

I will fix today.

** Also affects: dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dkms (Ubuntu)
   Importance: Undecided => Critical

** Changed in: dkms (Ubuntu)
   Status: New => Triaged

** Changed in: grub2 (Ubuntu)
   Status: New => Triaged

** Changed in: dkms (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: grub2 (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1558438

Title:
  "Disable secure boot" workflow is broken

Status in dkms package in Ubuntu:
  Triaged
Status in grub2 package in Ubuntu:
  Triaged

Bug description:
  I upgraded to grub2 2.02~beta2-36ubuntu1 and was presented with the
  new prompt to disable secure boot, since I have a dkms package
  installed.  The password I entered was 14 characters long.  On the
  terminal, I see:

  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  password should be 8~16 characters
  password should be 8~16 characters
  password should be 8~16 characters
  Abort

  Looking at the code:

  db_get dkms/secureboot_key
  length=`echo $RET | wc -c`
  if [ $length -lt 8 ] || [ $length -gt 16 ]; then
  db_fset dkms/text/bad_secureboot_key seen false
  db_input critical dkms/text/bad_secureboot_key
  STATE=$(($STATE - 2))
  elif [ $length -ne 0 ]; then
  echo "${RET}\n${RET}" | mokutil 
--disable-validation >/dev/null || true
  fi

  There are a few problems here:

   * You *must* use echo "$RET" rather than echo $RET; the password could 
contain metacharacters.  In general you should always surround any $-expansion 
in a shell script with "" unless you specifically know that you're in one of 
the special cases where you need to not do so.
   * This is a /bin/bash script for historical reasons.  echo "${RET}\n${RET}" 
is non-portable syntax and only works in shells such as dash with the other 
style of echo.  You should use this instead: printf '%s\n%s\n' "$RET" "$RET"
   * While you're here, it seems to me that a password confirmation page would 
be a good idea, given that you obviously can't see what you're typing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1558438/+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 1544809] Re: kernel security update fails if a 2nd Ubuntu on same machine

[Mathieu Trudel-Lapierre]

Reassigning to grub2, which seems more appropriate at a quick glance.
I'll look to reproduce this tomorrow.

** Package changed: linux (Ubuntu) => grub2 (Ubuntu)

-- 
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/1544809

Title:
  kernel security update fails if a 2nd Ubuntu on same machine

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  There is a security issue when multiple instances of Ubuntu (or other
  distributions) are installed on the same hardware.  In my case I have
  14.04 LTS and 16.04 alpha (plus some others).

  After installing 14.04 LTS as the main system on an UEFI machine there
  is a file,  that effectively points to
  whichever installation has control of the boot process and which
  instance of GRUB2 gets run.  If a second install, for example, a test
  of 16.04 alpha, is made then that file is over written.

  Rebooting 14.04 LTS via 16.04 alpha's GRUB2 or other means and
  installing a standard kernel security update does NOT make the new
  kernel available on subsequent reboots because even though 14.04 LTS's
  GRUB2 has been updated it is never run.  16.04 alpha's GRUB2 (which is
  ignorant of 14.04 LTS's update) is run because that is what
   points to.

  There are many ways to fix this problem.

  1)
  Make all installations maintain a link to the most recent kernel.  Ubuntu 
does this, there are links in the root directory current and old of kernel and 
intrd.  Make all boot loaders look for those links.  If Ubuntu configured GRUB2 
to look for /vmlinuz it could find the current kernel even if the kernel had 
been upgraded after GRUB2 was updated.  Ubuntu configured GRUB2 does not do 
this.  Of course it is impossible to get all software from all sources to "play 
nice", but you could make multiple installations of Ubuntu co-operate with each 
other.  

  2)
  Check where  points to and "take it back", if 
necessary.  
  Modified  attached.  

  3)
  Use an EFI style boot loader on EFI machines.  There is an Ubuntu repository 
for rEFInd, which has worked well for me.  This has the added advantage that if 
anyone makes a test installation like 16.04 alpha and then deletes it (not an 
unreasonable thing to do with an alpha release) then the machine does not 
become unbootable - because  would be pointing 
to an non-existent instance of GRUB2.  BTW rEFInd and GRUB2 can be made to 
co-exist in various way, if you want.  

  END)

  I can not see how to make an attachment to this bug report, so I will paste 
my zz-update-grub here as text, and ubuntu-bug did not work for me.
  
  $ ubuntu-bug linux
  usage: whoopsie-upload-all [-h] [-t TIMEOUT]
  whoopsie-upload-all: error: unrecognized arguments: linux
  <\cut-n-paste from terminal>

  
  #! /bin/sh
  set -e

  which update-grub >/dev/null 2>&1 || exit 0

  if type running-in-container >/dev/null 2>&1 && \
 running-in-container >/dev/null; then
  exit 0
  fi

  set -- $DEB_MAINT_PARAMS
  mode="${1#\'}"
  mode="${mode%\'}"
  case $0:$mode in
  # Only run on postinst configure and postrm remove, to avoid wasting
  # time by calling update-grub multiple times on upgrade and removal.
  # Also run if we have no DEB_MAINT_PARAMS, in order to work with old
  # kernel packages.
  
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
  CFG1='/boot/efi/EFI/ubuntu/grub.cfg'
  CFG2='/boot/grub/grub.cfg'
  if [ -e $CFG1 ]; then
  # This is an EFI system.
  # Does that config file point to this installation?
  # Get UUID of installation that that file points to
  UUID=$(grep "\<[[:xdigit:]-]\{36\}\>" $CFG1 \
  | cut --delimiter=' ' --fields=2)
  # Is file format stable?
  # Could use "sed" rather than "cut" to find UUID.
  # UUID=$(sed -n -e 's/^.*\(\<[[:xdigit:]-]\{36\}\>\).*$/\1/p' 
$CFG1)

  # Get device name for this installation
  # Spaces are needed, in case grub2 is on the root partition.
  DEVICE=$(mount \
  | grep " $(df --output=target $CFG2 \
  | tail --lines=1) " \
  | cut --delimiter=' ' --fields=1)

  # Do they both have the same line in blkid?
  if ["$(blkid | grep $DEVICE)" \
  != \
  "$(blkid | grep $UUID)" ] ;
  then
  # They do NOT match.  
  # That EFI entry does not point to this installation. 
 
  # Configuring grub on this installation is pointless. 
 
  # Options; 
  #   hope that the other installation(s) is well 
configured 

[Kernel-packages] [Bug 1490212] Re: "Modaliases" field missing from debian control file

[Mathieu Trudel-Lapierre]

Adam,

Generally this looks pretty good; but let's focus on just the modaliases
issues for this bug. Can you file separate bug reports for the other
problems?

As for software-properties, I suspect there are probably no issues
there; everything can be fixed by modifying just b43-fwcutter (by the
look of things).

I'm adjusting the bug status accordingly.

** Changed in: software-properties (Ubuntu)
   Status: New => Invalid

** Changed in: b43-fwcutter (Ubuntu)
   Status: New => Triaged

** Changed in: b43-fwcutter (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/1490212

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

[Mathieu Trudel-Lapierre]

** Changed in: bcmwl (Ubuntu)
   Status: New => In Progress

** Changed in: bcmwl (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1498074

Title:
  Package is not being installed if you install from a usb pendrive
  created from disks

Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  Pre-requisite: Laptop with bcmwl supported chipset, intel based macs or dell 
xps for example.

  1. Grab the latest 15.10 daily image from cdimages
  2. Plug a usb pendrive into the system
  3. Open Disks
  4. Format the pendrive
  5. Select restore image to drive
  6. Select the image you just downloaded
  7. Click on okay if the install is happening on the pendrive
  8. Click on okay again to confirm
  9. Add the user password for permission to write to the drive
  10. Insert the written image into the laptop you want to install on
  11. In the uefi menu select the pendrive
  12. Select the live session
  13. Open system settings
  14. Open Software and updates
  15. Tap on the Additional Drivers tab

  EXPECTED:
  I expect to the bcmwl driver available to install

  ACTUAL:
  I see only micro code driver for the cpu (see screenshot)

  Included files:
  Screenshot
  /etc/apt/sources.list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1498074/+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 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel

[Mathieu Trudel-Lapierre]

Could you please share the partition layout for that system? Which
partitioning method you picked or if you specified some manual
partitioning. Also, please include how many disks are included, of what
size. I will try to reproduce this bug in a virtual machine for further
debugging.

** Changed in: grub2 (Ubuntu)
   Status: Triaged => Incomplete

-- 
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/1455268

Title:
  update-grub (grub-probe) during package installation on Cisco UCS B260
  servers - Precise deployment fails with hwe-t kernel

Status in grub2 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  In bug 1437475, deploying Precise with maas was failing with curtin
  error with generic ephemeral image.

  With hwe-t kernel it gets passed the curtin error.. However, grub
  looks to be stuck. Looking at the diff for install log minutes apart
  right before deployment gets marked as failed by maas, it looks to be
  retrying the last step:

  Last lines of curtin install log:
  ===
  Unpacking linux-generic-lts-trusty (from 
.../linux-generic-lts-trusty_3.13.0.52.45_amd64.deb) ...
  Setting up linux-image-3.13.0-52-generic (3.13.0-52.86~precise1) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-52-generic /boot/vmlinuz-3.13.0-52-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-52-generic
  df: Warning: cannot read table of mounted file systems: No such file or 
directory
  run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 
3.13.0-52-generic /boot/vmlinuz-3.13.0-52-generic
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.2.0-80-generic
  Found kernel: /boot/vmlinuz-3.13.0-52-generic
  Found kernel: /boot/memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  Found linux image: /boot/vmlinuz-3.2.0-80-generic
  Found initrd image: /boot/initrd.img-3.2.0-80-generic
  Found memtest86+ image: /boot/memtest86+.bin
  done
  Setting up linux-image-generic-lts-trusty (3.13.0.52.45) ...
  Setting up linux-headers-3.13.0-52 (3.13.0-52.86~precise1) ...
  Setting up linux-headers-3.13.0-52-generic (3.13.0-52.86~precise1) ...
  Setting up linux-headers-generic-lts-trusty (3.13.0.52.45) ...
  Setting up linux-generic-lts-trusty (3.13.0.52.45) ...
  Leaving 'diversion of /etc/init/ureadahead.conf to 
/etc/init/ureadahead.conf.disabled by cloud-init'
  8192+0 records in
  8192+0 records out
  8589934592 bytes (8.6 GB) copied, 6.10194 s, 1.4 GB/s
  Setting up swapspace version 1, size = 8388604 KiB
  no label, UUID=56f58ad7-bd54-4c17-be2f-893d3c70cd7e
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  Found linux image: /boot/vmlinuz-3.2.0-80-generic
  Found initrd image: /boot/initrd.img-3.2.0-80-generic
  Found memtest86+ image: /boot/memtest86+.bin
  done
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  ===

  Diff output:
  ===
  ubuntu@pullman-01:~$ diff install.log var/log/curtin/install.log 
  219,221d218
  < Generating grub.cfg ...
  < Found linux image: /boot/vmlinuz-3.13.0-52-generic
  < Found initrd image: /boot/initrd.img-3.13.0-52-generic
  ubuntu@pullman-01:~$ 
  ===

  I am attaching some logs I collected including content of /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+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 1464560] Re: Backport request: include PRD support for OpenPower kernels

[Mathieu Trudel-Lapierre]

One of the aspects of this is to ship opal-prd tools in the archive; for
that, we need uapi/asm/opal-prd.h (but it will also require the opal-prd
device to exist to be of any use) to be available on each of the
releases on which the opal-prd tools need to be shipped -- see bug
1467542.

-- 
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/1464560

Title:
  Backport request: include PRD support for OpenPower kernels

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Utopic:
  New
Status in linux source package in Vivid:
  New

Bug description:
  [Impact]

  Following up on patches that were skipped in bug 1439562, this request
  is for the PRD (Processor Runtime Diagnostics) support in the ppc64le
  kernel.

  [Fix]

  cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers
  7185795 powerpc/powernv: fix construction of opal PRD messages
  0d7cd85 powerpc/powernv: Add opal-prd channel
  594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface
  48c0615 powerpc/powernv: Merge common platform device initialisation

  $ git describe 0d7cd85 594fcb9 48c0615 7185795 cdf2bc1
  v4.1-rc3-86-g0d7cd85
  v4.1-rc3-85-g594fcb9
  v4.1-rc3-84-g48c0615
  v4.1-rc3-147-g7185795
  v4.1-rc3-148-gcdf2bc1

  Let me know if you need any info (or dependencies) for these.

  [Test Case]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+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 1469240] [NEW] Please ship dm-service-time in multipath-modules

[Mathieu Trudel-Lapierre]

Public bug reported:

multipath-tools 0.5.0 has changed the default path selector algorithm
from round-robin to service-time.

In the interest of properly handling the transition, I'd like for
multipath-modules to ship *both* dm-round-robin and dm-service-time, so
that we don't need to coordinate landing a kernel with multipath-tools,
and avoid breakage.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Chris J Arges (arges)
 Status: In Progress

-- 
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/1469240

Title:
  Please ship dm-service-time in multipath-modules

Status in linux package in Ubuntu:
  In Progress

Bug description:
  multipath-tools 0.5.0 has changed the default path selector algorithm
  from round-robin to service-time.

  In the interest of properly handling the transition, I'd like for
  multipath-modules to ship *both* dm-round-robin and dm-service-time,
  so that we don't need to coordinate landing a kernel with multipath-
  tools, and avoid breakage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469240/+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 1455268] Re: update-grub (grub-probe) during package installation on Cisco UCS B260 servers - Precise deployment fails with hwe-t kernel

[Mathieu Trudel-Lapierre]

For grub2 we're still waiting to see the result of running '/usr/sbin
/grub-probe --device /dev/sda1 --target=fs_uuid' under strace, so
setting the status to Incomplete..

** Changed in: grub2 (Ubuntu)
   Status: New = Incomplete

-- 
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/1455268

Title:
  update-grub (grub-probe) during package installation on Cisco UCS B260
  servers - Precise deployment fails with hwe-t kernel

Status in grub2 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In bug 1437475, deploying Precise with maas was failing with curtin
  error with generic ephemeral image.

  With hwe-t kernel it gets passed the curtin error.. However, grub
  looks to be stuck. Looking at the diff for install log minutes apart
  right before deployment gets marked as failed by maas, it looks to be
  retrying the last step:

  Last lines of curtin install log:
  ===
  Unpacking linux-generic-lts-trusty (from 
.../linux-generic-lts-trusty_3.13.0.52.45_amd64.deb) ...
  Setting up linux-image-3.13.0-52-generic (3.13.0-52.86~precise1) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.13.0-52-generic /boot/vmlinuz-3.13.0-52-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  update-initramfs: Generating /boot/initrd.img-3.13.0-52-generic
  df: Warning: cannot read table of mounted file systems: No such file or 
directory
  run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 
3.13.0-52-generic /boot/vmlinuz-3.13.0-52-generic
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Ignoring non-Xen Kernel on Xen domU host: vmlinuz-3.2.0-80-generic
  Found kernel: /boot/vmlinuz-3.13.0-52-generic
  Found kernel: /boot/memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-52-generic 
/boot/vmlinuz-3.13.0-52-generic
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  Found linux image: /boot/vmlinuz-3.2.0-80-generic
  Found initrd image: /boot/initrd.img-3.2.0-80-generic
  Found memtest86+ image: /boot/memtest86+.bin
  done
  Setting up linux-image-generic-lts-trusty (3.13.0.52.45) ...
  Setting up linux-headers-3.13.0-52 (3.13.0-52.86~precise1) ...
  Setting up linux-headers-3.13.0-52-generic (3.13.0-52.86~precise1) ...
  Setting up linux-headers-generic-lts-trusty (3.13.0.52.45) ...
  Setting up linux-generic-lts-trusty (3.13.0.52.45) ...
  Leaving 'diversion of /etc/init/ureadahead.conf to 
/etc/init/ureadahead.conf.disabled by cloud-init'
  8192+0 records in
  8192+0 records out
  8589934592 bytes (8.6 GB) copied, 6.10194 s, 1.4 GB/s
  Setting up swapspace version 1, size = 8388604 KiB
  no label, UUID=56f58ad7-bd54-4c17-be2f-893d3c70cd7e
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  Found linux image: /boot/vmlinuz-3.2.0-80-generic
  Found initrd image: /boot/initrd.img-3.2.0-80-generic
  Found memtest86+ image: /boot/memtest86+.bin
  done
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.13.0-52-generic
  Found initrd image: /boot/initrd.img-3.13.0-52-generic
  ===

  Diff output:
  ===
  ubuntu@pullman-01:~$ diff install.log var/log/curtin/install.log 
  219,221d218
   Generating grub.cfg ...
   Found linux image: /boot/vmlinuz-3.13.0-52-generic
   Found initrd image: /boot/initrd.img-3.13.0-52-generic
  ubuntu@pullman-01:~$ 
  ===

  I am attaching some logs I collected including content of /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1455268/+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 1443325] Re: ISST-LTE:Ubuntu15.04: task aio-stress:12277 blocked for more than 120 seconds.

[Mathieu Trudel-Lapierre]

Reassigning to the linux package; the kernel team would more likely know
if there is a fix available for this.

** Package changed: ubuntu = linux (Ubuntu)

-- 
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/1443325

Title:
  ISST-LTE:Ubuntu15.04: task aio-stress:12277 blocked for more than 120
  seconds.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13 01:29:44 
==
  Defect Description:
  ===

  I am having one ubuntu 15.04 LE lpar running with regression
  run(BASE/IO/TCP). After some hours of run i was not able to get
  virtual terminal of lpar but i am able to login via ssh. I did ssh and
  i saw these stack traces in dmesg:

  [14889.385371] blk_update_request: critical target error, dev dm-10, sector 
13842352
  [14889.385389] dm-16: WRITE SAME failed. Manually zeroing.
  [16080.244960] INFO: task aio-stress:12275 blocked for more than 120 seconds.
  [16080.244976]   Not tainted 3.19.0-12-generic #12-Ubuntu
  [16080.244979] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [16080.244983] aio-stress  D 3fff7e420818 0 12275  12092 
0x0004
  [16080.244985] Call Trace:
  [16080.244989] [c007704633f0] [c0015a4c] __switch_to+0x1fc/0x350
  [16080.244992] [c00770463440] [c0a3601c] __schedule+0x37c/0x8d0
  [16080.244994] [c00770463670] [c0a3a8b4] 
schedule_timeout+0x254/0x2f0
  [16080.244996] [c00770463760] [c0a377dc] 
wait_for_common+0xec/0x240
  [16080.244998] [c007704637e0] [c02ff1c8] 
writeback_inodes_sb_nr+0xb8/0xe0
  [16080.245000] [c00770463880] [c02ffa78] 
try_to_writeback_inodes_sb_nr+0x98/0xd0
  [16080.245002] [c007704638c0] [c03774bc] 
ext4_nonda_switch+0xdc/0xf0
  [16080.245004] [c00770463900] [c037e340] 
ext4_da_write_begin+0x90/0x3d0
  [16080.245006] [c007704639c0] [c02134f4] 
generic_perform_write+0xf4/0x280
  [16080.245008] [c00770463a60] [c02159e0] 
__generic_file_write_iter+0x2a0/0x430
  [16080.245009] [c00770463ac0] [c0371428] 
ext4_file_write_iter+0x118/0x480
  [16080.245011] [c00770463b80] [c0329c78] aio_run_iocb+0x268/0x450
  [16080.245013] [c00770463ce0] [c032afc4] do_io_submit+0x294/0x670
  [16080.245015] [c00770463e30] [c0009258] syscall_exit+0x0/0x98
  [16080.245017] INFO: task aio-stress:12276 blocked for more than 120 seconds.
  [16080.245022]   Not tainted 3.19.0-12-generic #12-Ubuntu
  [16080.245025] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.

  
  I am running IO regression run from last many weeks but i have not seen this 
issue in any previous kernel. 

  root@riverlp1:~# cat /etc/issue
  Ubuntu Vivid Vervet (development branch) \n \l

  
  root@riverlp1:~# uname -a
  Linux riverlp1 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:54 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
  root@riverlp1:~#

  
  Contact Info: hemantkba...@in.ibm.com

  == Comment: #1 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13
  01:32:40 ==

  
  == Comment: #2 - Hemant Kumar hemantkba...@in.ibm.com - 2015-04-13 01:35:52 
==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443325/+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 1446064] Re: ISST-SAN: Filesystem converted into read only after interface failover

[Mathieu Trudel-Lapierre]

Reassigning to linux; this seems most likely to be a filesystem/ibmvfc
driver issue.

** Package changed: ubuntu = linux (Ubuntu)

-- 
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/1446064

Title:
  ISST-SAN: Filesystem converted into read only after interface failover

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0  ==
  I was running interface failover tests on the Storage Texan2 ( TMS9840). 
zop03-01 has disks coming from Texan2 via NIPV.

  Interface failover basically brings down a interface, so that other
  inetrfaces take over, waits for 10 min and then brings it back up.
  There are 4 interfaces on texan2.

  
  While the third one was brought down, the IO on zop03-01 was stopped. I was 
running tests to create directories and files on the FS which were created on 
the multipath disks. The tests suddenly started to fail when the interface 
failover happened on the 3rd interface.

  Now i see that when i login to the system everything is read only.

  root@zop03-01:~# touch abc
  touch: cannot touch ?abc?: Read-only file system
  root@zop03-01:~#

  
  root@zop03-01:~# lsb_release -sc; uname -m; uname -r
  vivid
  ppc64le
  3.19.0-9-generic

  
  root@zop03-01:~# less /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # file system mount point   type  options   dump  pass
  /dev/mapper/mpath10-part2 /   ext4errors=remount-ro 0   1
  /dev/mapper/mpath10-part3 noneswapsw  0   0
  kte:/kte/ktenfs soft,rw,nolock,auto,exec   0 0
  kte:/data   /datanfs soft,rw,nolock,auto,exec   0 0
  kte:/distros/distros nfs soft,rw,nolock,auto,exec   0 0
  kte:/images /imagesnfs soft,rw,nolock,auto,exec   0 0
  root@zop03-01:~# 

  
  root@zop03-01:~# df -lh
  Filesystem  Size  Used Avail Use% Mounted on
  udev7.5G 0  7.5G   0% /dev
  tmpfs   1.6G   38M  1.5G   3% /run
  /dev/sdah2   48G   29G   16G  65% /
  tmpfs   7.6G 0  7.6G   0% /dev/shm
  tmpfs   5.0M  128K  4.9M   3% /run/lock
  tmpfs   7.6G 0  7.6G   0% /sys/fs/cgroup
  tmpfs   1.6G 0  1.6G   0% /run/user/0
  root@zop03-01:~# 

  
  root@zop03-01:~# fsck.ext4 /dev/sdah2
  e2fsck 1.42.12 (29-Aug-2014)
  /dev/sdah2: recovering journal
  /dev/sdah2 contains a file system with errors, check forced.
  Pass 1: Checking inodes, blocks, and sizes
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information
  Free blocks count wrong (4957824, counted=5069276).
  Fixy? yes
  Free inodes count wrong (2952662, counted=2953167).
  Fixy? yes

  /dev/sdah2: * FILE SYSTEM WAS MODIFIED *
  /dev/sdah2: * REBOOT LINUX *
  /dev/sdah2: 186417/3139584 files (1.2% non-contiguous), 7488804/12558080 
blocks
  root@zop03-01:~# 
  =

  == Comment: #6  ==

  There is no issue now. System is all fine. But i can recreate it
  easily. If i startIO tests and parallelly start interface
  failover tests, it can be recreated.

  But i just dont want it to get into the same state. and you do an
  fsck, reboot solves the problem.

  We need to get into the root cause for why the system is going to bad
  state.

  
  == Comment: #8  ==

  Re-creating the issue with more details:

  The IO tests were running ( IO tests basically create directories and files 
on the FS).
  I started the interface failover tests. It basically fails the interface on 
the SAN subsystem and failsover to the next available interface.There are such 
4 interfaces available.The SAN is texan2.

  
  WHen the interface was failed, The IO halted for a moment, by that i mean:

  Created Directory /FS3-part1/test1 rc = 0 at 04/17/2015 12:24:05
  Created Directory /FS4-part1/test1 rc = 0 at 04/17/2015 12:24:05
  Created Directory /FS3-part2/test1 rc = 0 at 04/17/2015 12:24:05
  Created Directory /FS1-part3/test1 rc = 0 at 04/17/2015 12:24:05
  Created Directory /FS1-part1/test1 rc = 0 at 04/17/2015 12:24:06
  Created Directory /FS7-part1/test1 rc = 0 at 04/17/2015 12:24:07
  Created Directory /FS0-part2/test1 rc = 0 at 04/17/2015 12:24:08
  Created Directory /FS0-part1/test1 rc = 0 at 04/17/2015 12:24:08
  Created Directory /FS0-part3/test1 rc = 0 at 04/17/2015 12:24:09


  
  === Here it halted

  On the console, i was seeing messages like:

  root@zop03-01:~# [35488.779299] sd 4:0:0:5: [sdab] Command (2A) failed: 
transaction cancelled (200:600) flags: 0 fcp_rsp: 0, resid=0, scsi_status: 0
  [35488.779344] sd 4:0:0:5: 

[Kernel-packages] [Bug 1451378] Re: Network-manager fail to start on full duplex

[Mathieu Trudel-Lapierre]

Reassigning to Linux. NM is not responsible for negotiating duplex;
performance issues caused by this would probably warrant looking into
what the driver does.

** Package changed: network-manager (Ubuntu) = linux (Ubuntu)

-- 
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/1451378

Title:
  Network-manager fail to start on full duplex

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ dpkg -l network-manager
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersionArchitecture   
Description
  
+++-===-==-==-
  ii  network-manager 0.9.10.0-4ubuntu15 i386   network 
management framework (daemon and userspace tools)

  $ uname -a
  Linux 192-168-0-3 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:01 UTC 
2015 i686 i686 i686 GNU/Linux

  $ lspci | grep Ethernet
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

  #Driver in use:r8169

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/192--168--0--102--vg-root ro splash quiet libata.dma=0

  $ lspci 
  00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub 
(rev 02)
  00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated 
Graphics Controller (rev 02)
  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 01)
  00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 
(rev 01)
  00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #1 (rev 01)
  00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #2 (rev 01)
  00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #3 (rev 01)
  00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #4 (rev 01)
  00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI 
Controller (rev 01)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
  00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface 
Bridge (rev 01)
  00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller 
(rev 01)
  00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller 
[IDE mode] (rev 01)
  00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01)
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

  Info:On session Unity Network applet figure online but internet is slow on 
1Mbs to 0Mbs.
  Sometimes from applet set  enable/disable from many times to start normal but 
not allways have succed.
  Temporary i add on file on MetworkManager to solve this issue:
  $ cat /etc/NetworkManager/dispatcher.d/pre-up.d/01set_half
  #!/bin/sh -e
  # Script for setting halfduplex

  if [ -z $1 ]; then
  echo $0: error missing interface 12
  exit 2;
  fi

  /sbin/ethtool -s $1 duplex half speed 100

  My system is atom :
  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 28
  model name: Intel(R) Atom(TM) CPU  230   @ 1.60GHz
  stepping  : 2
  microcode : 0x218
  cpu MHz   : 1598.645
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 1
  apicid: 0
  initial apicid: 0
  fdiv_bug  : no
  f00f_bug  : no
  coma_bug  : no
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 10
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr 
pdcm movbe lahf_lm dtherm
  bugs  :
  bogomips  : 3197.29
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 32 bits physical, 48 bits virtual
  power management:

  processor : 1
  vendor_id : GenuineIntel
  cpu family: 6
  model : 28
  model name: Intel(R) Atom(TM) CPU  230   @ 1.60GHz
  stepping  : 2
  microcode : 0x218
  cpu MHz   : 1598.645
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 1
  apicid: 1
  initial apicid: 1
  fdiv_bug  : no
  f00f_bug  : no
  coma_bug  : no
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 10
  wp: yes
  

[Kernel-packages] [Bug 1409102] Re: WiFi is slower on Ubuntu than Windows.

[Mathieu Trudel-Lapierre]

Given that this is reportedly fixed by updating a driver, it's not a bug
in NetworkManager (so I'm removing the task, we don't need to track it
there).

Also, as a further data point, I wonder how running a low-latency might
affect things like wifi performance. I think it's not impossible that it
has a bit of an impact on it as well.

** No longer affects: network-manager-applet

-- 
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/1409102

Title:
  WiFi is slower on Ubuntu than Windows.

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My wireless internet connection, no matter what dongle I use as an
  interface, is always slower and I have more DNS issues unable to find
  website than what I ever get on even the Windows 10 Developer Beta
  running on my same machine within a different hard disk.

  Using Ubuntu, my internet connection will often slow to a screeching
  halt, videos fail to stream properly from popular sites a'la Youtube
  or such, I get DNS issues reported by Chrome and Firefox in which my
  current connection cannot find a website although connected, and
  last but not least, my connection will cut in and out intermittently
  though I have set the MAC address of my router as the BSSID. Windows
  10 does not give me these issues, and has been more stable
  connectivity-wise from day one of the first public beta of Windows 10.

  Something is terribly wrong, and I do not know what. I have tried what
  seems like everything to fix the problem, and I still have the same
  issues. If Ubuntu cannot support common wireless devices and drivers,
  why would the general public want to prefer Ubuntu over something more
  stable?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libnm-gtk-common 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-28.38-lowlatency 3.16.7-ckt1
  Uname: Linux 3.16.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  9 14:34:48 2015
  Dependencies:
   
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-08 (62 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.11  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1f1c9b8fa-dda4-443c-9143-093770dd40a4   
802-3-ethernet1420688531   Wed 07 Jan 2015 10:42:11 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/2
   KCS96 1   79387fc2-a0c8-452c-8dd3-a632947dbe73   
802-11-wireless   1420831940   Fri 09 Jan 2015 02:32:20 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/1
   HTC One Network   a509d61f-6a95-438f-b66f-8fde34f8e1ed   bluetooth   
  0never  nono 
/org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/3  
   2C:8A:72:02:18:B5 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1409102/+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 1409102] Re: WiFi is slower on Ubuntu than Windows.

[Mathieu Trudel-Lapierre]

I meant ubuntu-reviewers, above.

** Tags removed: patch

-- 
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/1409102

Title:
  WiFi is slower on Ubuntu than Windows.

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My wireless internet connection, no matter what dongle I use as an
  interface, is always slower and I have more DNS issues unable to find
  website than what I ever get on even the Windows 10 Developer Beta
  running on my same machine within a different hard disk.

  Using Ubuntu, my internet connection will often slow to a screeching
  halt, videos fail to stream properly from popular sites a'la Youtube
  or such, I get DNS issues reported by Chrome and Firefox in which my
  current connection cannot find a website although connected, and
  last but not least, my connection will cut in and out intermittently
  though I have set the MAC address of my router as the BSSID. Windows
  10 does not give me these issues, and has been more stable
  connectivity-wise from day one of the first public beta of Windows 10.

  Something is terribly wrong, and I do not know what. I have tried what
  seems like everything to fix the problem, and I still have the same
  issues. If Ubuntu cannot support common wireless devices and drivers,
  why would the general public want to prefer Ubuntu over something more
  stable?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libnm-gtk-common 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-28.38-lowlatency 3.16.7-ckt1
  Uname: Linux 3.16.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  9 14:34:48 2015
  Dependencies:
   
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-08 (62 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.11  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1f1c9b8fa-dda4-443c-9143-093770dd40a4   
802-3-ethernet1420688531   Wed 07 Jan 2015 10:42:11 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/2
   KCS96 1   79387fc2-a0c8-452c-8dd3-a632947dbe73   
802-11-wireless   1420831940   Fri 09 Jan 2015 02:32:20 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/1
   HTC One Network   a509d61f-6a95-438f-b66f-8fde34f8e1ed   bluetooth   
  0never  nono 
/org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/3  
   2C:8A:72:02:18:B5 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1409102/+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 1409102] Re: WiFi is slower on Ubuntu than Windows.

[Mathieu Trudel-Lapierre]

Also, since the attached files aren't patches but rather deb packages,
I'll go ahead and undo the patch tag and flags.

Could you try and communicate with Bogdan Koval (bodyakov), and see if
you guys could come up with a proper patch in diff format for the
changes required? Then attach it here again and subscribe ubuntu-
sponsors again.

-- 
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/1409102

Title:
  WiFi is slower on Ubuntu than Windows.

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My wireless internet connection, no matter what dongle I use as an
  interface, is always slower and I have more DNS issues unable to find
  website than what I ever get on even the Windows 10 Developer Beta
  running on my same machine within a different hard disk.

  Using Ubuntu, my internet connection will often slow to a screeching
  halt, videos fail to stream properly from popular sites a'la Youtube
  or such, I get DNS issues reported by Chrome and Firefox in which my
  current connection cannot find a website although connected, and
  last but not least, my connection will cut in and out intermittently
  though I have set the MAC address of my router as the BSSID. Windows
  10 does not give me these issues, and has been more stable
  connectivity-wise from day one of the first public beta of Windows 10.

  Something is terribly wrong, and I do not know what. I have tried what
  seems like everything to fix the problem, and I still have the same
  issues. If Ubuntu cannot support common wireless devices and drivers,
  why would the general public want to prefer Ubuntu over something more
  stable?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libnm-gtk-common 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-28.38-lowlatency 3.16.7-ckt1
  Uname: Linux 3.16.0-28-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  9 14:34:48 2015
  Dependencies:
   
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-08 (62 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.11  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1f1c9b8fa-dda4-443c-9143-093770dd40a4   
802-3-ethernet1420688531   Wed 07 Jan 2015 10:42:11 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/2
   KCS96 1   79387fc2-a0c8-452c-8dd3-a632947dbe73   
802-11-wireless   1420831940   Fri 09 Jan 2015 02:32:20 PM ESTyes   
no /org/freedesktop/NetworkManager/Settings/1
   HTC One Network   a509d61f-6a95-438f-b66f-8fde34f8e1ed   bluetooth   
  0never  nono 
/org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/3  
   2C:8A:72:02:18:B5 bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1409102/+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 1359689] Re: cryptsetup password prompt not shown

[Mathieu Trudel-Lapierre]

** Also affects: linux (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
   Status: Triaged

** Changed in: linux (Ubuntu Utopic)
   Status: New = Triaged

** Changed in: linux (Ubuntu Utopic)
   Importance: Undecided = Critical

-- 
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/1359689

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1162781] Re: bluez package out of date, 5.23 is available in debian sid/jessie

[Mathieu Trudel-Lapierre]

Yes, the BlueZ 5 migration is still being worked on, and targetted for
Vivid. PulseAudio 6 was part of the issue, but wasn't the only thing
blocking the migration. There are many pieces that need to be updated or
confirmed to work (blueman, indicator-blueooth, gnome-bluetooth, to name
a few). The blueprint linked above will get updated as work gets done.
There is also coordination that needs to happen with the Ubuntu Touch
teams to not interfere with their releases.

Unassigning myself, given that I'm not the only person working on this.

** Changed in: bluez (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)

-- 
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/1162781

Title:
  bluez package out of date, 5.23 is available in debian sid/jessie

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Looks like there have been a lot of improvements to bluez since the
  4.x series. Would be nice to get the latest release pulled in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+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 1177424] Re: [Touch] no permission to access bluez on dbus

[Mathieu Trudel-Lapierre]

There are no changes required to bluez for pulseaudio support, things
already work on the desktop.

Furthermore, given that we've since had multiple reports of bluetooth
headsets working properly on Touch, I'll close this as Invalid -- it
probably didn't work before, but it works now, even if we don't know
what was the difference.

** Changed in: bluez (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)

** Changed in: bluez (Ubuntu)
   Status: Confirmed = Invalid

-- 
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/1177424

Title:
  [Touch] no permission to access bluez on dbus

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm trying today's touch preview image, trying to get bluetooth
  headsets working. After installing the package (see bug 1177421 ),
  PulseAudio gets the following error message:

  bluetooth-util.c: org.bluez.Manager.GetProperties() failed:
  org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2
  matched rules; type=method_call, sender=:1.3 (uid=32011 pid=260
  comm=pulseaudio --start --log-target=syslog )
  interface=org.bluez.Manager member=GetProperties error
  name=(unset) requested_reply=0 destination=org.bluez (uid=0
  pid=99 comm=/usr/sbin/bluetoothd )

  ...it looks like there is some permission error as pulseaudio is not
  allowed to talk to the bluez daemon over D-Bus. As a result,
  pulseaudio does not detect the headset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1177424/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Mathieu Trudel-Lapierre]

I see it was fixed in utopic for d-i already; are we good on vivid too?

-- 
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/1386490

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1386490/+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 994931] Re: Altering use_tempaddr drops all IPv6 addresses

[Mathieu Trudel-Lapierre]

I can't exactly test that IPv6 is fine in general with this, but it
doesn't appear to have regressed on 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/994931

Title:
  Altering use_tempaddr drops all IPv6 addresses

Status in The Linux Kernel:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Utopic:
  Invalid

Bug description:
  $ uname -a
  Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 
UTC 2012 i686 i686 i386 GNU/Linux

  $ sysctl net.ipv6.conf.eth2.use_tempaddr
  net.ipv6.conf.eth2.use_tempaddr = 2
  # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)

  # Add a static IPv6 address:
  $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2

  # Verify that it has been set up, and that a temporary address and a SLAAC 
address also exist:
  $ ip -6 addr list dev eth2
  4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
  inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary 
dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic 
 valid_lft 86393sec preferred_lft 14393sec
  inet6 2001:470:9321:f003::1122/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link 
 valid_lft forever preferred_lft forever

  # Disable RFC 4941 temporary addresses:
  $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0
  net.ipv6.conf.eth2.use_tempaddr = 0

  $ ip -6 addr list dev eth2
  4: eth2: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
  inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative 
 valid_lft forever preferred_lft forever

  I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed,
  including statically-configured and non-temporary SLAAC-configured
  addresses.  (The link-local address reappears quickly but the
  'tentative' flag indicates that it has been newly re-added.  The SLAAC
  address reappears after a slightly longer interval as the kernel
  continues to undergo SLAAC, but the static address is gone forever
  unless manually reinstated.)

  The same happens if use_tempaddr is changed from 0 back to 2.

  The expected outcome is that only temporary addresses are affected by a 
change to use_tempaddr.
  --- 
  AcpiTables:
   
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 May  5 03:53 seq
   crw-rw---T 1 root audio 116, 33 May  5 03:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  DistroRelease: Ubuntu 12.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro  
console=hvc0
  ProcModules:
   lp 17455 0 - Live 0x
   parport 40930 1 lp, Live 0x
   xenfs 17877 1 - Live 0x
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994931/+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 1049266] Re: pairing Wii Balance Board not supported in 4.101

[Mathieu Trudel-Lapierre]

It's not about dragging feet, really just that updating to 5.0 isn't so
simple, and requires careful coordination to avoid breaking more things
that get fixed by the update. BlueZ 5 is being looked at by many teams
right now, and we're still working on the transition.

This looks like a great, simple patch that someone looking to start
working on Ubuntu development could easily put together in the package
and submit for review and sponsored upload. I tagged this bitesize.

** Tags added: bitesize

** Changed in: bluez (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)

-- 
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/1049266

Title:
  pairing Wii Balance Board not supported in 4.101

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  The following code in 4.101 checks whether a device should receive the
  special Wii passkey:

vendor = btd_device_get_vendor(device);
product = btd_device_get_product(device);

device_get_name(device, name, sizeof(name));
name[sizeof(name) - 1] = 0;

if (g_str_equal(name, Nintendo RVL-CNT-01) ||
(vendor == 0x057e  product == 0x0306)) {

  However, this does not work for the Wii Balance Board, which reports
  its name as Nintendo RVL-WBC-01. I'd suggest to add a second
  comparison with this string.

  P.S. I haven't found any working upstream bug tracker, which is why I
  report this here, hoping that somebody from upstream will pick it up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1049266/+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 1412419] Re: Visibility issues on rtm

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1419874 ***
https://bugs.launchpad.net/bugs/1419874

marking as a duplicate of bug 1419874

** This bug has been marked a duplicate of bug 1419874
   krillin bluetooth discoverability enabled on boot

-- 
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/1412419

Title:
  Visibility issues on rtm

Status in bluez package in Ubuntu:
  New

Bug description:
  PRE_REQUISITES:
  Two phone with rtm on

  STEPS:
  1. On mako goto settings bluetooth
  2. On Krillin goto settings bluetooth
  3. Both phones should now discover each other
  4. Close both settings app
  5. Bootstrap Flash one phone so it has no record of the other
  6. Now open its settings bluetooth app
  7. It now discovers the other phone still.

  EXPECTATION:
  I only expect visibility to happen while the bt page is open.

  ACTUAL:
  It seems that once triggered nothing stops the visibility, the same may be 
true of vivid but I have only test this on rtm

  POSSIBLE SOLUTION:
  Have a toggle switch available in the indicator like there is on the desktop 
possibly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1412419/+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 1359689] Re: cryptsetup password prompt not shown

[Mathieu Trudel-Lapierre]

Esokrates, could you try to boot your system after adding
'plymouth:debug' to the kernel command line in grub; and attaching
/var/log/plymouth-debug.log; first making sure it doesn't include your
passphrase for the disk encryption? If that doesn't trigger the bug, you
may need to edit /etc/default/grub to add 'plymouth:debug' there and
reconfigure grub.

So, after testing this for a while it looks to me like this is in fact a
problem with drm, at least on radeon, and likely on nouveau as well. On
my radeon system, it appears that plymouth tries to start the drm
renderer and fails because it can't find the right encoder, or CRTC, to
notice that the screen is lit -- that is, unless it was already lit and
updated as such in drm by going through the grub menu. It asks libdrm
for the available encoders, but the currently selected encoder for the
connector remains 0; and if I bypass this and have it check the encoder
for it's selected crtc, that value is also left at 0.

It seems like upstream linux commit
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/drm_crtc.c?id=abd69c55dd8f1f71b33b8c6165217f4329db8f25
should help, and in fact if I use the mainline kernel 3.19 rc1, things
appear to be working properly; so I've opened a linux task for this
issue.

-- 
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/1359689

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1359689] Re: cryptsetup password prompt not shown

[Mathieu Trudel-Lapierre]

** Changed in: plymouth (Ubuntu)
   Status: Incomplete = Triaged

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1359689

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689/+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 1413363] Re: bluetooth speaker and suspension issue

[Mathieu Trudel-Lapierre]

In that case we'll need the logs from ubuntu-system-settings; on re-
connection there should be a message, something like Host down or
Connection refused. Perhaps there is something extra we need to do in
this particular case for the headset to be happy with re-connecting.

-- 
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/1413363

Title:
  bluetooth speaker and suspension issue

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Open settings bluetooth
  2. Turn on your blue tooth speaker
  3. Pair the speaker
  4. Open the music app
  5. Play music
  6. Pause the music
  7. Let the phone suspend
  8. After a while it goes into deep sleep and the speaker disconnects
  9. Wake the phone press the play button

  EXPECTED:
  I expected the music to play out of the bluetooth speaker

  ACTUAL:
  A long pause, then a click then the music plays from the internal speaker.  
You can no longer get the music to play  from the bluetooth speaker.

  Things I've tried:
  Reboot the phone re connect to the bt speaker music still plays from the loud 
speaker on the phone.
  Turned off the speaker, restarted it still plays through the Loud speaker on 
the phone

  WORK AROUND:
  Forget the connection. Re pair the device now press play now it works as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1413363/+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 1416001] Re: ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

[Mathieu Trudel-Lapierre]

We're reportedly already bulding the other ibmv* modules as builtin, so
I'm opening a task for linux so the Kernel Team can weigh in making this
one builtin as well, or if it would be preferable to just keep it in
initrd.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1416001

Title:
  ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #1 - Hemant Kumar hemantkba...@in.ibm.com - 2015-01-20 11:27:19 
==
  Defect Description:
  ---

  I am trying to install ubuntu15.04LE on multipath disks, but while
  installtion installer is not able to find multipath disks.

  For enabling multipath support is have set disk-
  detect/multipath/enable=true parameter in grub menu while
  installation.

  Here is the error which i am getting:

lqqu [!] Detect disks tqqqk
x x
x No disk drive was detected. If you know the name of the driver needed   x
x by your disk drive, you can select it from the list.x
x x
x Driver needed for your disk drive:  x
x x
x continue with no disk drive x
x login to iSCSI targets  x
x 3w-9xxx  a  x
x 3w-sas   a  x
x 3w-  a  x
x DAC960   a  x
x a100u2w  a  x
x aacraid  a  x
x aic79xx  a  x
x aic7xxx x
x x
x Go Back   x
x x
mqj

  Tab moves; Space selects; Enter activates buttons

  
  I have tried installing other distros and the installer is able to find the 
disks but ubuntu installer is giving error.

  lpar is at installation prompt, please have a look.

  

  == Comment: #10 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:22:52 ==
  (In reply to comment #6)
   This seems to be a more fundamental error than multipath; the installer
   cannot find any storage at all. I expect you will see the same error w/o the
   above mutlipath parameter.  Can you try this and see if that is true?

  I tried the Ubuntu install without multipath enabled and still hit the
  issue. So it is not related to multipath. On the Detect disks
  screen, I scrolled through the list of available drivers and did not
  find ibmvfc.

   So the installer is assuming, since it finds no storage, that you have some
   adapter installed for which it has no driver.  I don't know if that's true
   or not, but if you can identify the required driver for the adapter you are
   targeting, that would be helpful.  Any other information about the adapter
   hardware would be helpful too.

  The Ubuntu installer does not have the ibmvfc module.

  ~ # uname -a
  Linux highlp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 
ppc64le GNU/Linux
  ~ # lsmod
  Module  Size  Used by
  usb_storage71250  0 
  ~ # modinfo ibmvfc
  modinfo: ERROR: Module ibmvfc not found.

  
  == Comment: #12 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:27:44 ==
  This is from a separate lpar, used to get the ibmvfc info for a running 
Ubuntu 15.04 system.

  (see attachment: modinfo ibmvfc)

  == Comment: #17 - David Heller helle...@us.ibm.com - 2015-01-28 14:13:46 ==
  So clearly ibmvfc is not a builtin on the ppc64el kernel.

  After poking around some more I can verify the ibmvfc.ko is missing
  from the installer initrd files -- both the netboot one and the one on
  the ISO.  I did find one installed system where the module is present
  so it's around but just not in the installer.

  So, I think the next step is to mirror this and request ibmvfc.ko be
  added to the installer.  The other 

[Kernel-packages] [Bug 1409750] Re: grub2/kernel EFI firware size interface

[Mathieu Trudel-Lapierre]

This change is now in vivid as well:
 grub2 (2.02~beta2-21) unstable; urgency=medium
 .
   [ Mathieu Trudel-Lapierre ]
   * Fix overlap check in check_blocklists for load_env (backported patch
 from upstream commit 1f6af2a9; LP: #1311247).
 .
   [ Steve McIntyre ]
   * Add support for running a 64-bit Linux kernel on a 32-bit EFI (closes:
 #775202).
 .
   [ Colin Watson ]
   * Use mtmsr rather than mtmsrd in ppc64el-disable-vsx.patch, since the
 VSX Available bit is in the lower half of the MSR anyway, and mtmsrd
 faults on 32-bit systems (closes: #776400).

** Changed in: grub2 (Ubuntu)
   Status: Triaged = Fix Released

-- 
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/1409750

Title:
  grub2/kernel EFI firware size interface

Status in grub2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Seems that grub2 needs the ability to size the EFI implementation it
  is running on.  This is being exposed via the kernel in a patch queued
  for v3.20 (http://comments.gmane.org/gmane.linux.kernel.efi/5229).
  This is being taken early in debian under debian #775191 (linux) and
  debian #775202 (grub2) (https://bugs.debian.org/775191,
  https://bugs.debian.org/775202).  Additional discussion is available
  here:  http://blog.einval.com/2015/01/11#Jessie-EFI_5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1409750/+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 1413363] Re: bluetooth speaker and suspension issue

[Mathieu Trudel-Lapierre]

Could you also try to re-pair the speaker by pressing a button after the
system is resumed?

** Package changed: bluez-utils (Ubuntu) = bluez (Ubuntu)

** Changed in: bluez (Ubuntu)
   Status: New = Incomplete

-- 
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/1413363

Title:
  bluetooth speaker and suspension issue

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Open settings bluetooth
  2. Turn on your blue tooth speaker
  3. Pair the speaker
  4. Open the music app
  5. Play music
  6. Pause the music
  7. Let the phone suspend
  8. After a while it goes into deep sleep and the speaker disconnects
  9. Wake the phone press the play button

  EXPECTED:
  I expected the music to play out of the bluetooth speaker

  ACTUAL:
  A long pause, then a click then the music plays from the internal speaker.  
You can no longer get the music to play  from the bluetooth speaker.

  Things I've tried:
  Reboot the phone re connect to the bt speaker music still plays from the loud 
speaker on the phone.
  Turned off the speaker, restarted it still plays through the Loud speaker on 
the phone

  WORK AROUND:
  Forget the connection. Re pair the device now press play now it works as 
expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1413363/+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 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

[Mathieu Trudel-Lapierre]

It looks like any moving of a file which comes from the read-only
underlying filesystem. It doesn't behave the same when one deletes a
file instead of moving.

It seems like it's probably a bug in overlayfs, so I'm adding a task for
linux so the kernel team can take a look.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  New
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

[Mathieu Trudel-Lapierre]

ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2119 F pulseaudio
CasperVersion: 1.347
DistroRelease: Ubuntu 15.04
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150116)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: ubiquity
PackageArchitecture: amd64
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash --
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.18.0-9-generic N/A
 linux-backports-modules-3.18.0-9-generic  N/A
 linux-firmware1.140
RfKill:
 
Tags:  vivid vivid ubiquity-2.21.4 ubuntu
Uname: Linux 3.18.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20140531_171129-lamiak
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-utopic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20140531_171129-lamiak:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-utopic
dmi.sys.vendor: QEMU


** Tags added: apport-collected ubiquity-2.21.4

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1408495] AlsaInfo.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300046/+files/AlsaInfo.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] CurrentDmesg.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300050/+files/CurrentDmesg.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] CRDA.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1408495/+attachment/4300048/+files/CRDA.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Dependencies.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300051/+files/Dependencies.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Casper.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: Casper.txt
   https://bugs.launchpad.net/bugs/1408495/+attachment/4300049/+files/Casper.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcCpuinfo.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300055/+files/ProcCpuinfo.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] BootDmesg.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300047/+files/BootDmesg.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Lspci.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1408495/+attachment/4300052/+files/Lspci.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityDebug.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UbiquityDebug.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300058/+files/UbiquityDebug.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityDm.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UbiquityDm.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300059/+files/UbiquityDm.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UdevDb.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1408495/+attachment/4300062/+files/UdevDb.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcInterrupts.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300056/+files/ProcInterrupts.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquitySyslog.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UbiquitySyslog.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300061/+files/UbiquitySyslog.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UpstartUbiquity.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UpstartUbiquity.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300064/+files/UpstartUbiquity.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UbiquityPartman.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UbiquityPartman.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300060/+files/UbiquityPartman.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] UdevLog.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300063/+files/UdevLog.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] ProcModules.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300057/+files/ProcModules.txt

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] WifiSyslog.txt

[Mathieu Trudel-Lapierre]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1408495/+attachment/4300065/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu Vivid)
   Status: Incomplete = Confirmed

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1410480 ***
https://bugs.launchpad.net/bugs/1410480

This seems like a duplicate of bug 1410480.

** This bug has been marked a duplicate of bug 1410480
   overlayfs v1: renaming existing file uses chardev whiteout (should be 
symlink)

-- 
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/1408495

Title:
  Ubiquity crashes prior to keyboard configuration in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in ubiquity source package in Vivid:
  Confirmed

Bug description:
  As best as I can tell, if anything other than a US keyboard layout is
  selected from the boot menu, ubi-console-setup will crash prior to the
  keyboard configuration. The dialogue displayed says:

  ubi-console-setup failed with exit code 2. Further information
  maybe found in /var/log/syslog.

  There are the relevant lines from /var/log/syslog:

  Jan  7 23:30:39 ubuntu ubiquity: 
/var/lib/dpkg/info/keyboard-configuration.config: 34160: .: Can't open 
/etc/default/keyboard
  Jan  7 23:30:39 ubuntu ubiquity[2323]: log-output -t ubiquity setxkbmap 
-layout gb -option
  Jan  7 23:30:39 ubuntu ubiquity[2323]: debconffilter_done: ubi-console-setup 
(current: ubi-console-setup)
  Jan  7 23:30:39 ubuntu ubiquity[2323]: dbfilter_handle_status: 
('ubi-console-setup', 2)

  The dialogue has 3 buttons, Quit, Continue Anyway and Try Again. If
  you choose Try Again it is possible to complete the install. If you
  choose Continue Anyway the installer will progress and eventually
  crash completely as which point apport was able to harvest the
  attached logs.

  
  WORKAROUND: After you see the ubi-console-setup crashed dialog, open a 
terminal and do

sudo rm /etc/default/keyboard
sudo mv /etc/default/keyboard.pre-ubiquity /etc/default/keyboard

  then click Continue anyway in the dialog. This should prevent the
  crash at the end of installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.2
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.347
  Date: Wed Jan  7 23:36:41 2015
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150107)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408495/+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 1400827] Re: BlueZ crashing when connecting input channel to a keyboard

[Mathieu Trudel-Lapierre]

** 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/1400827

Title:
  BlueZ crashing when connecting input channel to a keyboard

Status in the base for Ubuntu mobile products:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu RTM:
  In Progress

Bug description:
  On the phone, pairing a keyboard makes BlueZ crash when connecting the
  input channel (either by calling org.bluez.Input.Connect() on D-Bus or
  by pressing some keys on the keyboard to make the keyboard open the
  channel.

  In order to pair a keyboard with an Ubuntu phone, you need to either
  apply this branch to ubuntu-system-settings [1] or do it manually with
  bluez-simple-agent and dbus-send/qdbus.

  
  [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1400827/+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 1400827] Re: BlueZ crashing when connecting input channel to a keyboard

[Mathieu Trudel-Lapierre]

** Changed in: bluez (Ubuntu)
   Status: New = In Progress

** Changed in: bluez (Ubuntu)
   Importance: Undecided = High

** Also affects: bluez (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: bluez (Ubuntu RTM)
   Status: New = In Progress

** Changed in: bluez (Ubuntu RTM)
   Importance: Undecided = High

** Changed in: bluez (Ubuntu RTM)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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/1400827

Title:
  BlueZ crashing when connecting input channel to a keyboard

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu RTM:
  In Progress

Bug description:
  On the phone, pairing a keyboard makes BlueZ crash when connecting the
  input channel (either by calling org.bluez.Input.Connect() on D-Bus or
  by pressing some keys on the keyboard to make the keyboard open the
  channel.

  In order to pair a keyboard with an Ubuntu phone, you need to either
  apply this branch to ubuntu-system-settings [1] or do it manually with
  bluez-simple-agent and dbus-send/qdbus.

  
  [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+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 1400827] Re: BlueZ crashing when connecting input channel to a keyboard

[Mathieu Trudel-Lapierre]

This still looks like a bug that should have been fixed by bluez
4.101-0ubuntu21; could you please confirm that this is indeed the
version of bluez that was installed, and running, on the system when you
got the crash?

I'm saying fixed, because it's been tested on some hardware,
specifically for armhf and without adverse effects on amd64 or other
architectures, but it doesn't mean it's necessary the proper, best
solution on all hardware.

-- 
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/1400827

Title:
  BlueZ crashing when connecting input channel to a keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  On the phone, pairing a keyboard makes BlueZ crash when connecting the
  input channel (either by calling org.bluez.Input.Connect() on D-Bus or
  by pressing some keys on the keyboard to make the keyboard open the
  channel.

  In order to pair a keyboard with an Ubuntu phone, you need to either
  apply this branch to ubuntu-system-settings [1] or do it manually with
  bluez-simple-agent and dbus-send/qdbus.

  
  [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+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 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working

[Mathieu Trudel-Lapierre]

There were mentions of it happening after a resume from hibernate. Teo,
could you please confirm whether or not you've used hibernate again and
if it has triggered the bug? You mention later that it happens randomly,
but I just want to make it very certain that it can't be reliably
triggered by hibernation... rather than assuming anything.

To pinpoint this to an update that could have caused this issue, it
would be useful to have /var/log/apt/history.log for 2014-08-05 and a
few days earlier, if you still have that; along with if you remember
when the computer had last been rebooted before you did last reboot you
mention in this bug report. I realize this is a long time ago, but if
you remember, or if you usually shut down your computer every few days,
etc. then it can help figuring out from the apt history log whether a
specific package was updated around the same time and could be the cause
of the issue, or be a trigger for a BIOS bug.

Meaningful packages could still be acpi-support, linux, etc...

Thanks!

-- 
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/1353129

Title:
  [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
  stopped working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All of a sudden, the volume keys from the keyboard have stopped
  working.

  The volume control on the top right corner of the screen does work if
  used with the mouse.

  I have both an external usb keyboard with dedicated volume + and -
  keys, and the builtin laptop keyboard where the volume +/-keys are the
  combination of the Fn key plus the up/down arrows.

  All these used to work up to a few minutes ago. Now none of them works.
  I think they stopped working with the last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2303 F pulseaudio
   /dev/snd/pcmC0D0p:   teo2303 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:13:35 2014
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (298 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+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 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings

[Mathieu Trudel-Lapierre]

Reassigned to ubuntu-system-settings; this is an issue in how the
operations are selected for connection and disconnection.

** Package changed: bluez (Ubuntu) = ubuntu-system-settings (Ubuntu)

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = In Progress

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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/1369964

Title:
  Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth
  settings

Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress

Bug description:
  ENVIRONMENT:
  krillin ubuntu-rtm/14.09-proposed build 44.
  BQ Avrha Altavoz Vivaldi Bluetooth speaker:
  http://www.bqreaders.com/gb/accessories-aquaris.html

  SUMMARY:
  Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings

  STEPS:
  1) Turn on speaker so that it is in pairing mode
  2) On Ubuntu device pair with the speaker
  3) Play music through the speaker
  4) From Bluetooth settings, select the speaker device and press Disconnect 
button

  EXPECTED RESULT:
  The device should disconnect.

  ACTUAL RESULT:
  The disconnect button has no effect. Music continues to play through the 
Bluetooth speaker.

  For other Bluetooth devices the Disconnect button works. This bug is
  specific to this particular device.

  ADDITIONAL INFO:

  hcitool inq:
  12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414

  hcitool info:

   BD Address: 12:1F:83:05:03:B4
   Device Name: Avrha Vivaldi
   LMP Version: 2.0 (0x3) LMP Subversion: 0x2
   Manufacturer: Accel Semiconductor Ltd. (74)
   Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80
3-slot packets 5-slot packets encryption slot offset
timing accuracy role switch hold mode sniff mode
RSSI channel quality SCO link HV2 packets
HV3 packets CVSD power control transparent SCO
EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan
interlaced pscan inquiry with RSSI 3-slot EDR ACL
5-slot EDR ACL extended features
   Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1369964/+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 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)

[Mathieu Trudel-Lapierre]

I uploaded the fixes for both gnome-bluetooth and bluez to trusty;
pending review by the SRU team.

** Description changed:

+ [Impact]
+ 
+  * Fixes issues connecting bluetooth devices using SSP (Simple Secure
+ Pairing); which does include many newer bluetooth devices, especially
+ keyboards.
+ 
+ [Test Case]
+ 
+  * Try to connect a bluetooth keyboard using the wizard; especially one
+ of the following models:
+ 
+ Logitech Bluetooth Keyboard K760
+ Logitech Bluetooth Keyboard K810
+ HP Bluetooth Keyboard K4000
+ 
+ [Regression Potential]
+ 
+  * It must be ensured that keyboards that could already be paired
+ successfully still work properly; specifically, especially for keyboards
+ but for any other devices, that pairing still works despite changes to
+ the SSP code.
+ 
+ [Other Info]
+ 
+ 
+ ---
+ 
  When I try to connect my bluetooth keyboard using bluetooth-wizard, it
  ever fails:
  
  ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760'
  failed: Authentication Failed
  
  This keyboard works fine with another computer under ubuntu 11.04.
  This keyboard works fine with this computer and Windows 7 (arghhh).
  This computer ubuntu 12.04 works fine with my bluetooth mouse.
  
  I can attach manually this keyboard to this computer using :
  
  sudo hidd --search
  
  My computer is a Samsung 305U1A
  My bluetooth interface is :
  
  Bus 003 Device 002: ID 0a5c:219c Broadcom Corp.

-- 
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/1035431

Title:
  bluetooh-wizard failed to connect to a keyboard(logitech)

Status in GNOME Bluetooth:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in “bluez” package in Ubuntu:
  Fix Released
Status in “gnome-bluetooth” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Triaged
Status in “gnome-bluetooth” source package in Precise:
  Triaged
Status in “bluez” source package in Trusty:
  In Progress
Status in “gnome-bluetooth” source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * Fixes issues connecting bluetooth devices using SSP (Simple Secure
  Pairing); which does include many newer bluetooth devices, especially
  keyboards.

  [Test Case]

   * Try to connect a bluetooth keyboard using the wizard; especially
  one of the following models:

  Logitech Bluetooth Keyboard K760
  Logitech Bluetooth Keyboard K810
  HP Bluetooth Keyboard K4000

  [Regression Potential]

   * It must be ensured that keyboards that could already be paired
  successfully still work properly; specifically, especially for
  keyboards but for any other devices, that pairing still works despite
  changes to the SSP code.

  [Other Info]

  
  ---

  When I try to connect my bluetooth keyboard using bluetooth-wizard, it
  ever fails:

  ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760'
  failed: Authentication Failed

  This keyboard works fine with another computer under ubuntu 11.04.
  This keyboard works fine with this computer and Windows 7 (arghhh).
  This computer ubuntu 12.04 works fine with my bluetooth mouse.

  I can attach manually this keyboard to this computer using :

  sudo hidd --search

  My computer is a Samsung 305U1A
  My bluetooth interface is :

  Bus 003 Device 002: ID 0a5c:219c Broadcom Corp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1369964] Re: Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings

[Mathieu Trudel-Lapierre]

Oh, I was really expecting this would have worked from the start; with
the changes that were made recently to allow it to pair.

Please, could you provide /home/phablet/.cache/upstart/application-
legacy-ubuntu-system-settings-.log ? As I recall, this particular device
doesn't do HSP; so we need to see it use disconnection via the generic
stereo Audio interfaces; and that should already be the default.
Regardless, exactly which interface used and why it failed should show
up in the log.

** Changed in: bluez (Ubuntu)
   Status: New = Incomplete

-- 
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/1369964

Title:
  Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth
  settings

Status in “bluez” package in Ubuntu:
  Incomplete

Bug description:
  ENVIRONMENT:
  krillin ubuntu-rtm/14.09-proposed build 44.
  BQ Avrha Altavoz Vivaldi Bluetooth speaker:
  http://www.bqreaders.com/gb/accessories-aquaris.html

  SUMMARY:
  Cannot disconnect BQ Vivaldi Bluetooth speaker using Bluetooth settings

  STEPS:
  1) Turn on speaker so that it is in pairing mode
  2) On Ubuntu device pair with the speaker
  3) Play music through the speaker
  4) From Bluetooth settings, select the speaker device and press Disconnect 
button

  EXPECTED RESULT:
  The device should disconnect.

  ACTUAL RESULT:
  The disconnect button has no effect. Music continues to play through the 
Bluetooth speaker.

  For other Bluetooth devices the Disconnect button works. This bug is
  specific to this particular device.

  ADDITIONAL INFO:

  hcitool inq:
  12:1F:83:05:03:B4 clock offset: 0x264c class: 0x240414

  hcitool info:

   BD Address: 12:1F:83:05:03:B4
   Device Name: Avrha Vivaldi
   LMP Version: 2.0 (0x3) LMP Subversion: 0x2
   Manufacturer: Accel Semiconductor Ltd. (74)
   Features page 0: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80
3-slot packets 5-slot packets encryption slot offset
timing accuracy role switch hold mode sniff mode
RSSI channel quality SCO link HV2 packets
HV3 packets CVSD power control transparent SCO
EDR ACL 2 Mbps EDR ACL 3 Mbps interlaced iscan
interlaced pscan inquiry with RSSI 3-slot EDR ACL
5-slot EDR ACL extended features
   Features page 1: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1369964/+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 1364008] Re: Cannot pair with Altavoz Vivaldi Bluetooth speaker

[Mathieu Trudel-Lapierre]

The fix for this has landed in RTM: ubuntu-system-settings
(0.3+14.10.20140909~rtm-0ubuntu1).

It is now available in the proposed RTM image; so I'll mark this as Fix
Released.

** Changed in: bluez (Ubuntu)
   Status: New = Fix Released

-- 
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/1364008

Title:
  Cannot pair with Altavoz Vivaldi Bluetooth speaker

Status in “bluez” package in Ubuntu:
  Fix Released

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 9.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  Cannot pair with Avrha Altavoz Vivaldi Bluetooth speaker:
  http://www.bqreaders.com/gb/accessories-aquaris.html

  Device is Bluetooth v2.0 +EDR

  [Note that the other listed Bluetooth Speaker Strauss does work]

  
  STEPS:
  1) Turn on speaker so that it is in pairing mode
  2) On krillin attempt to pair with the speaker

  EXPECTED RESULT:
  The pairing should be successful

  ACTUAL RESULT:
  In the list of Bluetooth devices a greyed-out speaker icon is listed with the 
name '...'
  The name is never resolved and it is not possible to start a pairing request 
with the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1364008/+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 1273629] Re: HSP fails on Ubuntu Touch [Bluetooth headset does not work]

[Mathieu Trudel-Lapierre]

I think we can mark this as Fix Released by now; fixes for this have
been landed in ubuntu-touch and ubuntu-rtm images for a while and we've
tested it, it does appear to work properly.

-- 
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/1273629

Title:
  HSP fails on Ubuntu Touch [Bluetooth headset does not work]

Status in “bluez” package in Ubuntu:
  Fix Committed

Bug description:
  When on Ubuntu Touch, HSP consistently fails to route any audio to the
  paired audio device.

  bluez-test-device create BT address
  bluez-test-audio connect BT address

  The above should create and pair a detected (in discoverable mode)
  bluetooth device, by default setting it up for HSP.

  The following excerpt from syslog on my mako shows the issue, with a
  bluetooth headset device failing to bring up HSP -- pulseaudio can
  acquire the first transport, but never release it:

  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:start_inquiry() hci0 length 8
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: Discovery session 0x41f77f98 
with :1.132 activated
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_ref() 
0x41f77f98: ref=1
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() 
hci0: new state 1
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:session_remove() Discovery session 0x41f77f98 with :1.132 
deactivated
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:session_remove() Stopping discovery
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:hciops_stop_discovery() index 0
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:hciops_stop_inquiry() hci0
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() 
hci0: new state 0
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:create_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_create_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_create() 
Creating device /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=1
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:device_set_temporary() temporary 1
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=2
  Jan 28 09:47:54 ubuntu-phablet kernel: [ 3389.758613] l2cap_sock_connect: 
failed -115
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:conn_complete() status 0x00
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_version_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_features_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_name_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:device_probe_drivers() Probing drivers for 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/manager.c:serial_probe() path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 1108--1000-8000-00805f9b34fb
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/port.c:create_serial_device() Registered interface org.bluez.Serial on 
path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/manager.c:serial_probe() path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 111e--1000-8000-00805f9b34fb
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
input/manager.c:headset_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=3
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
input/device.c:input_device_new() Registered interface org.bluez.Input on path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=4
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/device.c:audio_device_register() Registered interface org.bluez.Audio on 
path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/manager.c:handle_uuid() Found Headset record
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/headset.c:headset_init() Registered interface org.bluez.Headset on path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/manager.c:handle_uuid() Found 

[Kernel-packages] [Bug 1364008] Re: Cannot pair with Altavoz Vivaldi Bluetooth speaker

[Mathieu Trudel-Lapierre]

Hmm, this didn't include the information I expected. Here's a different
command to use, again with the speaker in range:

hcitool inq

You should get a list of all the devices in range and their class, etc.;
the class information is what I need.

In the meantime, I'll dig in the code and make sure all types of
speakers are properly handled, but I'd like to make certain this is
indeed saying it's a speaker, and not some other multimedia device.

-- 
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/1364008

Title:
  Cannot pair with Altavoz Vivaldi Bluetooth speaker

Status in “bluez” package in Ubuntu:
  New

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 9.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  Cannot pair with Avrha Altavoz Vivaldi Bluetooth speaker:
  http://www.bqreaders.com/gb/accessories-aquaris.html

  Device is Bluetooth v2.0 +EDR

  [Note that the other listed Bluetooth Speaker Strauss does work]

  
  STEPS:
  1) Turn on speaker so that it is in pairing mode
  2) On krillin attempt to pair with the speaker

  EXPECTED RESULT:
  The pairing should be successful

  ACTUAL RESULT:
  In the list of Bluetooth devices a greyed-out speaker icon is listed with the 
name '...'
  The name is never resolved and it is not possible to start a pairing request 
with the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1364008/+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 1273629] Re: HSP fails on Ubuntu Touch [Bluetooth headset does not work]

[Mathieu Trudel-Lapierre]

** Changed in: bluez (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
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/1273629

Title:
  HSP fails on Ubuntu Touch [Bluetooth headset does not work]

Status in “bluez” package in Ubuntu:
  Fix Released

Bug description:
  When on Ubuntu Touch, HSP consistently fails to route any audio to the
  paired audio device.

  bluez-test-device create BT address
  bluez-test-audio connect BT address

  The above should create and pair a detected (in discoverable mode)
  bluetooth device, by default setting it up for HSP.

  The following excerpt from syslog on my mako shows the issue, with a
  bluetooth headset device failing to bring up HSP -- pulseaudio can
  acquire the first transport, but never release it:

  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:start_inquiry() hci0 length 8
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: Discovery session 0x41f77f98 
with :1.132 activated
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: src/adapter.c:session_ref() 
0x41f77f98: ref=1
  Jan 28 09:47:41 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() 
hci0: new state 1
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:session_remove() Discovery session 0x41f77f98 with :1.132 
deactivated
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:session_remove() Stopping discovery
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:hciops_stop_discovery() index 0
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:hciops_stop_inquiry() hci0
  Jan 28 09:47:49 ubuntu-phablet bluetoothd[4621]: plugins/hciops.c:set_state() 
hci0: new state 0
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:create_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_create_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: src/device.c:device_create() 
Creating device /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=1
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:device_set_temporary() temporary 1
  Jan 28 09:47:54 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=2
  Jan 28 09:47:54 ubuntu-phablet kernel: [ 3389.758613] l2cap_sock_connect: 
failed -115
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:conn_complete() status 0x00
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_version_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_features_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
plugins/hciops.c:remote_name_information() hci0 status 0
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:device_probe_drivers() Probing drivers for 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/manager.c:serial_probe() path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 1108--1000-8000-00805f9b34fb
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/port.c:create_serial_device() Registered interface org.bluez.Serial on 
path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
serial/manager.c:serial_probe() path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D: 111e--1000-8000-00805f9b34fb
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
input/manager.c:headset_probe() path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=3
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
input/device.c:input_device_new() Registered interface org.bluez.Input on path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/adapter.c:adapter_get_device() 00:1A:7D:54:32:8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:btd_device_ref() 0x41f936e8: ref=4
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/device.c:audio_device_register() Registered interface org.bluez.Audio on 
path /org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/manager.c:handle_uuid() Found Headset record
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/headset.c:headset_init() Registered interface org.bluez.Headset on path 
/org/bluez/4621/hci0/dev_00_1A_7D_54_32_8D
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
audio/manager.c:handle_uuid() Found Handsfree record
  Jan 28 09:47:55 ubuntu-phablet bluetoothd[4621]: 
src/device.c:device_set_temporary() temporary 

[Kernel-packages] [Bug 1364008] Re: Cannot pair with Altavoz Vivaldi Bluetooth speaker

[Mathieu Trudel-Lapierre]

Could this be tested on an Ubuntu desktop? I'd like to know what type
this device is saying it is; we already support most speakers as Other
audio devices, we support Headphones, Handsfree, etc.

Once connected, you should be able to figure out the state of the device
with the following command:

hcitool info bluetooth address

** Changed in: bluez (Ubuntu)
   Status: New = Incomplete

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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/1364008

Title:
  Cannot pair with Altavoz Vivaldi Bluetooth speaker

Status in “bluez” package in Ubuntu:
  Incomplete

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 9.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  Cannot pair with Avrha Altavoz Vivaldi Bluetooth speaker:
  http://www.bqreaders.com/gb/accessories-aquaris.html

  Device is Bluetooth v2.0 +EDR

  [Note that the other listed Bluetooth Speaker Strauss does work]

  
  STEPS:
  1) Turn on speaker so that it is in pairing mode
  2) On krillin attempt to pair with the speaker

  EXPECTED RESULT:
  The pairing should be successful

  ACTUAL RESULT:
  In the list of Bluetooth devices a greyed-out speaker icon is listed with the 
name '...'
  The name is never resolved and it is not possible to start a pairing request 
with the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1364008/+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 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)

[Mathieu Trudel-Lapierre]

** Changed in: bluez (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: gnome-bluetooth (Ubuntu Precise)
   Status: New = In Progress

** Changed in: gnome-bluetooth (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: gnome-bluetooth (Ubuntu Precise)
   Status: In Progress = Triaged

** Changed in: bluez (Ubuntu Precise)
   Status: New = Triaged

** Changed in: bluez (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: bluez (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: gnome-bluetooth (Ubuntu Precise)
   Importance: Undecided = Medium

** Changed in: gnome-bluetooth (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: gnome-bluetooth (Ubuntu Trusty)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: bluez (Ubuntu Trusty)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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/1035431

Title:
  bluetooh-wizard failed to connect to a keyboard(logitech)

Status in GNOME Bluetooth:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in “bluez” package in Ubuntu:
  Fix Released
Status in “gnome-bluetooth” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Triaged
Status in “gnome-bluetooth” source package in Precise:
  Triaged
Status in “bluez” source package in Trusty:
  In Progress
Status in “gnome-bluetooth” source package in Trusty:
  In Progress

Bug description:
  When I try to connect my bluetooth keyboard using bluetooth-wizard, it
  ever fails:

  ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760'
  failed: Authentication Failed

  This keyboard works fine with another computer under ubuntu 11.04.
  This keyboard works fine with this computer and Windows 7 (arghhh).
  This computer ubuntu 12.04 works fine with my bluetooth mouse.

  I can attach manually this keyboard to this computer using :

  sudo hidd --search

  My computer is a Samsung 305U1A
  My bluetooth interface is :

  Bus 003 Device 002: ID 0a5c:219c Broadcom Corp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1355152] Re: Can't pair any Bluetooth audio device with Ubuntu Touch

[Mathieu Trudel-Lapierre]

Thanks.

This bug belongs to ubuntu-system-settings; I believe this will require
some fixes to the agent to properly handle these devices.

Could you please add debug logs from bluez as well as the log for the
ubuntu-system-settings app?  (/home/phablet/.cache/upstart/application-
legacy-ubuntu-system-settings-.log)

** Package changed: bluez (Ubuntu) = ubuntu-system-settings (Ubuntu)

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = Triaged

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

** Summary changed:

- Can't pair any Bluetooth audio device with Ubuntu Touch
+ [bluetooth] Can't pair PIN-requiring  audio devices with Ubuntu Touch

-- 
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/1355152

Title:
  [bluetooth] Can't pair PIN-requiring  audio devices with Ubuntu Touch

Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged

Bug description:
  I tried pairing several devices with my Ubuntu Touch device. All of
  them fail:

  * Nokia-BH 503 (HFP + A2DP + AVRCP)
  * Nokia-BH 905i (HFP + A2DP + AVRCP)
  * Latest BMW infotainment system (HFP)

  All of those devices are found during inquiry. Trying to pair them
  causes the PIN entry popup to appear on the phone, however, after
  confirming that it just sits there and waits forever, never completing
  the pairing process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355152/+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 1307198] Re: Bluetooth shuts down contact with mouse

[Mathieu Trudel-Lapierre]

Closing as Invalid since the issue is reportedly solve, but we don't
know why/how the other mouse does not work.

Sorry for the delay in responding.

** Changed in: bluez (Ubuntu)
   Status: New = Invalid

-- 
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/1307198

Title:
  Bluetooth shuts down contact with mouse

Status in “bluez” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  My Dell Vostro 3555 purchased in Sept 2011 is equipped with Bluetooth.

   I used a bluetooth mouse from then on and never lost contact between
  computer and mouse, not even when changing the battery in the mouse.
  Since installing 1404LTS Beta 2 the connection is shut down when the
  computer is shut down and sometimes when the computer goes into
  hibernation.  This results in having to manually goto the Bluetooth
  GUI and the mouse and force the connection.

   The Bluetooth GUI has three on/off buttons,  bluetooth , visibility
  on Ubuntu-0 and mouse. The mouse button is off wenever I start the
  system.  This did not happen in any Ubuntu version of Linux I have had
  on this computer, other than in 14.04LTS.  This is a nuisance, and
  prevents me from demonstrating how good Ubuntu Linux really is.

   Having to sit in a demo and manually pressing a button on the mouse
  until the on/off button turns on immediately turns off any interest a
  newbie might have.

  A quick fix would be appreciated.

  At this point I have no idea od what corroborating info I need to
  provide, but will send anything asked for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1307198/+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 1212287] Re: bluetooth will not reconnect after first disconnect

[Mathieu Trudel-Lapierre]

Thanks, closing as Invalid.

** Changed in: bluez (Ubuntu)
   Status: New = Invalid

-- 
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/1212287

Title:
  bluetooth will not reconnect after first disconnect

Status in “bluez” package in Ubuntu:
  Invalid

Bug description:
  Bluetooth had been working well for me until recently. I'm running
  Ubuntu 13.04 with a bluetooth USB dongle that I use to pair with
  various headphones.

  Suddenly, after the first successful connection to the headphone, once
  I disconnect either from the headphone side or the computer side, the
  headphones will no longer reconnect.

  I've found that to reconnect, I need to

   stop bluetooth;rmmod bnep btusb rfcomm bluetooth ; start
  bluetooth

  then remove and reinsert the bluetooth USB dongle. Then I can
  reconnect.

  I've been using the same hardware for quite a while and this problem
  is very recent.  The only software changes are by the patches which I
  always accept.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Wed Aug 14 10:34:08 2013
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationDate: Installed on 2012-12-14 (242 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Hewlett-Packard HP Z210 Workstation
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic 
root=UUID=0659f1b3-4361-442f-bf62-b9b3393a3b95 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to raring on 2013-04-27 (109 days ago)
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J51 v01.44
  dmi.board.asset.tag: 2UA145126W
  dmi.board.name: 1588h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA145126W
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ51v01.44:bd11/27/2012:svnHewlett-Packard:pnHPZ210Workstation:pvr:rvnHewlett-Packard:rn1588h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z210 Workstation
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:18:E4:0D:18:12  ACL MTU: 192:8  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:87163 acl:36 sco:1679 events:79 errors:0
TX bytes:86224 acl:41 sco:1666 commands:22 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1212287/+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 1199059] Re: Bug #948613 Enable the Source and Gateway audio profiles in bluez by default patch breaks A2DP audio sink devices(orig.: A2DP audio sink devices failed to work wi

[Mathieu Trudel-Lapierre]

The fact that this is fixed just by enabling module-bluetooth-discover,
I think we should definitely investigate whether this is something
broken by blueman... reassigning.

** Also affects: blueman (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: blueman (Ubuntu)
   Status: New = Confirmed

** Changed in: bluez (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: bluez (Ubuntu)
   Importance: Undecided = Medium

** Changed in: blueman (Ubuntu)
   Importance: Undecided = Medium

** Summary changed:

- Bug #948613 Enable the Source and Gateway audio profiles in bluez by 
default patch breaks A2DP audio sink devices(orig.: A2DP audio sink devices 
failed to work with bluetoothd : Unable to select SEP in system log.)
+ blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed 
to work with bluetoothd : Unable to select SEP in system 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/1199059

Title:
  blueman and pulse's module-bluetooth-discover (A2DP audio sink devices
  failed to work with bluetoothd : Unable to select SEP in system
  log.)

Status in “blueman” package in Ubuntu:
  Confirmed
Status in “bluez” package in Ubuntu:
  Incomplete
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “bluez” package in Debian:
  Fix Released

Bug description:
  All my A2DP profile devices can't create a audio device properly...
  My 2 13.04 machines both have this issue(1 notebook, 2 bluetooth dongles)
  UPDATE: Upgraded to 13.10, still reproducible

  Possible root cause  fix: Please refer #15

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jul  9 01:01:38 2013
  InstallationDate: Installed on 2013-01-26 (162 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130126)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic 
root=UUID=9bce9679-da3a-44fd-84ec-b16339a84004 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to raring on 2013-03-01 (128 days ago)
  dmi.bios.date: 08/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 00:15:83:54:59:9F  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN ISCAN
    RX bytes:29508 acl:1270 sco:0 events:461 errors:0
    TX bytes:5249 acl:165 sco:0 commands:95 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1199059/+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 1255101] Re: Bluetooth doesn't work

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948

** This bug has been marked a duplicate of bug 1285948
   Can't send files over bluetooth

-- 
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/1255101

Title:
  Bluetooth doesn't work

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  Can't send or recieve files with bluetooth and any mobile phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov 26 14:44:24 2013
  InstallationDate: Installed on 2013-11-10 (15 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=d88c271e-1207-451d-bfb8-d7a2053a1acf ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.6A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3566
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.46
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0695130046160:rvnHewlett-Packard:rn3566:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 0695130046160
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 9C:B7:0D:66:40:F5  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:27919 acl:145 sco:0 events:400 errors:0
TX bytes:24398 acl:151 sco:0 commands:158 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1255101/+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 599999] Re: Can't send files to phone

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948

** This bug has been marked a duplicate of bug 1285948
   Can't send files over bluetooth

-- 
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/59

Title:
  Can't send files to phone

Status in “bluez” package in Ubuntu:
  New

Bug description:
  Binary package hint: bluez

  I have Ubuntu 10.04 installed and a Nexus One running the latest
  Android version. Every time I'm trying to send a file to Nexus One, it
  will fail. It will see the phone, it will try to connect, and when it
  will try to send the file, it will fail. The laptop with Ubuntu is a
  DELL, same model that the first Ubuntu/DELL product was sold with, a
  few years ago (so it's a compatible one). I can send files to/and/from
  the Nexus One to Windows XP just fine, so I'm pretty sure the bug is
  with Ubuntu.

  Please let me know what kind of logs you need to debug this, and how
  to obtain them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/59/+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 1250615] Re: Systematically always rejects all transfers from mobile device. Ne way to send a file to this computer

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948

** This bug has been marked a duplicate of bug 1285948
   Can't send files over bluetooth

-- 
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/1250615

Title:
  Systematically always rejects all transfers from mobile device. Ne way
  to send a file to this computer

Status in “bluez” package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 13.04 on an Acer laptop.
  All file transfers via bluetooth from a (Android) mobile device get 
systematically rejected.

  This is somehow different (as far as observed symptoms are concerned)
  from #958661

  On another computer, where I also had Ubuntu 13.04 (upgraded from
  earlier releases), transfers from bluetooth device would usually work;
  then at random times (probably after suspending and resuming) they
  would start being systematically rejected; turning bluetooth
  physically off and on again via the hardware switch would fix the
  issue. That's issue 958661.

  Now, on this other computer, all file transfers are always
  systematically rejected. I've never, ever been able to send a file via
  bluetooth to this computer. I'm sending them from the same device that
  would (usually) succeed to send them to the old computer.

  I can, however, browse files from the computer on the same device. So,
  bluetooth does kind of work in general, it's not like I don't have
  bluetooth. But incoming file transfers get systematically rejected and
  I can't find any setting anywhere that says that file transfers are to
  be rejected or accepted.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Tue Nov 12 21:19:42 2013
  InstallationDate: Installed on 2013-10-11 (32 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1714 acl:9 sco:0 events:87 errors:0
TX bytes:2489 acl:10 sco:0 commands:64 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1250615/+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 1253032] Re: Bluetooth file transfer fails everytime.Shows an error message like: GDBus.Error:org.openobex.Error.Failed:Unable to request session

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948

** This bug has been marked a duplicate of bug 1285948
   Can't send files over bluetooth

-- 
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/1253032

Title:
  Bluetooth file transfer fails everytime.Shows an error message like: 
  GDBus.Error:org.openobex.Error.Failed:Unable to request session 

Status in “bluez” package in Ubuntu:
  Incomplete

Bug description:
  The bluetooth service can add devices, view the files in the device
  using FTP and even can delete files from it (paired/connected device).
  But the system bluetooth fails to send or receive files from a device.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evince 3.6.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Wed Nov 20 15:27:58 2013
  InstallationDate: Installed on 2013-10-28 (22 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to raring on 2013-11-12 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1253032/+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 958661] Re: bluetooth suddenly rejects all transfers (worked yesterday)

[Mathieu Trudel-Lapierre]

*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948

** This bug has been marked a duplicate of bug 1285948
   Can't send files over bluetooth

-- 
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/958661

Title:
  bluetooth suddenly rejects all transfers (worked yesterday)

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  I often send image files via bluetooth from my android phone to my
  ubuntu PC.

  It worked fine until yesterday, but now I systematically get the
  remote bluetooth device rejected the request.

  Nothing has changed in the way I transfer files and I'm trying from
  the very same phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic 3.0.0-16.29
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo   32650 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
     Mixer name : 'Realtek ALC660-VD'
     Components : 'HDA:10ec0660,1043,0011 
HDA:10573055,10431316,00100700'
     Controls  : 25
     Simple ctrls  : 16
  Date: Sun Mar 18 17:55:36 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic N/A
   linux-backports-modules-3.0.0-16-generic  N/A
   linux-firmware1.60.1
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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