date:20160514

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Fails to resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Resuming from suspend used to work previously in 16.04.

  On resume I see a blank screen and nothing seems to respond. I've
  tried Ctrl+Alt+F1 and then Ctrl+Alt+Delete. Also tried the power
  button. No response.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shahar 2292 F pulseaudio
   /dev/snd/controlC0:  shahar 2292 F pulseaudio
   /dev/snd/controlC2:  shahar 2292 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Feb  9 22:51:40 2016
  HibernationDevice: RESUME=UUID=f2bd5594-8447-422c-a345-492ede4de1d9
  InstallationDate: Installed on 2010-10-12 (1946 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X10SRA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/root 
ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (88 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd11/27/2014:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788/+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 1557278] Re: dm-crypt

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  dm-crypt

Status in linux package in Ubuntu:
  Expired

Bug description:
  aes-xts-128 mode bit not supported in this kernel
  so existing encrypted drive (/) could not be mounted

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-83-generic 3.13.0-83.127
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pavel  2048 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 15 05:21:57 2016
  MachineType: LENOVO 20206
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=UUID=0d637c5b-aeab-4085-80af-e1988b0c8eb7 ro splash quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  StagingDrivers: keucr
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H9ET74WW(1.11)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20206
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn20206:pvrLenovoB590:rvnLENOVO:rn20206:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20206
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557278/+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 1581904] [NEW] Pools get lots on reboot

2016-05-14 Thread Lisio

Public bug reported:

System:

ubuntu: 16.04
zfsutils-linux: 0.6.5.6-0ubuntu8

Create sparse files and create pool:

root@server:/# fallocate -l 100G /web/lxd/100gb.01
root@server:/# fallocate -l 100G /web/lxd/100gb.02
root@server:/# zpool create lxd /web/lxd/100gb.01
root@server:/# zpool add lxd /web/lxd/100gb.02

Check:

root@server:/# zpool list
NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
lxc199G77K   199G - 0% 0%  1.00x  ONLINE  -

After reboot:

root@server:/etc/apt# zpool list
no pools available

Try to create another pool with that files:

root@server:/# zpool create lxc /web/lxd/100gb.01 /web/lxd/100gb.02
invalid vdev specification
use '-f' to override the following errors:
/web/lxd/100gb.01 is part of potentially active pool 'lxd'
/web/lxd/100gb.02 is part of potentially active pool 'lxd'

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: zfsutils-linux 0.6.5.6-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun May 15 05:53:51 2016
InstallationDate: Installed on 2016-04-21 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Pools get lots on reboot

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  System:

  ubuntu: 16.04
  zfsutils-linux: 0.6.5.6-0ubuntu8

  Create sparse files and create pool:

  root@server:/# fallocate -l 100G /web/lxd/100gb.01
  root@server:/# fallocate -l 100G /web/lxd/100gb.02
  root@server:/# zpool create lxd /web/lxd/100gb.01
  root@server:/# zpool add lxd /web/lxd/100gb.02

  Check:

  root@server:/# zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxc199G77K   199G - 0% 0%  1.00x  ONLINE  -

  After reboot:

  root@server:/etc/apt# zpool list
  no pools available

  Try to create another pool with that files:

  root@server:/# zpool create lxc /web/lxd/100gb.01 /web/lxd/100gb.02
  invalid vdev specification
  use '-f' to override the following errors:
  /web/lxd/100gb.01 is part of potentially active pool 'lxd'
  /web/lxd/100gb.02 is part of potentially active pool 'lxd'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 05:53:51 2016
  InstallationDate: Installed on 2016-04-21 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1581904/+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 1567558] Re: ZFS is confused by user namespaces (uid/gid mapping) when used with acltype=posixac

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  ZFS is confused by user namespaces (uid/gid mapping) when used with
  acltype=posixac

Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Confirmed

Bug description:
  This report is copy/paste from the following upstream issue:
  https://github.com/zfsonlinux/zfs/issues/4177

  I was asked to file a matching Ubuntu bug for tracking.

  
  Hello,

  # First a quick introduction to the world of containers

  I'm the project leader for LXC and LXD, working on containers on
  Linux. We now extensively use the user namespaces to provide an extra
  layer of security in Linux containers.

  The user namespace allows one to map a range of uid and gid from the
  host or parent namespace into another range of uid and gid of a new
  namespace.

  Typically what's done is that 65536 uids and gids are set aside per
  non-system users on the host. Those users through a couple of setuid
  helpers (newuidmap and newgidmap) can then setup a uid and gid map for
  their processes. Their 65536 allocation is therefore mapped from
  uid/gid 0 to 65536 of the new namespace, providing a POSIX-compatible
  environment.

  That means that given a user on the host with uid and gid range 10
  through 165536, uid 100 in their container will be mapped to uid
  100100 outside of it.

  # The problem with ZFS

  When using ZFS with acltype=posixacl and an ACL entry on the host set
  for a uid (or gid) that's then mapped into the container, the
  container doesn't see the right mapped value when querying the acl
  from inside the namespace.

  # Example with zfs (broken)

  root@dakara:~# zfs create lxd/test -o mountpoint=/tmp/test
  root@dakara:~# zfs set acltype=posixacl lxd/test
  root@dakara:~# cd /tmp/test/
  root@dakara:/tmp/test# mkdir a
  root@dakara:/tmp/test# setfacl -m default:user:100100:rwX a
  root@dakara:/tmp/test# setfacl -m user:100100:rwX a
  root@dakara:/tmp/test# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test# lxc-usernsexec -m u:0:10:65536 -m g:0:10:65536 
-- /bin/bash
  root@dakara:/tmp/test (in userns)# ls -lh
  total 512
  drwxrwxr-x+ 2 nobody nogroup 2 Jan  7 22:19 a

  root@dakara:/tmp/test (in userns)# getfacl -n a
  # file: a
  # owner: nobody
  # group: nogroup
  user::rwx
  user:4294967295:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:4294967295:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Example with ext4 (working)

  root@dakara:/tmp/test.ext4# mkdir a

  root@dakara:/tmp/test.ext4# setfacl -m default:user:100100:rwX a

  root@dakara:/tmp/test.ext4# setfacl -m user:100100:rwX a

  root@dakara:/tmp/test.ext4# getfacl a
  # file: a
  # owner: root
  # group: root
  user::rwx
  user:100100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  root@dakara:/tmp/test.ext4# lxc-usernsexec -m u:0:10:65536 -m 
g:0:10:65536 -- /bin/bash
  root@dakara:/tmp/test.ext4 (in userns)# ls -lh
  total 4.0K
  drwxrwxr-x+ 2 nobody nogroup 4.0K Jan  7 22:22 a

  root@dakara:/tmp/test.ext4 (in userns)# getfacl -n a
  # file: a
  # owner: 65534
  # group: 65534
  user::rwx
  user:100:rwx
  group::r-x
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:100:rwx
  default:group::r-x
  default:mask::rwx
  default:other::r-x

  # Environment

  This was noticed on Ubuntu 14.04 using the zfs stable PPA. I first
  found it in production environments first with file servers
  misbehaving due to the problem, then reproduced it on my development
  systems.

  The zfs version here is 0.6.5.3-1~trusty and I've seen this on 3.13,
  3.16, 3.19 and 4.2 kernels (not that it should matter, the dkms code
  was the same). zfs-dkms is at 2.53-zfs1.

  The lxc-usernsexec helper tool I'm using there comes from the LXC
  package in Ubuntu. It essentially causes a call to fork() followed by
  a call to unshare(CLONE_NEWUSER), then calls the newuidmap and
  newgidmap setuid helpers with the provided map so that the namespace
  can be configured properly.

  You could reproduce something similar using the simple unshare tool
  and manual writes to /proc/PID/{u,g}id_map

To manage not

[Kernel-packages] [Bug 1552504] Re: clicking noise on acer 131t-c1yf

2016-05-14 Thread bhikkhu subhuti

Switched to Mate 16.04 since the clicking noise is present in Lubuntu after
installing pulseaudio for Skype to run.
The Noise is only in the left speaker.
Mute fixes it but not acceptable as a fix.
Changing the balance to the right speaker DOES NOT FIX THIS (strange).
Disabling the microphone does not fix this either.

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

Title:
clicking noise on acer 131t-c1yf

Status in linux package in Ubuntu:
Incomplete

Bug description:
My machine is solid state.
I updated the intel graphics driver
I update a few days ago via ubuntu udpater

There is a subtle clicking noise coming from the left speaker.

The mint 17 usb makes the noise too and then warns me that that the graphics
gpu will not be used and then the clicking stops.
ubuntu makes the noise.
Lubuntu 16.04 does not make the noise, until I installed pulseaudio.
before that, it would make the noise if I installed and ran, metacity and or
audacity.

Windows 10 does not make the noise.

I saw some comments on askubuntu.com
I think it is a conflict with the nouveau driver not loading properly. This
is why the soundcard and graphics affect the problem
Usually, this bug is caused by alsa automute (removed) and power-save for the
sound card. I was unable to set the settings so that the file changes would
"stick" the kernel keeps overwriting the files even if I mark them as nobody
can change.

I posted the links in the comments

I suspect this is a CherryView Bug.

This bug has been reported on ubuntu forums and ask ubuntu and no responses.
This bug still exists for Lubuntu 16.04 with the latest kernel 4.6-rc6
The bios has be downgraded to 1.09 from 1.12 since it did not fix the problem.

Bhikkhu Subhuti

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-27-generic 4.2.0-27.32
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bksubhuti 1067 F pulseaudio
CurrentDesktop: Unity
Date: Fri Mar 4 08:28:59 2016
HibernationDevice: RESUME=UUID=709ea197-e6fb-428b-9c1f-4b258452b10c
InstallationDate: Installed on 2016-02-04 (29 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire R3-131T
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed
root=UUID=ec51921a-2804-40c5-96f4-9597628656cb ro noprompt persistent quiet
splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.2.0-27-generic N/A
linux-backports-modules-4.2.0-27-generic N/A
linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire R3-131T
dmi.board.vendor: Acer
dmi.board.version: V1.09
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.09:bd07/21/2015:svnAcer:pnAspireR3-131T:pvrV1.09:rvnAcer:rnAspireR3-131T:rvrV1.09:cvnAcer:ct10:cvrV1.09:
dmi.product.name: Aspire R3-131T
dmi.product.version: V1.09
dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552504/+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 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

2016-05-14 Thread Martin Wimpress

My system:

Machine:   System: Intel (portable) product: SharkBay Platform v: 0.1
   Mobo: Topstar model: WhiteTip Mountain1 Fab2 v: Fab2
   Bios: American Megatrends v: 5.6.5 date: 03/17/2015
CPU:   Dual core Intel Core i3-5010U (-HT-MCP-) cache: 3072 KB 
   clock speeds: max: 2100 MHz 1: 2000 MHz 2: 2001 MHz 3: 2000 MHz
   4: 2000 MHz
Graphics:  Card: Intel HD Graphics 5500
   Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
   Resolution: 1920x1080@60.00hz
   GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
   GLX Version: 3.0 Mesa 11.2.1

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

Title:
  Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  *** Temporary workaround ***
  Install Kernel from one of the following locations:
  - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.10-xenial/
  - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/
  ***

  Please inspect duplicate reports for more details:
  Bug #1522922
  Bug #1535048
  Bug #1552304
  Bug #1555158
  Bug #1561729
  Bug #1565234
  Bug #1568599
  Bug #1573392

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-22

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+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 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

2016-05-14 Thread Martin Wimpress

I've installed the following Mainline PPA kernel on today's Ubuntu MATE
16.10

  * http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/

All screen flicker is gone. Just running Ubuntu MATE 16.10, without this
kernel upgrade, the flicker was still present.

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

Title:
  Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  *** Temporary workaround ***
  Install Kernel from one of the following locations:
  - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.10-xenial/
  - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/
  ***

  Please inspect duplicate reports for more details:
  Bug #1522922
  Bug #1535048
  Bug #1552304
  Bug #1555158
  Bug #1561729
  Bug #1565234
  Bug #1568599
  Bug #1573392

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-22

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+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 1510344] Re: Keyboard Backlight Turns on at boot

2016-05-14 Thread Treviño

Mario, as for the lock/idle problem is a different issue.

Things depend also on the hardware and how the kernel supports the notification 
of the kbd backlight changes, but if all is well supported this change should 
help:
https://code.launchpad.net/~3v1n0/unity-settings-daemon/keep-cached-kbd-backlight-updated/+merge/294662

It would be cool if you can try unity-settings-daemon with that patch.

Also, please provide logs when running
 gdbus monitor  --system --dest org.freedesktop.UPower

And:
  udevadm monitor

While you use the keybindings to change the keyboard backlight and
during a lock/idle/suspend cycle.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H: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/dell-sputnik/+bug/1510344/+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 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-05-14 Thread Dario

Thank you to everyone. It worked for me with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nomux=1 i8042.reset
i8042.dumbkbd"

But yes, it's true that about the LED, but personally, I don't really
care.

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  Problem

[Kernel-packages] [Bug 1574211] Re: The "nolapic" boot option causes a kernel panic

2016-05-14 Thread levien

I tested the mainline kernel 4.6.0-040600rc7, and the problem does not
occur with this version. I also tested 4.4.10-040410, in which the
problem did occur. It seems that the problem is indeed fixed in the
upstream 4.6 kernel series, but not in 4.4.

** Tags added: kernel-fixed-upstream

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

** Description changed:

  The kernel parameter "nolapic" causes an unrecoverable kernel panic with
  the 4.4.0-21 kernel in Xenial (16.04). I've verified this on two
  different machines. The 4.2.0-36 kernel from 15.10 boots without
  problems, with the same options. The kernel-logs contain no information
  on the failed boot attempts.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  levien 2391 F pulseaudio
-  /dev/snd/controlC0:  levien 2391 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  levien 2391 F pulseaudio
+  /dev/snd/controlC0:  levien 2391 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Apr 24 11:54:14 2016
  HibernationDevice: RESUME=UUID=df18bec1-dd4a-4c76-bb15-065133e0ffd0
  InstallationDate: Installed on 2016-02-11 (72 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
-  lono wireless extensions.
-  
-  enp0s10   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp0s10   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=c0232677-d281-4213-a6ec-682260728775 ro nolapic quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-36-generic N/A
-  linux-backports-modules-4.2.0-36-generic  N/A
-  linux-firmware1.157
+  linux-restricted-modules-4.2.0-36-generic N/A
+  linux-backports-modules-4.2.0-36-generic  N/A
+  linux-firmware1.157
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  The "nolapic" boot option causes a kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel parameter "nolapic" causes an unrecoverable kernel panic
  with the 4.4.0-21 kernel in Xenial (16.04). I've verified this on two
  different machines. The 4.2.0-36 kernel from 15.10 boots without
  problems, with the same options. The kernel-logs contain no
  information on the failed boot attempts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  levien 2391 F pulseaudio
   /dev/snd/controlC0:  levien 2391 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Apr 24 11:54:14 2016
  HibernationDevice: RESUME=UUID=df18bec1-dd4a-4c76-bb15-065133e0ffd0
  InstallationDate: Installed on 2016-02-11 (72 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   lono wireless extensions.

   enp0s10   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=c0232677-d281-4213-a6ec-682260728775 ro nolapic quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-36-generic N/A
   linux-backports-modules-4.2.0-36-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days

[Kernel-packages] [Bug 1054298] Re: xbacklight doesn't work, but xrandr does and so does /sys/class/backlight

2016-05-14 Thread saeed najdm

for ubuntu 16.04 on HP pavilion dv6 and Nvidia Graphic driver,
the problem is the same.

xbacklight -set 100 > NOT WORKS
xrandr --output LVDS-0 --set Backlight 100> NOT WORKS
xrandr --output LVDS-0 --brightness 1 > WORKS(IT
HAS A DIFFERENT EFFECT!)
echo 1 |sudo tee /sys/class/backlight/acpi_video0/brightness > WORKS

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

Title:
xbacklight doesn't work, but xrandr does and so does
/sys/class/backlight

Status in linux package in Ubuntu:
Expired

Bug description:
Sony Vaio P
Ubuntu Precise and Quantal
kernel 3.5.0
gma500_gfx kernel driver
modesetting xorg driver
Assume the current quantal & quantal-proposed versions of everything.

xbacklight doesn't work. No backlight change, and no output from the program.
"xbacklight" and "xbacklight -get" show nothing, no output from the program
at all.
"xbacklight -set50" and "xbacklight-d :0 -set 50" does nothing nor prints any
output.

However both sysfs and xrandr work fine.

Specifically:
xrandr --verbose lists outputs and shows the main screen has backlight
property,
and "xrandr --output LVDS-0 --set backlight 50" changes the backlight
brightness.

And

"cat /sys/class/backlight/psb-bl/actual_brightness" shows the current
brightness, and
"echo 50 >/sys/class/backlight/psb-bl/brightness" changes the brightness.

I have written the following script to use in place of xbacklight:

http://forums.bodhilinux.com/index.php?/topic/5985-brightness-scripts/page__view__findpost__p__56911

This script, both the sysfs and xrandr methods of it, works fine for me on
the same machine.
(for sysfs, I had to make a udev rule to allow users to write to the sysfs
files, as noted on that page and in the --help output of the script)
It requires zenity for the user interactive options. Not needed for the
non-interactive options.

--
bkw

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

[Kernel-packages] [Bug 1579550] Re: System does not detected Creative SB1550 corectly

2016-05-14 Thread x15

Hello Joseph,
I've installed the latest kernel (4.6.0-040600rc7-generic).
The situation was same I've got a same kernel message: "Audigy2 value: Special 
config."

I've able to get stereo output from the card by enabling a mysterious "Audigy 
A" switch in the alamixer.
The tone control works too.

I think it is not a final solution...

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

Title:
  System does not detected Creative SB1550 corectly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS AMD64 does not detects Creative SB1550 PCI-E sound card.
  This card is not old, I've bought it recently.

  http://en.europe.creative.com/p/sound-blaster/sound-blaster-audigy-rx

  "The Audigy 5/Rx is essentially an Audigy 4 behind a PLX PCIe-
  bridge with an additional TOSLINK output."

  lspci -v:
  02:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
  Subsystem: Creative Labs SB0400 Audigy2 Value
  Flags: bus master, medium devsel, latency 32, IRQ 16
  I/O ports at e000 [size=64]
  Capabilities: [dc] Power Management version 2
  Kernel driver in use: snd_emu10k1
  Kernel modules: snd_emu10k1

  lspci -vn:
  02:00.0 0401: 1102:0008
  Subsystem: 1102:1024
  Flags: bus master, medium devsel, latency 32, IRQ 16
  I/O ports at e000 [size=64]
  Capabilities: [dc] Power Management version 2
  Kernel driver in use: snd_emu10k1
  Kernel modules: snd_emu10k1

  dmesg:
  snd_emu10k1 :02:00.0: Audigy2 value: Special config.

  I've installed all ^alsa-* packages like utils,firmware, etc.
  I've found the "SB1550" string in a 
/lib/modules/4.4.0-22-generic/kernel/sound/pci/emu10k1/snd-emu10k1.ko module...

  There is some links:
  
http://www.linux-hardware-guide.com/in/2014-08-26-creative-sound-blaster-audigy-rx-sb1550-7-1-sound-sound-card-pcie
  http://mailman.alsa-project.org/pipermail/alsa-devel/2015-March/089705.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579550/+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 1581871] Re: CVE-2016-4794

CVE-2016-4794

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1581871] [NEW] CVE-2016-4794

*** This bug is a security vulnerability ***

Public security bug reported:

Unknown description

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status:

[Kernel-packages] [Bug 1581869] Re: CVE-2016-4581

CVE-2016-4581

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1581869] [NEW] CVE-2016-4581

*** This bug is a security vulnerability ***

Public security bug reported:

OOPS when the first propagated copy was a slave

Break-Fix: f2ebb3a921c1ca1e2ddd9242e95a1989a50c4c68
5ec0811d30378ae104f250bfc9b3640242d81e3f

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importa

[Kernel-packages] [Bug 1581866] Re: CVE-2016-4578

CVE-2016-4578

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1579550] Re: System does not detected Creative SB1550 corectly

2016-05-14 Thread x15

Hello Brad,

I've try to collect log but I've got an error message:
$ sudo apport-collect 1579550
ERROR: Could not import module, is a package upgrade in progress?  Error: No 
module named PyQt5.QtCore
after installing python-apport...

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

Title:
  System does not detected Creative SB1550 corectly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS AMD64 does not detects Creative SB1550 PCI-E sound card.
  This card is not old, I've bought it recently.

  http://en.europe.creative.com/p/sound-blaster/sound-blaster-audigy-rx

  "The Audigy 5/Rx is essentially an Audigy 4 behind a PLX PCIe-
  bridge with an additional TOSLINK output."

  lspci -v:
  02:00.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
  Subsystem: Creative Labs SB0400 Audigy2 Value
  Flags: bus master, medium devsel, latency 32, IRQ 16
  I/O ports at e000 [size=64]
  Capabilities: [dc] Power Management version 2
  Kernel driver in use: snd_emu10k1
  Kernel modules: snd_emu10k1

  lspci -vn:
  02:00.0 0401: 1102:0008
  Subsystem: 1102:1024
  Flags: bus master, medium devsel, latency 32, IRQ 16
  I/O ports at e000 [size=64]
  Capabilities: [dc] Power Management version 2
  Kernel driver in use: snd_emu10k1
  Kernel modules: snd_emu10k1

  dmesg:
  snd_emu10k1 :02:00.0: Audigy2 value: Special config.

  I've installed all ^alsa-* packages like utils,firmware, etc.
  I've found the "SB1550" string in a 
/lib/modules/4.4.0-22-generic/kernel/sound/pci/emu10k1/snd-emu10k1.ko module...

  There is some links:
  
http://www.linux-hardware-guide.com/in/2014-08-26-creative-sound-blaster-audigy-rx-sb1550-7-1-sound-sound-card-pcie
  http://mailman.alsa-project.org/pipermail/alsa-devel/2015-March/089705.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579550/+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 1581866] [NEW] CVE-2016-4578

*** This bug is a security vulnerability ***

Public security bug reported:

information leak

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-goldfish (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-lts-quantal (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-lts-raring (Ubuntu Vivid)
 Importa

[Kernel-packages] [Bug 1581865] Re: CVE-2016-3070

CVE-2016-3070

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

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1581865] [NEW] CVE-2016-3070

*** This bug is a security vulnerability ***

Public security bug reported:

Null pointer dereference in trace_writeback_dirty_page()

Break-Fix: - 42cb14b110a5698ccf26ce59c4441722605a3743

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Medium
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-vivid (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Affects: linux-flo (Ubuntu Vivid)
 Importance: Undecided
 Status

[Kernel-packages] [Bug 1579351] Re: /proc/sys/abi/ldt16 does not exist

2016-05-14 Thread 1448412

Hi,

thanks for your response!

I tested

linux-image-4.6.0-040600rc7-generic_4.6.0-040600rc7.201605120803_amd64

=> it also lacks /proc/sys/abi/ldt16.


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

** Tags added: kernel-bug-exists-upstream

** Description changed:

  Hi,
  
  I guess I stumbled upon a VERY old problem;
  
  I can't make some of my windows-programs work, despite they have a gold
  rating in wine.
  
  Some old Windows binaries that include 16-Bit Code need the kernel to
  have echo 1 >> /proc/sys/abi/ldt16 enabled, but that pseudo-file does
  not exist on my 16.04 Ubuntu system.
  
  root@Johnnyfive:~# echo 1 >> /proc/sys/abi/ldt16
  -bash: /proc/sys/abi/ldt16: Datei oder Verzeichnis nicht gefunden
  root@Johnnyfive:~# ls /proc/sys/abi/
  vsyscall32
  
  The issue is discussed in lots of places:
  --> https://lkml.org/lkml/2014/5/7/508
  --> https://forum.winehq.org/viewtopic.php?f=8&t=22700
  --> http://ubuntuforums.org/archive/index.php/t-2228133.html
  
- The issue seems to be a very old regression, a bug on this was filed and 
closed in 2014. 
+ The issue seems to be a very old regression, a bug on this was filed and 
closed in 2014.
  --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328965
  
- So I think that this is a very old and annoying regression that just wont 
stop 
+ So I think that this is a very old and annoying regression that just wont stop
  keep coming back. Could you please include the fix once and for all?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ulrich 1816 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ulrich 1816 F pulseaudio
  CurrentDesktop: LXDE
  Date: Sat May  7 12:36:44 2016
  HibernationDevice: RESUME=UUID=93df4898-fb0b-4278-ade1-ccfffb092022
  InstallationDate: Installed on 2016-04-02 (35 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  enp3s0no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  enp3s0no wireless extensions.
+ 
+  lono wireless extensions.
  MachineType: Shuttle Inc. SX58
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/fivegroup-root ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-21-generic N/A
-  linux-backports-modules-4.4.0-21-generic  N/A
-  linux-firmware1.157
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (12 days ago)
  dmi.bios.date: 03/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: SX58
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: V10
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd03/02/2010:svnShuttleInc.:pnSX58:pvrV10:rvnShuttleInc.:rnSX58:rvrV10:cvnIntel:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SX58
  dmi.product.version: V10
  dmi.sys.vendor: Shuttle Inc.

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

Title:
  /proc/sys/abi/ldt16 does not exist

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I guess I stumbled upon a VERY old problem;

  I can't make some of my windows-programs work, despite they have a
  gold rating in wine.

  Some old Windows binaries that include 16-Bit Code need the kernel to
  have echo 1 >> /proc/sys/abi/ldt16 enabled, but that pseudo-file does
  not exist on my 16.04 Ubuntu system.

  root@Johnnyfive:~# echo 1 >> /proc/sys/abi/ldt16
  -bash: /proc/sys/abi/ldt16: Datei oder Verzeichnis nicht gefunden
  root@Johnnyfive:~# ls /proc/sys/abi/
  vsyscall32

  The issue is discussed in lots of places:
  --> https://lkml.org/lkml/2014/5/7/508
  --> https://forum.winehq.org/viewtopic.php?f=8&t=22700
  --> http://ubuntuforums.org/archive/index.php/t-2228133.html

  The issue seems to be a very old regression, a bug on this was filed and 
closed in 2014.
  --> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328965

  So I think that this is a very old and annoying regression that just wont stop
  keep coming back. Could you please include the fix once and for all

[Kernel-packages] [Bug 1527889] Re: Resolution >1080p (like 1440p) doesn't work on Intel Braswell ( Asrock N3150 )

2016-05-14 Thread Tommy de Neef

I have a Zotac ZBOX nano also with Intel Celeron n3150 which is also
affected by this bug.

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

Title:
  Resolution >1080p (like 1440p) doesn't work on Intel Braswell ( Asrock
  N3150 )

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  It seems that it tries many times display but no result, But 1080p
  works without issue. Not sure if it's some bios settings, now it is in
  UEFI mode. I will investigate it further.

  I turned off the other screen, it doesn't help

  In logs it looks pretty normal, but the screen is turned , but blank
  and the icon of the chainged source is coming from time to time.

  [  1499.601] (II) intel(0): resizing framebuffer to 2560x1440
  [  1499.668] (II) intel(0): switch to mode 2560x1440@60.0 on DP2 using pipe 
0, position (0, 0), rotation normal, reflection none

  The screen is Dell 2713H

  
  However there some errors in log

  Dec 19 15:30:19 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:26 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:26 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:05 stalagnat sudo[5511]:  mastier : TTY=pts/1 ; 
PWD=/home/mastier ; USER=root ; COMMAND=/bin/cat /var/log/Xorg.0.log
  Dec 19 15:32:05 stalagnat sudo[5511]: pam_unix(sudo:session): session opened 
for user root by mastier(uid=0)
  Dec 19 15:32:05 stalagnat sudo[5511]: pam_unix(sudo:session): session closed 
for user root
  Dec 19 15:32:07 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:07 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:21 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:intel_cpu_fifo_underrun_irq_handler 
[i915]] *ERROR* CPU pipe A FIFO underrun
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:06 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:09 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:09 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2016-05-14 Thread Viktor Pal

I'm using 4.6.0 rc6 since about a week and haven't experienced this issue since 
then.
I would treat this as an evidence though. Will be continuing testing with the 
4.6 kernel series.
Installed the kernel from here: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f

[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage

2016-05-14 Thread François Leurent

Same issue here, uname -a
4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 
x86_64 GNU/Linux
free -m
  totalusedfree  shared  buff/cache   available
Mem:   1836  681608  12 1591722
Swap:  1949   01949
(i'll edit this in a few minute, with top result (uptime is 0s)

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

Title:
  kswapd0 100% CPU usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+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 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2016-05-14 Thread Chad Germann

I am experiencing this on a Logitech K350

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Archi

[Kernel-packages] [Bug 1581852] [NEW] linux-firmware is missing intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq and bluetooth isn't pairing devices

2016-05-14 Thread slimbook

Public bug reported:

Hello,
We have problems with the bluetooth of wifi card Intel 7265 N 
The driver is updated, we check checked kernel.org
But dsmeg shows not find the file bluetooth:

kernel: [   12.428031] bluetooth hci0: Direct firmware load for 
intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq failed with error -2
kernel: [   12.428034] Bluetooth: hci0 failed to open Intel firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq(-2)

This is an Intel 7265 N card,this isn't AC, but this also has bluetooth, and 
Intel don't indicate compatibility with limitations (Intel does in other 
models):
http://ark.intel.com/es-es/products/84177/Intel-Dual-Band-Wireless-N-7265

We have tested the same hardware, and same Ubuntu installation, with the
model wifi 7265 AC and bluetooth works, only not works with 7265 N.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157 [modified: lib/firmware/iwlwifi-3160-16.ucode 
lib/firmware/iwlwifi-7265-16.ucode lib/firmware/iwlwifi-7265D-16.ucode]
Uname: Linux 4.4.9-040409-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Sat May 14 19:48:25 2016
Dependencies:
 
InstallationDate: Installed on 2016-04-30 (14 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  linux-firmware is missing intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq and
  bluetooth isn't pairing devices

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello,
  We have problems with the bluetooth of wifi card Intel 7265 N 
  The driver is updated, we check checked kernel.org
  But dsmeg shows not find the file bluetooth:

  kernel: [   12.428031] bluetooth hci0: Direct firmware load for 
intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq failed with error -2
  kernel: [   12.428034] Bluetooth: hci0 failed to open Intel firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.1.14.d.bseq(-2)

  This is an Intel 7265 N card,this isn't AC, but this also has bluetooth, and 
Intel don't indicate compatibility with limitations (Intel does in other 
models):
  http://ark.intel.com/es-es/products/84177/Intel-Dual-Band-Wireless-N-7265

  We have tested the same hardware, and same Ubuntu installation, with
  the model wifi 7265 AC and bluetooth works, only not works with 7265
  N.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157 [modified: lib/firmware/iwlwifi-3160-16.ucode 
lib/firmware/iwlwifi-7265-16.ucode lib/firmware/iwlwifi-7265D-16.ucode]
  Uname: Linux 4.4.9-040409-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat May 14 19:48:25 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-04-30 (14 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1581852/+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 1322068] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working

2016-05-14 Thread Battant

Hello,

With ubuntu 16.04 LTS 64 bit and the kernel

uname -a
4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 
x86_64 GNU/Linux

The bluetooth seems work.

Best regards

Battant

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

Title:
  [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With my Clevo W253EU laptop, after installing Ubuntu 14.04 LTS, I cannot turn 
on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the 
results are:
  Ubuntu 12.04.LTS it works
  Ubuntu 12.04.1 LTS it works
  Ubuntu 12.04.2 LTS it works
  Ubuntu 12.04.3 LTS it does not working
  Ubuntu 12.04.4 LTS it does not working

  Upstream post: http://marc.info/?l=linux-acpi&m=142227943520605&w=2

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sibold 1910 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 09:31:55 2014
  HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab
  InstallationDate: Installed on 2014-05-17 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+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 1581769] Re: DRM: intel set pch fifo_underrun_reporting [i915]

apport information

** Description changed:

  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel due
  to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:
  
  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun
  
  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/
  
  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-03 (41 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_IN:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_IN
+  SHELL=/bin/bash
+ Tags:  xenial
+ Uname: Linux 4.4.9-040409-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  Unreportabl

[Kernel-packages] [Bug 1550779] Re: [i915]] ERROR CPU pipe A FIFO underrun - Xorg glitches

2016-05-14 Thread Hubert Hesse

I'm still seeing the issue with latest:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.10-xenial/
Where other people report the issues are fixed for them

However not as severe as with 4.2.0-30.36

Can someone please advise what to do? My questions from #14 are still 
unaddressed:
Can anyone confirm the steps I took where all right?
What's the difference between the kernel I compiled and the officially 
distributed one (4.2.0-27)? Any patches to reproduce the official binary?

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1

[Kernel-packages] [Bug 1049466] Re: Need support of Ralink RT3290 wifi support

2016-05-14 Thread Alexandre Magno

Høst, maybe the manufacturer needs to talk with the Ubuntu team, give
them sufficient information about their hardware! Note that Dell
notebooks are very much compatibles.

corrado venturini, try rebuild it.

My last message about it:
https://bugs.launchpad.net/bluetooth/+bug/1189721/comments/191

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

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+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 1574905] Re: Error when releas upgrade

2016-05-14 Thread Alexander Svetlov

Thank you Joseph.
  I resolve the problem by removing intel video drivers.

2016-05-06 1:20 GMT+07:00 Joseph Salisbury
:

> You may need to run the following from a terminal:
>
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
>
> Then re-install the package or updates.
>
> If that does not resolve your issue, please mark the bug as "Confirmed"
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1574905
>
> Title:
>   Error when releas upgrade
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When My Kubuntu distributive is upgrading, error appear: Could not
>   calculate the upgrade system. Then process of upgrade end.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: linux-image-4.2.0-35-generic 4.2.0-35.40
>   ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
>   Uname: Linux 4.2.0-35-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  svasan 1112 F pulseaudio
>/dev/snd/controlC1:  svasan 1112 F pulseaudio
>   CurrentDesktop: KDE
>   Date: Tue Apr 26 06:51:09 2016
>   HibernationDevice: RESUME=UUID=238d8f5e-9d4c-4b48-a8a4-b3fd435201a7
>   HotplugNewDevices:
>
>   HotplugNewMounts:
>
>   InstallationDate: Installed on 2016-04-15 (10 days ago)
>   InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   IwConfig:
>enp4s0no wireless extensions.
>
>lono wireless extensions.
>   MachineType: Gigabyte Technology Co., Ltd. Z68A-D3-B3
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_RU.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 VESA VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic
> root=UUID=927483c4-d85f-4166-a5a6-560f70d4676d ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.2.0-35-generic N/A
>linux-backports-modules-4.2.0-35-generic  N/A
>linux-firmware1.149.3
>   RfKill:
>
>   SourcePackage: linux
>   Symptom: storage
>   UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
>   UdevMonitorLog:
>monitor will print the received events for:
>UDEV - the event which udev sends out after rule processing
>   UdisksMonitorLog:
>Monitoring the udisks daemon. Press Ctrl+C to exit.
>06:51:35.365: The udisks-daemon is running (name-owner :1.18).
>   UpgradeStatus: Upgraded to wily on 2016-04-25 (0 days ago)
>   dmi.bios.date: 05/02/2011
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: F2
>   dmi.board.name: Z68A-D3-B3
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: x.x
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd05/02/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68A-D3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68A-D3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: Z68A-D3-B3
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574905/+subscriptions
>


** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1574905

Title:
  Error when releas upgrade

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  When My Kubuntu distributive is upgrading, error appear: Could not
  calculate the upgrade system. Then process of upgrade end.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-35-generic 4.2.0-35.40
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  svasan 1112 F pulseaudio
   /dev/snd/controlC1:  svasan 1112 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 26 06:51:09 2016
  HibernationDevice: RESUME=UUID=238d8f5e-9d4c-4b48-a8a4-b3fd435201a7
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-04-15 (10 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z68A-D3-B3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DI

[Kernel-packages] [Bug 1424293] Re: BYD trackpad detected as PS/2 mouse

2016-05-14 Thread Martin Wimpress

@penalvch - I'm running this kernel, which I believe has your BYD patch
included.

  * http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/

dmesg tells me the following:

[2.379157] mousedev: PS/2 mouse device common for all mice
[  238.400656] psmouse serio1: byd: Unrecognized Z: pkt = 09 00 00 ce
[  238.400666] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 4
[  238.420196] psmouse serio1: TouchPad at isa0060/serio1/input0 - driver 
resynced.

However, the BYD trackpad supports very few features. Multi finger touch
is not recognised, multi finger swipe is not recognised. I cursious to
understand why you didn't base the BYD patch you submitted to the kernel
on this one the following?

  * https://github.com/raedwulf/linux/tree/byd

It has had several contributors and all features of the BYD trackpad
work correctly.

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

Title:
  BYD trackpad detected as PS/2 mouse

Status in linux package in Ubuntu:
  Triaged

Bug description:
  In 14.04.2, I expected to be able to use as touchpad with two finger
  vertical/horizontal scrolling. Currently only able to use plainly. The
  exact device is this:
  http://bydit.com/doce/products/microelectronics/2474.html

  I: Bus=0011 Vendor=0002 Product=0005 Version=
  N: Name="ImPS/2 Generic Wheel Mouse"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input7
  U: Uniq=
  H: Handlers=mouse0 event10
  B: PROP=0
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=103

  Output of xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ USB 2.0 Camera  id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]

  ---
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vjftw  1362 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=d58116d7-f5eb-4b3c-b986-a9a29b608880
  InstallationDate: Installed on 2015-04-25 (28 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 003 Device 002: ID 8087:8001 Intel Corp.
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 058f:3821 Alcor Micro Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation SharkBay Platform
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=cd943b28-f170-4ce9-b836-18c395f1df6d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: Fab2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/03/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SharkBay Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/

[Kernel-packages] [Bug 1572666] Re: CVE-2016-3955

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Fix Committed

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

Title:
  CVE-2016-3955

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source packa

[Kernel-packages] [Bug 1578496] Re: CVE-2016-4485

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Fix Committed

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

Title:
  CVE-2016-4485

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wi

[Kernel-packages] [Bug 1578497] Re: CVE-2016-4486

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Fix Committed

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

Title:
  CVE-2016-4486

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wi

[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init

2016-05-14 Thread Darek

I can't run apport-collect. Maybe because I'm chrooted?

root@lubuntu:/# sudo apt-get install python-apport
Reading package lists... Done
Building dependency tree   
Reading state information... Done
python-apport is already the newest version.
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-24 linux-headers-3.13.0-24-generic
  linux-image-3.13.0-24-generic linux-image-extra-3.13.0-24-generic
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
root@lubuntu:/# apport-collect 1581761
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

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

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

Title:
  Kernel panic - not syncing - Attempted to kill init

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to 
kill init'. I tried to use previous kernel, then reinstall kernels but all that 
didn't help me. I have luks encrypted partition which contains multiple lvm 
with ext4 volumes. This was working since 14.04 was released so this not 
standard configuration should not cause this issue.
  I am able to run live cd, then decrypt luks partition and mount volumes and 
chroot. All seems to be ok. I fsck lvm and all is ok.
  I found similar issue 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest 
to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping 
for 5 secs" message on the stacktrace in the middle) but this didn't solve the 
issue. Maybe I enter this hack too early in the script?

  No more idea... so mayday, mayday...
  I attached photo of the stacktrace and report of 'apport-cli linux-generic'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+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 1581777] Re: igb transmit queue times out

2016-05-14 Thread Foster "Forst" Snowhill

Tested with latest mainline kernel (linux-
image-4.6.0-040600rc7-generic), problem persists, appropriate tag added.

** Tags added: kernel-bug-exists-upstream

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

Title:
  igb transmit queue times out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using an Intel I210AT built-in PCI-E NIC passed through from the ESXi
  6 host to an Ubuntu 16.04 server virtual machine. Network is unusable
  due to constant "transmit queue 0 timed out" errors.

  Issue is NOT present on a 14.04.4 machine running "3.19.0-59-generic
  #65~14.04.1-Ubuntu SMP Tue Apr 19 18:57:09 UTC 2016" kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 14 12:09 seq
   crw-rw 1 root audio 116, 33 May 14 12:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Sat May 14 12:22:44 2016
  HibernationDevice: RESUME=UUID=c31589d1-6ec7-471b-9073-180b6f2886f3
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware7,1
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1c9de470-43c0-4955-80ab-85497792601e ro noplymouth 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2015
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.0.B64.1506250318
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.0.B64.1506250318:bd06/25/2015:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581777/+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 1581814] Re: can't start bluetooth

2016-05-14 Thread Daniele

$ apport-collect 1581814
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=3PxFVP5LZQ8ptd0Xcrqb&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...

Waiting to hear from Launchpad about your decision...

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
dpkg-query: no packages found matching linux
.

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (1.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): V
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 370, in 
if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 569, in 
run_update_report
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 209, in ui_present_report_details
self.collect_info()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 967, in 
collect_info
if self.report['ProblemType'] == 'Crash':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
raise KeyError(key)
KeyError: 'ProblemType'

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

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

Title:
  can't start bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth works (Asus Zenbook UX301LA) neither on Ubuntu 16.04 nor Linux Mint 
17.3 (both systems updated). 
  Bluetooth used to work on previous versions of Ubuntu and Mint. The Asus is 
two year-old and a quick look inside the pc shows no sign of dirt. It doesn't 
seem possible to remove the wireless card without resorting to wire-cutting + 
soldering. 

  the following occurs: 
  1) with wifi enabled (wifi works perfectly):
  a) icon in taskbar is grayed out;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>both bluetooth and bluetooth visibility appear as "off" + the message 
"bluetooth is disabled" appears.

  2) with wifi disabled and after re-booting Asus:
  a) icon in taskbar lits up;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>bluetooth appears as "on" and bluetooth visibility appear as "off" + 
the message "bluetooth is disabled" appears.

  here are a couple of terminal outputs (if relevant, forgive my total
  ignorance on the subject):

  ubuntu-bug linux
  == ApportVersion =
  2.14.1-0ubuntu3.19

  == Architecture =
  amd64

  == CurrentDesktop =
  X-Cinnamon

  == Date =
  Sat May 14 14:39:57 2016

  == Dependencies =
  adduser 3.113+nmu3ubuntu3
  apt-utils 1.0.1ubuntu2.13
  base-passwd 3.5.33
  busybox-initramfs 1:1.21.0-1ubuntu1
  coreutils 8.21-1ubuntu5.4
  cpio 2.11+dfsg-1ubuntu1.2
  dbus 1.6.18-0ubuntu4.3
  debconf 1.5.51ubuntu2
  debconf-i18n 1.5.51ubuntu2
  debianutils 4.4
  :

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  [sudo] password for weword: 
DS Parameter set: channel 11
DS Parameter set: channel 1
DS Parameter set: channel 1
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 11
DS Parameter set: channel 36

  cat /var/log/dmesg | grep "firmware version"
  [1.743848] psmouse serio4: elantech: assuming hardware version 4 (with 
firmware version 0x671f07)
  [3.527075] iwlwifi :02:00.0: loaded firmware version 25.17.12.0 
op_mode iwlmvm

  additional info: I tried to update the bios - extracted the latest
  BIOS 207 (if I chose the right one in the first place) - onto flash
  card but Bios>Advanced>Start EasyFlash can't detect any file on my
  (FAT32-formatted) flash card.

  any idea?

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

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1581814

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  can't start bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth works (Asus Zenbook UX301LA) neither on Ubuntu 16.04 nor Linux Mint 
17.3 (both systems updated). 
  Bluetooth used to work on previous versions of Ubuntu and Mint. The Asus is 
two year-old and a quick look inside the pc shows no sign of dirt. It doesn't 
seem possible to remove the wireless card without resorting to wire-cutting + 
soldering. 

  the following occurs: 
  1) with wifi enabled (wifi works perfectly):
  a) icon in taskbar is grayed out;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>both bluetooth and bluetooth visibility appear as "off" + the message 
"bluetooth is disabled" appears.

  2) with wifi disabled and after re-booting Asus:
  a) icon in taskbar lits up;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>bluetooth appears as "on" and bluetooth visibility appear as "off" + 
the message "bluetooth is disabled" appears.

  here are a couple of terminal outputs (if relevant, forgive my total
  ignorance on the subject):

  ubuntu-bug linux
  == ApportVersion =
  2.14.1-0ubuntu3.19

  == Architecture =
  amd64

  == CurrentDesktop =
  X-Cinnamon

  == Date =
  Sat May 14 14:39:57 2016

  == Dependencies =
  adduser 3.113+nmu3ubuntu3
  apt-utils 1.0.1ubuntu2.13
  base-passwd 3.5.33
  busybox-initramfs 1:1.21.0-1ubuntu1
  coreutils 8.21-1ubuntu5.4
  cpio 2.11+dfsg-1ubuntu1.2
  dbus 1.6.18-0ubuntu4.3
  debconf 1.5.51ubuntu2
  debconf-i18n 1.5.51ubuntu2
  debianutils 4.4
  :

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  [sudo] password for weword: 
DS Parameter set: channel 11
DS Parameter set: channel 1
DS Parameter set: channel 1
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 11
DS Parameter set: channel 36

  cat /var/log/dmesg | grep "firmware version"
  [1.743848] psmouse serio4: elantech: assuming hardware version 4 (with 
firmware version 0x671f07)
  [3.527075] iwlwifi :02:00.0: loaded firmware version 25.17.12.0 
op_mode iwlmvm

  additional info: I tried to update the bios - extracted the latest
  BIOS 207 (if I chose the right one in the first place) - onto flash
  card but Bios>Advanced>Start EasyFlash can't detect any file on my
  (FAT32-formatted) flash card.

  any idea?

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

Re: [Kernel-packages] [Bug 1581769] Missing required logs.

administrator@SAMSUNG-NP350V5X-S01IN:~$ sudo apport-collect 1581769
[sudo] password for administrator:
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before
import to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
dpkg-query: no packages found matching linux
Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.
[0514/191015:ERROR:nss_util.cc(98)] Failed to create
/home/administrator/.pki/nssdb directory.
[0514/191015:FATAL:chrome_main_delegate.cc(411)] Check failed:
process_type.empty(). Unable to get the user data directory for process
type: zygote
#0 0x7f7d0630bdee base::debug::StackTrace::StackTrace()
#1 0x7f7d0632a42e logging::LogMessage::~LogMessage()
#2 0x561b021bd4eb 
#3 0x7f7d0dce3da2 
#4 0x7f7d0dce27fd content::ContentMain()
#5 0x561b021bc8ea 
#6 0x7f7cfa971830 __libc_start_main
#7 0x561b021bc7a9 

[0514/191040:ERROR:nss_util.cc(98)] Failed to create
/home/administrator/.pki/nssdb directory.
[0514/191040:FATAL:chrome_main_delegate.cc(411)] Check failed:
process_type.empty(). Unable to get the user data directory for process
type: zygote
#0 0x7f2e5e026dee base::debug::StackTrace::StackTrace()
#1 0x7f2e5e04542e logging::LogMessage::~LogMessage()
#2 0x561f33a7a4eb 
#3 0x7f2e659feda2 
#4 0x7f2e659fd7fd content::ContentMain()
#5 0x561f33a798ea 
#6 0x7f2e5268c830 __libc_start_main
#7 0x561f33a797a9 

The authorization page:
 (
https://launchpad.net/+authorize-token?oauth_token=PGWNKM5cJXSWBdLDGCWH&allow_permission=DESKTOP_INTEGRATION
)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
[0514/191626:ERROR:nss_util.cc(98)] Failed to create
/home/administrator/.pki/nssdb directory.
[0514/191626:FATAL:chrome_main_delegate.cc(411)] Check failed:
process_type.empty(). Unable to get the user data directory for process
type: zygote
#0 0x7fd24c15ddee base::debug::StackTrace::StackTrace()
#1 0x7fd24c17c42e logging::LogMessage::~LogMessage()
#2 0x56076601f4eb 
#3 0x7fd253b35da2 
#4 0x7fd253b347fd content::ContentMain()
#5 0x56076601e8ea 
#6 0x7fd2407c3830 __libc_start_main
#7 0x56076601e7a9 

^CTraceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 594, in 
app.run_argv()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in
run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 573, in
run_update_report
attachment_comment='apport information')
  File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py",
line 367, in update
bug = self.launchpad.bugs[id]
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/resource.py",
line 1000, in __getitem__
shim_resource._ensure_representation()
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/resource.py",
line 381, in _ensure_representation
representation = self._root._browser.get(self._wadl_resource)
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/_browser.py",
line 436, in get
response, content = self._request(url, extra_headers=headers)
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/_browser.py",
line 387, in _request
str(url), method=method, body=data, headers=headers)
  File "/usr/lib/python2.7/dist-packages/lazr/restfulclient/_browser.py",
line 357, in _request_and_retry
url, method=method, body=body, headers=headers)
  File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1577,
in request
(response, new_content) = self._request(conn, authority, uri,
request_uri, method, body, headers, redirections, cachekey)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line
132, in _request
return self.retry_on_bad_token(response, content, *args)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line
144, in retry_on_bad_token
self.launchpad.credentials, self.launchpad.credential_store)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
545, in __call__
self.make_end_user_authorize_token(credentials, request_token_string)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
658, in make_end_user_authorize_token
self.web_root)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
232, in exchange_request_token_for_access_token
response, content = _http_post(url, headers, params)
  File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
112, in _http_post
url, method='POST', headers=headers, body=urlencode(params))
  File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1607,
in request
(response, content) = self._request(conn, authority, uri, request_uri,
method, body, headers, redirections, cachekey)
  File "/usr/lib/python2.7/dist-packages/httpli

[Kernel-packages] [Bug 1581814] [NEW] can't start bluetooth

2016-05-14 Thread Daniele

Public bug reported:

Bluetooth works (Asus Zenbook UX301LA) neither on Ubuntu 16.04 nor Linux Mint 
17.3 (both systems updated). 
Bluetooth used to work on previous versions of Ubuntu and Mint. The Asus is two 
year-old and a quick look inside the pc shows no sign of dirt. It doesn't seem 
possible to remove the wireless card without resorting to wire-cutting + 
soldering. 

the following occurs: 
1) with wifi enabled (wifi works perfectly):
a) icon in taskbar is grayed out;
b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>both bluetooth and bluetooth visibility appear as "off" + the message 
"bluetooth is disabled" appears.

2) with wifi disabled and after re-booting Asus:
a) icon in taskbar lits up;
b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>bluetooth appears as "on" and bluetooth visibility appear as "off" + 
the message "bluetooth is disabled" appears.

here are a couple of terminal outputs (if relevant, forgive my total
ignorance on the subject):

ubuntu-bug linux
== ApportVersion =
2.14.1-0ubuntu3.19

== Architecture =
amd64

== CurrentDesktop =
X-Cinnamon

== Date =
Sat May 14 14:39:57 2016

== Dependencies =
adduser 3.113+nmu3ubuntu3
apt-utils 1.0.1ubuntu2.13
base-passwd 3.5.33
busybox-initramfs 1:1.21.0-1ubuntu1
coreutils 8.21-1ubuntu5.4
cpio 2.11+dfsg-1ubuntu1.2
dbus 1.6.18-0ubuntu4.3
debconf 1.5.51ubuntu2
debconf-i18n 1.5.51ubuntu2
debianutils 4.4
:

sudo iw dev wlan0 scan | grep -i "ds parameter set"
[sudo] password for weword: 
DS Parameter set: channel 11
DS Parameter set: channel 1
DS Parameter set: channel 1
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 11
DS Parameter set: channel 36

cat /var/log/dmesg | grep "firmware version"
[1.743848] psmouse serio4: elantech: assuming hardware version 4 (with 
firmware version 0x671f07)
[3.527075] iwlwifi :02:00.0: loaded firmware version 25.17.12.0 op_mode 
iwlmvm

additional info: I tried to update the bios - extracted the latest BIOS
207 (if I chose the right one in the first place) - onto flash card but
Bios>Advanced>Start EasyFlash can't detect any file on my
(FAT32-formatted) flash card.

any idea?

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

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

Title:
  can't start bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bluetooth works (Asus Zenbook UX301LA) neither on Ubuntu 16.04 nor Linux Mint 
17.3 (both systems updated). 
  Bluetooth used to work on previous versions of Ubuntu and Mint. The Asus is 
two year-old and a quick look inside the pc shows no sign of dirt. It doesn't 
seem possible to remove the wireless card without resorting to wire-cutting + 
soldering. 

  the following occurs: 
  1) with wifi enabled (wifi works perfectly):
  a) icon in taskbar is grayed out;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>both bluetooth and bluetooth visibility appear as "off" + the message 
"bluetooth is disabled" appears.

  2) with wifi disabled and after re-booting Asus:
  a) icon in taskbar lits up;
  b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth 
settings>bluetooth appears as "on" and bluetooth visibility appear as "off" + 
the message "bluetooth is disabled" appears.

  here are a couple of terminal outputs (if relevant, forgive my total
  ignorance on the subject):

  ubuntu-bug linux
  == ApportVersion =
  2.14.1-0ubuntu3.19

  == Architecture =
  amd64

  == CurrentDesktop =
  X-Cinnamon

  == Date =
  Sat May 14 14:39:57 2016

  == Dependencies =
  adduser 3.113+nmu3ubuntu3
  apt-utils 1.0.1ubuntu2.13
  base-passwd 3.5.33
  busybox-initramfs 1:1.21.0-1ubuntu1
  coreutils 8.21-1ubuntu5.4
  cpio 2.11+dfsg-1ubuntu1.2
  dbus 1.6.18-0ubuntu4.3
  debconf 1.5.51ubuntu2
  debconf-i18n 1.5.51ubuntu2
  debianutils 4.4
  :

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  [sudo] password for weword: 
DS Parameter set: channel 11
DS Parameter set: channel 1
DS Parameter set: channel 1
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 6
DS Parameter set: channel 11
DS Parameter set: channel 36

  cat /var/log/dmesg | grep "firmware version"
  [1.743848] psmouse serio4: elantech: assuming hardware version 4 (with 
firmw

[Kernel-packages] [Bug 1581761] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1581761

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Kernel panic - not syncing - Attempted to kill init

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to 
kill init'. I tried to use previous kernel, then reinstall kernels but all that 
didn't help me. I have luks encrypted partition which contains multiple lvm 
with ext4 volumes. This was working since 14.04 was released so this not 
standard configuration should not cause this issue.
  I am able to run live cd, then decrypt luks partition and mount volumes and 
chroot. All seems to be ok. I fsck lvm and all is ok.
  I found similar issue 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest 
to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping 
for 5 secs" message on the stacktrace in the middle) but this didn't solve the 
issue. Maybe I enter this hack too early in the script?

  No more idea... so mayday, mayday...
  I attached photo of the stacktrace and report of 'apport-cli linux-generic'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+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 1581761] Re: Kernel panic - not syncing - Attempted to kill init

2016-05-14 Thread Paul White

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

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

Title:
  Kernel panic - not syncing - Attempted to kill init

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to 
kill init'. I tried to use previous kernel, then reinstall kernels but all that 
didn't help me. I have luks encrypted partition which contains multiple lvm 
with ext4 volumes. This was working since 14.04 was released so this not 
standard configuration should not cause this issue.
  I am able to run live cd, then decrypt luks partition and mount volumes and 
chroot. All seems to be ok. I fsck lvm and all is ok.
  I found similar issue 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest 
to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping 
for 5 secs" message on the stacktrace in the middle) but this didn't solve the 
issue. Maybe I enter this hack too early in the script?

  No more idea... so mayday, mayday...
  I attached photo of the stacktrace and report of 'apport-cli linux-generic'.

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1581769/+attachment/4662864/+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/1581769

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581769/+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 1581769] Re: DRM: intel set pch fifo_underrun_reporting [i915]

apport information

** Description changed:

  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel due
  to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:
  
  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun
  
  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/
  
  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20.1-0ubuntu1
+ Architecture: amd64
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-03 (40 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.4.9-040409-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581769/+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 1581761] [NEW] Kernel panic - not syncing - Attempted to kill init

You have been subscribed to a public bug:

Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to 
kill init'. I tried to use previous kernel, then reinstall kernels but all that 
didn't help me. I have luks encrypted partition which contains multiple lvm 
with ext4 volumes. This was working since 14.04 was released so this not 
standard configuration should not cause this issue.
I am able to run live cd, then decrypt luks partition and mount volumes and 
chroot. All seems to be ok. I fsck lvm and all is ok.
I found similar issue 
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest 
to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping 
for 5 secs" message on the stacktrace in the middle) but this didn't solve the 
issue. Maybe I enter this hack too early in the script?

No more idea... so mayday, mayday...
I attached photo of the stacktrace and report of 'apport-cli linux-generic'.

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

-- 
Kernel panic - not syncing - Attempted to kill init
https://bugs.launchpad.net/bugs/1581761
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1581005] Re: Dell XPS 15 9550 Freezes when HDMI is plugged in

2016-05-14 Thread Mike O'Connell

Looks like 63a1281b651b8ebc04c829254c62bd6fbaf83eb0 has the fix.

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

Title:
  Dell XPS 15 9550 Freezes when HDMI is plugged in

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

Bug description:
  This is fixed upstream in the 4.6.0 series.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2087 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 07:25:29 2016
  HibernationDevice: RESUME=UUID=20adf9e8-41f0-4bf8-8075-dcff091511d4
  InstallationDate: Installed on 2016-03-12 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ea2a2622-df89-4bf1-8f58-99f313ed3908 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581005/+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 1049466] Re: Need support of Ralink RT3290 wifi support

2016-05-14 Thread corrado venturini

was working fine on Ubuntu 16.04 and also on 16.10 before last updates. After 
last updates on 16.10 the wifi dropdown menu is empty. no way to connect. i'm 
writing from 16.04, i will go back to 16.10 to prepare some doc. I have 16.04 
and 16.10 on different partitions of same laptop HP250. If i start with 16.10 i 
see no wifi; then if i do restart and reboot on 16.04 i still have no wifi. to 
have wifi i must shutdown-poweroff and restart with 16.04 or 14.04. 
Please specify what doc is needed.

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

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+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 1581769] Re: DRM: intel set pch fifo_underrun_reporting [i915]

apport information

** Tags added: apport-collected xenial

** Description changed:

  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel due
  to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:
  
  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun
  
  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/
  
- It didn't workout for the time being. Is there anything else as
- required?
+ It didn't workout for the time being. Is there anything else as required?
+ --- 
+ ApportVersion: 2.20.1-0ubuntu1
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-04-03 (40 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_IN:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_IN
+  SHELL=/bin/bash
+ Tags:  xenial
+ Uname: Linux 4.4.9-040409-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581769/+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 1581799] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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 1581799] Re: radeon driver hangs : nothing else that static effect on display

2016-05-14 Thread magowiz

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+attachment/4662838/+files/lspci-vnvn.log

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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 1581799] Re: radeon driver hangs : nothing else that static effect on display

2016-05-14 Thread magowiz

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+attachment/4662839/+files/version.log

** Description changed:

  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.
  
  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
- I'll attach further files (dmesg.log , version.log, lspci-vnvn.log .
+ I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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 1581799] [NEW] radeon driver hangs : nothing else that static effect on display

2016-05-14 Thread magowiz

Public bug reported:

Hi,
since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard due 
to drop support of fglrx driver (that was working) and due to radeon opensource 
driver not working with my VGA.

Mine video card:
$ lspci -nn | grep VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

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

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1581799/+attachment/4662837/+files/dmesg.log

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581799/+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 1555786] Re: [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

2016-05-14 Thread Chris Valean

Hi Joe,

The link provided is not valid. I also checked all the folders from your
repo dated 13-May-2016 but none seem to have the 32bit packages.

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

Title:
  [Hyper-V] VM with ubuntu 32bit with linux-next does not boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We identified that at least ubuntu (let's take 15.10) does not boot if
  installed in the 32bit architecture, and using the linux-next upstream
  kernel 4.5 on it. This has been seen on other distributions as well.

  We took both the official linux-next branch from kernel.org and the one from 
kernel.ubuntu.com v4.5-rc7.
  For the compilation process we went either with the 4.2 kernel config file 
from the installed running kernel, and also built the config separately. 
  No errors have been encountered during the build or install process of the 
4.5 kernel, however at boot, the VM will just hang.
  There are no call traces or messages at boot to show any pottential issue.

  Have you seen this on your end when testing the 32bit build?
  Attaching the full serial log for reference, however I don't see any errors 
in the kernel boot process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555786/+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 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2016-05-14 Thread Guntbert Reiter

Tested with 4.6.0-040600rc7-generic from the archive mentioned above.

No success: xev still only shows buttons 1 and 3, but not button 2 (the
scroll-wheel (buttons 4, 5) is registered too).

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 9. Type: XIButtonClass
Buttons supported: 24
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" 
"Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown"
Button state:
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
Reporting 6 classes:
Class originated from: 10. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button 0" "Button Unknown" "Button Unknown" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right"
Button state:
Class originated from: 10. Type: XIKeyClass
Keycodes supported: 248
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
Class originated from: 10. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/

[Kernel-packages] [Bug 1581777] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  igb transmit queue times out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using an Intel I210AT built-in PCI-E NIC passed through from the ESXi
  6 host to an Ubuntu 16.04 server virtual machine. Network is unusable
  due to constant "transmit queue 0 timed out" errors.

  Issue is NOT present on a 14.04.4 machine running "3.19.0-59-generic
  #65~14.04.1-Ubuntu SMP Tue Apr 19 18:57:09 UTC 2016" kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 14 12:09 seq
   crw-rw 1 root audio 116, 33 May 14 12:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Sat May 14 12:22:44 2016
  HibernationDevice: RESUME=UUID=c31589d1-6ec7-471b-9073-180b6f2886f3
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware7,1
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1c9de470-43c0-4955-80ab-85497792601e ro noplymouth 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2015
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.0.B64.1506250318
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.0.B64.1506250318:bd06/25/2015:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

Re: [Kernel-packages] [Bug 1565106] Re: Wifi works on W10 but not on Ub 16.04 nor 14.04

2016-05-14 Thread winux

Hi Jo

Finally I could install the new kernel after an ultimate update & upgrade.
Here is the result:

on the old PC: no change, no wifi

On the brand new one:
I started with RJ45 ethernet OK
then I unplugged RJ45
impossible to activate wifi

I rebooted
wifi OK

I made a stop/start
impossible to activate wifi

I made sure I was in 4.6
$uname -a
 Linux PCi 4.6.040600rc7generic

On top of that, same as with the previous kernel, I cannot start the W10
volume, even though the W10 quick start is inhibated

2016-05-13 18:02 GMT+02:00 Joseph Salisbury 
:

> This appears to be an upstream bug.
>
> The upstream v4.6-rc7 kernel is now available. Can you give this kernel
> a try?  It can be downloaded from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1565106
>
> Title:
>   Wifi works on W10 but not on Ub 16.04 nor 14.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+subscriptions
>

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

Title:
  Wifi works on W10 but not on Ub 16.04 nor 14.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi
  I just bought a laptop "HP Envy x360 15-w100nf". Everything's fine except wifi
  - It works on w10
  - but not on Ub 16.04 / 4.4.0-15 / 64 bits
  - nor Ub 14.04

  I've spent hours of discussions and tests on wifi forum
  URL = https://forum.ubuntu-fr.org/viewtopic.php?id=1987186
  (unfortunately it's in French but command line tests are quite understandable)

  Now I think nobody can help me on the forum because we've tried everything, 
that's why I assume it's a bug.
  I'm ready to make every test which could help solving this problem

  In the meantime, have a nice day (actually a nice night ... in France !)
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clubmicronet   1295 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b66db7f5-8c76-4cbb-829f-610caa034e13
  InstallationDate: Installed on 2016-03-22 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: HP HP ENVY x360 Convertible
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=39204032-2bfd-4402-b4a8-87db0dd6075f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-15-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/10/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/10/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565106/+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 1581769] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1581769

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as
  required?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581769/+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 1581777] [NEW] igb transmit queue times out

2016-05-14 Thread Foster "Forst" Snowhill

Public bug reported:

Using an Intel I210AT built-in PCI-E NIC passed through from the ESXi 6
host to an Ubuntu 16.04 server virtual machine. Network is unusable due
to constant "transmit queue 0 timed out" errors.

Issue is NOT present on a 14.04.4 machine running "3.19.0-59-generic
#65~14.04.1-Ubuntu SMP Tue Apr 19 18:57:09 UTC 2016" kernel.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.39
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 May 14 12:09 seq
 crw-rw 1 root audio 116, 33 May 14 12:09 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
Date: Sat May 14 12:22:44 2016
HibernationDevice: RESUME=UUID=c31589d1-6ec7-471b-9073-180b6f2886f3
InstallationDate: Installed on 2016-05-13 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware7,1
PciMultimedia:
 
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1c9de470-43c0-4955-80ab-85497792601e ro noplymouth 
crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2015
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW71.00V.0.B64.1506250318
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.0.B64.1506250318:bd06/25/2015:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware7,1
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  igb transmit queue times out

Status in linux package in Ubuntu:
  New

Bug description:
  Using an Intel I210AT built-in PCI-E NIC passed through from the ESXi
  6 host to an Ubuntu 16.04 server virtual machine. Network is unusable
  due to constant "transmit queue 0 timed out" errors.

  Issue is NOT present on a 14.04.4 machine running "3.19.0-59-generic
  #65~14.04.1-Ubuntu SMP Tue Apr 19 18:57:09 UTC 2016" kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 14 12:09 seq
   crw-rw 1 root audio 116, 33 May 14 12:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Sat May 14 12:22:44 2016
  HibernationDevice: RESUME=UUID=c31589d1-6ec7-471b-9073-180b6f2886f3
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware7,1
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=1c9de470-43c0-4955-80ab-85497792601e ro noplymouth 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: l

[Kernel-packages] [Bug 1581769] [NEW] DRM: intel set pch fifo_underrun_reporting [i915]

Public bug reported:

I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel due
to suspend and wakeup issued and it is cleared now. But however im
getting an error on bootload as follows:

[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
[drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO 
underrun

I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=wiley
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

It didn't workout for the time being. Is there anything else as
required?

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


** Tags: 16.04 driver drm installation intel issue 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/1581769

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  New

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as
  required?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581769/+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 1579515] Re: suspend and wakeup prob in Samsung Notebook with Ubuntu 16.04 LTS