[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[spike speigel]

This seems to have also fixed another issue where my sound would switch
to HDMI sink from headphones when changing screen resolutions in XFCE:


https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1858250
https://bugzilla.xfce.org/show_bug.cgi?id=16335

** Bug watch added: Xfce Bugzilla #16335
   https://bugzilla.xfce.org/show_bug.cgi?id=16335

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1855782] Re: Typo in the documentation: "systen" -> "system"

[spike speigel]

** Bug watch added: bugzilla.gnome.org/ #786829
   https://bugzilla.gnome.org/show_bug.cgi?id=786829

** Also affects: dconf via
   https://bugzilla.gnome.org/show_bug.cgi?id=786829
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to d-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1855782

Title:
  Typo in the documentation: "systen" -> "system"

Status in dconf:
  Unknown
Status in d-conf package in Ubuntu:
  Confirmed

Bug description:
  Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have
  it fixed.

  The "NAME" section of dconf7
  manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html)
  says "dconf - A configuration systen".

  "systen" should be a typo for "system".

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1855782/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Tags added: carbon gen6 lenovo thinkpad x1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on 

[Touch-packages] [Bug 1340076] Re: HDMI audio is severely distorted.

[spike speigel]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1340076

Title:
  HDMI audio is severely distorted.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have recently installed Ubuntu onto a newly built computer with an
  ASRock H87 Performance Motherboard. I am using a TV monitor for a
  screen, connected with HDMI. The visuals work fine but the audio is
  severely distorted and echoes.

  When testing the sound in the hardware settings, it sounds like
  "FRONTFRONTFRONTFRONT" with static or overdrive getting more and more
  prominent as the sound goes on. I have changed the Alsamixer levels
  but found no change. The built-in sound card also shows up when i look
  for it as per the Sound Troubleshooting page.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: snd_hda_codec_generic snd_hda_controller fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2371 F pulseaudio
   /dev/snd/controlC1:  luke   2371 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 10 17:52:52 2014
  InstallationDate: Installed on 2014-07-09 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [To Be Filled By O.E.M., ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1340076/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1718064] Re: py3compile crashed with configparser.DuplicateOptionError in _read(): While reading from '/usr/share/python3/debian_defaults' [line 10]: option 'old-versions' in sec

[spike speigel]

I have done as you suggested.  Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1718064

Title:
  py3compile crashed with configparser.DuplicateOptionError in _read():
  While reading from '/usr/share/python3/debian_defaults' [line 10]:
  option 'old-versions' in section 'DEFAULT' already exists

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  andom crash on desktop shortly after mounting a DVD

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: python3-minimal 3.6.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 18 17:34:19 2017
  ExecutablePath: /usr/bin/py3compile
  InstallationDate: Installed on 2017-04-29 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 /usr/bin/py3compile -p python3-minimal 
/usr/share/python3/
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.2-1ubuntu1
  PythonArgs: ['/usr/bin/py3compile', '-p', 'python3-minimal', 
'/usr/share/python3/']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SourcePackage: python3-defaults
  Title: py3compile crashed with configparser.DuplicateOptionError in _read(): 
While reading from '/usr/share/python3/debian_defaults' [line 10]: option 
'old-versions' in section 'DEFAULT' already exists
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1718064/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** No longer affects: initramfs-tools (Debian)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** Tags added: bionic

** Tags added: xps

** Tags added: 9360

** Tags added: i965

** Tags added: kbl

** Tags added: bxt

** Tags added: intel

** Tags added: dell

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[spike speigel]

** Tags added: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1743423] Re: frozen login window' unable to login; must reboot' cursor moves no mouse clicks

[spike speigel]

Not sure if I have the same issue, but if I let my system go to
sleep/suspend at the login screen, when I resume I cannot click in the
password prompt and thus cannot type my password to login.  For some
reason the mouse will not give the password prompt text box focus.

It will give the password prompt text box focus if I first select
another option from the user drop down list such as "Other..." or any
other user, and then select my user again.  Suddenly I can enter my
password.  Maybe this workaround might work for you as well.

Like I said, your issue may be different.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1743423

Title:
  frozen login window' unable to login; must reboot' cursor moves no
  mouse clicks

Status in lightdm package in Ubuntu:
  New

Bug description:
  Denial o9f Service caused by holding a key that repeats for a long
  time.  eg.  cat takes nap on keyboard, cloting piled on keyboard

  Before submitting bug report I checked online and saw many other
  reports goin back about 15 months.  I saw no mention of  updates or
  how to reproduce.  In my case the cursor continues to move around, but
  unable to use cursor to reboot.  I can only use power off as none of
  they keys are working.

  Good thing the power button results are acceptable. and most
  applications fully recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Jan 14 19:20:22 2018
  InstallationDate: Installed on 2016-02-22 (692 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[spike speigel]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

[spike speigel]

** Tags added: trusty zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

[spike speigel]

Is this the same issue as bug #857651 ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1667113

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

Thanks Paul, that workaround helped me.  The 9.14 GuC loads now.  I
tried downloading the new 9.39 GuC on intel's site, and changing the
version in the hook script, but the 9.39 firmware would not load for
some reason.  Maybe due to both firmware versions existing in
/lib/firmware/i915/ on my system and the older one being seen/used
first.  I might try again later and moving the older firmware, but am
content with it loading as it is now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

I looked into this a bit more, and it seems Ubuntu is basing off of
linux-firmware at kernel.org and not following Debian's use of firmware-
misc-nonfree.  I'm removing the watch related to firmware-misc-nonfree,
but there appears to still be an issue with update-initramfs and the
i915 firmware for Kabylake and Broxton systems.

** Changed in: initramfs-tools (Debian)
   Importance: Unknown => Undecided

** Changed in: initramfs-tools (Debian)
   Status: Fix Released => New

** Changed in: initramfs-tools (Debian)
 Remote watch: Debian Bug tracker #854695 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Tags added: xenial zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

UGH, apparently Launchpad like to link bugs for you, and in this case,
it linked the Debian bug #s to unrelated projects/package bugs...Please
disregard the links in Comment #1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

It appears that bug #857997 in Debian's tracker was merged into Bug
#854695.  Just wanted to note that, and update the external tracker URL.

** Bug watch added: Debian Bug tracker #854695
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854695

** Changed in: initramfs-tools (Debian)
 Remote watch: Debian Bug tracker #857997 => Debian Bug tracker #854695

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

** Bug watch added: Debian Bug tracker #857997
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857997

** Also affects: initramfs-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857997
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Description changed:

  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
  exist.  I've also verified the Kabylake GuC firmware matches the correct
  file size and md5 listed on 01.org.
  
  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.
  
- I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
- Broxton systems might have the same issue?
+ I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
+ initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
+ same issue?
  
  Output and logs:
  -
  
  ls -al /lib/firmware/i915/kbl_*
  
  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
  
  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
  
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0
  
  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0
  
  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0
  
  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
  
  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256
  
  HuC status 0x6000:
  
  dmesg
  
  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  [1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
  [1.836129] 

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Tags added: broxton kabylake

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
  Broxton systems might have the same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Summary changed:

- initramfs not adding i915 GuC firmware, firmware fails to load
+ update-initramfs not adding i915 GuC firmware, firmware fails to load

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1728238

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
  Broxton systems might have the same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device 

[Touch-packages] [Bug 1728238] Re: initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

** Description changed:

  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
  exist.  I've also verified the Kabylake GuC firmware matches the correct
  file size and md5 listed on 01.org.
  
  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.
  
+ I'm running a Dell XPS 13 9360 w/ Kabylake.  Perhaps Broxton systems
+ might have the same issue?
+ 
  Output and logs:
  -
-  
+ 
  ls -al /lib/firmware/i915/kbl_*
-  
+ 
  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
  
  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
-  
+ 
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0
-  
+ 
  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0
-  
+ 
  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0
-  
+ 
  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
-  
+ 
  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256
-  
+ 
  HuC status 0x6000:
-  
+ 
  dmesg
-  
+ 
  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  [1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
  [1.836129] logitech-hidpp-device 0003:046D:4051.0006: input,hidraw3: USB 
HID v1.11 Mouse [Logitech M510] on usb-:00:14.0-2:1
  [

[Touch-packages] [Bug 1728238] [NEW] initramfs not adding i915 GuC firmware, firmware fails to load

[spike speigel]

Public bug reported:

The i915 Kabylake GuC firmware is failing to load on boot, and
generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
exist.  I've also verified the Kabylake GuC firmware matches the correct
file size and md5 listed on 01.org.

I then ran update-initramfs verbosely, and see that only
/lib/firmware/i915/skl_guc_ver6_1.bin is being added.
/lib/firmware/i915/bxt_guc_ver8_7.bin and
/lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

Output and logs:
-
 
ls -al /lib/firmware/i915/kbl_*
 
-rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin 
-> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
 
GuC firmware status:
path: i915/kbl_guc_ver9_14.bin
fetch: FAIL
load: NONE
version wanted: 9.14
version found: 0.0
header: offset is 0; size = 0
uCode: offset is 0; size = 0
RSA: offset is 0; size = 0
 
GuC status 0x0001:
Bootrom status = 0x0
uKernel status = 0x0
MIA Core status = 0x0
 
Scratch registers:
0: 0x0
1: 0x0
2: 0x0
3: 0x0
4: 0x0
5: 0x0
6: 0x0
7: 0x0
8: 0x0
9: 0x0
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
 
sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
 
HuC firmware status:
path: i915/kbl_huc_ver02_00_1810.bin
fetch: SUCCESS
load: SUCCESS
version wanted: 2.0
version found: 2.0
header: offset is 0; size = 128
uCode: offset is 128; size = 218304
RSA: offset is 218432; size = 256
 
HuC status 0x6000:
 
dmesg
 
[1.052879] hidraw: raw HID events driver (C) Jiri Kosina
[1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method 
not found
[1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
[1.082308] nvme nvme0: pci function :3c:00.0
[1.095073] Setting dangerous option enable_guc_loading - tainting kernel
[1.095075] Setting dangerous option enable_guc_submission - tainting kernel
[1.097867] [drm] Memory usable by graphics device = 4078M
[1.097869] checking generic (9000 1fb) vs hw (9000 1000)
[1.097869] fb: switching to inteldrmfb from EFI VGA
[1.097899] Console: switching to colour dummy device 80x25
[1.098049] [drm] Replacing VGA console driver
[1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[1.104157] [drm] Driver supports precise vblank timestamp query.
[1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
[1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
[1.298572]  nvme0n1: p1 p2
[1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
[1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1.433243] usb 1-1: Product: USB+PS2 Keyboard
[1.433244] usb 1-1: Manufacturer: Generic
[1.446460] usbcore: registered new interface driver usbhid
[1.446461] usbhid: USB HID core driver
[1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
[1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
[1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
[1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
[1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
[1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1.695657] usb 1-2: Product: USB Receiver
[1.695658] usb 1-2: Manufacturer: Logitech
[1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
[1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
[1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
[1.836129] logitech-hidpp-device 0003:046D:4051.0006: input,hidraw3: USB 
HID v1.11 Mouse [Logitech M510] on usb-:00:14.0-2:1
[1.838085] input: Logitech K750 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4002.0007/input/input10
[1.838283] logitech-hidpp-device 0003:046D:4002.0007: input,hidraw4: USB 
HID v1.11 Keyboard [Logitech K750] on usb-:00:14.0-2:2
[1.896270] psmouse serio1: synaptics: queried max coordinates: x [..5666], 
y 

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[spike speigel]

Hello, I just started seeing this on Ubuntu 17.10.

** Tags added: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1556419

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated

[spike speigel]

nf_conntrack: default automatic helper assignment has been turned off
for security reasons and CT-based  firewall rule not found. Use the
iptables CT target to attach helpers instead.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1556419

Title:
   nf_conntrack: automatic helper assignment is deprecated

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Get this logged into journalctl (since a moment):

   kernel: nf_conntrack: automatic helper assignment is deprecated and
  it will be removed soon. Use the iptables CT target to attach helpers
  instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1942 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1942 F...m pulseaudio
   /dev/snd/controlC0:  oem1942 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Mar 12 14:52:09 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1698594] Re: Kubuntu Installer for 17.04 crashes reproducable with a too small /boot partition due to "No space left on device"

[spike speigel]

Not sure if using dkms, but if so may be related to bug 1515513

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1698594

Title:
  Kubuntu Installer for 17.04 crashes reproducable with a too small
  /boot partition due to "No space left on device"

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  i have experienced reproducable crashes of the installer. The problem
  seems to be that my boot partition is to small. I have a /boot
  partition of about 100 MB

  The problem seems to be that the initrd file in the boot partition is
  very big and cannot be properly updated.

  Is there a restriction to the size of a /boot partition? 100 MB seems
  to be way to little, even though the initial installation is possible.
  But at the end of the installation process the installer crashes.

  = start  -> see full log at the end of the report
  update-initramfs: Generating /boot/initrd.img-4.10.0-22-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  = end 

  
  I used my existing paritions and i would at least expect a warning (hint) 
that the /boot partition needs to be of a certain size (or just prevents 
installation with a too small boot partition).

  I am also having problems updating the kernel, which seems to be the
  same cause of the crash of the installer:

  
  here is some information:

  wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo fdisk -l
  Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x241c6624

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sda1  * 2048 390625279 390623232 186,3G  7 HPFS/NTFS/exFAT
  /dev/sda2   390625280 39081983919456095M 83 Linux
  /dev/sda3   390819840 586131455 195311616  93,1G 83 Linux
  /dev/sda4   586133502 976771071 390637570 186,3G  5 Extended
  /dev/sda5   586133504 586717183583680   285M 82 Linux swap / Solaris
  /dev/sda6   586719232 976771071 390051840   186G 83 Linux

  
  wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo mount
  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=4042808k,nr_inodes=1010702,mode=755)
  devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=813128k,mode=755)
  /dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
  securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
  tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
  tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=3715)
  debugfs on /sys/kernel/debug type debugfs (rw,relatime)
  mqueue on /dev/mqueue type mqueue (rw,relatime)
  hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
  fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
  /dev/sda2 on /boot type ext2 
(rw,relatime,block_validity,barrier,user_xattr,acl)
  /dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
  tmpfs on /run/user/119 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=119,gid=127)
  tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=1000,gid=1000)
  

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[spike speigel]

Not sure if using dkms, but if so may be related to bug 1515513

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1678187

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1597661] Re: When /boot is full, repeated mkinitramfs runs can fill up /

[spike speigel]

Related to bug 1515513

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1597661

Title:
  When /boot is full, repeated mkinitramfs runs can fill up /

Status in One Hundred Papercuts:
  Confirmed
Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  My /boot partition filled up so when I (or unattended upgrades) next
  attempted to install a kernel, it failed.  On failure, mkinitramfs
  leaves a temporary directory in /var/tmp.

  If you (or unattended upgrades) do this enough times, you can end up
  with substantial, non-obvious disk usage.

  (I believe that this is fixed in Debian: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=814345)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 30 09:12:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-30 (700 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-03-07 (114 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1597661/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1037285] Re: /boot fills up after many kernel upgrades

[spike speigel]

bug # 1515513 is a contributing factor.  DKMS has been patched upstream
for that particular bug.  Not sure when Ubuntu will update or
incorporate the patch into their packaged version of dkms.

Are there any other files left behind after kernel updates that might
cause these kinds of update problems?  Are there different circumstances
in which a file may or may not be deleted?

It affects every install that uses dkms and updates kernels in the long
run.

This doesn't put any Linux distribution in a favorable light.

This bug eventually leaves the system in an insecure, unstable state.

And this has been happening since at least 2012 (that's when I first
noticed updates failing due to lack of space in /boot).  As others have
stated, it is impossible to resolve manually for those who are not
technical and just want to use the desktop.  My father has actually had
this happen on the Ubuntu install I set up for him.

I agree. I think it should be handled as a security issue with a higher
priority.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1037285

Title:
  /boot fills up after many kernel upgrades

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  THIS ISSUE MAY PREVENT SECURITY UPDATES TO THE KERNEL.

  Obsolete versions of the kernel remain installed on a system, causing a full 
/boot or wasting space on single-partition installations.
  This has the effect that (some) software updates no longer work (at least 
those to the kernel):

  update-initramfs: Generating /boot/initrd.img-3.2.0-29-generic

  gzip: stdout: No space left on device
  [...]
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  To resolve this, the user must figure out which packages to deinstall.
  A novice user will not know what to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1037285/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[spike speigel]

/usr/share/pulseaudio/alsa-mixer/paths/analog-input-headphone-mic.conf

I just found this from a separate bug thread.  This looks interesting.
The options for volume are:

volume = ignore | merge | off | zero | 

# What to do with this volume: ignore it, merge it into the device
# volume slider, always set it to the lowest value possible, or always
# set it to 0 dB (for whatever that means), or always set it to
#  (this only makes sense in path configurations where
# the exact hardware and driver are known beforehand).

Is this touched by Pulse when updates are applied?  I was going to test
out zero and ignore to see what happens.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[spike speigel]

I still haven't figured out how Pulse determines the default levels it
forces upon the user at each start of the service.  I think it should
respect those levels set within ALSA/the system.  If Pulse can't respect
selected values, then I'd like to know where it gets its default values.
That way I can manually change them and force my default values down
Pulse's throat.

pactl is a hot mess to understand.  I don't see a way to set volume on
ports at all.  Maybe it isn't even possible using pactl.

/etc/pulse/default.pa
/etc/pulse/system.pa

don't seem to provide help either.  I tried modifying a few things
there, and it broke the automatic muting when switching between
headphones and internal speakers.  So I put all that back the way it
was.

I also noticed if:

1.  I have alsamixer open along with pavucontrol
2.  Set the headphone mic dB gain to 10% in alsamixer
3.  In pavucontrol select the "Microphone" from the dropdown under the "Input 
Devices" tab

Result:
pavucontrol resets the dB gain to 0%, "the default" without me even touching 
the volume slider...in fact I CAN'T touch the volume slider for the mic.  Why 
can't Pulse work with functionality ALSA clearly provides?

Googling for answers on pulse and volume issues just seems to return a
lot of annoyed users and scripted hack answers which really aren't
solutions.

If I had a way to set the port volume for the mic and have it remain
that way permanently, that would work for me.  After reducing the dB
gain I can still up the volume to compensate without the hiss returning.

If we can determine it is a bug somewhere and fix it at the root, even
better.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

@vanvugt  I do have both cable types (with and without cable mic).  In
testing the Quiet Comfort 15s:

Bose CQ 15 w/ normal cable - The hiss is present with 0 dB headphone mic
gain, but far more reduced than the Sony earbuds.  It is almost
unnoticeable.  If I weren't trying to hear it, I'd miss it.

Bose CQ 15 w/ mic cable - I cannot detect any hiss present with 0 db
gain.


@esokrarkose  I'm sorry I misunderstood what you were saying about your
experience with the hiss.  I thought you were saying it only happened
while playing a sound.  I too experience the constant hiss with my
earbuds.  I don't doubt the hiss in normal headphones.

The Bose CQs do produce the hiss with one cable type.  It is barely
noticeable and much more subdued than the earbuds.  I'm not sure what
Bose does if anything with the sound signal coming from the headphone
jack.  Maybe it's just reduced due to higher quality speakers than say
my earbuds.  As I understand it the noise cancellation is meant for
external sounds, but like you said, maybe it plays a role in making the
hiss less audible.  The noise cancellation itself does produce a level
of white noise.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

Out of curiosity I tried my Bose Quiet Comfort 15s, and I can't detect
the hiss in those at either a dB gain of 0.00 or 10.00 with the
headphone mic boost.

That is odd.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

I would like to say I have plain old Sony earbuds, and the sound is very
noticeable without playing any sound what so ever.  As previously
mentioned, upping the dB gain on the headphone mic boost from 0.00 to
10.00 completely stops the hissing for whatever reason.

Also, the Arch Linux wiki has some related notes regarding TLP and
hissing through headphones reported.  I've not messed with TLP at all.
/etc/default/tlp as referenced in the wiki does not exist on my system.

https://wiki.archlinux.org/index.php/Dell_XPS_13_(9360)#Troubleshooting

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

Here's an earlier bug report (~Dec 2015):

http://lkml.iu.edu/hypermail/linux/kernel/1512.1/02819.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** No longer affects: dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

** No longer affects: dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** Project changed: initramfs-tools => dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in Dell Sputnik:
  Invalid
Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1515513/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Description changed:

  One notices *.old-dkms files being left behind still sitting on the disk
  after purging the related kernel. This can cause /boot to become full,
  and when it gets really bad, even sudo apt-get autoremove won't fix the
  problem - only deleting the old-dkms files manually solves the problem.
+ 
+ Note:  Filling up the /boot partition causes updates to fail.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in Dell Sputnik:
  New
Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1515513/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

Will the fix be included in Zesty or Artful?

** Tags added: artful yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1651433] Re: bluetooth mouse random disconnects

[spike speigel]

** Tags added: xenial

** Also affects: bluez
   Importance: Undecided
   Status: New

** Project changed: bluez => dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1651433

Title:
  bluetooth mouse random disconnects

Status in Dell Sputnik:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I received the Dell XPS 13 DE (9350) accompanied by the WD15 docking station 
last September. Ever since I used it with my Logitech MX Master bluetooth mouse.
  This worked very well and reliably for September through November.
  But Since about start of December, it disconnects frequently and without any 
apparent reason.
  I can get it back to order by disabling and re-enabling the bluetooth radio 
of the notebook. After I re-enable the bt radio and move the mouse it work 
immediately without any delay.
  Sometimes it disconnects after 10 seconds. Sometimes I can work for 10 hours 
without any disconnect.
  For the entire lifetime the device has been running xenial. Currently I'm on 
kernel Linux XPS13ulr 4.4.0-53-generic #74-Ubuntu SMP
  Because the issue started happening at a certain date, I strongly believe 
that it was caused by and upgrade, possibly kernel.

  I wanted to see if the same disconnects also happen with other BT devices. 
But for as long as I had the Jabra Halo 2 headset connected, also the mouse 
worked reliably. 
  The mouse is my only BT LE device. Maybe that makes a difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651433/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack

[spike speigel]

** Also affects: pulseaudio
   Importance: Undecided
   Status: New

** Project changed: pulseaudio => dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1650259

Title:
  [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from
  the headphone jack

Status in Dell Sputnik:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The problem is that there is no sound at the jack for the headphones.

  Internal speaker are silenced when inserted a headphone jack but there is no 
sound output.
  Tested a live MS windows and sound worked!

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaki   2355 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 15 12:41:55 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-06-25 (173 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaki   2355 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-09-07 (98 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 0H67KH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03: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/dell-sputnik/+bug/1650259/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1688317] Re: PCI/internal sound card not detected

[spike speigel]

** Also affects: alsa-driver
   Importance: Undecided
   Status: New

** Project changed: alsa-driver => dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1688317

Title:
  PCI/internal sound card not detected

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound card detected at all, no sound for laptop/bluetooth
  headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu May  4 10:41:20 2017
  InstallationDate: Installed on 2017-01-25 (98 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1688317/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor

[spike speigel]

** Tags added: xenial

** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1467595

Title:
  cursor sometimes disappears on XPS 13 9343 and external monitor

Status in Dell Sputnik:
  New
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using
  an external display port monitor. Occasionally, the mouse cursor
  disappears (sometimes after screen lock, other times just normal
  usage). I saw something on stack exchange that said this might help:

  gsettings set org.gnome.settings-daemon.plugins.cursor active false

  I've done this and it sometimes helps and sometimes doesn't. I've also
  just seen the cursor come back on its own after a few minutes without
  doing anything. Trying to interact with the touch screen, then the
  mouse has no effect. Unplugging and replugging the mouse has no
  effect. Using the touchpad has no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 22 11:19:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-06-13 (8 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet 
splash vt.handoff=7
  SourcePackage: unity
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 10:53:54 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1467595/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

** Also affects: pulseaudio
   Importance: Undecided
   Status: New

** Project changed: pulseaudio => dell-sputnik

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[spike speigel]

** Tags added: zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1583801

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  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/alsa-driver/+bug/1583801/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

** Tags added: zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Tags added: zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1671873] Re: Upgrade to Yakkety removes eth0 from /etc/network/interfaces

[spike speigel]

Possible dup of 1676547 ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1671873

Title:
  Upgrade to Yakkety removes eth0 from /etc/network/interfaces

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded this machine from Kubuntu 16.04 to Kubuntu 16.10
  using the uprading UI. Before the upgrade, I had lo and eth0 in
  /etc/network/interfaces. After the upgrade, there was only lo, no eth0
  anymore, leaving me without a network connection. I had to re-enter
  eth0 into the file and restart the networking service to get
  networking functionality again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 10 17:24:57 2017
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   auto eth0
   iface eth0 inet dhcp
  InstallationDate: Installed on 2012-01-28 (1868 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.100.254 dev eth0 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.100.0/24 dev eth0  proto kernel  scope link  src 192.168.100.3
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-03-09 (1 days ago)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671873/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[spike speigel]

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

** This bug is no longer a duplicate of bug 1658921
   NetworkManager does not manage wired connection
** This bug has been marked a duplicate of bug 1676547
   No network connectivity after upgrade from 16.04 to 16.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

[spike speigel]

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

** This bug has been marked a duplicate of bug 1676547
   No network connectivity after upgrade from 16.04 to 16.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1658921

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1683836] Re: WIFI stoped working when updating 16.10 -> 17.04

[spike speigel]

Possible dup of bug 1676547 ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1683836

Title:
  WIFI stoped working when updating 16.10 -> 17.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Network manager detects 'Bus 001 Device 004: ID 148f:5370 Ralink
  Technology, Corp. RT5370 Wireless Adapter'. It detects WIFI network,
  but fails to connect. I booted with older kernel
  vmlinuz-4.8.0-46-generic: same result.  I installed ubuntu 16.10 to
  same computer and WIFI does work.  Password is OK.

  Authentication seems to fail in Ubuntu 17.04:
  Apr 18 17:13:01 k10 NetworkManager[727]: 
  [1492524781.2784] policy: auto-activating connection 'ZyXELbb3a'
  [1492524781.2798] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (5362ba4d-c40e-40a3-8e17-4e3deaab48ae)
  [1492524781.2801] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
  [1492524781.6699] device (wlxc83a35cde1eb): set-hw-addr: set-cloned MAC 
address to C8:3A:35:CD:E1:EB (permanent)
  [1492524781.9391] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492524781.9394] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
  [1492524781.9395] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
  [1492524781.9748] device (wlxc83a35cde1eb): state change: need-auth -> 
prepare (reason 'none') [60 40 0]
  [1492524781.9782] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492524781.9792] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
  [1492524781.9796] Config: added 'ssid' value 'ZyXELbb3a'
  [1492524781.9800] Config: added 'scan_ssid' value '1'
  [1492524781.9803] Config: added 'key_mgmt' value 'WPA-PSK'
  [1492524781.9806] Config: added 'auth_alg' value 'OPEN'
  [1492524781.9808] Config: added 'psk' value ''
  [1492524781.9821] sup-iface[0x55d34390d2d0,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
  [1492524782.0010] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> scanning
  [1492524783.3941] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
  [1492524783.5787] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected
  [1492524793.5868] device (wlxc83a35cde1eb): supplicant interface state: 
disconnected -> scanning
  [1492524794.9891] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
  [1492524795.1145] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected

  
  Ubuntu 16.10 is same to authentication:
  Apr 18 13:46:10 k15 NetworkManager[714]: 
  [1492512370.3874] policy: auto-activating connection 'ZyXELbb3a'
  [1492512370.3884] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (fd199068-2375-4268-bb74-d60484d1fadb)
  [1492512370.3886] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
  [1492512370.3887] manager: NetworkManager state is now CONNECTING
  [1492512370.3895] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492512370.3897] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
  [1492512370.3898] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
  [1492512370.3936] device (wlxc83a35cde1eb): state change: need-auth -> 
prepare (reason 'none') [60 40 0]
  [1492512370.3940] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
  [1492512370.3943] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
  [1492512370.3943] Config: added 'ssid' value 'ZyXELbb3a'
  [1492512370.3944] Config: added 'scan_ssid' value '1'
  [1492512370.3944] Config: added 'key_mgmt' value 'WPA-PSK'
  [1492512370.3944] Config: added 'auth_alg' value 'OPEN'
  [1492512370.3944] Config: added 'psk' value ''
  [1492512370.3949] sup-iface[0x55da7c3f2210,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
  [1492512371.8005] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> authenticating
  [1492512371.8071] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> associating
  [1492512371.8216] device (wlxc83a35cde1eb): supplicant interface state: 
associating -> 4-way handshake
  [1492512371.8482] device (wlxc83a35cde1eb): supplicant interface state: 4-way 
handshake -> completed
  [1492512371.8482] device (wlxc83a35cde1eb): Activation: (wifi) Stage 2 of 5 
(Device Configure) successful.  Connected to wireless network 

[Touch-packages] [Bug 1637129] Re: network-manager suddenly reports ethernet is unmanaged

[spike speigel]

** Tags added: yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1637129

Title:
  network-manager suddenly reports ethernet is unmanaged

Status in network-manager package in Ubuntu:
  New

Bug description:
  Using 16.10

  ethernet stopped working, network indicator & nmcli reports that my ethernet 
is unmanaged.
  ifconfig reports it has no ip address. I turn on wifi and it works fine.

  Doing ifconfig  up; dhclient  works for
  getting ip address

  I did have network-manager snap installed for a brief amount of time,
  but have since removed it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637129/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

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

** This bug has been marked a duplicate of bug 1676547
   No network connectivity after upgrade from 16.04 to 16.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1681884

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends

[spike speigel]

For anyone who might find their way here while using newer versions of
Ubuntu such as 16.04 LTS, 16.10, 17.04...

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/446657

Title:
  Bluetooth's on/off status doesn't update from the SetProperty D-Bus
  method that bluetoothd sends

Status in GNOME Bluetooth:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in bluez package in Fedora:
  Unknown

Bug description:
  Binary package hint: gnome-bluetooth

  Gnome's bluetooth applet should get a bluetooth device's on/off status
  through dbus from SetProperty setting sent by bluetoothd. This
  information was given in
  http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a
  setting controlling this feature: RememberPowered=true in
  /etc/bluetooth/main.conf

  Questions:
  Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't 
do anything for it? Does bluez's SetProperty actually find the last (if even 
saved) bluetooth status?

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct  8 20:54:15 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: gnome-bluetooth 2.28.1-0ubuntu1
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: gnome-bluetooth
  Uname: Linux 2.6.31-12-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[spike speigel]

@aapo-rantalainen

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

[spike speigel]

@cibersheep

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1296114

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in rfkill package in Ubuntu:
  Incomplete
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[spike speigel]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1073669

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

Merged upstream :D

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

Looks like that patch has just sat there since last year :(

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

ALC256 looks like a codec, and I always thought ALC 3246 was the Realtek
"model/chip".  Not sure if my thoughts on that are accurate.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

What's the diff between ALC256 and ALC3246??  It seems the 9350 has the
ALC3246 as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543888] Re: LightDM crashes/hangs during resume from suspend

[spike speigel]

This is happening to me in 16.04 LTS.

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1543888

Title:
  LightDM crashes/hangs during resume from suspend

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  lightdm:
Installed: 1.16.7-0ubuntu1
Candidate: 1.16.7-0ubuntu1
Version table:
   *** 1.16.7-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.16.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

  Expected: To be able to resume from suspend and be able to reliably
  use my desktop.

  What happened: Sometimes the UI is completely nonresponsive to
  keystrokes or mouse input after opening the lid of the computer. I am
  forced to cut the power.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.7-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Tue Feb  9 18:20:50 2016
  InstallationDate: Installed on 2014-11-28 (438 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to wily on 2016-01-14 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1543888/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

** Tags added: 9360 alsa dell headphones pulse realtek xenial xps

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[spike speigel]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

[spike speigel]

I'm experiencing this in 16.04 LTS as well...

$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux


** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1296114

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in rfkill package in Ubuntu:
  Incomplete
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

Also found this:

https://github.com/dell/dkms/issues/2

It's known upstream in debian and dkms, but whether dkms or initramfs-
tools should be responsible for cleaning up files left behind by
dkms...I dunno.  What you posted sounded like it made sense to me.

I just wanted to note at least dkms has an upstream bug report (which
was opened May 2016).

** Bug watch added: github.com/dell/dkms/issues #2
   https://github.com/dell/dkms/issues/2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Could this be the same issue as bug #1676547 ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1681884

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1681884] Re: [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Both the onboard wifi and ethernet through the Dell DA200 USB-C adapter
work properly in 16.04 LTS running the following kernel:

$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1681884

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1681884] [NEW] [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

[spike speigel]

Public bug reported:

Upon a "clean" upgrade (No software installed except base system from
ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
Network Manager fails to detect wiFi device in 17.04 Zesty after a few
boots/updates.  Wifi works initially.  I apply Zesty updates.  I
autoremoved some packages.  I reboot.  Wifi is killed.  I cannot report
the bug using "ubuntu-bug" because I have no network connectivity.

The wifi device was not detected despite re-enabling Dell's Xenial repos
after upgrades.

I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
Plugging ethernet cable into that does not work either.  It seemed the
adapter was "half" recognized.  Something did show up in Network Manager
after fiddling with settings, but no network connectivity ever occurred.
I can create a separate bug for that if needed.

I subsequently had to revert back to 16.04 LTS with a clean install to
report the bug.  I'm not so familiar with what the Dell repos provide
for Xenial.  Do they provide the drivers needed for the wifi?  Or is
that supplied through the kernel?  Could the autoremove have caused the
wifi drivers to be removed?

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 17.04 9360 autoremove dell latest-bios-1.3.2 manager network repo 
upgrade wifi xenial zesty

** Tags added: latest-bios-1.3.2

** Summary changed:

- [Dell 9360] NetworkManager fails to detect wifi device in 17.04 Zesty
+ [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04 Zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1681884

Title:
  [Dell XPS 9360] NetworkManager fails to detect wifi device in 17.04
  Zesty

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upon a "clean" upgrade (No software installed except base system from
  ISO, then upgrade) from 16.04 LTS -> 16.10 -> 17.04 on a Dell 9360,
  Network Manager fails to detect wiFi device in 17.04 Zesty after a few
  boots/updates.  Wifi works initially.  I apply Zesty updates.  I
  autoremoved some packages.  I reboot.  Wifi is killed.  I cannot
  report the bug using "ubuntu-bug" because I have no network
  connectivity.

  The wifi device was not detected despite re-enabling Dell's Xenial
  repos after upgrades.

  I have a Dell DA200 adapter USB-C to HDMI/VGA/Ethernet/USB 3.0.
  Plugging ethernet cable into that does not work either.  It seemed the
  adapter was "half" recognized.  Something did show up in Network
  Manager after fiddling with settings, but no network connectivity ever
  occurred.  I can create a separate bug for that if needed.

  I subsequently had to revert back to 16.04 LTS with a clean install to
  report the bug.  I'm not so familiar with what the Dell repos provide
  for Xenial.  Do they provide the drivers needed for the wifi?  Or is
  that supplied through the kernel?  Could the autoremove have caused
  the wifi drivers to be removed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681884/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

[spike speigel]

I'm experiencing this behavior with a Dell XPS 13 9360 Developer Edition

I'm not running xfce.  I'm using stock Unity, but lightdm is running.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1581302

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1636905] Re: Sound card not recognized on Dell Vostro 5568

[spike speigel]

Hi there hakon,

I too have Realtek ALC3246 in my Dell XPS 13 9360

grep "Codec:" /proc/asound/card*/codec*
/proc/asound/card0/codec#0:Codec: Realtek ALC3246
/proc/asound/card0/codec#2:Codec: Intel Kabylake HDMI

I ran through all the commands you listed in comment #4, and I had the
same output except:

lspci -v | grep Audio
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) (prog-if 80)

I have the extra "(prog-if 80)"

I'm not dual booting.  I've not experienced sound stop working, but I've
also seldom used suspend.  But when I have suspended, sound has always
worked.

I did not receive my system until Feb 2017.  It is a different model,
but we appear to share the same audio.  What version of Pulseaudio and
ALSA are you using?  What version of Ubuntu do you have now?  What
kernel version are you running?  Does your system have the latest BIOS?

I've tried the latest 4.4, 4.8, and even 4.10 kernels under 16.04 LTS
without issue, all using the latest LTS versions of Pulseaudio and ALSA.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1636905

Title:
  Sound card not recognized on  Dell Vostro 5568

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just reinstalled a fresh Ubuntu 16.10 on my Dell Vostro 5568 laptop.

  The audio controller on the laptop is a Realtek ALC3246 with Waves
  MaxxAudio Pro. The external interface connector is a microphone
  in/stereo headphones/external speakers connector.

  When I select "System Settings->Sound" the output device in the dialog
  window shows as "Dummy Output" and when I press the "Test Sound"
  button no sound is heard from either front left or front right speaker
  ( I have ensured sound is not muted ).

  Note: Before reinstalling, I asked a question on askubuntu,com:

  http://askubuntu.com/q/841759/156688

  So reinstallation of Ubuntu 16.10 did not help on my sound problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636905/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[spike speigel]

Same issue here.  No sound via headphones (headset) when Ubuntu boots
with them plugged in

[Dell XPS 13 9360 Developer Edition]
Ubuntu 16.04 LTS

I can get them to start playing audio by unplugging them and plugging
them back in, but I shouldn't have to. :(

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1583801

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  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/alsa-driver/+bug/1583801/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[spike speigel]

Found a DKMS bug report here:

https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[spike speigel]

This might be aggravated by this DKMS bug which was found in v2.2.0.3,
which incidentally is used in Ubuntu 16.04 LTS, and maybe other
versions.  It doesn't remove old initrd files in /boot *which lead to
full /boot issues and subsequent update problems*

I manually removed a bunch of old initrd images the other day.

http://askubuntu.com/questions/616512/purging-old-kernels-fails-to-
remove-old-initrd-files

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584

** Bug watch added: Debian Bug tracker #717584
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717584

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

Switching to the xserver-xorg-hwe-16.04 package from plain xserver-xorg
(using xserver-xorg-video-intel-hwe-16.04
(2:2.99.917+git20160706-1ubuntu1~16.04.1)) has fixed the issue with
screen flicker in chrome.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  New

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

Fond I have to switch to xserver-xorg-hwe-16.04 from xserver-xorg in
order to prevent broken dependency issues and completely install hwe
versions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

Mesa:   v12.0.6-0ubuntu0.16.04.1
xserver-xorg-video-intel:   2:2.99.917+git20160325-1ubuntu1.2

Although I have the 16.04.1 Hardware Enablement (HWE) kernel, it appears
there is an HWE version of xserver-xorg-video-intel I was not aware of,
and which was not automatically selected with the HWE kernel.  I will
try that now (Using my current 16.04.1 LTS xenial HWE install).

xserver-xorg-video-intel-hwe-16.04:
2:2.99.917+git20160706-1ubuntu1~16.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

It is!

I've also kept this one-liner in my bash history so I don't have to
enter alsamixer and use multiple key strokes:

amixer -c 0 set 'Headphone Mic Boost',0 1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

I tested the current live image you suggested via USB drive.  I had to
enable additional package repos and install google-chrome-stable.  I did
not add the Dell Xenial/Zesty repos, as I was not sure those are
required with the newer Zesty kernel.  I also could not add the Dell
Xenial/Zesty repos and reboot to have them properly loaded.  The USB
drive has some file persistence, but not when dealing with system files.
Any package installs/updates were lost upon reboot.

I did not experience the issue running the current Zesty live image, but
I'm also not sure the latest intel drivers were being used.

If live image customization is something you think I should use, I can
go that route.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

I actually moved to the LTS HWE kernel sometime last week to see if that
might help.  I can say it has made no difference.

$ uname -a
Linux blackhole 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1641467] Re: Mouse flickering and disappearing near the top of screen

[spike speigel]

Hmm nvmd I see GeForce GT 540M listed...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1641467

Title:
  Mouse flickering and disappearing near the top of screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  So I'm not sure this is an xorg bug, I couldn't figure out what xorg
  is. But I recently upgraded to ubuntu 16.10 and started seeing this
  bug where my mouse will flicker and disappear when near the top of the
  screen. It still works clicking-wise. It also seems to be especially
  severe when using Google Chrome, where it completely disappears and
  flickers the entire time while mousing over the menu uptions (i.e the
  close button, the tabs etc...). However recently I noticed this also
  happens when google chrome is off, though it flickers much less.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Nov 14 00:01:59 2016
  DistUpgraded: 2016-11-11 16:58:41,906 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  InstallationDate: Installed on 2016-08-30 (74 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=8efe8f71-2303-4aff-921a-1f80026e1b6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-11-11 (2 days ago)
  dmi.bios.date: 03/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 15HX.M042.20120302.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 15HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: RF511/RF411/RF711
  dmi.product.version: 15HX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Nov 13 17:46:35 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1641467] Re: Mouse flickering and disappearing near the top of screen

[spike speigel]

Could this be a dup of https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/+bug/1586539 ??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1641467

Title:
  Mouse flickering and disappearing near the top of screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  So I'm not sure this is an xorg bug, I couldn't figure out what xorg
  is. But I recently upgraded to ubuntu 16.10 and started seeing this
  bug where my mouse will flicker and disappear when near the top of the
  screen. It still works clicking-wise. It also seems to be especially
  severe when using Google Chrome, where it completely disappears and
  flickers the entire time while mousing over the menu uptions (i.e the
  close button, the tabs etc...). However recently I noticed this also
  happens when google chrome is off, though it flickers much less.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Nov 14 00:01:59 2016
  DistUpgraded: 2016-11-11 16:58:41,906 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  InstallationDate: Installed on 2016-08-30 (74 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=8efe8f71-2303-4aff-921a-1f80026e1b6e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-11-11 (2 days ago)
  dmi.bios.date: 03/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 15HX.M042.20120302.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 15HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: RF511/RF411/RF711
  dmi.product.version: 15HX
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Nov 13 17:46:35 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

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

https://bugs.chromium.org/p/chromium/issues/detail?id=606152

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  New

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] Re: Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

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

** This bug has been marked a duplicate of bug 1586539
   Major screen flickering in Chromium and Google Chrome

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  New

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 22 09:14:10 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5194 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

I would like to share that I found this post referring to a similar
issue where sound settings weren't maintained, maintained being a better
word than saved because I believe alsamixer might properly save the
settings.

According to the post it is pulseaudio which is actually modifying the
settings:

http://askubuntu.com/a/549939

I tested as suggested, by modifying the "Headphone Mic Boost" within
alsamixer and exiting.  I then ran:

pulseaudio -k

And pulseaudio reset the "Headphone Mic Boost" to dB gain 0.00, 0.00.
The hissing reappeared.

If I could get pulseaudio to stop resetting the "Headphone Mic Boost" in
alsamixer, then that would be an acceptable workaround.

But, I think the real issue still needs to be resolved.  One would
expect a dB gain 0.00, 0.00 to be absolutely silent.  The user should
not need to kick it up a notch to dB gain 10.00, 10.00.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1666994] [NEW] Screen flicker on Dell XPS 13 9360 Developer Edition

[spike speigel]

Public bug reported:

I get a periodic screen flicker across the top of the screen when using
the mouse in that area.  Otherwise, no other issues like blank
screening, corruption, or the like.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Feb 22 10:43:56 2017
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:075b]
InstallationDate: Installed on 2017-02-04 (17 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. XPS 13 9360
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Feb 22 09:14:10 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5194 
 vendor SHP
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1666994

Title:
  Screen flicker on Dell XPS 13 9360 Developer Edition

Status in xorg package in Ubuntu:
  New

Bug description:
  I get a periodic screen flicker across the top of the screen when
  using the mouse in that area.  Otherwise, no other issues like blank
  screening, corruption, or the like.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 10:43:56 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-02-04 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

I'm experiencing the same issue:

Dell XPS 13 Developer Edition

BIOS v1.3.2

Ubuntu 16.04

spike@blackhole:~$ uname -a
Linux blackhole 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

spike@blackhole:~$ apt search alsa-base
Sorting... Done
Full Text Search... Done
alsa-base/xenial,xenial,now 1.0.25+dfsg-0ubuntu5 all [installed]
  ALSA driver configuration files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1654448

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp