[Kernel-packages] [Bug 1997201] Re: BlueZ 5.66 release

[Jeremy Bicha]

I've uploaded this for you.

I did notice that the "original" tarball you provided and is compatible
with the Launchpad git tree doesn't match the original tarball used by
Debian for 5.66.

Not a problem here, but if we ever did get the bluez packaging closer in
sync with Debian, it might be nice to use the same tarballs.

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  BlueZ 5.66 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release to Lunar:

  http://www.bluez.org/release-of-bluez-5-66/

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


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

[Kernel-packages] [Bug 1988364] Re: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

[Jeremy Bicha]

** Also affects: bluez (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  Triaged

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

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


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

[Kernel-packages] [Bug 1986796] Re: amd64-microcode conflicts with linux-firmware

[Jeremy Bicha]

This was also detected by autopkgtests:
https://autopkgtest.ubuntu.com/packages/v/vrms/kinetic/amd64

** Changed in: amd64-microcode (Ubuntu)
   Importance: Undecided => High

** Changed in: amd64-microcode (Ubuntu)
   Status: Confirmed => Triaged

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

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

** Changed in: linux-firmware (Ubuntu)
   Status: New => Triaged

** Tags added: rls-kk-incoming update-excuse

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

Title:
  amd64-microcode conflicts with linux-firmware

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Occurs on kubuntu, gnome and xfce versions of kinetic proposed -- most
  recent updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: amd64-microcode 3.20191218.1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Aug 17 08:07:09 2022
  InstallationDate: Installed on 2022-06-10 (67 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220610)
  SourcePackage: amd64-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1738272] Re: microcode packages, like firmware packages, should be in main

[Jeremy Bicha]

By the way, Debian created a new component, non-free-firmware, last
month. I don't believe any Debian packages have switched to it yet.
Based on this bug history, I'm guessing we'd want to automatically
import those packages to universe then (or main where we want it part of
our Canonical-supported set).

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

Title:
  microcode packages, like firmware packages, should be in main

Status in firmware-sof package in Ubuntu:
  New
Status in intel-microcode package in Ubuntu:
  Fix Released
Status in iucode-tool package in Ubuntu:
  Fix Released

Bug description:
  The MIR for intel-microcode and iucode-tool in LP: #139 requested
  that these packages be shipped in restricted.

  The iucode-tool package is free software, and is shipped in restricted
  only because of the circular recommends with intel-microcode.

  The intel-microcode package contains non-free software (free
  redistribution, but no source code).  However, this code is not part
  of the OS; it runs /under/ the OS on the CPU, and is analogous to
  linux-firmware, which we do include in main.

  The question of suitability for restricted vs. main in Ubuntu was not
  examined as part of the previous MIR, and the security team signed off
  on it for "restricted or main as appropriate"; so I think the decision
  to put it in restricted was not based on a thorough examination of the
  facts by an archive admin, and does not represent a precedent that
  needs to be examined further.

  I believe that these two packages should be promoted to main for
  consistency.

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


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

[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release

[Jeremy Bicha]

I've uploaded this to kinetic-proposed and am unsubscribing ubuntu-
sponsors. Thanks!

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

Title:
  BlueZ 5.65 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.65 to kinetic:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz

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


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

[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release

[Jeremy Bicha]

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  BlueZ 5.65 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.65 to kinetic:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz

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


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

[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

[Jeremy Bicha]

I have verified that gnome-remote-desktop 42.1.1-0ubuntu1 depends on
fuse3

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

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

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  Fix Committed
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions


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

[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

[Jeremy Bicha]

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

** Also affects: fuse3 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gnome-remote-desktop (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: fuse3 (Ubuntu)

** No longer affects: fuse3 (Ubuntu Jammy)

** No longer affects: linux (Ubuntu Jammy)

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  In Progress
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970411/+subscriptions


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

[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

[Jeremy Bicha]

0x5605ed301820
+ args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
+ argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
+ result = 
  
  Further details:
-  - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
+  - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

** Changed in: gnome-remote-desktop (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-remote-desktop (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in fuse3 package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop package in Debian:
  New

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
  rdp_fuse_clipboard = 0x5605ed301820
  args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
  argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
  result = 

  Further details:
   - https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f

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


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

[Kernel-packages] [Bug 1970412] Re: [VROC] Ubuntu doesn't support 3rd SATA

[Jeremy Bicha]

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

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

Title:
  [VROC] Ubuntu doesn't support 3rd SATA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  An effort has been made to enable 3rd SATA support in kernel, but 
unfortunately the patch didn't make it to upstream (we are still working to 
make it happen). Without it certain utility programs cannot function properly 
when 3rd SATA is engaged.
  The patch itself adds Intel Emmitsburg PCH RAID PCI IDs to the list of 
supported controllers. Would you kindly apply this patch to 22.04 release?

  Patch to be applied: https://lore.kernel.org/linux-
  ide/20201119104318.79297-1-mika.westerb...@linux.intel.com/

  Regards,
  Lukasz

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


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

[Kernel-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

[Jeremy Bicha]

I closed the gnome-bluetooth part of this bug since this was apparently
fixed in pulseaudio instead.

** Changed in: gnome-bluetooth (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in blueman source package in Xenial:
  New
Status in gnome-bluetooth source package in Xenial:
  Invalid
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings 
(the correct device's options don't appear in the right pane). Hence no 
Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (its options appear in the 
right pane when clicked and the selection stays on that device).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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


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

[Kernel-packages] [Bug 1847478] Re: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule"

[Jeremy Bicha]

** Information type changed from Public to Public Security

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

Title:
  eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF
  is set on suppress rule"

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  An unprivileged local attacker could cause a denial of service, or
  possibly execute arbitrary code due to an ipv6 regression.

  [Test Case]

  An unpatched system will crash with the following command:

  $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set
  dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add
  table main suppress_prefixlength 0 && ping -f 1234::1'

  [Regression Potential]

  Low. The change could theoretically introduce a memory leak but that
  would still be an improvement over immediate loss of system
  availability.

  [Original Description]

  Having recently upgraded to Eoan Ermine from Disco Dingo, my
  previously rock-solid wireguard now locks the system up shortly after
  I take the connection down with wg-quick down wg0.

  Package:

  wireguard:
    Installed: 0.0.20190913-1ubuntu1
    Candidate: 0.0.20190913-1ubuntu1
    Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  Kernel:
  5.3.0-13-generic

  Snipped from /var/log/syslog:

  kernel: [  776.930804] BUG: unable to handle page fault for address: 
1070
  kernel: [  776.930807] #PF: supervisor read access in kernel mode
  kernel: [  776.930808] #PF: error_code(0x) - not-present page
  kernel: [  776.930809] PGD 0 P4D 0
  kernel: [  776.930811] Oops:  [#1] SMP NOPTI
  kernel: [  776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G  
 OE 5.3.0-13-generic #14-Ubuntu
  kernel: [  776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 
1.7.0 08/05/2019
  kernel: [  776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0
  kernel: [  776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 
01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 
<48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50
  kernel: [  776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202
  kernel: [  776.930821] RAX: 0080 RBX: a0933c829360 RCX: 
0007
  kernel: [  776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: 
a0933c828f00
  kernel: [  776.930823] RBP: beb841a9fcf0 R08:  R09: 

  kernel: [  776.930823] R10:  R11: a093948fd800 R12: 
a0933c829360
  kernel: [  776.930824] R13: a0933c828f38 R14: 0001 R15: 
a0933c829360
  kernel: [  776.930825] FS:  7fbcd8a82700() GS:a0939e4c() 
knlGS:
  kernel: [  776.930826] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [  776.930827] CR2: 1070 CR3: 00049172a004 CR4: 
003606e0
  kernel: [  776.930828] Call Trace:
  kernel: [  776.930832]  ip6_datagram_dst_update+0x15e/0x280
  kernel: [  776.930835]  ? _raw_read_unlock_bh+0x20/0x30
  kernel: [  776.930837]  __ip6_datagram_connect+0x1da/0x380
  kernel: [  776.930839]  ip6_datagram_connect+0x2d/0x50
  kernel: [  776.930841]  inet_dgram_connect+0x3f/0xc0
  kernel: [  776.930843]  __sys_connect+0xf1/0x130
  kernel: [  776.930846]  ? do_fcntl+0xe4/0x550
  kernel: [  776.930848]  ? fput+0x13/0x15
  kernel: [  776.930849]  __x64_sys_connect+0x1a/0x20
  kernel: [  776.930852]  do_syscall_64+0x5a/0x130
  kernel: [  776.930854]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  kernel: [  776.930855] RIP: 0033:0x7fbcde6324eb
  kernel: [  776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 
ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 
<48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44
  kernel: [  776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 
002a
  kernel: [  776.930859] RAX: ffda RBX: ff94 RCX: 
7fbcde6324eb
  kernel: [  776.930859] RDX: 001c RSI: 7fbcd8a7ecf0 RDI: 
0022
  kernel: [  776.930860] RBP: 7fbcd8a7edb0 R08:  R09: 
7fbcd8a7edf8
  kernel: [  776.930861] R10: 7fbcd8a7edf0 R11: 0293 R12: 
250e77c19710
  kernel: [  776.930862] R13: 250e77c19900 R14: 7fbcd8a7edc8 R15: 
7fbcd8a7edc8
  kernel: [  776.930863] Modules linked in: binfmt_misc wireguard(OE) 
ip6_udp_tunnel udp_tunnel ccm rfcomm uhid algif_hash algif_skcipher af_alg cmac 
bnep sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_byt snd_sof_intel_ipc 

[Kernel-packages] [Bug 1818430] [NEW] Please update aufs driver

[Jeremy Bicha]

Public bug reported:

The latest Debian package of aufs-tools fails to build on Ubuntu 19.04
because it is looking for a non-RC version of aufs. Currently, Ubuntu's
aufs reports as "4.x-rcN-20180917"

References
--
https://sources.debian.org/src/aufs-tools/unstable/ver.c
https://launchpad.net/ubuntu/+source/aufs-tools/1:4.14+20190211-1
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=82ab94a2db

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


** Tags: disco kernel-fs

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

Title:
  Please update aufs driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest Debian package of aufs-tools fails to build on Ubuntu 19.04
  because it is looking for a non-RC version of aufs. Currently,
  Ubuntu's aufs reports as "4.x-rcN-20180917"

  References
  --
  https://sources.debian.org/src/aufs-tools/unstable/ver.c
  https://launchpad.net/ubuntu/+source/aufs-tools/1:4.14+20190211-1
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=82ab94a2db

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

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

[Kernel-packages] [Bug 1754370] Re: Sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main)

[Jeremy Bicha]

This bug was fixed in the package makedumpfile - 1:1.6.3-2
Sponsored for Thadeu Lima de Souza Cascardo (cascardo)

---
makedumpfile (1:1.6.3-2) unstable; urgency=medium

  * Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021)
  * Add an autopkgtest that test that a crash produces a compressed dump
file.
  * Create initrd for previously installed kernels. (LP: #1751329)

 -- Thadeu Lima de Souza Cascardo   Mon, 05 Mar
2018 09:28:55 -0300

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

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

Title:
  Sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main)

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  Please sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main)

  Changelog entries since current bionic version 1:1.6.3-1:

  makedumpfile (1:1.6.3-2) unstable; urgency=medium

* Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021)
* Add an autopkgtest that test that a crash produces a compressed dump
  file.
* Create initrd for previously installed kernels. (LP: #1751329)

   -- Thadeu Lima de Souza Cascardo   Mon, 05 Mar
  2018 09:28:55 -0300

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

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

[Kernel-packages] [Bug 1751329] Re: kdump-tools won't load until after network is online

[Jeremy Bicha]

** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Low
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Confirmed

** No longer affects: makedumpfile (Ubuntu Bionic)

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Low

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

** Changed in: makedumpfile (Ubuntu Artful)
   Importance: Undecided => Low

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

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

Title:
  kdump-tools won't load until after network is online

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Triaged
Status in makedumpfile source package in Artful:
  Triaged

Bug description:
  This, at least, causes kdump-tools to load only after some timeout. It
  could be loaded much earlier.

  kdump-tools only requires the network to be online when it's
  configured to dump to ssh or nfs, and only when dumping, not when
  loading.

  We should have three services/units here:

  1) the loading service, does not require network;
  2) the dumping service, that works for local dumps, does not require network;
  3) the dumping service, that works remotely, requires network.

  Now, as per LP#1681909, maybe we should not require network-online,
  but use some other way to verify that the host where we want to dump
  is online, given a certain (configured) timeout.

  Cascardo.

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

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

[Kernel-packages] [Bug 1761889] Re: Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main)

[Jeremy Bicha]

https://launchpad.net/ubuntu/+source/thunderbolt-tools/0.9.3-2

** Changed in: thunderbolt-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main)

Status in thunderbolt-tools package in Ubuntu:
  Fix Released

Bug description:
  Please sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable
  (main)

  Changelog entries since current bionic version 0.9.3-1:

  thunderbolt-tools (0.9.3-2) unstable; urgency=medium

* Set UDEV_BIN_DIR to /lib/udev (LP: #1761757)

   -- Colin King   Fri, 6 Apr 2018 14:52:11
  +0100

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

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

[Kernel-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

[Jeremy Bicha]

** Also affects: nvidia-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-settings package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Kernel-packages] [Bug 1736617] [NEW] Port nvidia-settings to gtk3

[Jeremy Bicha]

Public bug reported:

gtk3 was declared stable in September 2016 with the gtk 3.22 release.
nvidia-settings should switch to gtk3.

nvidia-settings is one of the last dozen packages to keep gtk2 in main.

https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic gtk2-demotion

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

Title:
  Port nvidia-settings to gtk3

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  gtk3 was declared stable in September 2016 with the gtk 3.22 release.
  nvidia-settings should switch to gtk3.

  nvidia-settings is one of the last dozen packages to keep gtk2 in
  main.

  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion

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

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

[Kernel-packages] [Bug 1727057] Re: Drag and Drop Malfunction

[Jeremy Bicha]

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => New

** Tags added: wayland

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

Title:
  Drag and Drop Malfunction

Status in nautilus package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 17.04 64bit to 17.10 transferring a file
  from one folder to another fails with drag and drop. The grab will
  move the file but not drop it. It is as if the mouse-up does not
  register. The grab remains but mouse will not release until I log out
  of my account and log in again. The right click "move to" will work to
  move files.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe   10841 F pulseaudio
   /dev/snd/controlC1:  joe   10841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:31:02 2017
  HibernationDevice: RESUME=UUID=8aeb251b-127a-4963-905c-dda8e223e0ba
  InstallationDate: Installed on 2015-11-20 (703 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=159fdd5e-4a8b-4a5b-850f-5dabb27d2be3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
  dmi.bios.date: 03/26/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/26/2012:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

[Jeremy Bicha]

I am reassigning this bug to the kernel since that's usually who the
iio-sensor-proxy developer blames for issues like this.

You can try filing an issue with iio-sensor-proxy though.
https://github.com/hadess/iio-sensor-proxy/

If you open the system status menu in the far right of the top bar, you
can click the icon at the bottom of the menu that looks like a rotated
rectangle to lock or unlock screen auto-rotation. That might be a good
workaround.

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

[Jeremy Bicha]

** Bug watch added: Red Hat Bugzilla #1500834
   https://bugzilla.redhat.com/show_bug.cgi?id=1500834

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1500834
   Importance: Unknown
   Status: Unknown

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

Title:
  Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Fedora:
  Unknown

Bug description:
  I have a virtualbox VM running artful which I upgrade every day. Today
  when upgrading from kernel  4.12.0-12.13 to 4.13.0-11.12, after a
  reboot gdm3 failed to display the login screen. All I got was a black
  screen, but I could access a virtual terminal.

  Downgrading the kernel back to 4.12.0-12.13 fixed the issue.

  jibel suggested to trying disabling wayland in gdm (by uncommenting
  #WaylandEnable=false in /etc/gdm3/custom.conf), and that did the trick
  too, but only X11 sessions were available of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1726 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 1726 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
   /dev/snd/timer:  ubuntu 1726 f pulseaudio
  Date: Thu Sep 21 15:40:40 2017
  InstallationDate: Installed on 2017-06-07 (106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=e23963bd-97af-4402-b681-376a6fcaae62 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1723271] [NEW] Hide kerneloops applet from Startup Applications

[Jeremy Bicha]

Public bug reported:

Ubuntu still includes the Startup Applications app in the default
install (it was dropped in gnome-session upstream years ago).

To prevent users from being able to easily disable system services that
they probably shouldn't, Ubuntu makes sure that apps included by default
set NoDisplay=true in their autostart files. This hides the services
from the Startup Applications app.

Test Case
=
Open Startup Applications
Does kerneloops-applet show in the list?

Other Info
==
SSH Key Agent is intentionally in the Startup Applications list.

By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
https://github.com/mate-desktop/mate-session-manager/issues/134

** Affects: kerneloops (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: artful

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

Title:
  Hide kerneloops applet from Startup Applications

Status in kerneloops package in Ubuntu:
  Triaged

Bug description:
  Ubuntu still includes the Startup Applications app in the default
  install (it was dropped in gnome-session upstream years ago).

  To prevent users from being able to easily disable system services
  that they probably shouldn't, Ubuntu makes sure that apps included by
  default set NoDisplay=true in their autostart files. This hides the
  services from the Startup Applications app.

  Test Case
  =
  Open Startup Applications
  Does kerneloops-applet show in the list?

  Other Info
  ==
  SSH Key Agent is intentionally in the Startup Applications list.

  By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
  https://github.com/mate-desktop/mate-session-manager/issues/134

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

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

[Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

[Jeremy Bicha]

Doug, if the package needs python, then it should be marked as a
dependency.

** Changed in: nvidia-prime (Ubuntu)
   Status: Invalid => New

** Changed in: nvidia-settings (Ubuntu)
   Status: Invalid => New

** Tags added: rls-aa-incoming

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1712495] Re: Please sponsor bluez 5.46-0ubuntu2 to artful

[Jeremy Bicha]

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

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

Title:
  Please sponsor bluez 5.46-0ubuntu2 to artful

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Please sponsor bluez 5.46-0ubuntu2 to artful

  This fixes a crash of zyga's that's been discussed a lot in the past
  but never opened as an official bug report. It has however already
  been fixed upstream and will be included in 5.47.

  It's not yet clear exactly which existing LP bug/error reports this
  will resolve. We'll find out later by tracking errors.ubuntu.com (I
  suspect it might resolve a couple).

  If you need a proper bug report then please ask
  zygmunt.kryni...@canonical.com

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

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

[Kernel-packages] [Bug 1694827] Re: [VIZIO SB3820, playback] Playback problem, Device not listed in Sound and can't be used without workarounds.

[Jeremy Bicha]

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

** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  [VIZIO SB3820, playback] Playback problem, Device not listed in Sound
  and can't be used without workarounds.

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I try to connect to my Bluetooth speaker using Ubuntu GNOME (a
  Vizio SB3820 sound bar) it is not listed in the sound devices until I
  use a workaround from this site:

  https://askubuntu.com/questions/824404/bluetooth-speaker-connected-
  but-not-listed-in-sound-output

  Specifically,

  "Install blueman sudo apt install blueman
  Delete the paired device in the bluetooth settings.
  Run these commands in terminal: bash
  sudo pkill pulseaudio
  sudo /etc/init.d/bluetooth restart
  Turn off headphones.
  Turn on headphones, and press green/go until headphones notification voice 
says "Ready to pair."
  Launch blueman, and from the upper right menu, right-click the icon to bring 
up the blueman menu. Select Setup new device.
  Pair the device, and when you are given an option, not headphones, not 
handsfree. Use the Audio sink option.
  Then when you look into the audio settings panel, the device should be 
displayed."

  In my case, the situation is more like killing pulseaudio, restarting
  the bluetooth service, and reconnecting to the device using Blueman as
  an audio sink, NOT using the GNOME Bluetooth applet.

  If I do this, the device appears as a sound device and worksuntil
  I reboot the computer.

  I was told to file a bug on this by the #ubuntu-gnome IRC channel
  using ubuntu-bug audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ryan   3043 F...m pulseaudio
   /dev/snd/controlC0:  ryan   3043 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed May 31 15:47:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: VIZIO SB3820
  Symptom_Type: None of the above
  Title: [VIZIO SB3820, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2UCN10T
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK2
  dmi.modalias: 
dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2:
  dmi.product.name: 80UE
  dmi.product.version: Lenovo YOGA 900-13ISK2
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1694791] Re: Please remove libmpc from the sync blacklist

[Jeremy Bicha]

** Summary changed:

- Sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)
+ Please remove libmpc from the sync blacklist

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

Title:
  Please remove libmpc from the sync blacklist

Status in libmpc package in Ubuntu:
  New

Bug description:
  
  I came across this package, wondering why Debian has a newer version which 
didn't seem to automatically sync in Artful. After some digging, I discovered 
that the package had been blacklisted [1] and thus prevented from syncing. 
Originally done because the binary packages provided were also offered by a 
different package libmpcdec (bug 540019). 

  However, I did some more digging and found that libmpcdec had been
  removed shortly after [2]. With this other package gone, I wonder if
  there is still reasons to keep libmpc in the blacklist or whether it
  could be synced to the latest version available in Debian?

  [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt
  [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory




  Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)

  Changelog entries since current artful version 2:0.1~r459-4.1build1:

  libmpc (2:0.1~r495-1) unstable; urgency=medium

    * Team upload.
    * New upstream release. (Closes: #837096)
    * debian/rules: Add get-orig-source target to fetch newer upstream
  snapshots.
    * debian/patches:
  - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included
    upstream.
  - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file.

   -- Sebastian Ramacher   Mon, 12 Sep 2016
  20:34:33 +0200

  libmpc (2:0.1~r475-2) unstable; urgency=medium

    * Team upload.
    * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix
  FTBFS. (Closes: #816529)
    * Update Vcs fields.
    * Bump standards to 3.9.8.

   -- James Cowgill   Wed, 31 Aug 2016 21:16:41
  +0100

  libmpc (2:0.1~r475-1) unstable; urgency=medium

    * New upstream release:
  - Contains a minor API change of removing some enum values that
    are not used anywhere in Debian.
    * debian/patches/05_visibility.patch:
  - Minor build system fix to declare HAVE_VISIBILITY.

   -- Sebastian Dröge   Sat, 19 Sep 2015 20:59:38
  +0200

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

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

[Kernel-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

[Jeremy Bicha]

** Also affects: gnome-bluetooth (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** No longer affects: bluez (Ubuntu Xenial)

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

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

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in blueman source package in Xenial:
  New
Status in gnome-bluetooth source package in Xenial:
  New
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings 
(the correct device's options don't appear in the right pane). Hence no 
Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Kernel-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

[Jeremy Bicha]

** No longer affects: bluez (Ubuntu Xenial)

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

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

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Kernel-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

[Jeremy Bicha]

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

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in bluez source package in Xenial:
  New
Status in pulseaudio source package in Xenial:
  New

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Kernel-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Jeremy Bicha]

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

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

** No longer affects: bluez (Ubuntu Xenial)

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

** Changed in: pulseaudio (Ubuntu Xenial)
   Importance: Undecided => High

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

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

Vincent, is it at all possible for you to test Ubuntu GNOME 17.04 before
and after this proposed fix? I don't have the hardware to verify your
fix and the Ubuntu Stable Release Update team really likes for bugfixes
to be verified.

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Linux:
  Won't Fix
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

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

[Kernel-packages] [Bug 1690669] [NEW] Please build libxnvctrl0/-dev for s390x

[Jeremy Bicha]

Public bug reported:

The Debian version of this package is built for all architectures:

https://buildd.debian.org/status/package.php?p=nvidia-settings

Please do the same for Ubuntu also.

In particular, qtwebengine-opensource-src needs libxnvctrl-dev (which
depends on libxnvctrl0) to build on s390x. qtwebengine in turned is
needed for the KDE PIM components (and probably other parts of the KDE
platfrom).

https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.7.1
+dfsg-6build1/+build/12459543

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please build libxnvctrl0/-dev for s390x

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  The Debian version of this package is built for all architectures:

  https://buildd.debian.org/status/package.php?p=nvidia-settings

  Please do the same for Ubuntu also.

  In particular, qtwebengine-opensource-src needs libxnvctrl-dev (which
  depends on libxnvctrl0) to build on s390x. qtwebengine in turned is
  needed for the KDE PIM components (and probably other parts of the KDE
  platfrom).

  https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.7.1
  +dfsg-6build1/+build/12459543

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

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

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

** Also affects: gnome-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=782211
   Importance: Unknown
   Status: Unknown

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

Title:
  E6430 brightness control not working

Status in gnome-settings-daemon:
  Unknown
Status in Linux:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  In Progress
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+subscriptions

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

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

** Description changed:

- The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
- Source Nouveau driver shows the brightness slider moving but does not
- affect the brightness.
+ Impact
+ --
+ It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.
+ 
+ Test Case
+ -
+ From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
+ Restart.
+ Does the brightness control now work correctly?
+ 
+ Regression Potential
+ 
+ This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.
+ 
+ Original Bug Report
+ ---
+ The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.
  
  When using the kernel boot option acpi_backlight=vendor , the brightness
  control works.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
-  0 nouveaufb
-  1 inteldrmfb
+  0 nouveaufb
+  1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-19-generic N/A
-  linux-backports-modules-4.10.0-19-generic  N/A
-  linux-firmware 1.164
+  linux-restricted-modules-4.10.0-19-generic N/A
+  linux-backports-modules-4.10.0-19-generic  N/A
+  linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  E6430 brightness control not working

Status in Linux:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  In Progress
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 2

[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

I am closing the 'linux' portion of this bug because this apparently can
be fixed in gnome-settings-daemon and unity-settings-daemon.

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Triaged

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

** Also affects: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: unity-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

** No longer affects: linux (Ubuntu Zesty)

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Medium

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

Title:
  E6430 brightness control not working

Status in Linux:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon source package in Zesty:
  Triaged
Status in unity-settings-daemon source package in Zesty:
  Triaged

Bug description:
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
  Source Nouveau driver shows the brightness slider moving but does not
  affect the brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1682660] Re: Portait mode rotation on 2-in-1 is upside down

[Jeremy Bicha]

** Project changed: ubuntu-gnome => linux (Ubuntu)

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to
  enable  kxcjk_1013 i2c driver. Now in 17.04, when rotating to a
  portrait mode, screen is upside down in either physical direction.
  Landscape is correct orientation for both physical directions.zz

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

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

[Kernel-packages] [Bug 1678284] Re: broken progress/installation bars

[Jeremy Bicha]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1623856, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1623856
   Scrolled Windows in update-manager are too small to read

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

Title:
  broken progress/installation bars

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When ever a new software or package is installed, i find that i am
  unable to see the download progress of these software as the box
  shrink and i am unable to enlarge it. Please refer to the attached pic
  for more details.

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

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

[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

[Jeremy Bicha]

** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => In Progress

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** Also affects: gnome-shell (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: gnome-shell (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: gnome-shell (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu Yakkety)
   Importance: Undecided => Critical

** Description changed:

  To fix this now without waiting for the Stable Release Update
  =
  Install xserver-xorg-legacy
  
  Impact
  ==
  Many users are unable to use their computers after installing the NVIDIA 
proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not 
load.
  
  The problem is that many of nvidia-* driver packages do not depend on
  xserver-xorg-legacy which is needed for gdm/gnome-shell to work
  
  Test Case
  =
- 1. Check that the nvidia-* packages depend on xserver-xorg-legacy.
+ 1. Check that gnome-shell depends on xserver-xorg-legacy.
  
  2. Optionally, if you have an affected computer, set gdm as the default
  login manager (sudo apt install gdm3; sudo dpkg-reconfigure gdm3; sudo
  reboot). Does the login screen show up? And can you log in to gnome
  (sudo apt install gnome-shell)?
  
  Regression Potential
  
  Low. Installing a missing dependency should cause no issues; if it does, 
something is very broken already.
+ 
+ Other Info
+ ==
+ The most minimal fix here for 16.04 LTS and 16.10 is to just have gnome-shell 
depend on xserver-xorg-legacy. Updating all the nvidia-* packages in Ubuntu and 
the PPAs would be a lot more trouble; although that would still be a good idea 
so that this gnome-shell dependency could be dropped in future Ubuntu releases.
+ 
+ xserver-xorg-legacy is a very small package.
  
  Original Bug Report
  ===
  Using latest Ubuntu Gnome x64 daily build with all updates installed.
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.
  
  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.
  
  Bug is affecting more than just me. We were talking about workarounds in
  ubuntuforums. User fthx claims that switching to lightdm fixes the issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

** Changed in: ubuntu-gnome
   Status: Triaged => Fix Committed

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in g

[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

[Jeremy Bicha]

** Also affects: nvidia-drivers-ubuntu
   Importance: Undecided
   Status: New

** Changed in: nvidia-drivers-ubuntu
   Status: New => Confirmed

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  To fix this now without waiting for the Stable Release Update
  =
  Install xserver-xorg-legacy

  Impact
  ==
  Many users are unable to use their computers after installing the NVIDIA 
proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not 
load.

  The problem is that many of nvidia-* driver packages do not depend on
  xserver-xorg-legacy which is needed for gdm/gnome-shell to work

  Test Case
  =
  1. Check that the nvidia-* packages depend on xserver-xorg-legacy.

  2. Optionally, if you have an affected computer, set gdm as the
  default login manager (sudo apt install gdm3; sudo dpkg-reconfigure
  gdm3; sudo reboot). Does the login screen show up? And can you log in
  to gnome (sudo apt install gnome-shell)?

  Regression Potential
  
  Low. Installing a missing dependency should cause no issues; if it does, 
something is very broken already.

  Original Bug Report
  ===
  Using latest Ubuntu Gnome x64 daily build with all updates installed.
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

[Jeremy Bicha]

** Description changed:

- Using latest Ubuntu Gnome x64 daily build with all updates installed. 
+ To fix this now without waiting for the Stable Release Update
+ =
+ Install xserver-xorg-legacy
+ 
+ Impact
+ ==
+ Many users are unable to use their computers after installing the NVIDIA 
proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not 
load.
+ 
+ The problem is that many of nvidia-* driver packages do not depend on
+ xserver-xorg-legacy which is needed for gdm/gnome-shell to work
+ 
+ Test Case
+ =
+ 1. Check that the nvidia-* packages depend on xserver-xorg-legacy.
+ 
+ 2. Optionally, if you have an affected computer, set gdm as the default
+ login manager (sudo apt install gdm3; sudo dpkg-reconfigure gdm3; sudo
+ reboot). Does the login screen show up? And can you log in to gnome
+ (sudo apt install gnome-shell)?
+ 
+ Regression Potential
+ 
+ Low. Installing a missing dependency should cause no issues; if it does, 
something is very broken already.
+ 
+ Original Bug Report
+ ===
+ Using latest Ubuntu Gnome x64 daily build with all updates installed.
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.
  
  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.
  
  Bug is affecting more than just me. We were talking about workarounds in
  ubuntuforums. User fthx claims that switching to lightdm fixes the issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-14-generic N/A
-  linux-backports-modules-4.4.0-14-generic  N/A
-  linux-firmware1.156
+  linux-restricted-modules-4.4.0-14-generic N/A
+  linux-backports-modules-4.4.0-14-generic  N/A
+  linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  To fix this now without waiting for the Stable Release Update
  =
  Install xserver-xorg-legacy

  Impact
  ==
  Many users are unable to use their computers after installing the NVIDIA 
proprietary drivers to Ubuntu GNOME. Specifically, the log in screen does not 
load.

  The problem is that many of nvidia-* driver packages do not depend on
  xserver-xorg-legacy which is needed for gdm/gnome-shell to work

  Test Case
  =
  1. Check that the nvidia-* packages depend on xserver-xorg-legacy.

  2. Optionally, if you have an affected computer, set gdm as the
  default login manager (sudo apt install gdm3; sudo dpkg-reconfigure
  gdm3; sudo reboot). Does the login screen show up? And can you log in
  to gnome (sudo apt install gnome-shell)?

  Regression Potential

[Kernel-packages] [Bug 1651124] Re: Please sync dkms 2.3-2 from Debian sid (main)

[Jeremy Bicha]

This bug was fixed in the package dkms - 2.3-2
Sponsored for Aron Xu (happyaron)

---
dkms (2.3-2) unstable; urgency=medium

  [ Adam Cornad ]
  * Don't assume /boot/config-* exists, test first.

  [ Aron Xu ]
  * d/control: update VCS-*, std-ver: 3.9.8
  * d/rules: add shim support for Ubuntu derivatives

 -- Aron Xu   Wed, 28 Dec 2016 19:57:32 +0800

dkms (2.3-1) unstable; urgency=medium

  [ Adel Belhouane ]
  * Update mkbmdeb behavior (Closes: #830670)

  [ Aron Xu ]
  * Downgrade menu from Recommends to Suggests (Closes: #744054)
  * Imported Upstream version 2.3
  * Upstream post-release cherry-picks
  * d/compat: 7 -> 9

  [ D. Jared Dominguez ]
  * update URLs

 -- Aron Xu   Wed, 26 Oct 2016 14:26:44 +0800

dkms (2.2.1.0+git20160527-1) unstable; urgency=medium

  * Rebase to upstream commit eb402f72b9a71ccdd0d3610db8570195eb048f1f
  * Update patches

 -- Aron Xu   Tue, 23 Aug 2016 14:24:38 +0800

dkms (2.2.0.3-5) unstable; urgency=medium

  [ Aron Xu ]
  * Remove obsolete virtual package 'linux-image' from Recommends (Closes: 
#724566)
  * Do not ignore --kernelsourcedir (Closes: #653176)
  * Update upstream link to github
  * Use gbp-pq to manage patches

  [ Daniel Kahn Gillmor ]
  * Make dh_dkms name and version parsing more proper (Closes: #829123)

  [ Dirk Griesbach ]
  * Port apport hook to python3 and add python3-apport to Suggests (Closes: 
#707008)

  [ Thijs Kinkhorst ]
  * mkbmdeb: support for lean binary package with only the built modules 
(Closes: #554843)

 -- Aron Xu   Wed, 06 Jul 2016 05:51:37 +0800

dkms (2.2.0.3-4) unstable; urgency=medium

  * Acknowledge 2.2.0.3-2.1 NMU. (Closes: #822351)
  * Make sure apport code write files in binary mode. (Closes: #684377)
  * Build modules using all CPU cores. (Closes: #663114)
  * Improve message printed when kernel headers are missing. (Closes: #690866)
  * Add gbp.conf to ensure pristine-tar feature is used.

 -- Petter Reinholdtsen   Sun, 01 May 2016 15:27:22
+0200

dkms (2.2.0.3-3) unstable; urgency=medium

  [ Petter Reinholdtsen ]
  * Correct indentation of mkdeb in dkms(8) manual page. (Closes: #690865)
  * Drop the unneeded quilt build dependency. (Closes: #728550)
  * Added myself and Aron Xu as uploaders.

  [ Aron Xu ]
  * Added patches from Darik Horn and Ubuntu:
- Add support for BUILD_DEPENDS (Closes: #729015)
- Correct handling of POST_BUILD (Closes: #704989)

 -- Petter Reinholdtsen   Wed, 27 Apr 2016 10:20:15
+0200

dkms (2.2.0.3-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Add dkms-autopkgtest script from Ubuntu (Closes: #769095).
  * Updated Standards-Version from 3.9.2 to 3.9.7.

 -- Petter Reinholdtsen   Sat, 23 Apr 2016 19:55:25
+0200

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

** Tags added: upgrade-software-version

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

Title:
  Please sync dkms 2.3-2 from Debian sid  (main)

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  dkms upstream has become back to life in recent months, and merged
  many patches from downstream communities, thus merging with the new
  release is worthy to get old bug fixed and new features incorporated.

  All Ubuntu deltas are merged into Debian package with certain changes,
  thus they could be dropped.

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

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

[Kernel-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

[Jeremy Bicha]

** No longer affects: libosinfo (Ubuntu)

** No longer affects: libosinfo (Ubuntu Xenial)

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed
Status in hwdata source package in Xenial:
  New
Status in ptouch-driver source package in Xenial:
  Triaged
Status in usbutils source package in Xenial:
  New

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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

[Kernel-packages] [Bug 1651124] Re: Please merge dkms 2.3-1 from Debian testing (main)

[Jeremy Bicha]

Debian is beginning to get Secure Boot support.

https://lwn.net/Articles/703001/

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

Title:
   Please merge dkms 2.3-1 from Debian testing  (main)

Status in dkms package in Ubuntu:
  New

Bug description:
  dkms upstream has become back to life in recent months, and merged
  many patches from downstream communities, thus merging with the new
  release is worthy to get old bug fixed and new features incorporated.

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

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

[Kernel-packages] [Bug 1644981] Re: ExFAT Formatted SD Cards not mounted

[Jeremy Bicha]

Do you have exfat-utils and fuse-exfat installed?

They are not installed by default in Ubuntu, but that might change for
17.04 (that request is being tracked in bug 1649537 )

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

Title:
  ExFAT Formatted SD Cards not mounted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards
  work perfectly on 12.04, 14.04 and Windows.

  Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB 
device number 7 using xhci_hcd
  Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device 
found, idVendor=058f, idProduct=6366
  Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card 
Reader/Writer
  Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic
  Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 
058F63666485
  Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass 
Storage device detected
  Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 
1-8:1.0
  Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: 
"/sys/devices/pci:00/:00:14.0/usb1/1-8"
  Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device
  Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access   
  Multiple Card  Reader 1.00 PQ: 0 ANSI: 4
  Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi 
generic sg1 type 0
  Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached 
SCSI removable disk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.47.50
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   2240 F pulseaudio
   /dev/snd/controlC1:  sebastian   2240 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Nov 26 11:22:03 2016
  HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7
  InstallationDate: Installed on 2015-08-06 (477 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1221711] Re: Update regulations for Russia

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1284093
   Please update regulations to support VHT

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

Title:
  Update regulations for Russia

Status in wireless-regdb package in Ubuntu:
  Confirmed

Bug description:
  Regulations for Russia (related to 5GHz) are invalid. Raring is affected and 
as I can see, saucy is affected as well (isn't fixed in upstream as well).
  There is a fix in the patch attached.

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

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

[Kernel-packages] [Bug 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

[Jeremy Bicha]

Till, I don't think this bug has anything to do with libosinfo.

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

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

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

** Also affects: ptouch-driver (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: libosinfo (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: ptouch-driver (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Confirmed
Status in libosinfo package in Ubuntu:
  Incomplete
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Confirmed
Status in hwdata source package in Xenial:
  New
Status in libosinfo source package in Xenial:
  Incomplete
Status in ptouch-driver source package in Xenial:
  Triaged
Status in usbutils source package in Xenial:
  New

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

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

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

[Kernel-packages] [Bug 1629771] Re: Mouse integration does not work with Linux 4.8 guest without I/O APIC

[Jeremy Bicha]

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

** Tags added: bot-stop-nagging

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

** Changed in: virtualbox (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mouse integration does not work with Linux 4.8 guest without I/O APIC

Status in Virtualbox:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  My host and guest is Ubuntu 16.10 64-bit.

  I can't use my mouse to click anything inside the Ubuntu (Unity) 16.10
  guest. A workaround is to (install if necessary and) select the older
  yakkety Linux 4.4 kernel from the grub boot screen in the guest.

  Or open the VM Settings. Switch to the System tab and make sure "Enable I/O 
APIC" is turned on. This setting is recommended by VirtualBox:
  https://www.virtualbox.org/manual/ch03.html#intro-64bitguests

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: virtualbox 5.1.6-dfsg-2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct  3 01:53:20 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1621217] [NEW] Please add linux-signed to sync blacklist

[Jeremy Bicha]

Public bug reported:

Debian now has a linux-signed source. Although the version numbers are
still lower than Ubuntu's, that could change at any time. Since Ubuntu's
version numbering for linux-signed is native, a future Debian upload
could be auto-synced.

https://tracker.debian.org/pkg/linux-signed

Please add linux-signed to the sync blacklist like other kernel
packages.

https://people.canonical.com/~ubuntu-archive/sync-blacklist.txt

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

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

Title:
  Please add linux-signed to sync blacklist

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Debian now has a linux-signed source. Although the version numbers are
  still lower than Ubuntu's, that could change at any time. Since
  Ubuntu's version numbering for linux-signed is native, a future Debian
  upload could be auto-synced.

  https://tracker.debian.org/pkg/linux-signed

  Please add linux-signed to the sync blacklist like other kernel
  packages.

  https://people.canonical.com/~ubuntu-archive/sync-blacklist.txt

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

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

[Kernel-packages] [Bug 1613393] Re: Provide linux-perf package

[Jeremy Bicha]

doesn't need log files

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

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

Title:
  Provide linux-perf package

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Debian renamed their linux-tools package to linux-perf a year ago.

  
https://anonscm.debian.org/cgit/kernel/linux.git/commit/debian/changelog?id=c2faa8

  The Debian package perf-tools-unstable followed the new name so I had
  to upload an Ubuntu version to revert that change. It would be nice if
  we didn't have to maintain that difference in Ubuntu.

  https://bugs.debian.org/795090

  https://launchpad.net/ubuntu/+source/perf-tools-
  unstable/0.0.1~20160212+git0c13e83-1ubuntu1

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

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

[Kernel-packages] [Bug 1613393] [NEW] Provide linux-perf package

[Jeremy Bicha]

Public bug reported:

Debian renamed their linux-tools package to linux-perf a year ago.

https://anonscm.debian.org/cgit/kernel/linux.git/commit/debian/changelog?id=c2faa8

The Debian package perf-tools-unstable followed the new name so I had to
upload an Ubuntu version to revert that change. It would be nice if we
didn't have to maintain that difference in Ubuntu.

https://bugs.debian.org/795090

https://launchpad.net/ubuntu/+source/perf-tools-
unstable/0.0.1~20160212+git0c13e83-1ubuntu1

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

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

Title:
  Provide linux-perf package

Status in linux package in Ubuntu:
  New

Bug description:
  Debian renamed their linux-tools package to linux-perf a year ago.

  
https://anonscm.debian.org/cgit/kernel/linux.git/commit/debian/changelog?id=c2faa8

  The Debian package perf-tools-unstable followed the new name so I had
  to upload an Ubuntu version to revert that change. It would be nice if
  we didn't have to maintain that difference in Ubuntu.

  https://bugs.debian.org/795090

  https://launchpad.net/ubuntu/+source/perf-tools-
  unstable/0.0.1~20160212+git0c13e83-1ubuntu1

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

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

[Kernel-packages] [Bug 1589756] Re: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

[Jeremy Bicha]

When I tried back in June, the newer mainline kernels didn't work. When
I tried going back in time, I couldn't find an Ubuntu kernel that was
old enough to not have broken sound but new enough to still boot in
Ubuntu 16.04 LTS.

I'm thinking you'd want me to identify a kernel that works but it may
take me a while to get around to installing Ubuntu 12.04 or 14.04 on
this computer to try older kernels.

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

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

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSY

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https:/

[Kernel-packages] [Bug 1589756] PulseList.txt

[Jeremy Bicha]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678557/+files/PulseList.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://lau

[Kernel-packages] [Bug 1589756] Re: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

[Jeremy Bicha]

apport information

** Tags added: apport-collected

** Description changed:

  I don't have any audio output through the laptop's internal speakers but
  I get audio fine if I plug in external speakers.
  
  I can get audio working briefly by running
  
  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0
  
  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html
  
  but it doesn't last very long before the audio turns off again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
+ --- 
+ ApportVersion: 2.20.1-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
+  /dev/snd/controlC0:  jeremy 2493 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
+ InstallationDate: Installed on 2016-04-09 (58 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
+ MachineType: TOSHIBA Satellite L745
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-23-generic N/A
+  linux-backports-modules-4.4.0-23-generic  N/A
+  linux-firmware1.158
+ Tags:  yakkety
+ Uname: Linux 4.4.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/26/2012
+ dmi.bios.vendor: INSYDE
+ dmi.bios.version: 2.60
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: Base Board Product Name
+ dmi.board.vendor: Intel Corp.
+ dmi.board.version: Base Board Version
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: OEM Chassis Manufacturer
+ dmi.chassis.version: OEM Chassis Version
+ dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
+ dmi.product.name: Satellite L745
+ dmi.product.version: PSK0YU-05R02G
+ dmi.sys.vendor: TOSHIBA

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678546/+files/AlsaInfo.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get aud

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: htt

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

[Jeremy Bicha]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678554/+files/ProcEnviron.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https:/

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.

[Kernel-packages] [Bug 1589756] Lspci.txt

[Jeremy Bicha]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1589756/+attachment/4678551/+files/Lspci.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.ne

[Kernel-packages] [Bug 1589756] Lsusb.txt

[Jeremy Bicha]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1589756/+attachment/4678552/+files/Lsusb.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.ne

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.net/

[Kernel-packages] [Bug 1589756] IwConfig.txt

[Jeremy Bicha]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678549/+files/IwConfig.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launc

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https

[Kernel-packages] [Bug 1589756] RfKill.txt

[Jeremy Bicha]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1589756/+attachment/4678558/+files/RfKill.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://launchpad.

[Kernel-packages] [Bug 1589756] ProcInterrupts.txt

[Jeremy Bicha]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678555/+files/ProcInterrupts.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: h

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

[Jeremy Bicha]

apport information

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https:/

[Kernel-packages] [Bug 1589756] WifiSyslog.txt

[Jeremy Bicha]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1589756/+attachment/4678560/+files/WifiSyslog.txt

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

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA
  --- 
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e1fbfe5e-a6b3-4683-b964-109e7a5f7849
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  MachineType: TOSHIBA Satellite L745
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=da597564-0d10-41fc-babd-c29ef975bfe7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.158
  Tags:  yakkety
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

[Kernel-packages] [Bug 1589756] Re: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

[Jeremy Bicha]

** Tags added: kernel-sound

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  New

Bug description:
  I don't have any audio output through the laptop's internal speakers
  but I get audio fine if I plug in external speakers.

  I can get audio working briefly by running

  sudo hda-verb /dev/snd/hwC0D0 0x1f SET_POWER_STATE 0

  as suggested at 
  http://lkml.iu.edu/hypermail/linux/kernel/1301.1/02917.html

  but it doesn't last very long before the audio turns off again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 2493 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  6 21:49:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-09 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160408)
  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/pcmC0D0c:   jeremy 2493 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jeremy 2493 F...m pulseaudio
   /dev/snd/controlC0:  gdm2175 F pulseaudio
jeremy 2493 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-05R02G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-05R02G
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1467622] Re: [SATELLITE L750, Conexant CX20585, Speaker, Internal] Playback problem, speakers don't work

[Jeremy Bicha]

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Tags added: kernel-sound

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

Title:
  [SATELLITE L750, Conexant CX20585, Speaker, Internal] Playback
  problem, speakers don't work

Status in linux package in Ubuntu:
  New

Bug description:
  Sound works through headphones, but it does not through the speakers.
  HOWEVER, at logon, I can hear the drums sound, so it's not a hardware issue.
  SOMETIMES, executing "amixer -c0 set Headphone unmute 100%", as adviced in 
[1], works temporarily.
  I had same issue with Fedora 22, see [1] for context.

  [1] http://www.forums.fedoraforum.org/showthread.php?t=304857

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   1580 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jun 22 19:41:55 2015
  InstallationDate: Installed on 2015-06-19 (3 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Audio Interno - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [SATELLITE L750, Conexant CX20585, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.80:bd07/03/2012:svnTOSHIBA:pnSATELLITEL750:pvrPSK6ME-01900HCE:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE L750
  dmi.product.version: PSK6ME-01900HCE
  dmi.sys.vendor: TOSHIBA

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

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