[Touch-packages] [Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid

2019-10-21 Thread seahen
#1848974 may be a duplicate of this bug.

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

Title:
  apt-get install fails when UNRELATED package list is invalid

Status in apt package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 19.04
  Release:  19.04
  2) unknown (see below)
  3) Even when a package list from one source is invalid, I can still apt-get 
install and apt-get update packages from other sources, as long as they don't 
depend on packages in the bad list.
  4) I can't install a package from *any* source, even the ones that still 
yield valid package lists.

  On Xubuntu 19.04, I have the following in my sources.list:

  deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main
  deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main

  Currently those sources yield invalid package lists. However,
  installation of a package fails even when it comes from *another*
  source.

  $ sudo apt-get install stress
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  Shouldn't this affect only packages that come from the faulty package
  list or depend on ones that do? I get the same error when running

  $ apt-cache policy apt-get

  so I can't determine what version of apt-get I'm encountering this bug
  in.

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

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


[Touch-packages] [Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid

2019-10-21 Thread seahen
I have the same issue if I try apt instead of apt-get.

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

Title:
  apt-get install fails when UNRELATED package list is invalid

Status in apt package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 19.04
  Release:  19.04
  2) unknown (see below)
  3) Even when a package list from one source is invalid, I can still apt-get 
install and apt-get update packages from other sources, as long as they don't 
depend on packages in the bad list.
  4) I can't install a package from *any* source, even the ones that still 
yield valid package lists.

  On Xubuntu 19.04, I have the following in my sources.list:

  deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main
  deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main

  Currently those sources yield invalid package lists. However,
  installation of a package fails even when it comes from *another*
  source.

  $ sudo apt-get install stress
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  Shouldn't this affect only packages that come from the faulty package
  list or depend on ones that do? I get the same error when running

  $ apt-cache policy apt-get

  so I can't determine what version of apt-get I'm encountering this bug
  in.

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

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


[Touch-packages] [Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid

2019-10-21 Thread seahen
$ apt-cache policy apt
E: Encountered a section with no Package: header
E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

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

Title:
  apt-get install fails when UNRELATED package list is invalid

Status in apt package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 19.04
  Release:  19.04
  2) unknown (see below)
  3) Even when a package list from one source is invalid, I can still apt-get 
install and apt-get update packages from other sources, as long as they don't 
depend on packages in the bad list.
  4) I can't install a package from *any* source, even the ones that still 
yield valid package lists.

  On Xubuntu 19.04, I have the following in my sources.list:

  deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main
  deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main

  Currently those sources yield invalid package lists. However,
  installation of a package fails even when it comes from *another*
  source.

  $ sudo apt-get install stress
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  Shouldn't this affect only packages that come from the faulty package
  list or depend on ones that do? I get the same error when running

  $ apt-cache policy apt-get

  so I can't determine what version of apt-get I'm encountering this bug
  in.

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

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


[Touch-packages] [Bug 1849253] [NEW] apt-get install fails when UNRELATED package list is invalid

2019-10-21 Thread seahen
Public bug reported:

1) Description: Ubuntu 19.04
Release:19.04
2) unknown (see below)
3) Even when a package list from one source is invalid, I can still apt-get 
install and apt-get update packages from other sources, as long as they don't 
depend on packages in the bad list.
4) I can't install a package from *any* source, even the ones that still yield 
valid package lists.

On Xubuntu 19.04, I have the following in my sources.list:

deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main
deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main

Currently those sources yield invalid package lists. However,
installation of a package fails even when it comes from *another*
source.

$ sudo apt-get install stress
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.

Shouldn't this affect only packages that come from the faulty package
list or depend on ones that do? I get the same error when running

$ apt-cache policy apt-get

so I can't determine what version of apt-get I'm encountering this bug
in.

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

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

Title:
  apt-get install fails when UNRELATED package list is invalid

Status in apt package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 19.04
  Release:  19.04
  2) unknown (see below)
  3) Even when a package list from one source is invalid, I can still apt-get 
install and apt-get update packages from other sources, as long as they don't 
depend on packages in the bad list.
  4) I can't install a package from *any* source, even the ones that still 
yield valid package lists.

  On Xubuntu 19.04, I have the following in my sources.list:

  deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main
  deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main

  Currently those sources yield invalid package lists. However,
  installation of a package fails even when it comes from *another*
  source.

  $ sudo apt-get install stress
  Reading package lists... Error!
  E: Encountered a section with no Package: header
  E: Problem with MergeList 
/var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages
  E: The package lists or status file could not be parsed or opened.

  Shouldn't this affect only packages that come from the faulty package
  list or depend on ones that do? I get the same error when running

  $ apt-cache policy apt-get

  so I can't determine what version of apt-get I'm encountering this bug
  in.

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package klibc - 2.0.6-1ubuntu2

---
klibc (2.0.6-1ubuntu2) eoan; urgency=medium

  * Fix FTBFS on eoan and later with new linux and gcc (LP: #1843743)
- cf-protection.patch: Disable cf-protection for syscalls stub.
- mman-include.patch: Adjust for changes to linux headers in 5.3.

 -- Adam Conrad   Mon, 21 Oct 2019 15:39:37 -0600

** Changed in: klibc (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Eoan:
  Fix Committed

Bug description:
  [ SRU Justification / Impact ]
  klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.

  [ Test Case ]
  If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.

  [ Regression Potential ]
  One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.

  [ Original Bug Report ]
  
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
    |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1849183] Re: Bluetooth devices doesn't get listed while turn off and then on

2019-10-21 Thread Daniel van Vugt
** Package changed: alsa-driver (Ubuntu) => gnome-control-center
(Ubuntu)

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

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

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

Title:
  Bluetooth devices doesn't get listed while turn off and then on

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  When System Starts, first time Bluetooth devices(Say headphones) get
  connected smoothly. But after a point when headphones get
  disconnected, If I tried to reconnect Bluetooth settings don't list
  the devices. I turned it on/off multiple times but doesn't work. The
  only way that'd work after a system restart. Please can you check into
  this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghuvar   1999 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 23:39:04 2019
  InstallationDate: Installed on 2019-06-30 (113 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  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 ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1849232] [NEW] fusermount -u in bash script prepends /home to path if resource is busy

2019-10-21 Thread Majal
Public bug reported:

Kindly see this question in StackExchange:

https://superuser.com/q/1494196/253105

If a busy resource path is passed such as `fusermount -u
/path/to/busy/resource`, fusermount gives the following message:

`fusermount: failed to unmount /home/path/to/busy/resource: Device or
resource busy`

It prepends `/home` to the path in the warning message.

Tested on Ubuntu 18.04 from package util-linux 2.30.1-0ubuntu4.

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

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

Title:
  fusermount -u in bash script prepends /home to path if resource is
  busy

Status in util-linux package in Ubuntu:
  New

Bug description:
  Kindly see this question in StackExchange:

  https://superuser.com/q/1494196/253105

  If a busy resource path is passed such as `fusermount -u
  /path/to/busy/resource`, fusermount gives the following message:

  `fusermount: failed to unmount /home/path/to/busy/resource: Device or
  resource busy`

  It prepends `/home` to the path in the warning message.

  Tested on Ubuntu 18.04 from package util-linux 2.30.1-0ubuntu4.

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

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


[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7

2019-10-21 Thread Brian Murray
** Tags added: rls-ff-incoming

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

Title:
  apport python exception handler messes up python3.7

Status in Apport:
  New
Status in apport package in Ubuntu:
  Triaged
Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

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


[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session

2019-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions

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


[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session

2019-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions

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


[Touch-packages] [Bug 1759950] Re: Lid-close suspend: blank screen when switching to user session

2019-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xfce4-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Lid-close suspend: blank screen when switching to user session

Status in Light-Locker:
  New
Status in Xfce4 Power Manager:
  Confirmed
Status in light-locker package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in xfce4-power-manager package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Confirmed

Bug description:
  I'm currently testing Xubuntu 18.04 after a do-release-upgrade from
  16.04.

  I discovered a very weird issue. When doing S3 sleep via closing the
  lid, on resume the lock screen appears, I authenticate, but as soon as
  it switches to the user session the screen goes blank - not even a
  backlight.

  Switching to other ttys works and they display correctly but the GUI
  user session remains blank.

  If the system is manually suspended (not using the lid), then resumed
  either by opening the lid or pressing the power button, the GUI user
  session is fine.

  I narrowed it down to xfce4-power-manager and discovered disabling the
  lock-screen cured the issue.

  I cloned the repository and reviewed commits between 1.7 and 1.8.
  Fortunately there aren't many. Looking at 6365683 "Proper exit status
  for light-locker-command" I suspected the change in the SetActive
  return value, and reverted it.

  After a build/install cycle I've found the system now behaves
  correctly so I think the change should be reverted.

  I've created an issue upstream for this at

  https://github.com/the-cavalry/light-locker/issues/108

To manage notifications about this bug go to:
https://bugs.launchpad.net/light-locker/+bug/1759950/+subscriptions

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


[Touch-packages] [Bug 1846290] Re: Ubuntu 19.10 incorrectly selects audio output source

2019-10-21 Thread Bickhaus
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

** This bug has been marked a duplicate of bug 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  Ubuntu 19.10 incorrectly selects audio output source

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have two monitors hooked up to an AMD RX570 via displayport.  In the
  sound settings they appear as "Ellesmere HDMI Audio [Radeon RX
  470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the
  output device by default.  My speakers are connected to a green mini-
  jack line out jack on the motherboard.  Switching to line out gives me
  sound, and I have no other issues.

  Originally, I had upgraded to the beta from the command line in 19.04.
  I had not experienced this issue in 19.04, but upon first booting into
  19.10, I had to switch output device back to line out.  A fresh
  install of the beta iso gave the same result (one of my monitors
  connected to my video card was selected by default).  Note that my
  monitors are Dell U2415s but they do have line out jacks.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bick   1719 F pulseaudio
   /dev/snd/controlC0:  bick   1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 00:19:28 2019
  InstallationDate: Installed on 2019-10-02 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] - HDA 
ATI HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bick   1719 F pulseaudio
   /dev/snd/controlC0:  bick   1719 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Adam Conrad
The builds all succeeded, and tested booting on amd64 (the only arch
likely to be affected, due to cf-protection changes in the toolchain),
and it booted fine.  Marking v-done.

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

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Fix Committed

Bug description:
  [ SRU Justification / Impact ]
  klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.

  [ Test Case ]
  If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.

  [ Regression Potential ]
  One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.

  [ Original Bug Report ]
  
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
    |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1848784] Re: Crash in Qt 5.12.2

2019-10-21 Thread Alex Murray
This would appear to have security implications since I imagine if an
email were sent to a KMail recipient which was crafted in this same way
it would crash KMail? If this is likely true a CVE should be requested
from MITRE via https://cveform.mitre.org/ so that other distros etc can
ensure they ship this patch too.

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+subscriptions

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


[Touch-packages] [Bug 1440818] Re: apport-bug does not anonymize udevdb log

2019-10-21 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  apport-bug does not anonymize udevdb log

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  when apport-bug joins the output of 'udevadm info --export-db' as
  UdevDb.txt' in a bug report, various uuid related to partitions, file
  systems, and disks are not anonymized.

  More over serial number of disk, mac adress, or WWN are not anonymized
  either.

  I join a patch (to hookutils.py) that attempts to fix that

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashReports:
   640:1000:118:1466952:2015-04-02 01:07:55.905460014 +0200:2015-04-02 
02:29:42.472130210 +0200:/var/crash/_usr_bin_cryptkeeper.1000.crash
   600:109:118:0:2015-04-02 01:07:53.619086261 +0200:2015-04-02 
19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.uploaded
   664:1000:118:0:2015-04-02 01:07:52.598016638 +0200:2015-04-02 
19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.upload
   640:1000:118:8871994:2015-04-02 20:28:37.247845958 +0200:2015-04-02 
20:28:37.599849491 
+0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  CurrentDesktop: Unity
  Date: Mon Apr  6 19:28:41 2015
  InstallationDate: Installed on 2015-04-01 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Brian Murray
Hello Matthias, or anyone else affected,

Accepted klibc into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/klibc/2.0.6-1ubuntu2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: klibc (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-eoan

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Fix Committed

Bug description:
  [ SRU Justification / Impact ]
  klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.

  [ Test Case ]
  If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.

  [ Regression Potential ]
  One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.

  [ Original Bug Report ]
  
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
    |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-10-21 Thread dann frazier
** Description changed:

- After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
- stop on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
+ [Impact]
+ After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop 
+ on breakpoint when running a 32-bit application (on 64-bit Ubuntu). 
+ 
+ [Test Case]
  This can be reproduced with a simple “hello world” program:
  
- $ cat hello.c 
+ $ cat hello.c
  #include 
  int main()
  {
-// printf() displays the string inside quotation
-printf("Hello, World!");
-return 0;
+    // printf() displays the string inside quotation
+    printf("Hello, World!");
+    return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
- Starting program: /home/user/sandbox/a.out 
+ Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
  
  --- (and not stopping nor outputting the text…) ---
  
- It works well with a 64-bit build (leaving out the gcc’s -m32 option).
+ [Regression Risk]
+ Test case ran on arm64 and regression tested on amd64/i386.
  
- This problem has been already discussed on:
- https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-in-
- ld-linux-so-2-when-running-a-32-bit-executable-on-a-64
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: gdb 8.1-0ubuntu3.1
- ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
- Uname: Linux 4.15.0-65-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.7
- Architecture: amd64
- CurrentDesktop: XFCE
- Date: Tue Oct 15 14:37:37 2019
- InstallationDate: Installed on 2015-12-08 (1407 days ago)
- InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
- SourcePackage: gdb
- UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)
+ This regression was fixed on the upstream gdb-8.1 branch within a few
+ weeks of the breakage back in May 2018. Since then there have been no
+ other fixes in this area on that branch, implying this fixed the issue
+ and there were no further regressions discovered.

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  New
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop 
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu). 

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested on amd64/i386.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Adam Conrad
Oh, klibc has the same cc-option magic as the kernel's Kbuild does, so
that's the correct upstream answer.  I'll update my patch to use that
when I merge 2.0.7.

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Confirmed

Bug description:
  [ SRU Justification / Impact ]
  klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.

  [ Test Case ]
  If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.

  [ Regression Potential ]
  One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.

  [ Original Bug Report ]
  
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
    |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Adam Conrad
** Description changed:

- https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-
- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz
+ [ SRU Justification / Impact ]
+ klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.
+ 
+ [ Test Case ]
+ If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.
+ 
+ [ Regression Potential ]
+ One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.
+ 
+ [ Original Bug Report ]
+ 
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz
  
  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
- 8 | #include 
-   |  ^
+ 8 | #include 
+   |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Confirmed

Bug description:
  [ SRU Justification / Impact ]
  klibc is FTBFS in eoan.  As we have a history of SRUing klibc to add new 
features, we should probably make sure it's buildable.

  [ Test Case ]
  If it builds, we win.  Should also test that a machine with the new klibc 
installed still boots.

  [ Regression Potential ]
  One patch is just adding a missing include, and the other is altering the 
build of a stub only used to determine which syscalls are availble, a part of 
the build that will cause the rest of the build to fail if it's generated 
incorrectly.  Regression potential should be very low.

  [ Original Bug Report ]
  
https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
    |  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan

2019-10-21 Thread Adam Conrad
> The best guess I can come up with is that there's something different
> about the compiler defaults you're using

Derp, this was the hint I needed.  The attached patch fixes the build on
Ubuntu, though I can't think of a good way to upstream this, as the
compiler option in question isn't available throughout history.
Probably needs a test of some sort.

** Patch added: "cf-protection.patch"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+attachment/5299063/+files/cf-protection.patch

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

Title:
  klibc ftbfs in eoan

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Eoan:
  Confirmed

Bug description:
  https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-
  amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz

  gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c
  usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file 
or directory
  8 | #include 
|  ^
  compilation terminated.
  make[4]: *** [/<>/scripts/Kbuild.klibc:252: 
usr/klibc/sigsuspend.o] Error 1
  make[3]: *** [/<>/./Kbuild:9: all] Error 2
  make[2]: *** [Makefile:118: klibc] Error 2

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

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


[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

2019-10-21 Thread Kevin
@dwmw2

Were you able to make this work by doing this for firefox?

sudo mv /usr/lib/firefox/libnssckbi.so /usr/lib/firefox/libnssckbi.so.bak
sudo ln -s /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so 
/usr/lib/firefox/libnssckbi.so

https://askubuntu.com/questions/244582/add-certificate-authorities-
system-wide-on-firefox/1036637#1036637

I wasn't able to get it to work. Doing the above doesn't work at all for
me. I'm on 18.04.3

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

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

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


[Touch-packages] [Bug 1848916] Re: software-properties-gtk don't started

2019-10-21 Thread Sebastien Bacher
Thank you for your bug report. Do you get any error? Could start it from
a command line and see if messages are displayed there? Could you add
your 'journalctl -b 0' log after getting the issue?

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  software-properties-gtk don't started

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 20.04, software-properties-gtk don't started

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 20 11:55:28 2019
  InstallationDate: Installed on 2019-10-07 (12 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1849112] Re: could not enable respsoitory 19.10

2019-10-21 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  could not enable respsoitory 19.10

Status in software-properties package in Ubuntu:
  New

Bug description:
  couldn't enable canonical partner from other tab if india server
  enabled if main server eanbled it can tick but not from india server

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.7
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 18:50:05 2019
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1849112] [NEW] could not enable respsoitory 19.10

2019-10-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

couldn't enable canonical partner from other tab if india server enabled
if main server eanbled it can tick but not from india server

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16.7
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 21 18:50:05 2019
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco dist-upgrade
-- 
could not enable respsoitory 19.10
https://bugs.launchpad.net/bugs/1849112
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

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


[Touch-packages] [Bug 1849188] [NEW] fdisk fails to report heads/sectors/cylinders

2019-10-21 Thread small kitties
Public bug reported:

Hello Util-Linux Team,

The following is what I was trying to do:  
user@group:~$ sudo fdisk /dev/sda1
Command (m for help): p

The second line after entering "p" should show something like this:
"255 heads, 63 sectors/track, 497 cylinders, total 7997440 sectors"

However, this information is no longer available on Ubuntu 18.04.3. I
was originally using util-linux 2.31.1 (2.31.1-0.4ubuntu3.4 500). So, I
upgraded to util-linux 2.34-0 (2.34-0.1ubuntu2) and the problem is still
there.

For sanity sake, I VM'd an Ubuntu 14.04 which uses util-linux 2.20.1 and
tested that fdisk did work properly and produced the 'heads,
sectors/track, cylinders, total sectors' line.

Please let me know if this is something that can be fixed or re-added
into fdisk; or, of any other possible methods to produce such valuable
information in terminal.

Thank you for your time in attending to this problem.

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

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

Title:
  fdisk fails to report heads/sectors/cylinders

Status in util-linux package in Ubuntu:
  New

Bug description:
  Hello Util-Linux Team,

  The following is what I was trying to do:  
  user@group:~$ sudo fdisk /dev/sda1
  Command (m for help): p

  The second line after entering "p" should show something like this:
  "255 heads, 63 sectors/track, 497 cylinders, total 7997440 sectors"

  However, this information is no longer available on Ubuntu 18.04.3. I
  was originally using util-linux 2.31.1 (2.31.1-0.4ubuntu3.4 500). So,
  I upgraded to util-linux 2.34-0 (2.34-0.1ubuntu2) and the problem is
  still there.

  For sanity sake, I VM'd an Ubuntu 14.04 which uses util-linux 2.20.1
  and tested that fdisk did work properly and produced the 'heads,
  sectors/track, cylinders, total sectors' line.

  Please let me know if this is something that can be fixed or re-added
  into fdisk; or, of any other possible methods to produce such valuable
  information in terminal.

  Thank you for your time in attending to this problem.

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

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


[Touch-packages] [Bug 1849183] [NEW] Bluetooth devices doesn't get listed while turn off and then on

2019-10-21 Thread Raghuvar Prajapati
Public bug reported:

When System Starts, first time Bluetooth devices(Say headphones) get
connected smoothly. But after a point when headphones get disconnected,
If I tried to reconnect Bluetooth settings don't list the devices. I
turned it on/off multiple times but doesn't work. The only way that'd
work after a system restart. Please can you check into this

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raghuvar   1999 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 21 23:39:04 2019
InstallationDate: Installed on 2019-06-30 (113 days ago)
InstallationMedia:
 
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
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 ideapad 320-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
dmi.product.family: ideapad 320-15IKB
dmi.product.name: 80XL
dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
dmi.product.version: Lenovo ideapad 320-15IKB
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Bluetooth Setting Snapshot"
   
https://bugs.launchpad.net/bugs/1849183/+attachment/5299021/+files/Bluetooth%20On_Not%20Showing.png

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

Title:
  Bluetooth devices doesn't get listed while turn off and then on

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When System Starts, first time Bluetooth devices(Say headphones) get
  connected smoothly. But after a point when headphones get
  disconnected, If I tried to reconnect Bluetooth settings don't list
  the devices. I turned it on/off multiple times but doesn't work. The
  only way that'd work after a system restart. Please can you check into
  this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghuvar   1999 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 23:39:04 2019
  InstallationDate: Installed on 2019-06-30 (113 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  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 ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1847496] Update Released

2019-10-21 Thread Steve Langasek
The verification of the Stable Release Update for apt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

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

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


[Touch-packages] [Bug 1847496] Re: [trusty] policy not always initialized when building depcache

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.0.1ubuntu2.24

---
apt (1.0.1ubuntu2.24) trusty; urgency=medium

  [ Michael Vogt ]
  * Ensure we have a Policy in CacheFile.BuildDepCache() (LP: #1847496)

 -- Julian Andres Klode   Thu, 10 Oct 2019 11:24:58
+0200

** Changed in: apt (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

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

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


[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7

2019-10-21 Thread Calvin Cheng
Just ran into this same problem.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

$ python3 --version
Python 3.7.3

$ apt-cache policy python3.7
python3.7:
  Installed: 3.7.3-2~18.04.1
  Candidate: 3.7.3-2~18.04.1
  Version table:
 *** 3.7.3-2~18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.7.0~b3-1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

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

Title:
  apport python exception handler messes up python3.7

Status in Apport:
  New
Status in apport package in Ubuntu:
  Triaged
Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

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


[Touch-packages] [Bug 1849158] [NEW] Include the systemd package version in journal output

2019-10-21 Thread Dan Watkins
Public bug reported:

I'm currently debugging something based on journal output.  I,
helpfully, know what kernel was running due to this line:

  kernel: Linux version 5.3.0-13-generic (buildd@lgw01-amd64-012) (gcc
version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #14-Ubuntu SMP Tue Sep
24 02:46:08 UTC 2019 (Ubuntu 5.3.0-13.14-generic 5.3.0)

but it's not entirely clear which version of systemd was running:

  systemd[1]: systemd 242 running in system mode. ()

Even during in eoan's development cycle, we've had a number of different
"systemd 242"s that this could be.  In a stable LTS, we'll have many
more (32 and counting "systemd 237"s in bionic, for example).  It would
be good if we captured this information in the journal somewhere.

** Affects: systemd (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Include the systemd package version in journal output

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm currently debugging something based on journal output.  I,
  helpfully, know what kernel was running due to this line:

kernel: Linux version 5.3.0-13-generic (buildd@lgw01-amd64-012) (gcc
  version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #14-Ubuntu SMP Tue Sep
  24 02:46:08 UTC 2019 (Ubuntu 5.3.0-13.14-generic 5.3.0)

  but it's not entirely clear which version of systemd was running:

systemd[1]: systemd 242 running in system mode. ()

  Even during in eoan's development cycle, we've had a number of
  different "systemd 242"s that this could be.  In a stable LTS, we'll
  have many more (32 and counting "systemd 237"s in bionic, for
  example).  It would be good if we captured this information in the
  journal somewhere.

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

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


[Touch-packages] [Bug 1849156] [NEW] systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2019-10-21 Thread Paul Buonopane
Public bug reported:

Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
systemd-timesyncd.service from starting if the ntp package has been
installed.  However, ntp.service has a Conflicts directive for systemd-
timesyncd.service.  If both services are enabled, neither will start on
boot.  This breaks upgrades from < 19.10 to 19.10 for systems that have
both ntp and systemd installed.

Possible workarounds:

- Uninstall ntp
- Disable systemd-timesyncd.service

% lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

% apt-cache policy systemd
systemd:
  Installed: 242-7ubuntu3
  Candidate: 242-7ubuntu3
  Version table:
 *** 242-7ubuntu3 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
100 /var/lib/dpkg/status

% apt-cache policy ntp
ntp:
  Installed: 1:4.2.8p12+dfsg-3ubuntu2
  Candidate: 1:4.2.8p12+dfsg-3ubuntu2
  Version table:
 *** 1:4.2.8p12+dfsg-3ubuntu2 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe amd64 
Packages
100 /var/lib/dpkg/status

% dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

% sudo systemctl status ntp
● ntp.service - Network Time Service
   Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead)
 Docs: man:ntpd(8)

% sudo systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: inactive (dead)
Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
 Docs: man:systemd-timesyncd.service(8)

Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
Time Synchronization being skipped.

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

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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


[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2019-10-21 Thread Paul Buonopane
I realize that the title makes it sound as though this is intended
behavior.  To be clear, in this scenario, neither systemd-
timesyncd.service nor ntp.service start.  It's not just systemd-
timesyncd.service that doesn't start, as that would be intended
behavior.

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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


[Touch-packages] [Bug 1849153] [NEW] systemd-udev-settle.service blocks boot for ~90s with a debug-logged assertion failure

2019-10-21 Thread Dan Watkins
Public bug reported:

I started seeing this when I booted this morning, and I've seen it in
the 2 reboots since (one for a new kernel, one to capture debug logs).
After modifying /etc/udev/udev.conf to capture debug logging, I see:

$ journalctl -u systemd-udev-settle.service -b0
-- Logs begin at Wed 2019-08-14 09:26:57 EDT, end at Mon 2019-10-21 11:53:56 
EDT. --
Oct 21 11:42:50 surprise udevadm[678]: Assertion 's' failed at 
../src/libsystemd/sd-event/sd-event.c:1688, function 
sd_event_source_set_description(). Ignoring.
Oct 21 11:44:24 surprise systemd[1]: Started udev Wait for Complete Device 
Initialization.

(Of possible value for debugging: the last time I rebooted before I was
seeing this issue was on Oct 7th, so I had the 5.3.0-13-generic kernel
and, looking at the publishing history, an older version of systemd
too.)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: udev 242-7ubuntu3
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: i3
CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules
Date: Mon Oct 21 11:50:26 2019
InstallationDate: Installed on 2019-05-07 (166 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to eoan on 2019-05-08 (165 days ago)
dmi.bios.date: 01/25/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
mtime.conffile..etc.udev.udev.conf: 2019-10-21T11:39:04.067705

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


** Tags: amd64 apport-bug eoan

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

Title:
  systemd-udev-settle.service blocks boot for ~90s with a debug-logged
  assertion failure

Status in systemd package in Ubuntu:
  New

Bug description:
  I started seeing this when I booted this morning, and I've seen it in
  the 2 reboots since (one for a new kernel, one to capture debug logs).
  After modifying /etc/udev/udev.conf to capture debug logging, I see:

  $ journalctl -u systemd-udev-settle.service -b0
  -- Logs begin at Wed 2019-08-14 09:26:57 EDT, end at Mon 2019-10-21 11:53:56 
EDT. --
  Oct 21 11:42:50 surprise udevadm[678]: Assertion 's' failed at 
../src/libsystemd/sd-event/sd-event.c:1688, function 
sd_event_source_set_description(). Ignoring.
  Oct 21 11:44:24 surprise systemd[1]: Started udev Wait for Complete Device 
Initialization.

  (Of possible value for debugging: the last time I rebooted before I
  was seeing this issue was on Oct 7th, so I had the 5.3.0-13-generic
  kernel and, looking at the publishing history, an older version of
  systemd too.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: udev 242-7ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: i3
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules
  Date: Mon Oct 21 11:50:26 2019
  InstallationDate: Installed on 2019-05-07 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (165 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1848777] Re: Systemd is missing a patch to allow it to be used with SELinux

2019-10-21 Thread Balint Reczey
The fix is present in v240 and later.

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  Systemd is missing a patch to allow it to be used with SELinux

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New

Bug description:
  Ubuntu Version:
  Description: Ubuntu 18.04.3 LTS
  Release: 18.04

  Systemd version:
  Installed: 273-ubuntu10.29
  Candidate: 273-ubuntu10.31

  Expected Behavior:
  Systemd will only remount the cgroups if they need to be relabeled.

  Actual Behavior:
  Systemd will try to re-mount the cgroups for relabeling which will fail and 
break systemd services that use cgroups.

  Upstream fix:
  https://github.com/systemd/systemd/pull/8595

  Additional Notes:
  I was able to work around this issue by applying the patch linked and 
changing the line:
  
https://github.com/systemd/systemd/pull/8595/files#diff-9e1684efe63d10844b8dd6708fc60e8dR408
  To use the 237 version of fix label. E.G. (void) label_fix("/sys/fs/cgroup", 
true, true);
  While building the package from source.

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

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


[Touch-packages] [Bug 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.9

---
util-linux (2.27.1-6ubuntu3.9) xenial; urgency=medium

  * d/p/libblkid-nilfs2-add-length-check-before-crc32.patch:
Fix misdetection/false-positive of nilfs2 filesystem on
device with magic bytes coincidentally on end of device
and bad checksum ignored by udev blkid. (LP: #1842437)

 -- Mauricio Faria de Oliveira   Tue, 03 Sep 2019
11:32:50 -0300

** Changed in: util-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
  with udev

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users / systemd can fail to mount a filesystem by UUID
 (e.g., during boot, triggering emergency shell prompt)
 if the magic bytes for the nilfs filesystem are written
 to the right place in a partition of another filesystem,
 (for whatever reason or coincidence).

   * Note this can happen after the filesystem/mount is working
 correctly, so a change of behavior/problem can potentially
 be noticed when trying to mount the filesystem again, which
 can very well be the next time the system boots.

   * This happens because if udev blkid detects more than one
 filesystem, it does not print the UUID env vars required
 to create the /dev/disk/by-id symlinks and other things.

   * The fix enhances the check for valid nilfs superblock by
 specifically checking a value read from disk to be valid/
 within a value range, which addresses this one occurrence
 and prevents a lot more.

  [Test Case]

   * Synthetic test case written for this problem on comment #6.

  [Regression Potential]

   * Low.  The code is contained in the probe for the nilfs filesystem.

   * This just makes it be more restrictive about the possibly valid
 values for a few bytes read from disk (that now need to be within
 the acceptable range of valid values) so this only decreases false-
 positives, and cannot increase false-negatives of valid filesystems.

  [Original Description]

  The nilfs filesystem has a backup superblock at the end of the device.

  If the magic number is coincidentally found at the right position
  and the filesystem is on a partition/not-wholedisk device,
  the only check left is for checksum verification,
  which is explicitly ignored in 'udev built-in blkid'.

  This causes blkid to detect one actually valid filesystem with a
  superblock at the beginning of the device (e.g., ext4), and then
  an invalid nilfs2 filesystem due to a coincidental magic number
  at the end of the device.

  And this causes blkid to break out of the safeprobe routine
  (which expects a single filesystem to be detected), and not
  print the UUIDs, thus not creating /dev/disk/by-uuid/ links
  which prevent mounting the partition by-uuid at boot time,
  causing emergency shell/boot failures.

  This upstream fix resolved the problem by introducing a check
  for the 'bytes' paramenters in the superblock, which is read
  from disk, and turns out to have an out-of-range value.

  - 'liblkid: Add length check in probe_nilfs2 before crc32'
  
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2

  $ git describe --contains ac681a310c32319423297544833932f4d689a7a2
  v2.29-rc1~172

  Xenial, which is v2.27.1-based, is the only release that needs it.
  Bionic is v2.31.1, so all post-Xenial supported releases have it.

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

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


[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package bluez - 5.48-0ubuntu3.2

---
bluez (5.48-0ubuntu3.2) bionic; urgency=medium

  * d/p/lp1759836.patch: avoid endless udev events from new bind uevents
(LP: #1759836)

 -- Dan Streetman   Tue, 10 Sep 2019 17:25:22
-0400

** Changed in: bluez (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  [impact]

  on specific Dell systems, with a specific usb bluetooth device built-
  in, the udev rule 'hid2hci' provided by the 'bluez' package causes an
  endless loop of uevents resulting from 'bind' or 'unbind' kernel
  uevents.  These new events were added to the kernel after the
  'hid2hci' udev rule was written.

  [test case]

  the specific Dell system is required to be able to reproduce this, or
  at least the specific usb bluetooth hardware included in that system.

  Reproducing this is reportedly easy, for example comment 75 indicates
  it happens on every boot.

  When this happens, any process monitor (e.g. ps, top, etc) will show
  the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should
  show repeated 'bind' and 'unbind' events as mentioned in comment 39.

  [regression potential]

  as this alters what kernel uevents the 'hid2hci' udev rule processes,
  regressions would involve the affected usb bluetooth device failing to
  be set up, or otherwise not processing the uevents correctly.

  [other info]

  this is not fixed yet upstream, as of my last check, but has been
  submitted upstream as mentioned in comment 95.

  
  original description:

  --

  
  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not 
noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1772512] Update Released

2019-10-21 Thread Łukasz Zemczak
The verification of the Stable Release Update for libxkbcommon has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package libxkbcommon - 0.8.2-1~ubuntu18.04.1

---
libxkbcommon (0.8.2-1~ubuntu18.04.1) bionic; urgency=medium

  * Backport to bionic
- sync with upstream, drop CVE patches
- sync packaging, mark -dev packages M-A: same (LP: #1772512)

libxkbcommon (0.8.2-1) unstable; urgency=medium

  * New upstream release (Closes: #907302).
- Fixes CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.
  * control: Update vcs urls.
  * control: Priority optional for all packages.

libxkbcommon (0.8.0-2) unstable; urgency=medium

  * control: Mark -dev packages M-A: same. (LP: #1772512)
  * Split documentation from -dev to -doc. (Closes: #893855)
  * rules: Purge doxygen .md5 files.

 -- Timo Aaltonen   Tue, 05 Mar 2019 16:36:07 +0200

** Changed in: libxkbcommon (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15853

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15854

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15855

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15856

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15857

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15858

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15859

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15861

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15862

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15863

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15864

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


[Touch-packages] [Bug 1842437] Update Released

2019-10-21 Thread Łukasz Zemczak
The verification of the Stable Release Update for util-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem
  with udev

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users / systemd can fail to mount a filesystem by UUID
 (e.g., during boot, triggering emergency shell prompt)
 if the magic bytes for the nilfs filesystem are written
 to the right place in a partition of another filesystem,
 (for whatever reason or coincidence).

   * Note this can happen after the filesystem/mount is working
 correctly, so a change of behavior/problem can potentially
 be noticed when trying to mount the filesystem again, which
 can very well be the next time the system boots.

   * This happens because if udev blkid detects more than one
 filesystem, it does not print the UUID env vars required
 to create the /dev/disk/by-id symlinks and other things.

   * The fix enhances the check for valid nilfs superblock by
 specifically checking a value read from disk to be valid/
 within a value range, which addresses this one occurrence
 and prevents a lot more.

  [Test Case]

   * Synthetic test case written for this problem on comment #6.

  [Regression Potential]

   * Low.  The code is contained in the probe for the nilfs filesystem.

   * This just makes it be more restrictive about the possibly valid
 values for a few bytes read from disk (that now need to be within
 the acceptable range of valid values) so this only decreases false-
 positives, and cannot increase false-negatives of valid filesystems.

  [Original Description]

  The nilfs filesystem has a backup superblock at the end of the device.

  If the magic number is coincidentally found at the right position
  and the filesystem is on a partition/not-wholedisk device,
  the only check left is for checksum verification,
  which is explicitly ignored in 'udev built-in blkid'.

  This causes blkid to detect one actually valid filesystem with a
  superblock at the beginning of the device (e.g., ext4), and then
  an invalid nilfs2 filesystem due to a coincidental magic number
  at the end of the device.

  And this causes blkid to break out of the safeprobe routine
  (which expects a single filesystem to be detected), and not
  print the UUIDs, thus not creating /dev/disk/by-uuid/ links
  which prevent mounting the partition by-uuid at boot time,
  causing emergency shell/boot failures.

  This upstream fix resolved the problem by introducing a check
  for the 'bytes' paramenters in the superblock, which is read
  from disk, and turns out to have an out-of-range value.

  - 'liblkid: Add length check in probe_nilfs2 before crc32'
  
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2

  $ git describe --contains ac681a310c32319423297544833932f4d689a7a2
  v2.29-rc1~172

  Xenial, which is v2.27.1-based, is the only release that needs it.
  Bionic is v2.31.1, so all post-Xenial supported releases have it.

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

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


[Touch-packages] [Bug 1841058] Re: kernel version 4.4.0-1090-aws docker file system issue

2019-10-21 Thread Dan Streetman
Unsetting linux-aws back to New, as further investigation seems to
indicate there is a kernel bug (as well as sed bug)

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

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

Title:
  kernel version 4.4.0-1090-aws docker file system issue

Status in linux-aws package in Ubuntu:
  New
Status in sed package in Ubuntu:
  New

Bug description:
  When using kernel version 4.4.0-1090-aws 
  if you have running container and you do sed on some files then you cannot 
access them inside the container any more

  we use the nginx image and we can reproduce it everytime

  in the container we have chown and then sed commands on some nginx.conf files 
  after the sed we are getting persmission denied inside the container even 
that we use root.

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

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


[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2019-10-21 Thread Daniel Llewellyn
This affects Eoan if you install Ubuntu proper, add accounts to "Online
Accounts", then switch into an Ubuntu Mate session (installed via Apt on
top of the same system - apt install ubuntu-mate-desktop^)

** Tags added: eoan

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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


Re: [Touch-packages] [Bug 1848587] [NEW] lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

2019-10-21 Thread Seth Forshee
On Fri, Oct 18, 2019 at 03:03:43PM -, Christian Brauner wrote:
> Is this a flake or consistently reproducible?

It's reproducible.

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

Title:
  lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

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

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


[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command

2019-10-21 Thread Marius Gedminas
This is fixed on Ubuntu 19.10, where journalctl -g works fine.

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

Title:
  man journalctl gives info about -g option not present in command

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  man journalctl documents a --grep option, however:

  $ journalctl -g a
  journalctl: invalid option -- 'g'

  $ journalctl --grep a
  Compiled without pattern matching support

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 25 21:53:29 2018
  InstallationDate: Installed on 2017-06-21 (248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 004: ID 10d7:1102  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash 
acpi_rev_override=5 pci=noaer vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main

2019-10-21 Thread Marius Gedminas
journactl --grep works in Ubuntu 19.10 (but not 19.04 or older
versions).

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

Title:
  Journalctl compiled without pattern matching support, pcre2 is not in
  main

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Please add pattern matching support to journalctl.  At the moment, the
  -g (--grep) option as described in the man page doesn't work:

  ╰─▶ journalctl --grep=xhci-hcd 
  Compiled without pattern matching support

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

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


[Touch-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1025.28

---
linux-oem-osp1 (5.0.0-1025.28) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1025.28 -proposed tracker
(LP: #1846095)

  * Fix non-working Realtek USB ethernet after system resume (LP: #1847063)
- r8152: remove extra action copying ethernet address
- r8152: Refresh MAC address during USBDEVFS_RESET
- r8152: Set macpassthru in reset_resume callback

  * drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL
platforms (LP: #1847192)
- SAUCE: drm/i915: Fix audio power up sequence for gen10+ display
- SAUCE: drm/i915: extend audio CDCLK>=2*BCLK constraint to more platforms

  * [CML-U] Comet lake platform need ISH driver support (LP: #1843775)
- HID: intel-ish-hid: Add Comet Lake PCI device ID

  * [CML] New device IDs for CML-U (LP: #1843774)
- spi-nor: intel-spi: Add support for Intel Comet Lake SPI serial flash

  * Add new pci-id's for CML-S, ICL (LP: #1845317)
- drm/i915/icl: Add missing device ID
- drm/i915/cml: Add Missing PCI IDs

  * Thunderbolt support for ICL (LP: #1844680)
- thunderbolt: Drop duplicated get_switch_at_route()
- thunderbolt: Move LC specific functionality into a separate file
- thunderbolt: Cache adapter specific capability offset into struct port
- thunderbolt: Rename tunnel_pci to tunnel
- thunderbolt: Generalize tunnel creation functionality
- thunderbolt: Add functions for allocating and releasing HopIDs
- thunderbolt: Assign remote for both ports in case of dual link
- thunderbolt: Add helper function to iterate from one port to another
- thunderbolt: Extend tunnel creation to more than 2 adjacent switches
- thunderbolt: Correct path indices for PCIe tunnel
- thunderbolt: Move NVM upgrade support flag to struct icm
- thunderbolt: Use 32-bit writes when writing ring producer/consumer
- thunderbolt: Do not fail adding switch if some port is not implemented
- thunderbolt: Hide switch attributes that are not set
- thunderbolt: Expose active parts of NVM even if upgrade is not supported
- thunderbolt: Add support for Intel Ice Lake
- ACPI / property: Add two new Thunderbolt property GUIDs to the list

  * Intel 1650s/Wi-Fi 6 AX201 cannot connect to 802.11AX networks (LP: #1845138)
- cfg80211: add and use strongly typed element iteration macros
- mac80211: use element iteration macro in parsing
- cfg80211: add various struct element finding helpers
- nl80211: use for_each_element() in validate_ie_attr()
- mac80211: pass bssids to elements parsing function
- mac80211: move the bss update from elements to an helper
- cfg80211: Parsing of Multiple BSSID information in scanning
- cfg80211: use for_each_element() for multi-bssid parsing
- cfg80211: Properly track transmitting and non-transmitting BSS
- cfg80211: Move Multiple BSS info to struct cfg80211_bss to be visible
- cfg80211: parse multi-bssid only if HW supports it
- cfg80211: make BSSID generation function inline
- cfg80211: save multi-bssid properties
- mac80211: support multi-bssid
- mac80211: indicate support for multiple BSSID
- cfg80211: fix the IE inheritance of extension IEs
- cfg80211: fix memory leak of new_ie
- mac80211_hwsim: Declare support for Multi-BSSID
- cfg80211: add missing kernel-doc for multi-BSSID fields
- iwlwifi: mvm: support multiple BSSID
- iwlwifi: mvm: support HE context cmd API change

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  [ Ubuntu: 5.0.0-32.34 ]

  * disco/linux: 5.0.0-32.34 -proposed tracker (LP: #1846097)
  * CVE-2019-14814 // CVE-2019-14815 // CVE-2019-14816
- mwifiex: Fix three heap overflow at parsing element in 
cfg80211_ap_settings
  * CVE-2019-15505
- media: technisat-usb2: break out of loop at end of buffer
  * CVE-2019-2181
- binder: check for overflow when alloc for security context
  * Support Hi1620 zip hw accelerator (LP: #1845355)
- [Config] Enable HiSilicon QM/ZIP as modules
- crypto: hisilicon - add queue management driver for HiSilicon QM module
- crypto: hisilicon - add hardware SGL support
- crypto: hisilicon - add HiSilicon ZIP accelerator support
- crypto: hisilicon - add SRIOV support for ZIP
- Documentation: Add debugfs doc for hisi_zip
- crypto: hisilicon - add debugfs for ZIP and QM
- MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver
- crypto: hisilicon - fix kbuild warnings
- crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
- crypto: hisilicon - init curr_sgl_dma to fix compile warning
- crypto: hisilicon - add missing single_release
- crypto: hisilicon - fix error handle in hisi_zip_create_req_q
- crypto: hisilicon - Fix warning on printing %p with dma_addr_t
- crypto: hisilicon - Fix return value check in hisi_zip_acompress()
  

[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5

2019-10-21 Thread Łukasz Zemczak
Hello Matthias, or anyone else affected,

Accepted python3-stdlib-extensions into disco-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/python3-stdlib-
extensions/3.7.5-1~19.04 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: python3-stdlib-extensions (Ubuntu Disco)
   Status: New => Fix Committed

** Tags added: verification-needed-disco

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

Title:
  SRU: Update Python interpreter to 3.6.9 and 3.7.5

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in python3-defaults source package in Disco:
  New
Status in python3-stdlib-extensions source package in Disco:
  Fix Committed
Status in python3.7 source package in Disco:
  New
Status in python3-defaults source package in Eoan:
  New
Status in python3-stdlib-extensions source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Fix Committed

Bug description:
  Update Python interpreter to 3.6.9 and 3.7.5.  As done with earlier
  subminor upstream releases (LP: #1822993).

  SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
  3.6.9 release.

  python3-stdlib-extensions also updates the modules to the 3.6.9
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests. The new
  packages don't cause regressions in a test rebuild of the main
  component.

  TODO: update after test rebuild
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

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

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


[Touch-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-10-21 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: Triaged => In Progress

** Changed in: mesa (Ubuntu)
Milestone: ubuntu-19.04 => None

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in Eoan:
  Triaged
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL

2019-10-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1025.28

---
linux-oem-osp1 (5.0.0-1025.28) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1025.28 -proposed tracker
(LP: #1846095)

  * Fix non-working Realtek USB ethernet after system resume (LP: #1847063)
- r8152: remove extra action copying ethernet address
- r8152: Refresh MAC address during USBDEVFS_RESET
- r8152: Set macpassthru in reset_resume callback

  * drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL
platforms (LP: #1847192)
- SAUCE: drm/i915: Fix audio power up sequence for gen10+ display
- SAUCE: drm/i915: extend audio CDCLK>=2*BCLK constraint to more platforms

  * [CML-U] Comet lake platform need ISH driver support (LP: #1843775)
- HID: intel-ish-hid: Add Comet Lake PCI device ID

  * [CML] New device IDs for CML-U (LP: #1843774)
- spi-nor: intel-spi: Add support for Intel Comet Lake SPI serial flash

  * Add new pci-id's for CML-S, ICL (LP: #1845317)
- drm/i915/icl: Add missing device ID
- drm/i915/cml: Add Missing PCI IDs

  * Thunderbolt support for ICL (LP: #1844680)
- thunderbolt: Drop duplicated get_switch_at_route()
- thunderbolt: Move LC specific functionality into a separate file
- thunderbolt: Cache adapter specific capability offset into struct port
- thunderbolt: Rename tunnel_pci to tunnel
- thunderbolt: Generalize tunnel creation functionality
- thunderbolt: Add functions for allocating and releasing HopIDs
- thunderbolt: Assign remote for both ports in case of dual link
- thunderbolt: Add helper function to iterate from one port to another
- thunderbolt: Extend tunnel creation to more than 2 adjacent switches
- thunderbolt: Correct path indices for PCIe tunnel
- thunderbolt: Move NVM upgrade support flag to struct icm
- thunderbolt: Use 32-bit writes when writing ring producer/consumer
- thunderbolt: Do not fail adding switch if some port is not implemented
- thunderbolt: Hide switch attributes that are not set
- thunderbolt: Expose active parts of NVM even if upgrade is not supported
- thunderbolt: Add support for Intel Ice Lake
- ACPI / property: Add two new Thunderbolt property GUIDs to the list

  * Intel 1650s/Wi-Fi 6 AX201 cannot connect to 802.11AX networks (LP: #1845138)
- cfg80211: add and use strongly typed element iteration macros
- mac80211: use element iteration macro in parsing
- cfg80211: add various struct element finding helpers
- nl80211: use for_each_element() in validate_ie_attr()
- mac80211: pass bssids to elements parsing function
- mac80211: move the bss update from elements to an helper
- cfg80211: Parsing of Multiple BSSID information in scanning
- cfg80211: use for_each_element() for multi-bssid parsing
- cfg80211: Properly track transmitting and non-transmitting BSS
- cfg80211: Move Multiple BSS info to struct cfg80211_bss to be visible
- cfg80211: parse multi-bssid only if HW supports it
- cfg80211: make BSSID generation function inline
- cfg80211: save multi-bssid properties
- mac80211: support multi-bssid
- mac80211: indicate support for multiple BSSID
- cfg80211: fix the IE inheritance of extension IEs
- cfg80211: fix memory leak of new_ie
- mac80211_hwsim: Declare support for Multi-BSSID
- cfg80211: add missing kernel-doc for multi-BSSID fields
- iwlwifi: mvm: support multiple BSSID
- iwlwifi: mvm: support HE context cmd API change

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  [ Ubuntu: 5.0.0-32.34 ]

  * disco/linux: 5.0.0-32.34 -proposed tracker (LP: #1846097)
  * CVE-2019-14814 // CVE-2019-14815 // CVE-2019-14816
- mwifiex: Fix three heap overflow at parsing element in 
cfg80211_ap_settings
  * CVE-2019-15505
- media: technisat-usb2: break out of loop at end of buffer
  * CVE-2019-2181
- binder: check for overflow when alloc for security context
  * Support Hi1620 zip hw accelerator (LP: #1845355)
- [Config] Enable HiSilicon QM/ZIP as modules
- crypto: hisilicon - add queue management driver for HiSilicon QM module
- crypto: hisilicon - add hardware SGL support
- crypto: hisilicon - add HiSilicon ZIP accelerator support
- crypto: hisilicon - add SRIOV support for ZIP
- Documentation: Add debugfs doc for hisi_zip
- crypto: hisilicon - add debugfs for ZIP and QM
- MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver
- crypto: hisilicon - fix kbuild warnings
- crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
- crypto: hisilicon - init curr_sgl_dma to fix compile warning
- crypto: hisilicon - add missing single_release
- crypto: hisilicon - fix error handle in hisi_zip_create_req_q
- crypto: hisilicon - Fix warning on printing %p with dma_addr_t
- crypto: hisilicon - Fix return value check in hisi_zip_acompress()
  

[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-10-21 Thread Hui Wang
So, It looks like we need to set some coeff to make the internal mic
work, but only Realtek engineers know how to set the coeff registers.

And do one more test for external mic:

run sudo hdajacksensetest -a
plug the headset or external mic
run sudo hdajacksensetest -a  again

upload the output-before.txt and output-after.txt.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

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

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


[Touch-packages] [Bug 1849086] Re: [ASRock B450 Pro4, Realtek ALC892, Green Headphone Out, Front] No sound at all by default

2019-10-21 Thread Daniel van Vugt
** Summary changed:

- [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound 
at all by default
+ [ASRock B450 Pro4, Realtek ALC892, Green Headphone Out, Front] No sound at 
all by default

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

Title:
  [ASRock B450 Pro4, Realtek ALC892, Green Headphone Out, Front] No
  sound at all by default

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem happens on a freshly installed Ubuntu 18.04.

  On first boot after reinstall, the state of pavucontrol and Ubuntu's
  sound settings is as shown in the attachment 1.png

  When I change HDA-Audio Generic to Analog Stereo Duplex in
  pavucontrol, the state is as shown in the attachment 2.png and I still
  don't have sound on Front

  One workaround about this is to use pavucontrol to change the port to
  Headpones in Output Devices tab, as shown in attachment 3.png, and the
  Front will output sound.

  The problem is I have to change to Headphones in Output Devices every
  time I boot the system.

  The specs of my machine are:

  CPU: Ryzen 6 3600
  Motherboard: AsRock b450 PRO 4 with BIOS version 3.60

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 11:07:55 2019
  InstallationDate: Installed on 2019-10-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.60
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-10-21 Thread Timo Aaltonen
I believe this was fixed by qemu 4.0 in eoan.

** Changed in: qemu (Ubuntu Eoan)
   Status: Triaged => Fix Released

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Released
Status in mesa package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in Eoan:
  Triaged
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic

2019-10-21 Thread Timo Aaltonen
** Changed in: xorg-server (Ubuntu)
 Assignee: Timo Aaltonen (tjaalton) => (unassigned)

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

Title:
  Desktop live cd boots corrupted screen in Virtualbox on Bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Fix Released

Bug description:
  On a Bionic host running the standard archive version of Virtualbox
  and the daily ISO of Cosmic, the live session starts with a corrupted
  graphical display, as can be seen here:

  https://imgur.com/a/rkTId4S

  (also attached)

  Switching VTs to 2 and back to 1 clears the display and things work
  again.

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

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


[Touch-packages] [Bug 1849086] Re: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all by default

2019-10-21 Thread Aleksandar
** Attachment added: "3.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1849086/+attachment/5298841/+files/3.png

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

Title:
  [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front]
  No sound at all by default

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem happens on a freshly installed Ubuntu 18.04.

  On first boot after reinstall, the state of pavucontrol and Ubuntu's
  sound settings is as shown in the attachment 1.png

  When I change HDA-Audio Generic to Analog Stereo Duplex in
  pavucontrol, the state is as shown in the attachment 2.png and I still
  don't have sound on Front

  One workaround about this is to use pavucontrol to change the port to
  Headpones in Output Devices tab, as shown in attachment 3.png, and the
  Front will output sound.

  The problem is I have to change to Headphones in Output Devices every
  time I boot the system.

  The specs of my machine are:

  CPU: Ryzen 6 3600
  Motherboard: AsRock b450 PRO 4 with BIOS version 3.60

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 11:07:55 2019
  InstallationDate: Installed on 2019-10-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.60
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1849086] Re: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all by default

2019-10-21 Thread Aleksandar
** Attachment added: "2.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1849086/+attachment/5298840/+files/2.png

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

Title:
  [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front]
  No sound at all by default

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem happens on a freshly installed Ubuntu 18.04.

  On first boot after reinstall, the state of pavucontrol and Ubuntu's
  sound settings is as shown in the attachment 1.png

  When I change HDA-Audio Generic to Analog Stereo Duplex in
  pavucontrol, the state is as shown in the attachment 2.png and I still
  don't have sound on Front

  One workaround about this is to use pavucontrol to change the port to
  Headpones in Output Devices tab, as shown in attachment 3.png, and the
  Front will output sound.

  The problem is I have to change to Headphones in Output Devices every
  time I boot the system.

  The specs of my machine are:

  CPU: Ryzen 6 3600
  Motherboard: AsRock b450 PRO 4 with BIOS version 3.60

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 11:07:55 2019
  InstallationDate: Installed on 2019-10-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.60
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1849086] [NEW] [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all by default

2019-10-21 Thread Aleksandar
Public bug reported:

The problem happens on a freshly installed Ubuntu 18.04.

On first boot after reinstall, the state of pavucontrol and Ubuntu's
sound settings is as shown in the attachment 1.png

When I change HDA-Audio Generic to Analog Stereo Duplex in pavucontrol,
the state is as shown in the attachment 2.png and I still don't have
sound on Front

One workaround about this is to use pavucontrol to change the port to
Headpones in Output Devices tab, as shown in attachment 3.png, and the
Front will output sound.

The problem is I have to change to Headphones in Output Devices every
time I boot the system.

The specs of my machine are:

CPU: Ryzen 6 3600
Motherboard: AsRock b450 PRO 4 with BIOS version 3.60

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mate   1324 F pulseaudio
 /dev/snd/controlC1:  mate   1324 F pulseaudio
 /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
 /dev/snd/timer:  mate   1324 f pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 21 11:07:55 2019
InstallationDate: Installed on 2019-10-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mate   1324 F pulseaudio
 /dev/snd/controlC1:  mate   1324 F pulseaudio
 /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
 /dev/snd/timer:  mate   1324 f pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.60
dmi.board.name: B450 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic realtek sound

** Attachment added: "1.png"
   https://bugs.launchpad.net/bugs/1849086/+attachment/5298833/+files/1.png

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

Title:
  [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front]
  No sound at all by default

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem happens on a freshly installed Ubuntu 18.04.

  On first boot after reinstall, the state of pavucontrol and Ubuntu's
  sound settings is as shown in the attachment 1.png

  When I change HDA-Audio Generic to Analog Stereo Duplex in
  pavucontrol, the state is as shown in the attachment 2.png and I still
  don't have sound on Front

  One workaround about this is to use pavucontrol to change the port to
  Headpones in Output Devices tab, as shown in attachment 3.png, and the
  Front will output sound.

  The problem is I have to change to Headphones in Output Devices every
  time I boot the system.

  The specs of my machine are:

  CPU: Ryzen 6 3600
  Motherboard: AsRock b450 PRO 4 with BIOS version 3.60

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1324 F pulseaudio
   /dev/snd/controlC1:  mate   1324 F pulseaudio
   /dev/snd/pcmC1D0p:   mate   1324 F...m pulseaudio
   /dev/snd/timer:  mate   1324 f pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 11:07:55 2019
  InstallationDate: Installed on 2019-10-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: 

[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

2019-10-21 Thread Fernando Racca
*** This bug is a duplicate of bug 1817128 ***
https://bugs.launchpad.net/bugs/1817128

I've summarized my investigation so far in this new bug report:

It seems a combination of ZSH, Oh-My-Zsh and possibly Powerlevel10k
break the login screen somehow.

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081
https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280

** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296
   https://github.com/robbyrussell/oh-my-zsh/issues/8296

** Bug watch added: github.com/romkatv/powerlevel10k/issues #280
   https://github.com/romkatv/powerlevel10k/issues/280

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: 

[Touch-packages] [Bug 1741107] Re: [Alienware Area-51 R2, Nvidia GPU 71 HDMI/DP, Digital Out, HDMI] Playback problem

2019-10-21 Thread Jason McCracken
I have a similar set up and issue.  
I've plugged in my headphones and the "dongle" into my headhpone and mic jacks 
on my sound blaster Z.
No sound when I first install Kubuntu.  I default to using headphones.

I disabled the onboard creative audio in the BIOS when I first purchased
the system with the sound blaster Z.  The onboard audio does not show up
in Kubuntu (expected).

The Nvidia HDMI sound ports are both seen and take priority.  I cannot
change the priority order in the volume control gui.

Also, there are no other mixer options except for a very basic slider in
the volume control gui (Pulse Audio).

If I run the alsamixer app from the command line and unmute the
headphones I can head sound.  In order to save my configs I have to use
the alsactl store command.

All of this is an inconvenience and not the end of the world.  That
said, it would be nice to have more volume sliders in the Pulse Audio
GUI and change the priority of the devices so that HDMI is not seen as
the primary device.

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

Title:
  [Alienware Area-51 R2, Nvidia GPU 71 HDMI/DP, Digital Out, HDMI]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Both the headphone jack ports(front and back) do not work. No sound
  heard when connected to headphones or speakers using a 3.5 mm jack.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   ninja  2049 F...m pulseaudio
   /dev/snd/controlC0:  ninja  2049 F pulseaudio
   /dev/snd/controlC1:  ninja  2049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan  3 14:41:02 2018
  InstallationDate: Installed on 2017-12-16 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia successful
  Symptom_Card: GM204 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Alienware Area-51 R2, Nvidia GPU 71 HDMI/DP, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A01
  dmi.board.name: 0XJKKD
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA01:bd10/01/2014:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0XJKKD:rvrA01:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware

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

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


[Touch-packages] [Bug 1426851] Re: Power button shuts down computer if a Qt application is running

2019-10-21 Thread Neptilo
*** This bug is a duplicate of bug 1847974 ***
https://bugs.launchpad.net/bugs/1847974

@vanvugt This is not the same bug though. In my case, it is the computer
that shut down, not just apps.

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

Title:
  Power button shuts down computer if a Qt application is running

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04, the usual behavior of the power button is bringing a
  dialog with options (Lock, Suspend, Restart, Shutdown) and waiting for
  the user's choice.

  When a Qt application is running, for instance Qt Creator or Texmaker,
  (but not VLC, Clementine or Skype) and the power button is pressed, it
  instantly closes that Qt app (http://qt-
  project.org/forums/viewthread/47632/), brings the shut down dialog and
  then shuts down the computer without waiting for the user’s choice.

  I first asked about this on this forum: 
http://qt-project.org/forums/viewthread/53243/#222409
  and reported it at Qt Creator, thinking it was the only application causing 
it, where they told me to report it to Canonical: 
https://bugreports.qt.io/browse/QTCREATORBUG-14030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426851/+subscriptions

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


[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu 20.04

2019-10-21 Thread Timo Aaltonen
You mean doing upstream work to add support for it? No, I don't think
so.

** Summary changed:

- HDR support for Ubuntu 20.04
+ HDR support for Ubuntu

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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


[Touch-packages] [Bug 1426851] Re: Power button shuts down computer if a Qt application is running

2019-10-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1847974 ***
https://bugs.launchpad.net/bugs/1847974

This bug is getting a big old. Let's use bug 1847974.

** This bug has been marked a duplicate of bug 1847974
   Qt apps terminate on Power-Off dialog

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

Title:
  Power button shuts down computer if a Qt application is running

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04, the usual behavior of the power button is bringing a
  dialog with options (Lock, Suspend, Restart, Shutdown) and waiting for
  the user's choice.

  When a Qt application is running, for instance Qt Creator or Texmaker,
  (but not VLC, Clementine or Skype) and the power button is pressed, it
  instantly closes that Qt app (http://qt-
  project.org/forums/viewthread/47632/), brings the shut down dialog and
  then shuts down the computer without waiting for the user’s choice.

  I first asked about this on this forum: 
http://qt-project.org/forums/viewthread/53243/#222409
  and reported it at Qt Creator, thinking it was the only application causing 
it, where they told me to report it to Canonical: 
https://bugreports.qt.io/browse/QTCREATORBUG-14030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1426851/+subscriptions

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


[Touch-packages] [Bug 1847974] Re: Qt apps terminate on Power-Off dialog

2019-10-21 Thread Daniel van Vugt
** Summary changed:

- Some apps terminates on Power-Off dialog
+ Qt apps terminate on Power-Off dialog

** Package changed: gnome-shell (Ubuntu) => qtbase-opensource-src
(Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Opinion => Confirmed

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

Title:
  Qt apps terminate on Power-Off dialog

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Calling Power-Off dialog from system menu and then pressing cancel
  button terminates some apps like fbreader and telegram. Tested on
  Ubuntu 18.04 and 19.10.

  Steps to reproduce:
  1. Install fbreader from standard repository (sudo apt install fbreader)
  2. Run fbreader
  3. Press Gnome system menu - power button
  4. Power-Off dialog appeared - press Cancel button

  Expected result: fbreader still running.
  Actual result: fbreader terminated.

  Same issue with Telegram app (possible other Qt apps?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 14 11:35:58 2019
  DisplayManager: lightdm
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (719 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1847974/+subscriptions

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


[Touch-packages] [Bug 1847974] [NEW] Qt apps terminate on Power-Off dialog

2019-10-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Calling Power-Off dialog from system menu and then pressing cancel
button terminates some apps like fbreader and telegram. Tested on Ubuntu
18.04 and 19.10.

Steps to reproduce:
1. Install fbreader from standard repository (sudo apt install fbreader)
2. Run fbreader
3. Press Gnome system menu - power button
4. Power-Off dialog appeared - press Cancel button

Expected result: fbreader still running.
Actual result: fbreader terminated.

Same issue with Telegram app (possible other Qt apps?).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.2
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 11:35:58 2019
DisplayManager: lightdm
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2017-10-24 (719 days ago)

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic eoan
-- 
Qt apps terminate on Power-Off dialog
https://bugs.launchpad.net/bugs/1847974
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

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


[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time

2019-10-21 Thread Timo Aaltonen
verified myself

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

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


[Touch-packages] [Bug 1300367] Re: rsync 3.1.0 and 3.0.9 incompatibility

2019-10-21 Thread Gabriel Staples
*** This bug is a duplicate of bug 1384503 ***
https://bugs.launchpad.net/bugs/1384503

Work-around: just upgrade your rsync versions to ensure they are
*exactly the same* on both the sending and receiving PCs. See my answer
here: https://serverfault.com/questions/883487/unable-to-rsync-due-to-
broken-pipe/988794#988794.

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

Title:
  rsync 3.1.0 and 3.0.9 incompatibility

Status in rsync:
  In Progress
Status in rsync package in Ubuntu:
  Triaged

Bug description:
  When running rsync on a directory of a few hundred files from rsync
  3.0.9-4 on Ubuntu 13.04 Raring to rsync 3.1.0-2 on Ubuntu 14.04 Trusty
  rsync errors with:

  rsync error: error in rsync protocol data stream (code 12) at
  io.c(441) [sender=3.0.9]

  Here is the full command I'm trying to run:

  rsync --delay-updates -FF --compress --timeout=10 --archive --rsh 'ssh
  -o StrictHostKeyChecking=no' --out-format='<>%i %n%L'
  templates/dotfiles/ wirehive@172.2.0.1.128:/home/wirehive/

  If I repeatedly run this after maybe 4 times it will succeed.

  The same sounding bug is reported here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1014769
  and here:
  https://bugzilla.samba.org/show_bug.cgi?id=10332

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

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


[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-10-21 Thread Miroslav Matějů
@dannf Thanks, it works for me from both command line and Qt Creator.

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  New
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

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

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


[Touch-packages] [Bug 1848865] Re: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8

2019-10-21 Thread Sebastien Bacher
Could you report that upstream on
https://gitlab.gnome.org/GNOME/gtk/issues ?

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Spurious "key_press_event" when focus on entry widget using
  LANG=th_TH.UTF-8

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 will emit spurious "key_press_event" if the focus is currently
  on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems
  to disappear if the locale is set to something else (tested with
  C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell
  affects this.

  Step to reproduce:
  1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and 
"libgtk-3-dev" for compiling demo program.
  2. Download & compile the demo program "gtk3-entry-keyboard-event" attached 
in this bug. (The program is licensed under MIT.)
  3. Run the program with LANG=th_TH.UTF-8. The window will contain an input 
box on top and a button on the bottom.
  4. Click in the input box, then press a key on the keyboard. The program will 
print one line for each "key_press_event" delivered to the window, with keyval 
and hardware_keycode.

  Expected result: only a single line is printed. For example for "a":
  "window: 0x0061 0x0026"

  Actual result: 
- With LANG=th_TH.UTF-8, two lines are printed. The first line is the above 
line, while the second line has both values as zero: "window: 00 00"
- If, instead, the locale is LANG=C.UTF-8, the program will print only one 
line as expected.
- If iBus is installed and enabled, then 2 lines are printed with both 
lines containing the same code, no matter which locale it runs under.
- If this same program is run in Gnome-based Ubuntu session, then only one 
line is printed no matter which locale it runs under.

  This program is tested on Fedora and Manjaro with the correct result.
  Thus, this issue is Ubuntu-specific.

  I've tested it on Ubuntu 19.10 with pretty much the same result,
  except the iBus case is now working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 19 18:06:23 2019
  InstallationDate: Installed on 2018-05-03 (533 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1848865/+subscriptions

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


[Touch-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login

2019-10-21 Thread Karl Marks
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

Thanks for responding. Yes, the workaround works to comment out load-
module module-switch-on-connect.

Sorry, I thought I looked at all the bugs tagged with eoan, must have
overlooked it.

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

Title:
  Audio output device changes upon unlock/login

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04.

  
  Locking/Suspending and logging in changes my audio output device.
  This did not happen in 19.04.

  
   How to reproduce 

  When I lock my session with key combination "Win+L" and then unlock it again, 
the sound that's been playing through my headphones/speakers stops playing. 
When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is 
selected.
  When I select "Headphones - Built-in audio", sound continues playing.

  There is no related log output in dmesg.

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

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


[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se

2019-10-21 Thread Daniel van Vugt
Still monitoring for regressions:

https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

Everything looks OK right now. Give it a few more days or a week, then
consider it verified.

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from
  pa_sink_input_finish_move() from pa_sink_move_all_finish() from
  card_set_profile() from pa_card_set_profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Original Report]

  Changing between Logitech G933 digital and analog and Logitech G930
  digital and analog

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 17:20:34 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-02-22 (19 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=sv_SE.UTF-8
   LANGUAGE=sv
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_sink_input_finish_move () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   pa_sink_move_all_finish () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so
   pa_card_set_profile () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X99-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Touch-packages] [Bug 1667943] Re: HP Pavilion x2, kernel 4.10, PCI/internal sound card not detected

2019-10-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1665904 ***
https://bugs.launchpad.net/bugs/1665904

** This bug has been marked a duplicate of bug 1665904
   HP Pavilion x2, PCI/internal sound card not detected

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

Title:
  HP Pavilion x2, kernel 4.10, PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The problem continues !!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.10.0-041000-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Feb 25 18:59:11 2017
  InstallationDate: Installed on 2017-02-17 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd08/29/2016:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.11:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1832008] Re: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all

2019-10-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1832007 ***
https://bugs.launchpad.net/bugs/1832007

** This bug has been marked a duplicate of bug 1832007
   [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at 
all

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

Title:
  [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speaker and headphone jack has no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iksn   1266 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 21:58:35 2019
  InstallationDate: Installed on 2019-06-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iksn   1266 F pulseaudio
  Symptom_Jack: Green Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AFU Ver. F.61
  dmi.board.name: 143D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 64.16
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AFUVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook5220m:pvr:rvnHewlett-Packard:rn143D:rvrKBCVersion64.16:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 5220m
  dmi.product.sku: XN524AV
  dmi.sys.vendor: Hewlett-Packard

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

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


[Touch-packages] [Bug 1778399] Re: No headset detection since kernel update to 4.4.0.128

2019-10-21 Thread Daniel van Vugt
** Tags added: zenial

** Tags removed: zenial
** Tags added: xenial

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

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

Title:
  No headset detection since kernel update to 4.4.0.128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I an running Ubuntu 16.04 x86-64 on an Asus Zenbook with proposed repository 
activated.
  Since the kernel update to 4.4.0.128, headset is not detected anymore. It 
works fine with kernel version 4.4.0.127

  Another change since this update is that the sound parameters dialog
  shows me 3 additional HDMI entries for Output under "Play the sound
  through" (label translated from French) in addition to Speaker
  Internal audio. I do not know if that is linked or not.

  If I start my PC on kernel 4.4.0.127 I see only Speaker Internal audio
  and headset is detected and working when it is plugged-in.

  [...]:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Best regards. JBF

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

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