[Kernel-packages] [Bug 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2017-03-10 Thread Dave Morley
Tested via live session and via install all seems to be working as
expected.

-- 
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:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  WORKAROUND:
  The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.

  From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb

  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.

  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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2017-03-10 Thread Dave Morley
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done

-- 
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:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  WORKAROUND:
  The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.

  From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb

  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.

  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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2017-03-10 Thread Dave Morley
Will look into this today but I though it had been resolved already, let
me confirm it though.

-- 
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:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed

Bug description:
  WORKAROUND:
  The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.

  From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb

  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.

  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 1633019] [NEW] BT driver in dell xps 9343 not functioning

2016-10-13 Thread Dave Morley
Public bug reported:

Scanning reveals no mice, keyboards or computers.

Everything looks to be fine but the Bluetooth seemingly does nothing.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dave   2157 F pulseaudio
 /dev/snd/controlC1:  dave   2157 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 13 11:08:00 2016
HibernationDevice: RESUME=UUID=7a85aeaa-7621-4d4f-8dd3-f28c0426f22a
InstallationDate: Installed on 2016-10-13 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=ed0a9de6-b9f4-4471-843b-2d8d2135c189 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic  N/A
 linux-firmware1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  BT driver in dell xps 9343 not functioning

Status in linux package in Ubuntu:
  New

Bug description:
  Scanning reveals no mice, keyboards or computers.

  Everything looks to be fine but the Bluetooth seemingly does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2157 F pulseaudio
   /dev/snd/controlC1:  dave   2157 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 13 11:08:00 2016
  HibernationDevice: RESUME=UUID=7a85aeaa-7621-4d4f-8dd3-f28c0426f22a
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=ed0a9de6-b9f4-4471-843b-2d8d2135c189 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633019/+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 1614987] Re: cannot connect BT speaker to laptop running unity8

2016-10-11 Thread Dave Morley
** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  cannot connect BT speaker to laptop running unity8

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Laptop running unity8::

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  BT speaker: Avrha Strauss P/N:11BQALT01

  Steps to reproduce:

  1º On your laptop running unity8, go to System settings>Bluetooth and turn it 
on
  2º Turn on your BT speaker as well(on this model just press the BT button a 
few seconds for being discoverable)
  3º After a few seconds BT speaker should be found by the laptop, but it 
doesn't

  Current result: Laptop can discover and pair with Utouch and android
  devices, but is not seeing the BT speaker

  Expected result: Laptop should discover and be able to pair BT
  speakers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1614987/+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 1556970] [NEW] Kernel Panic when adb kicks in on certain devices

2016-03-14 Thread Dave Morley
Private bug reported:

STEPS:
1. flash arale or others
2. When adb kicks in the kernel on the laptop panics at worse or the entire 
system becomes unresponsive at best.

EXPECTED:
Device to flash

ACTUAL:
Kernel panics or system locks up completely and is unresponsive.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-12-generic 4.4.0-12.28
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  davmor22703 F pulseaudio
 /dev/snd/controlC2:  davmor22703 F pulseaudio
 /dev/snd/controlC1:  davmor22703 F pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 14 14:10:55 2016
HibernationDevice: RESUME=UUID=5d34732c-62da-4038-9b1d-e81b73195b20
InstallationDate: Installed on 2015-10-21 (144 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=99da44e6-2745-4584-ade2-55b5aae96930 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-12-generic N/A
 linux-backports-modules-4.4.0-12-generic  N/A
 linux-firmware1.156
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

** Information type changed from Public to Private

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

Title:
  Kernel Panic when adb kicks in on certain devices

Status in linux package in Ubuntu:
  New

Bug description:
  STEPS:
  1. flash arale or others
  2. When adb kicks in the kernel on the laptop panics at worse or the entire 
system becomes unresponsive at best.

  EXPECTED:
  Device to flash

  ACTUAL:
  Kernel panics or system locks up completely and is unresponsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22703 F pulseaudio
   /dev/snd/controlC2:  davmor22703 F pulseaudio
   /dev/snd/controlC1:  davmor22703 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 14 14:10:55 2016
  HibernationDevice: RESUME=UUID=5d34732c-62da-4038-9b1d-e81b73195b20
  InstallationDate: Installed on 2015-10-21 (144 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=99da44e6-2745-4584-ade2-55b5aae96930 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-12-generic N/A
   linux-backports-modules-4.4.0-12-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556970/+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 1543179] Re: image 242 no audio bt devices connect

2016-02-08 Thread Dave Morley
** Tags added: qa-silo

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

Title:
  image 242 no audio bt devices connect

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+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 1543179] [NEW] image 242 no audio bt devices connect

2016-02-08 Thread Dave Morley
Public bug reported:

STEPS:
1. Flash the latest daily rc-proposed image to a phone
2. Connect a bluetooth headset to the phone
3. Connect a speaker to the phone.

EXPECTED:
I expect the devices to connect and play audio

ACTUAL:
Speakers just connect and instantly disconnect

Headsets don't get trusted and disconnect instantly, Once you trust it
and then turn the headset off and back on again it connect can accept
calls but the audio from both the mic and earpiece don't function.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: bluez (Ubuntu)
 Importance: Critical
 Assignee: Simon Fels (morphis)
 Status: New

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  image 242 no audio bt devices connect

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+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 1535646] [NEW] BLUETOOTH MOUSE: with a mouse connected lock the device and leave for some time when you return the mouse is in sleep mode and the phone is in normal not windowed

2016-01-19 Thread Dave Morley
Public bug reported:

STEPS:
1. Flash a device
2. Connect a bluetooth mouse
3. Let the device sleep
4. Leave it for a couple of minutes
5. Wake the device do not move the mouse
6. Device is in phone mode
7. UNlock the device and move the mouse
8. Device after 30+ seconds flips back to windowed mode

EXPECTED:
When a mouse is connected I expect the device to always be in windows mode 
regardless of if the mouse is in sleep mode

ACTUAL:
When the mouse is in sleep mode it is like it is disconnected and the windowed 
mode is no longer active.

** Affects: canonical-pocket-desktop
 Importance: Undecided
 Status: New

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


** Tags: qa-manual-testing

** Tags added: qa-manual-testing

** Also affects: bluez (Ubuntu)
   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/1535646

Title:
  BLUETOOTH MOUSE: with a mouse connected lock the device and leave for
  some time when you return the mouse is in sleep mode and the phone is
  in normal not windowed mode

Status in canonical-pocket-desktop:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a device
  2. Connect a bluetooth mouse
  3. Let the device sleep
  4. Leave it for a couple of minutes
  5. Wake the device do not move the mouse
  6. Device is in phone mode
  7. UNlock the device and move the mouse
  8. Device after 30+ seconds flips back to windowed mode

  EXPECTED:
  When a mouse is connected I expect the device to always be in windows mode 
regardless of if the mouse is in sleep mode

  ACTUAL:
  When the mouse is in sleep mode it is like it is disconnected and the 
windowed mode is no longer active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1535646/+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 1535654] [NEW] BLUETOOTH MOUSE: with a mouse connected leave the device with a window on top

2016-01-19 Thread Dave Morley
Public bug reported:

STEPS:
1. Flash a device
2. Connect a bluetooth mouse
3. Open the web browser (It should be in windowed mode)
4. Goto ubuntu.com and now leave the device and watch the window
5. Around the time that the screen starts to dim the Window wil flash 
Fullscreen and then back to windowed mode again

EXPECTED:
I expect the device to remain in windowed mode as long as the mouse is connected

ACTUAL:
The mouse is allowed to disconnect while idle meaning that normal mode is 
triggered this then triggers the system to rewake and register the mouse again 
and flips back to windowed mode.

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


** Tags: qa-manual-testing

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

Title:
  BLUETOOTH MOUSE: with a mouse connected leave the device with a window
  on top

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a device
  2. Connect a bluetooth mouse
  3. Open the web browser (It should be in windowed mode)
  4. Goto ubuntu.com and now leave the device and watch the window
  5. Around the time that the screen starts to dim the Window wil flash 
Fullscreen and then back to windowed mode again

  EXPECTED:
  I expect the device to remain in windowed mode as long as the mouse is 
connected

  ACTUAL:
  The mouse is allowed to disconnect while idle meaning that normal mode is 
triggered this then triggers the system to rewake and register the mouse again 
and flips back to windowed mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1535654/+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 1535654] Re: BLUETOOTH MOUSE: with a mouse connected leave the device with a window on top

2016-01-19 Thread Dave Morley
** Tags added: qa-manual-testing

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

Title:
  BLUETOOTH MOUSE: with a mouse connected leave the device with a window
  on top

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a device
  2. Connect a bluetooth mouse
  3. Open the web browser (It should be in windowed mode)
  4. Goto ubuntu.com and now leave the device and watch the window
  5. Around the time that the screen starts to dim the Window wil flash 
Fullscreen and then back to windowed mode again

  EXPECTED:
  I expect the device to remain in windowed mode as long as the mouse is 
connected

  ACTUAL:
  The mouse is allowed to disconnect while idle meaning that normal mode is 
triggered this then triggers the system to rewake and register the mouse again 
and flips back to windowed mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1535654/+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 1516580] [NEW] Bluetooth firmware for dell xps 13

2015-11-16 Thread Dave Morley
Public bug reported:

STEPS:
1. Install 16.04 current on dell xps 13
2. Try connecting a bluetooth device.


EXPECTED:
I expect devices to just connect

ACTUAL:
I had to follow a guide here 
https://wiki.archlinux.org/index.php/Dell_XPS_13_(2015) to enable the firmware 
however it looks like the dell driver pack may include a .deb file for it.  
From Dell xps13_A08.fish.tar.gz contains a bluetooth firmware patch too by the 
look of things.

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Status: New

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => High

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

Title:
  Bluetooth firmware for dell xps 13

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install 16.04 current on dell xps 13
  2. Try connecting a bluetooth device.

  
  EXPECTED:
  I expect devices to just connect

  ACTUAL:
  I had to follow a guide here 
https://wiki.archlinux.org/index.php/Dell_XPS_13_(2015) to enable the firmware 
however it looks like the dell driver pack may include a .deb file for it.  
From Dell xps13_A08.fish.tar.gz contains a bluetooth firmware patch too by the 
look of things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1516580/+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 1516580] Re: Bluetooth firmware for dell xps 13

2015-11-16 Thread Dave Morley
Set as high as the xps 13 is our championed device.

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

Title:
  Bluetooth firmware for dell xps 13

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install 16.04 current on dell xps 13
  2. Try connecting a bluetooth device.

  
  EXPECTED:
  I expect devices to just connect

  ACTUAL:
  I had to follow a guide here 
https://wiki.archlinux.org/index.php/Dell_XPS_13_(2015) to enable the firmware 
however it looks like the dell driver pack may include a .deb file for it.  
From Dell xps13_A08.fish.tar.gz contains a bluetooth firmware patch too by the 
look of things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1516580/+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 1499789] Re: BLUEZ5: Connecting a keyboard shows no pip popup

2015-09-29 Thread Dave Morley
** Tags added: bluez5

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

Title:
  BLUEZ5: Connecting a keyboard shows no pip popup

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  You can not connect to a pin required keyboard as the dialogue is not
  shown.

  This means that the device for all intents and purposes looks to be
  connected, but if you disconnect from it you can not reconnect and the
  device doesn't actually type anything because although it looks
  connected it actually isn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499789/+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 1499789] [NEW] BLUEZ5: Connecting a keyboard shows no pip popup

2015-09-25 Thread Dave Morley
Public bug reported:

You can not connect to a pin required keyboard as the dialogue is not
shown.

This means that the device for all intents and purposes looks to be
connected, but if you disconnect from it you can not reconnect and the
device doesn't actually type anything because although it looks
connected it actually isn't.

** Affects: bluez (Ubuntu)
 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/1499789

Title:
  BLUEZ5: Connecting a keyboard shows no pip popup

Status in bluez package in Ubuntu:
  New

Bug description:
  You can not connect to a pin required keyboard as the dialogue is not
  shown.

  This means that the device for all intents and purposes looks to be
  connected, but if you disconnect from it you can not reconnect and the
  device doesn't actually type anything because although it looks
  connected it actually isn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499789/+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

2015-09-23 Thread Dave Morley
Mathieu didn't fix it b43 is still owning the driver for the card:

ubuntu@ubuntu:~$ sudo lsmod | grep b43
b43   417792  0
mac80211  724992  1 b43
cfg80211  536576  2 b43,mac80211
ssb65536  1 b43
bcma   53248  1 b43
ubuntu@ubuntu:~$ apt-cache policy bcmwl-kernel-source 
bcmwl-kernel-source:
  Installed: (none)
  Candidate: 6.30.223.248+bdcom-0ubuntu6
  Version table:
 6.30.223.248+bdcom-0ubuntu6 0
500 cdrom://Ubuntu 15.10 _Wily Werewolf_ - Alpha amd64 (20150922.1)/ 
wily/restricted amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ wily/restricted amd64 Packages
ubuntu@ubuntu:~$

-- 
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:
  Fix Released

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-23 Thread Dave Morley
sudo ubuntu-drivers list still only shows intel-microcode too

I'll hang around tonight and and see if we can get it resolved.

-- 
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:
  Fix Released

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-23 Thread Dave Morley
** Description changed:

+ WORKAROUND:
+ The issue here is that the driver is not able to be automatically installed 
you can however install it manually.
+ 
+ From the usbkey used to install the system copy the following files to your 
home:
+ Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
+ Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb
+ 
+ Now open terminal and from the home directory run sudo dpkg -i
+ dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
+ 0ubuntu6_amd64.deb
+ 
+ You should see a message to say networks available from the network-
+ indicator and then be able to connect to wifi.
+ 
  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

** Description changed:

  WORKAROUND:
- The issue here is that the driver is not able to be automatically installed 
you can however install it manually.
+ The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.
  
- From the usbkey used to install the system copy the following files to your 
home:
+ From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb
  
  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb
  
  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.
  
  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

-- 
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:
  Fix Released

Bug description:
  WORKAROUND:
  The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.

  From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb

  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.

  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 

[Kernel-packages] [Bug 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-23 Thread Dave Morley
** Changed in: bcmwl (Ubuntu)
   Status: Fix Released => In Progress

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

-- 
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:
  WORKAROUND:
  The issue here is that the driver is not able to be automatically installed, 
you can however install it manually.

  From the usbkey used to install the system copy the following files to your 
home directory:
  Ubuntu 15.10 amd64/pool/main/d/dkms dkms_2.2.0.3-2ubuntu2_all.deb
  Ubuntu 15.10 amd64/pool/restricted/b/bcmwl 
bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu6_amd64.deb

  Now open terminal and from the home directory run sudo dpkg -i
  dkms_2.2.0.3-2ubuntu2_all.deb bcmwl-kernel-source_6.30.223.248+bdcom-
  0ubuntu6_amd64.deb

  You should see a message to say networks available from the network-
  indicator and then be able to connect to wifi.

  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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-22 Thread Dave Morley
Okay so the macbook pro that normally has the same issue as the xps is
actually showing the bcmwl package as installable. So this could be an
issue specific to the xps13 it seems.

-- 
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:
  New

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-22 Thread Dave Morley
So running sudo lsmod

I see b43 so it looks like the b43 driver is trying to be installed
which it can't as it needs to bcmwl driver :(  Is there a way to
blacklist b43 for this chipset and have the bcmwl install for it
instead?

-- 
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:
  New

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-22 Thread Dave Morley
It was initially assumed the issue here was an out of sync archive with
the cd showing 0ubuntu4.1 and online archive 0ubuntu5 however after a
sync to get the archives straight on this morning image both show as
6.30.223.248+bcom-0ubuntu5 and sudo ubuntu-drivers still only shows
intel-microcode.

-- 
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:
  New

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-22 Thread Dave Morley
I can however at least install the package in the live session now with
sudo apt install bcmwl-kernel-sources

-- 
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:
  New

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 1498074] Re: Package is not being installed if you install from a usb pendrive created from disks

2015-09-21 Thread Dave Morley
** Attachment added: "nobcmwl.png"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1498074/+attachment/4470437/+files/nobcmwl.png

** Description changed:

  STEPS:
  Pre-requisite: Laptop with bcmwl supported chipset, intel based macs or dell 
xps for example.
  
- 1. Grab the latest daily image from cdimages
+ 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

-- 
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:
  New

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 1498074] [NEW] Package is not being installed if you install from a usb pendrive created from disks

2015-09-21 Thread Dave Morley
Public bug reported:

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

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

** Attachment added: "sources.list"
   
https://bugs.launchpad.net/bugs/1498074/+attachment/4470436/+files/sources.list

-- 
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:
  New

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 1495441] Re: Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered

2015-09-14 Thread Dave Morley
** Package changed: linux (Ubuntu) => unity8 (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/1495441

Title:
  Oom killer can trigger a crash which will cause a lot of io on the cpu
  stopping the call from being answered

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  STEPS:
  1. On a BQ device install the terminal and d-day tower defense
  2. Open the terminal and run free -h
  3. Open d-day and start the game playing
  4. Flip back to the terminal and run free -h again
  5. There should be about 21MB free
  6. Put the phone to sleep
  7. Now call the phone
  8. As the dialer app is opened it looks like the oom killer kills the open 
apps which in turn triggers apport which then hog the cpu

  EXPECT:
  I expect to the able to answer the call with no issues

  ACTUAL:
  The phone can lock up completely making it impossible to answer the call, the 
call goes to answering machine and when the phone is able to be used you get 
the missed call notification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495441/+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 1495441] [NEW] Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered

2015-09-14 Thread Dave Morley
Public bug reported:

STEPS:
1. On a BQ device install the terminal and d-day tower defense
2. Open the terminal and run free -h
3. Open d-day and start the game playing
4. Flip back to the terminal and run free -h again
5. There should be about 21MB free
6. Put the phone to sleep
7. Now call the phone
8. As the dialer app is opened it looks like the oom killer kills the open apps 
which in turn triggers apport which then hog the cpu

EXPECT:
I expect to the able to answer the call with no issues

ACTUAL:
The phone can lock up completely making it impossible to answer the call, the 
call goes to answering machine and when the phone is able to be used you get 
the missed call notification.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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


** Tags: qa-manual-testing

** Tags added: qa-manual-testing

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

Title:
  Oom killer can trigger a crash which will cause a lot of io on the cpu
  stopping the call from being answered

Status in Canonical System Image:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  STEPS:
  1. On a BQ device install the terminal and d-day tower defense
  2. Open the terminal and run free -h
  3. Open d-day and start the game playing
  4. Flip back to the terminal and run free -h again
  5. There should be about 21MB free
  6. Put the phone to sleep
  7. Now call the phone
  8. As the dialer app is opened it looks like the oom killer kills the open 
apps which in turn triggers apport which then hog the cpu

  EXPECT:
  I expect to the able to answer the call with no issues

  ACTUAL:
  The phone can lock up completely making it impossible to answer the call, the 
call goes to answering machine and when the phone is able to be used you get 
the missed call notification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495441/+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 1479438] [NEW] IN CAR: Battery levels not shared via bluetooth for in car experience

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

1. Connect the DUT to the car
2. On the display panel the battery always shows full

EXPECTED:
I expect to see the actual level of the battery on the device

ACTUAL:
The display always shows the battery at 100% I assume the default if no info is 
available.

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479438/+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 1479453] Re: IN CAR: Bluetooth is connected but occasionally a call comes in and there is no audio on bluetooth

2015-07-29 Thread Dave Morley
** Summary changed:

- IN CAR: Bluetooth is connect but occasionally a call comes in and there is no 
audio on bluetooth
+ IN CAR: Bluetooth is connected but occasionally a call comes in and there is 
no audio on 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/1479453

Title:
  IN CAR: Bluetooth is connected but occasionally a call comes in and
  there is no audio on bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT, a second device and a car that supports bluetooth phones 
(Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Receive multiple calls

  EXPECTED:
  I expect the call audio to always be routed through the car audio and be 
audible

  ACTUAL:
  After a number of calls all of a sudden you can accept the call but you get 
no audio from the call at all, the mic is still working as expected.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479453/+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 1479440] [NEW] IN CAR: Missed calls are not shared with the car via bluetooth

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirements: DUT, a secondary device and a car with bluetooth phone 
capabilities (Skoda Superb 2013 in my case)

1. Connect the DUT to the car
2. Using the menu system in the car navigate to missed calls
3. Message There are no missed calls
4. Call the DUT from the secondary device
5. Hang up the secondary device once the call is received
6. Check the missed calls log again (shows on the phone but not on the car)

EXPECTED:
I expect to see a list of missed calls

ACTUAL:
No missed call are available 

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Missed calls are not shared with the car via bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT, a secondary device and a car with bluetooth phone 
capabilities (Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Using the menu system in the car navigate to missed calls
  3. Message There are no missed calls
  4. Call the DUT from the secondary device
  5. Hang up the secondary device once the call is received
  6. Check the missed calls log again (shows on the phone but not on the car)

  EXPECTED:
  I expect to see a list of missed calls

  ACTUAL:
  No missed call are available 

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479440/+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 1479445] [NEW] IN CAR: Signal Strength not shown in car display

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirement: DUT with active sim and car that supports Bluetooth phones (Skoda 
Superb 2013 in my case)

1. Connect the DUT to the car
2. Check the console display for the strength of signal

EXPECTED:
I expect the display to show a similar strength to that on the phone

ACTUAL:
The signal strength is always at 0% however the display does show the Network 
connected to so there is some sort of feedback via bluetooth that there is a 
connection.

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Signal Strength not shown in car display

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirement: DUT with active sim and car that supports Bluetooth phones 
(Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Check the console display for the strength of signal

  EXPECTED:
  I expect the display to show a similar strength to that on the phone

  ACTUAL:
  The signal strength is always at 0% however the display does show the Network 
connected to so there is some sort of feedback via bluetooth that there is a 
connection.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479445/+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 1479449] [NEW] IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirements: DUT, a second device, a car with bluetooth phone support (Skoda 
Supberb 2013 in my case)

1. Connect the DUT to the car
2. From the second device call the car
3. The ringer starts

EXPECTED:
I expect all audio to come through the car speakers

ACTUAL:
The ringer is routed through the loud speaker of the phone not the car audio

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Bluetooth connected but ring happens through the DUT and not
  the Bluetooth audio

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT, a second device, a car with bluetooth phone support (Skoda 
Supberb 2013 in my case)

  1. Connect the DUT to the car
  2. From the second device call the car
  3. The ringer starts

  EXPECTED:
  I expect all audio to come through the car speakers

  ACTUAL:
  The ringer is routed through the loud speaker of the phone not the car audio

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479449/+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 1479453] [NEW] IN CAR: Bluetooth is connect but occasionally a call comes in and there is no audio on bluetooth

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirements: DUT, a second device and a car that supports bluetooth phones 
(Skoda Superb 2013 in my case)

1. Connect the DUT to the car
2. Receive multiple calls

EXPECTED:
I expect the call audio to always be routed through the car audio and be audible

ACTUAL:
After a number of calls all of a sudden you can accept the call but you get no 
audio from the call at all, the mic is still working as expected.

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Bluetooth is connect but occasionally a call comes in and
  there is no audio on bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT, a second device and a car that supports bluetooth phones 
(Skoda Superb 2013 in my case)

  1. Connect the DUT to the car
  2. Receive multiple calls

  EXPECTED:
  I expect the call audio to always be routed through the car audio and be 
audible

  ACTUAL:
  After a number of calls all of a sudden you can accept the call but you get 
no audio from the call at all, the mic is still working as expected.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479453/+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 1479442] [NEW] IN CAR: Previous Calls log is not shown in the car display

2015-07-29 Thread Dave Morley
Public bug reported:

STEPS:
Requirements: DUT a list of previous calls and a car that support bluetooth 
phones (Skoda Superb 2013 in my case)

1. Connect DUT to the car
2. In the car menu navigate to previous calls log

EXPECTED:
I expect to see a list of past calls similar to those I see on the phone itself

ACTUAL:
Car shows no previous calls log at all

VERSIONS:
current build number: 71
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-07-28 18:01:08
version version: 71
version ubuntu: 20150728
version device: 20150709-8965e37
version custom: 20150716-819-8-42

MODIFICATIONS:
Installation of silo19 for in car bt fix

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


** Tags: qa-manual-testing

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

Title:
  IN CAR: Previous Calls log is not shown in the car display

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: DUT a list of previous calls and a car that support bluetooth 
phones (Skoda Superb 2013 in my case)

  1. Connect DUT to the car
  2. In the car menu navigate to previous calls log

  EXPECTED:
  I expect to see a list of past calls similar to those I see on the phone 
itself

  ACTUAL:
  Car shows no previous calls log at all

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479442/+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 1432788] [NEW] Race in vivid means sometimes bluetooth is no available

2015-03-16 Thread Dave Morley
Public bug reported:

STEPS:
1. Flash a fresh image of vivid on a krillin device
2. Check if bluetooth is on
3. Reboot

EXPECTED:
I always expect bluetooth to be on

ACTUAL:
Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how 
ever it wouldn't connect to anything.

** Affects: bluez (Ubuntu)
 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/1432788

Title:
  Race in vivid means sometimes bluetooth is no available

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a fresh image of vivid on a krillin device
  2. Check if bluetooth is on
  3. Reboot

  EXPECTED:
  I always expect bluetooth to be on

  ACTUAL:
  Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how 
ever it wouldn't connect to anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1432788/+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 1423643] [NEW] Trusty.2 bcmwl-kernel-source is not installing on hwe kernel on macs

2015-02-19 Thread Dave Morley
Public bug reported:

STEPS:
1. Insert cd in macbook pro 2011
2. Select install
3. Select 3rd party drivers
4. Complete the install
5. Reboot
6. In the installed system do dpkg -l | grep bcmwl-kernel-source
7. Note wifi is disabled
8. Insert the cd again enable the cd as a package source
9. Try and install the package from additional software
10. Connect and ethernet cable and try and install the software

EXPECTED:
I expect to have a system installed with the bcmwl driver installed and wifi 
enable as with trusty and trusty.1

ACTUAL:
I can not install the driver, the additional software page locks up if I try 
and install the driver from the cd, It seems to install from the internet 
source but on reboot there is an instant crash reported and there is still no 
internet.

** Affects: bcmwl (Ubuntu)
 Importance: Critical
 Status: New

** Changed in: bcmwl (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  Trusty.2 bcmwl-kernel-source is not installing on hwe kernel on macs

Status in bcmwl package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Insert cd in macbook pro 2011
  2. Select install
  3. Select 3rd party drivers
  4. Complete the install
  5. Reboot
  6. In the installed system do dpkg -l | grep bcmwl-kernel-source
  7. Note wifi is disabled
  8. Insert the cd again enable the cd as a package source
  9. Try and install the package from additional software
  10. Connect and ethernet cable and try and install the software

  EXPECTED:
  I expect to have a system installed with the bcmwl driver installed and wifi 
enable as with trusty and trusty.1

  ACTUAL:
  I can not install the driver, the additional software page locks up if I try 
and install the driver from the cd, It seems to install from the internet 
source but on reboot there is an instant crash reported and there is still no 
internet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1423643/+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

2015-01-22 Thread Dave Morley
Mathieu I have pressed the connect button on the phone in setting
bluetooth (s10 the device) nothing happens, I have pressed buttons on
the speaker and nothing happens, the speakers ready to pair is done
automatically on power on so unless it finds a thing it has previously
connected to it will sit there beeping at you till the sun goes down or
the battery runs out :)

Nothing seems to allow the music to transfer back to the speaker unless
I forget it and re pair it from fresh then it works fine till my next
meal time :)

-- 
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 1412419] Re: Visibility issues on rtm

2015-01-19 Thread Dave Morley
** Summary changed:

- Vissibility issues on rtm
+ Visibility issues on rtm

-- 
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 1412419] [NEW] Vissibility issues on rtm

2015-01-19 Thread Dave Morley
Public bug reported:

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. 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.

** Affects: bluez (Ubuntu)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
 Status: New


** Tags: qa-sanity

** Changed in: bluez (Ubuntu)
   Importance: Undecided = Critical

-- 
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:
  Vissibility 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. 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 1412419] Re: Vissibility issues on rtm

2015-01-19 Thread Dave Morley
Set to critical due to potential security risk.

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

Title:
  Vissibility 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. 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 1412419] Re: Vissibility issues on rtm

2015-01-19 Thread Dave Morley
** Description changed:

  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. Flash one phone so it has no record of the other
+ 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.

-- 
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:
  Vissibility 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 1379485] [NEW] On krillin only 1 sim connects to the bluetooth device meaning only that sim rings on both device and bt headset

2014-10-09 Thread Dave Morley
Public bug reported:

STEPS:
1. Have a device with 2 sim cards
2. Connect to a bluetooth car/headset
(car is better it shows the network you are connected to)
3. Call sim number one (rings on phone but not bt device)
4. Call sim number two (rings on phone and bt device)

EXPECTED:
In both situations you expect the call to trigger the ringer on both of the 
sims numbers

ACTUAL:
For me only sim number 2 triggers the ringer on the device and the mobile.

** Affects: bluez (Ubuntu)
 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/1379485

Title:
  On krillin only 1 sim connects to the bluetooth device meaning only
  that sim rings on both device and bt headset

Status in “bluez” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Have a device with 2 sim cards
  2. Connect to a bluetooth car/headset
  (car is better it shows the network you are connected to)
  3. Call sim number one (rings on phone but not bt device)
  4. Call sim number two (rings on phone and bt device)

  EXPECTED:
  In both situations you expect the call to trigger the ringer on both of the 
sims numbers

  ACTUAL:
  For me only sim number 2 triggers the ringer on the device and the mobile.

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

2014-07-30 Thread Dave Morley
** Tags added: qa-daily-testing rtm14

** Tags added: rtm-blocker

-- 
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:
  In Progress

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 0
  Jan 

[Kernel-packages] [Bug 1346441] Re: Bluetooth doesn't transfer audio on reconnects

2014-07-30 Thread Dave Morley
** Tags added: qa-daily-testing rtm14

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

Title:
  Bluetooth doesn't transfer audio on reconnects

Status in “bluez” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Turn on your bluetooth speaker
  2. Open the settings app
  3. Open the bluetooth section
  4. Wait for the scan to pick the speaker
  5. Connect to it
  6. Play some music
  7. Note music plays through the speaker as expected.
  8. Reboot the phone
  9. On a sucessful reconnect to the speaker play some music again
  10. This time it plays through the Loud Speaker on the phone.
  11. Open settings app
  12. Goto bluetooth
  13. Disconnect from the speaker and then reconnect
  14. Now play the music
  15. now it plays through the speaker once more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu17
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Mon Jul 21 19:18:27 2014
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140721-020205)
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcKernelCmdLine: console=ttyHSL0,115200,n8 androidboot.hardware=mako 
lpj=67677 user_debug=31 uart_console=enable lcd_maker_id=primary lge.hreset=off 
lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 
androidboot.emmc=true androidboot.serialno=01c7d0fad74c8ee3 
androidboot.bootloader=MAKOZ30d androidboot.baseband=mdm bootreason=reboot
  ProcModules:
   
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  hciconfig:
   hci0:Type: BR/EDR  Bus: UNKNOWN
BD Address: 98:D6:F7:32:C5:59  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:0 acl:113 sco:0 events:25027 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
  syslog: Jul 21 18:07:47 ubuntu-phablet bluetoothd[2456]: Discovery session 
0xb8093a60 with :1.72 activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1346441/+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 1346441] [NEW] Bluetooth doesn't transfer audio on reconnects

2014-07-21 Thread Dave Morley
Public bug reported:

STEPS:
1. Turn on your bluetooth speaker
2. Open the settings app
3. Open the bluetooth section
4. Wait for the scan to pick the speaker
5. Connect to it
6. Play some music
7. Note music plays through the speaker as expected.
8. Reboot the phone
9. On a sucessful reconnect to the speaker play some music again
10. This time it plays through the Loud Speaker on the phone.
11. Open settings app
12. Goto bluetooth
13. Disconnect from the speaker and then reconnect
14. Now play the music
15. now it plays through the speaker once more.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu17
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.4-0ubuntu2
Architecture: armhf
Date: Mon Jul 21 19:18:27 2014
InstallationDate: Installed on 2014-07-21 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140721-020205)
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
ProcKernelCmdLine: console=ttyHSL0,115200,n8 androidboot.hardware=mako 
lpj=67677 user_debug=31 uart_console=enable lcd_maker_id=primary lge.hreset=off 
lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 
androidboot.emmc=true androidboot.serialno=01c7d0fad74c8ee3 
androidboot.bootloader=MAKOZ30d androidboot.baseband=mdm bootreason=reboot
ProcModules:
 
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
hciconfig:
 hci0:  Type: BR/EDR  Bus: UNKNOWN
BD Address: 98:D6:F7:32:C5:59  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:0 acl:113 sco:0 events:25027 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
syslog: Jul 21 18:07:47 ubuntu-phablet bluetoothd[2456]: Discovery session 
0xb8093a60 with :1.72 activated

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


** Tags: apport-bug armhf utopic

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

Title:
  Bluetooth doesn't transfer audio on reconnects

Status in “bluez” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Turn on your bluetooth speaker
  2. Open the settings app
  3. Open the bluetooth section
  4. Wait for the scan to pick the speaker
  5. Connect to it
  6. Play some music
  7. Note music plays through the speaker as expected.
  8. Reboot the phone
  9. On a sucessful reconnect to the speaker play some music again
  10. This time it plays through the Loud Speaker on the phone.
  11. Open settings app
  12. Goto bluetooth
  13. Disconnect from the speaker and then reconnect
  14. Now play the music
  15. now it plays through the speaker once more.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu17
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Mon Jul 21 19:18:27 2014
  InstallationDate: Installed on 2014-07-21 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140721-020205)
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  ProcKernelCmdLine: console=ttyHSL0,115200,n8 androidboot.hardware=mako 
lpj=67677 user_debug=31 uart_console=enable lcd_maker_id=primary lge.hreset=off 
lge.reset=mode_reset gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 
androidboot.emmc=true androidboot.serialno=01c7d0fad74c8ee3 
androidboot.bootloader=MAKOZ30d androidboot.baseband=mdm bootreason=reboot
  ProcModules:
   
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  hciconfig:
   hci0:Type: BR/EDR  Bus: UNKNOWN
BD Address: 98:D6:F7:32:C5:59  ACL MTU: 1024:6  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN 
RX bytes:0 acl:113 sco:0 events:25027 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
  syslog: Jul 21 18:07:47 ubuntu-phablet bluetoothd[2456]: Discovery session 
0xb8093a60 with :1.72 activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1346441/+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 1265564] Re: Regression: Maguro network-manager disconnects from wifi ap

2014-06-16 Thread Dave Morley
Maguro is nolonger supported so I will cancel this bug off now

** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: linux-maguro (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  Regression: Maguro network-manager disconnects from wifi ap

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux-maguro” package in Ubuntu:
  Invalid

Bug description:
  Over the holiday period I noticed that n-m would sometime show the
  networks available symbol in the indicator rather than the connected
  symbol.  Dragging the indicator down and clicking on the AP you want
  to connect to means that the connection is made again.

  davmor2@boromir:~$ cat syslog | grep Network
  Jan  2 10:28:48 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:48,969 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:28:50 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:50,159 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:28:50 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:50,167 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:31:15 ubuntu-phablet kernel: [   18.351837] type=1400 
audit(1388658675.414:3): apparmor=STATUS operation=profile_load parent=770 
profile=unconfined name=/usr/lib/NetworkManager/nm-dhcp-client.action 
pid=771 comm=apparmor_parser
  Jan  2 10:31:15 ubuntu-phablet kernel: [   18.366210] type=1400 
audit(1388658675.421:5): apparmor=STATUS operation=profile_replace 
parent=770 profile=unconfined 
name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=771 
comm=apparmor_parser
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info NetworkManager 
(version 0.9.8.4) is starting...
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info Read config file 
/etc/NetworkManager/NetworkManager.conf
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info WEXT support is 
enabled
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]: info DNS: loaded plugin 
dnsmasq
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
init!
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
update_system_hostname
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]: Error: ignoring 
out-of-block data 'source-directory /etc/network/interfaces.d'
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPluginIfupdown: 
management mode: unmanaged
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/p2p0,
 iface: p2p0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/p2p0,
 iface: p2p0): no ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0,
 iface: wlan0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0,
 iface: wlan0): no ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ifb0, iface: ifb0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ifb0, iface: ifb0): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ifb1, iface: ifb1)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ifb1, iface: ifb1): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0): no 
ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/lo, iface: lo)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/rmnet0, iface: rmnet0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 

[Kernel-packages] [Bug 1276674] Re: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm

2014-03-31 Thread Dave Morley
This is fixed and working for me on 31/03/2014

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: linux (Ubuntu)
   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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276674/+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 1276674] Re: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm

2014-02-05 Thread Dave Morley
In nvidia settings on prime systems you have Prime Profiles.  The
initial report was with the settings on intel(Power Saving Mode).  I
changed this setting to Nvidia (Performance Mode) to see if it made a
difference it didn't.  The second log is with the Settings on
Performance for comparison.

** Attachment added: nvidia-bug-report-1.log.gz
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+attachment/3970002/+files/nvidia-bug-report-1.log.gz

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

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Incomplete
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970034/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970044/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970045/+files/PulseList.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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970048/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1276674/+attachment/3970046/+files/RfKill.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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1276674/+attachment/3970047/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970049/+files/WifiSyslog.txt

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

** Description changed:

  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.
  
  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.
+ 
+ 
+ Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  davmor22204 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-7-generic N/A
-  linux-backports-modules-3.13.0-7-generic  N/A
-  linux-firmware1.123
+  linux-restricted-modules-3.13.0-7-generic N/A
+  linux-backports-modules-3.13.0-7-generic  N/A
+  linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: 

[Kernel-packages] [Bug 1276674] Re: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm

2014-02-05 Thread Dave Morley
This issue only seems to be reproducible if you are on the Discreet
hardware.  If you are on the intel only gfx there is nolonger an issue.

** Tags added: apport-collected

** Description changed:

  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.
  
  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.13.2-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  davmor22204 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
+ InstallationDate: Installed on 2014-01-10 (26 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
+ MachineType: LENOVO 2099
+ Package: nvidia-graphics-drivers-331
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-7-generic N/A
+  linux-backports-modules-3.13.0-7-generic  N/A
+  linux-firmware1.123
+ Tags:  trusty
+ Uname: Linux 3.13.0-7-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/23/2012
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 5DCN89WW(V8.00)
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: INVALID
+ dmi.board.vendor: LENOVO
+ dmi.board.version: 3193WIN8 STD MLT
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo IdeaPad Y580
+ dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
+ dmi.product.name: 2099
+ dmi.product.version: Lenovo IdeaPad Y580
+ dmi.sys.vendor: LENOVO

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

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1276674] ProcEnviron.txt

2014-02-05 Thread Dave Morley
apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970042/+files/ProcEnviron.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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970043/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1276674/+attachment/3970039/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1276674/+attachment/3970040/+files/Lsusb.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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970041/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970035/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1276674/+attachment/3970037/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

2014-02-05 Thread Dave Morley
apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1276674/+attachment/3970036/+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/1276674

Title:
  Suspend works flawlessly however resume leads to a checker board
  screen rather that lightdm

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon installing nvidia-331 and nvidia-prime if I suspend the laptop
  everything goes down as expected.  However upon resume I get a
  checkerboard style page rather than the lightdm login page.

  If I disable the nvidia stuff from the optimus box and just have the
  intel gfx running suspend and resume work again.

  
  Please note that the issue only seems to happen when the nvidia discreet gfx 
card is in use.  If the device is switched to intel only then it doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  Date: Wed Feb  5 15:57:56 2014
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davmor22204 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=62804170-83e5-4cc9-9a1f-98ddc77cd5b4
  InstallationDate: Installed on 2014-01-10 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109)
  MachineType: LENOVO 2099
  Package: nvidia-graphics-drivers-331
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed 
root=UUID=587783ba-5cab-4b34-8a3d-77044efe5185 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-7-generic N/A
   linux-backports-modules-3.13.0-7-generic  N/A
   linux-firmware1.123
  Tags:  trusty
  Uname: Linux 3.13.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN89WW(V8.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN89WW(V8.00):bd08/23/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: 2099
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276674/+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 1265564] Re: Regression: Maguro network-manager disconnects from wifi ap

2014-01-02 Thread Dave Morley
Joesph I've tagged it r100 as it was around the weekend that I noticed
it.

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

Title:
  Regression: Maguro network-manager disconnects from wifi ap

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Over the holiday period I noticed that n-m would sometime show the
  networks available symbol in the indicator rather than the connected
  symbol.  Dragging the indicator down and clicking on the AP you want
  to connect to means that the connection is made again.

  davmor2@boromir:~$ cat syslog | grep Network
  Jan  2 10:28:48 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:48,969 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:28:50 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:50,159 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:28:50 ubuntu-phablet ubuntu-download-manager[7598]: 2014-01-02 
10:28:50,167 - DEBUG - Network is accessible, performing download request 
  Jan  2 10:31:15 ubuntu-phablet kernel: [   18.351837] type=1400 
audit(1388658675.414:3): apparmor=STATUS operation=profile_load parent=770 
profile=unconfined name=/usr/lib/NetworkManager/nm-dhcp-client.action 
pid=771 comm=apparmor_parser
  Jan  2 10:31:15 ubuntu-phablet kernel: [   18.366210] type=1400 
audit(1388658675.421:5): apparmor=STATUS operation=profile_replace 
parent=770 profile=unconfined 
name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=771 
comm=apparmor_parser
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info NetworkManager 
(version 0.9.8.4) is starting...
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info Read config file 
/etc/NetworkManager/NetworkManager.conf
  Jan  2 10:31:16 ubuntu-phablet NetworkManager[927]: info WEXT support is 
enabled
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]: info DNS: loaded plugin 
dnsmasq
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
init!
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
update_system_hostname
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]: Error: ignoring 
out-of-block data 'source-directory /etc/network/interfaces.d'
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPluginIfupdown: 
management mode: unmanaged
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/p2p0,
 iface: p2p0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/p2p0,
 iface: p2p0): no ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0,
 iface: wlan0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0,
 iface: wlan0): no ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ifb0, iface: ifb0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ifb0, iface: ifb0): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ifb1, iface: ifb1)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ifb1, iface: ifb1): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ip6tnl0, iface: ip6tnl0): no 
ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/lo, iface: lo)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown 
configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/rmnet0, iface: rmnet0)
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/rmnet0, iface: rmnet0): no 
ifupdown configuration found.
  Jan  2 10:31:17 ubuntu-phablet NetworkManager[927]:SCPlugin-Ifupdown: 

[Kernel-packages] [Bug 1234361] Re: Bluetooth panel not getting scan results

2013-12-29 Thread Dave Morley
Confirming this is now fixed for me on maguro

I will file a new bug for the fact that my headset doesn't work :)

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

Title:
  Bluetooth panel not getting scan results

Status in “bluez” package in Ubuntu:
  Fix Released
Status in “lxc-android-config” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  Mako running build 76

  The scan does not detect the bluetooth headset.
  hcitool scan does find it

  Scanning ...
00:18:16:20:00:FE   RF-MAB2
10:40:F3:7E:12:B1   ubuntu-0

  bt-monitor output is (note the Name and Alias and the Glib assertion)

  [Adapter: ubuntu-phablet-0 (98:D6:F7:31:C6:A6)] Device found:
  [00:18:16:20:00:FE]

  (bt-monitor:4149): GLib-GObject-CRITICAL **: g_value_get_string: assertion 
'G_VALUE_HOLDS_STRING (value)' failed
Name: (null)
Alias: 00-18-16-20-00-FE
Address: 00:18:16:20:00:FE
Icon: audio-card
Class: 0x240404
LegacyPairing: 0
Paired: 0
RSSI: -58

  bt-monitor on desktop:

  [Adapter: pat-samsung-0 (88:53:2E:1B:4C:D3)] Device found:
  [00:18:16:20:00:FE]
Name: RF-MAB2
Alias: RF-MAB2
Address: 00:18:16:20:00:FE
Icon: audio-card
Class: 0x240404
LegacyPairing: 1
Paired: 0
RSSI: -48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1234361/+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