kernel-packages team mailing list archive

1. kernel-packages team
2. Mailing list archive
3. Messages by thread

Messages by thread

Messages sent to the kernel-packages mailing list, ordered by thread from the newest to oldest.

• [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled, (continued)
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: xormar, 2016-05-20
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: xormar, 2016-05-20
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: Christopher M. Penalver, 2016-06-05
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: Daniel, 2016-06-06
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: Christopher M. Penalver, 2016-06-07
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: xormar, 2016-06-07
  • [Bug 1582858] Re: kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
    From: Christopher M. Penalver, 2016-06-07
• [Bug 1582858] [NEW] kernel 4.4.0-22-generic in 16.04 sees no disks on HP Proliant DL165 G7 if IOMMU is enabled
  From: Launchpad Bug Tracker, 2016-05-17
• [Bug 1582918] [NEW] Failed to build bcmwl-package for kernel 4.6.0-gnu
  From: epic456, 2016-05-17
• [Bug 1582918] Re: Failed to build bcmwl-package for kernel 4.6.0-gnu
  From: Daniel van Vugt, 2016-05-18
• [Bug 1582918] Re: Failed to build bcmwl-package for kernel 4.6.0-gnu
  From: Adwin, 2016-05-20
• [Bug 1582864] [NEW] use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-05-17
• [Bug 1582864] Missing required logs.
  From: Brad Figg, 2016-05-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-05-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Joseph Salisbury, 2016-05-18
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-05-20
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Kamal Mostafa, 2016-05-20
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Philipp Kern, 2016-05-21
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Joseph Salisbury, 2016-05-24
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Kamal Mostafa, 2016-05-25
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-05-25
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Launchpad Bug Tracker, 2016-05-31
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Kamal Mostafa, 2016-06-14
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Kamal Mostafa, 2016-06-14
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-06-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Mike Gerow, 2016-06-17
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Launchpad Bug Tracker, 2016-06-27
• [Bug 1582864] Re: use after free of BOS in usb_reset_and_verify_device
  From: Launchpad Bug Tracker, 2016-06-27
• [Bug 1582852] [NEW] IMA crashes while verifying signatures
  From: Stefan Berger, 2016-05-17
• [Bug 1582852] Missing required logs.
  From: Brad Figg, 2016-05-17
• [Bug 1582852] Re: IMA crashes while verifying signatures
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582852] Re: IMA crashes while verifying signatures
  From: Joseph Salisbury, 2016-05-18
• [Bug 1582852] Re: IMA crashes while verifying signatures
  From: Joseph Salisbury, 2016-05-20
• [Bug 1582852] Re: IMA crashes while verifying signatures
  From: Stefan Berger, 2016-05-20
• [Bug 1582852] Re: IMA crashes while verifying signatures
  From: Joseph Salisbury, 2016-05-24
• [Bug 1582823] Missing required logs.
  From: Brad Figg, 2016-05-17
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: hackel, 2016-05-17
• <Possible follow-ups>
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: hackel, 2016-05-18
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Launchpad Bug Tracker, 2016-05-23
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Bastian, 2016-05-23
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Alberto Salvia Novella, 2016-05-27
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Christopher M. Penalver, 2016-06-05
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Petteri Aimonen, 2016-06-10
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Petteri Aimonen, 2016-06-10
• [Bug 1582823] Re: Text not rendering correctly after resume from suspend
  From: Christopher M. Penalver, 2016-06-11
• [Bug 618838] Re: Apple Magic Trackpad requires PIN to pair, fails manual pairing
  From: Konrad Zapałowicz, 2016-05-17
• <Possible follow-ups>
• [Bug 618838] Re: Apple Magic Trackpad requires PIN to pair, fails manual pairing
  From: Stephan, 2016-05-17
• [Bug 897255] Re: RFCOMM channel 1 and automatic channel choosing broken cause of DUN
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1189739] Re: bluez-alsa devices are invisible to the alsa api and /proc/asound
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1191101] Re: bluetooth doesn't work
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1582780] [NEW] linux: 3.19.0-60.67 -proposed tracker
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-05-17
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-05-17
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-05-18
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Chris J Arges, 2016-05-18
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Chris J Arges, 2016-05-18
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-05-19
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-05-19
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Steve Beattie, 2016-05-19
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Steve Beattie, 2016-05-19
• [Bug 1582780] modoc (ppc64el) - tests ran: 13, failed: 12
  From: Brad Figg, 2016-05-20
• [Bug 1582780] modoc (ppc64el) - tests ran: 18, failed: 18
  From: Brad Figg, 2016-05-20
• [Bug 1582780] modoc (ppc64el) - tests ran: 18, failed: 18
  From: Brad Figg, 2016-05-20
• [Bug 1582780] modoc (ppc64el) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-20
• [Bug 1582780] rukbah (amd64) - tests ran: 81, failed: 0
  From: Brad Figg, 2016-05-20
• [Bug 1582780] fozzie (amd64) - tests ran: 15, failed: 2
  From: Brad Figg, 2016-05-21
• [Bug 1582780] fozzie (i386) - tests ran: 13, failed: 2
  From: Brad Figg, 2016-05-21
• [Bug 1582780] fozzie (amd64) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582780] fozzie (i386) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582780] fozzie (amd64) - tests ran: 18, failed: 5
  From: Brad Figg, 2016-05-22
• [Bug 1582780] fozzie (i386) - tests ran: 18, failed: 3
  From: Brad Figg, 2016-05-22
• [Bug 1582780] fozzie (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] dagmar (amd64) - tests ran: 40, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] fozzie (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] dagmar (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] dagmar (amd64) - tests ran: 15, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] dagmar (i386) - tests ran: 15, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] dagmar (amd64) - tests ran: 18, failed: 2
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onibi (amd64) - tests ran: 40, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onibi (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onza (amd64) - tests ran: 40, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onibi (amd64) - tests ran: 15, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onibi (i386) - tests ran: 15, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onza (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582780] onza (amd64) - tests ran: 18, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] dagmar (i386) - tests ran: 18, failed: 3
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onibi (amd64) - tests ran: 18, failed: 2
  From: Brad Figg, 2016-05-23
• [Bug 1582780] dagmar (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] dagmar (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onza (i386) - tests ran: 18, failed: 1
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onza (amd64) - tests ran: 18, failed: 2
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onibi (i386) - tests ran: 18, failed: 3
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onibi (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onibi (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onza (i386) - tests ran: 18, failed: 3
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onza (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] onza (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-23
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Po-Hsu Lin, 2016-05-30
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Po-Hsu Lin, 2016-06-02
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-06-08
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Kamal Mostafa, 2016-06-08
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Brad Figg, 2016-06-08
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Launchpad Bug Tracker, 2016-06-09
• [Bug 1582780] Re: linux: 3.19.0-60.67 -proposed tracker
  From: Adam Conrad, 2016-06-10
• [Bug 776363] Re: Bluetooth service needs to be restarted before a Bluetooth dongle works
  From: Konrad Zapałowicz, 2016-05-17
• <Possible follow-ups>
• [Bug 776363] Re: Bluetooth service needs to be restarted before a Bluetooth dongle works
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 891878] Re: iPhone bluetooth tethering only works the first time iPhone is paired
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1176680] Re: Bluetooth dangerously unstable on Dell Q15R (N5110)
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1186530] Re: Bluetooth audio devices disconnects
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1582776] [NEW] HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Jay Berkenbilt, 2016-05-17
• [Bug 1582776] Status changed to Confirmed
  From: Brad Figg, 2016-05-17
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Jay Berkenbilt, 2016-05-17
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Joseph Salisbury, 2016-05-17
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Stefan Bader, 2016-05-18
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Stefan Bader, 2016-05-18
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Joseph Salisbury, 2016-05-18
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Jay Berkenbilt, 2016-05-18
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Jay Berkenbilt, 2016-05-18
• [Bug 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
  From: Joseph Salisbury, 2016-05-24
• [Bug 1582771] [NEW] Vivid update to v3.19.8-ckt21 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582771] Re: Vivid update to v3.19.8-ckt21 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582771] Re: Vivid update to v3.19.8-ckt21 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582771] Re: Vivid update to v3.19.8-ckt21 stable release
  From: Launchpad Bug Tracker, 2016-06-09
• [Bug 735523] Re: bluetooth keyboard connected but not working
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1088888] Re: bluetooth doesnt work on lenovo g580
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1164227] Re: Bluetooth daemon crashes when using mobile phone as network device (PAN/NAP)
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1166960] Re: bluetooth discovery: nothing if found
  From: Konrad Zapałowicz, 2016-05-17
• [Bug 1582765] [NEW] linux: 4.2.0-37.43 -proposed tracker
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-05-17
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-05-17
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-05-18
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Chris J Arges, 2016-05-18
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Chris J Arges, 2016-05-18
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-05-19
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-05-19
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Steve Beattie, 2016-05-19
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Steve Beattie, 2016-05-19
• [Bug 1582765] modoc (ppc64el) - tests ran: 13, failed: 12
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 18, failed: 18
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 18, failed: 18
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 2, failed: 2
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 65, failed: 65
  From: Brad Figg, 2016-05-20
• [Bug 1582765] modoc (ppc64el) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-20
• [Bug 1582765] rukbah (amd64) - tests ran: 83, failed: 0
  From: Brad Figg, 2016-05-20
• [Bug 1582765] dwalin (amd64) - tests ran: 2, failed: 0
  From: Brad Figg, 2016-05-20
• [Bug 1582765] dwalin (amd64) - tests ran: 65, failed: 0
  From: Brad Figg, 2016-05-20
• [Bug 1582765] dwalin (amd64) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-20
• [Bug 1582765] fozzie (amd64) - tests ran: 15, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (amd64) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (i386) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (amd64) - tests ran: 18, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onza (amd64) - tests ran: 15, failed: 2
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onibi (amd64) - tests ran: 15, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onza (i386) - tests ran: 13, failed: 2
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (i386) - tests ran: 18, failed: 7
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (amd64) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] fozzie (i386) - tests ran: 1, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onibi (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onibi (amd64) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582765] onibi (i386) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-21
• [Bug 1582765] dagmar (amd64) - tests ran: 15, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (amd64) - tests ran: 18, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (i386) - tests ran: 13, failed: 1
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (amd64) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (i386) - tests ran: 15, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onibi (amd64) - tests ran: 18, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (amd64) - tests ran: 18, failed: 6
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (i386) - tests ran: 18, failed: 8
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (i386) - tests ran: 18, failed: 7
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] dagmar (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (amd64) - tests ran: 18, failed: 3
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onibi (i386) - tests ran: 18, failed: 4
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onibi (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (i386) - tests ran: 18, failed: 4
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onibi (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (amd64) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] onza (i386) - tests ran: 136, failed: 0
  From: Brad Figg, 2016-05-22
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Po-Hsu Lin, 2016-05-30
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Po-Hsu Lin, 2016-06-03
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Po-Hsu Lin, 2016-06-03
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-06-08
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Kamal Mostafa, 2016-06-08
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Brad Figg, 2016-06-08
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Launchpad Bug Tracker, 2016-06-09
• [Bug 1582765] Re: linux: 4.2.0-37.43 -proposed tracker
  From: Adam Conrad, 2016-06-10
• [Bug 224110] useful links
  From: payo, 2016-05-17
• [Bug 1582758] [NEW] Wily update to v4.2.8-ckt10 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582758] Re: Wily update to v4.2.8-ckt10 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582758] Re: Wily update to v4.2.8-ckt10 stable release
  From: Kamal Mostafa, 2016-05-17
• [Bug 1582758] Re: Wily update to v4.2.8-ckt10 stable release
  From: Launchpad Bug Tracker, 2016-06-09
• [Bug 1582759] [NEW] Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives
  From: Michael Schaller, 2016-05-17
• [Bug 1582759] Re: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives
  From: Michael Schaller, 2016-05-17
• [Bug 1582759] Missing required logs.
  From: Brad Figg, 2016-05-17

 •  Take the tour  •  Read the guide  •  Help for mailing lists  

© 2004-2016 Canonical Ltd.  •  Terms of use  •  Contact Launchpad Support  •  System status