date:20200124

** Changed in: mawk (Debian)
   Status: New => Confirmed

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

Title:
  mawk 1.3.3-17ubuntu2 incorrectly handles "/" in "[ ]" expressions

Status in mawk package in Ubuntu:
  Confirmed
Status in mawk package in Debian:
  Confirmed

Bug description:
  Binary package hint: mawk

  Description:  Ubuntu 9.04
  Release:  9.04

  Package version:   mawk 1.3.3-13ubuntu1

  
  Whilst attempting to run a shell script to automate the build procedure for 
an embedded platform I came across a parsing error in the mawk installation on 
my Ubuntu 9.04 box.  I followed this up with the script author, and then the 
mawk maintainer, and determined that:

(a).  The behavior of mawk 1.3.3-13ubuntu1 is incorrect
(b).  The incorrect behavior exhibited by mawk 1.3.3-13ubuntu1 is not 
exhibited by the upstream sources mawk-1.3.3-20090920 when built on my Ubuntu 
box

  The error case can be demonstrated using this script fragment:

  
  for interpretter in gawk mawk;
  do
  echo "Running with $interpretter..."
  echo
  echo "diecimila.name=Arduino Diecimila, Duemilanove, or Nano w/ATmega168" | \
  $interpretter -v FS== '{boardname=$2; gsub(/[^a-zA-Z0-9_,./():-]/, "", 
boardname); print boardname }'
  echo
  done

  
  When run using my system's mawk installation I get the following output:

  
  Running with gawk...

  ArduinoDiecimila,Duemilanove,orNanow/ATmega168

  Running with mawk...

  mawk: line 1: regular expression compile failed (bad class -- [], [^] or [)
  [^a-zA-Z0-9_,.
  mawk: line 1: syntax error at or near )
  bash: echo: write error: Broken pipe

  
  When run using the upstream mawk I get the following output:

  
  Running with gawk...

  ArduinoDiecimila,Duemilanove,orNanow/ATmega168

  Running with ./mawk...

  ArduinoDiecimila,Duemilanove,orNanow/ATmega168

  
  For reference, I built the upstream mawk package as follows:

  ./compile && make

  That is, I used whatever defaults the autoconf script picked for my
  system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/490736/+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 1332114] Re: Please update mawk to latest upstream release

** Changed in: mawk (Debian)
   Status: New => Confirmed

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

Title:
  Please update mawk to latest upstream release

Status in mawk package in Ubuntu:
  Triaged
Status in mawk package in Debian:
  Confirmed

Bug description:
  mawk in Ubuntu is 18 years old and very buggy (see
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and
  https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other
  products, like bug #1331381) :(

  Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4-
  upstream releases, see http://invisible-island.net/mawk/CHANGES.html

  Please update mawk to latest upstream release - all the other major
  distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to
  mawk 1.3.4-2014. Five years since the bug  asking to upload new
  mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu
  - sticking to 1.3.3 is now causing headeach to lots of people rather
  than saving from regressions, see for example bug #1005077 :(

  Please, update mawk package before major Ubuntu 16.04 LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+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 1074404] Re: Segfault with mawk

** Changed in: mawk (Debian)
   Status: New => Confirmed

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

Title:
  Segfault with mawk

Status in mawk package in Ubuntu:
  Confirmed
Status in mawk package in Debian:
  Confirmed

Bug description:
  release: ubuntu 12.04.1 LTS
  mawk version: 1.3.3-17
  Got a segfault with: echo "x" | awk "/x/ { print \"(`cat test`)\"; next; } { 
print; }" -

  'test' file attached

  removing a few chars from the test files resolves the issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1074404/+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 1852855] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

2020-01-24 Thread Launchpad Bug Tracker

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 10

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  got error while dpkg command

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Sat Nov 16 19:41:53 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:unattended-upgrades:1.1ubuntu1.18.04.7~16.04.4
   Setting up unattended-upgrades (1.1ubuntu1.18.04.7~16.04.4) ...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2019-03-04 (257 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1852855/+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 1860676] Re: apt-get dist-upgrade -y hangs during e2fsprogs update

2020-01-24 Thread Jonathan Kamens

I can no longer reproduce it either. *shrug*

P.S. Hi Ted long time no see.

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

Title:
  apt-get dist-upgrade -y hangs during e2fsprogs update

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  My recent apt-get dist-upgrade -y hung here:

  ...
  update-initramfs: deferring update (trigger activated)
  e2scrub_all.service is a disabled or a static unit not running, not starting 
it.

  I did a pstree on the apt-get process and saw this:

  apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
  )───systemd-tty-ask(863)

  Relevant processes:

  root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
  root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 
/bin/systemctl restart e2scrub_all.timer e2scrub_reap.service

  I killed the systemd-tty-ask-password-agent process, and it became
  defunct but didn't die. So I killed the systemctl restart process, and
  the upgrade continued, apparently without noticing that the systemctl
  restart failed, which is a separate issue.

  When I ran "sudo systemctl restart e2scrub_all.timer
  e2scrub_reap.service" from the command line after the upgrade, it also
  hung with systemd-tty-ask-password-agent apparently waiting for
  something, so this problem isn't unique to upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: e2fsprogs 1.45.3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 09:37:04 2020
  InstallationDate: Installed on 2019-09-12 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+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 1860676] Re: apt-get dist-upgrade -y hangs during e2fsprogs update

2020-01-24 Thread Theodore Ts'o

Hmm... I can't duplicate this on Debian testing, which is using a newer
version of e2fsprogs (1.45.5-2).  The e2scrub_reap.service file is
identical with Ubuntu's 1.45.3-4ubuntu2.1, though.  And looking at the
service file, I have no idea why systemctl would be trying to paskk for
a password, given that it is running as root.

 {/home/tytso}  
1046% sudo systemctl restart e2scrub_reap.service
[sudo] password for tytso: 
 {/home/tytso}  
1047% sudo systemctl status e2scrub_reap.service
● e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots
 Loaded: loaded (/lib/systemd/system/e2scrub_reap.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) since Fri 2020-01-24 22:20:55 EST; 3s ago
   Docs: man:e2scrub_all(8)
Process: 1106527 ExecStart=/sbin/e2scrub_all -A -r (code=exited, 
status=0/SUCCESS)
   Main PID: 1106527 (code=exited, status=0/SUCCESS)

Jan 24 22:20:55 lambda systemd[1]: Starting Remove Stale Online ext4 Metadata 
Check Snapshots...
Jan 24 22:20:55 lambda systemd[1]: e2scrub_reap.service: Succeeded.
Jan 24 22:20:55 lambda systemd[1]: Started Remove Stale Online ext4 Metadata 
Check Snapshots.

It is true that /sbin/e2scrub_all has changed significantly between
1.45.3 and 1.45.5; but it looked like you never got as far as actually
executing e2scrub_reap.service, and if it did, it shouldn't be calling
systemctl in reap mode.

Does "sudo /sbin/e2scrub_all -A -r" hang for you?

The only other thing which you might try i,  commenting out this line
from /lib/systemd/system/e2scrpb_reap.service, and see if it fixes the
hang:

AmbientCapabilities=CAP_SYS_ADMIN CAP_SYS_RAWIO

If it does, I have no idea why it might be working for me using Debian
testing (which is using systemd 244-3) and why it ight be failing for
you with Ubuntu.   Remember, systemd is your *friend*.  It is the best
init replacement compared to all the others.  All Hail Systemd!  :-/

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

Title:
  apt-get dist-upgrade -y hangs during e2fsprogs update

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  My recent apt-get dist-upgrade -y hung here:

  ...
  update-initramfs: deferring update (trigger activated)
  e2scrub_all.service is a disabled or a static unit not running, not starting 
it.

  I did a pstree on the apt-get process and saw this:

  apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
  )───systemd-tty-ask(863)

  Relevant processes:

  root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
  root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 
/bin/systemctl restart e2scrub_all.timer e2scrub_reap.service

  I killed the systemd-tty-ask-password-agent process, and it became
  defunct but didn't die. So I killed the systemctl restart process, and
  the upgrade continued, apparently without noticing that the systemctl
  restart failed, which is a separate issue.

  When I ran "sudo systemctl restart e2scrub_all.timer
  e2scrub_reap.service" from the command line after the upgrade, it also
  hung with systemd-tty-ask-password-agent apparently waiting for
  something, so this problem isn't unique to upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: e2fsprogs 1.45.3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 09:37:04 2020
  InstallationDate: Installed on 2019-09-12 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+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 1159933] Re: mawk %d maxes out at 0x7FFFFFFF instead of 0xFFFFFFFF

** Changed in: mawk (Debian)
   Status: New => Confirmed

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

Title:
  mawk %d maxes out at 0x7FFF instead of 0x

Status in mawk package in Ubuntu:
  Confirmed
Status in mawk package in Debian:
  Confirmed

Bug description:
  I'm honestly not sure if this is a bug or just an implementation
  decision, but it's different than gawk or original-awk, so I'm
  reporting it.  This caused problems for coreboot which is using awk to
  calculate addresses up at the 0xFFFX range.  We worked around it
  by using %.0f to print the values.

  using the test:
 printf %u 0x | awk '{printf("%.0f %u %d", $1 , $1 , $1  )}'

  mawk:
  4294967295 2147483647 2147483647

  original-awk:
  4294967295 2147483648 4294967295

  gawk:
  4294967295 4294967295 4294967295

  I'm using ubuntu 12.04.02 LTS, and mawk 1.3.3-17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1159933/+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 1860806] Re: Ubuntu 19.04 new ethernet problem

2020-01-24 Thread JamesH

OK I see now. I mistook Ubuntu 19.04 as the next LTS after 18.04. So my choices 
will be:
1. Clean install of 18.04LTS
2. Upgrade to 19.10
3. Upgrade to 20.04 daily (after upgrade to 19.10)

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

Title:
  Ubuntu 19.04 new ethernet problem

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 (64 bit) on OptiPlex-7010
  On every power on I have no wired Ethernet connection or even an icon to 
enable it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1849773] Autopkgtest regression report (poppler/0.80.0-0ubuntu1.1)

All autopkgtests for the newly accepted poppler (0.80.0-0ubuntu1.1) for eoan 
have finished running.
The following regressions have been reported in tests triggered by the package:

kopanocore/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#poppler

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  
/usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

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

Bug description:
  [Impact]
  Selecting text in evince crashes for some files in eoan

  [Test case]

  Open the pdf in bug 1855596 and select some text.

  [Regression potential]
  This adds a check for a null pointer before using the pointer; it's limited 
to a small function checking if a font is glyphless so there is basically no 
risk for regressio

  [Error tracker]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evince.  This problem was most recently seen with package version 3.34.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

** Tags added: champagne

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1860826] [NEW] pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

Public bug reported:

Hello, after upgrading to focal I found the following in my journalctl
output:

Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory


The login package stopped packaging this file:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
and now forcibly removes the file:
https://paste.ubuntu.com/p/myh9cGWrHD/

However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Fri Jan 24 23:35:33 2020
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pam
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  New

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1860762] Re: Upgrade with zfs-on-root failures

My machine did not reboot successfully; because I followed The Guide, my
system has a root password, and I was prompted for it at the systemd
emergency shell. (Which is super-confusing, because I forgot I had set a
password.)

The error message appeared to be along the lines of "bpool failed to
import because it was most recently used on another machine". (This is a
lie; rpool, on the same nvme, didn't say the same thing.)

I was able to proceed again after a 'zpool import -f bpool', reboot, and
then things seemed to work well.

Thanks

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

Title:
  Upgrade with zfs-on-root failures

Status in initramfs-tools package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I followed rlaager's howto for installing Ubuntu 18.04 LTS with ZFS
  root (but used disco). I've also set up sanoid to perform periodic
  snapshots of bpool (which stores /boot).

  The upgrade from disco to eoan didn't go well:

  [.. trimmed to fit in the comment box; more context in attachment ..]

  /ubuntu@autosnap_2020-01-24_04:00:05_frequently
  Found initrd image: initrd.img-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:00:05_frequently
  Found linux image: vmlinuz-5.0.0-39-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.0.0-39-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found linux image: vmlinuz-5.0.0-40-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.0.0-40-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found linux image: vmlinuz-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Adding boot menu entry for EFI firmware configuration
  done
  Processing triggers for dbus (1.12.14-1ubuntu2) ...
  Processing triggers for initramfs-tools (0.133ubuntu10) ...
  update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic
  cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
  cryptsetup: WARNING: Couldn't determine root device
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for shim-signed (1.39+15+1533136590.3beb971-0ubuntu1) ...
  Nothing to do.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1build1) ...
  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Setting up initramfs-tools (0.133ubuntu10) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.133ubuntu10) ...
  update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/initramfs-tools.0.crash'
  cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
  cryptsetup: WARNING: Couldn't determine root device
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade 
  process. 

  To continue please press [ENTER]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.4
  ProcVersionSignature: Ubuntu 5.0.0-40.44-generic 5.0.21
  Uname: Linux 5.0.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CrashDB: ubuntu
  Date: Fri Jan 24 06:02:32 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2020-01-24 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit

[Touch-packages] [Bug 1859013] Autopkgtest regression report (openssh/1:8.0p1-6ubuntu0.1)

All autopkgtests for the newly accepted openssh (1:8.0p1-6ubuntu0.1) for eoan 
have finished running.
The following regressions have been reported in tests triggered by the package:

libnet-scp-perl/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#openssh

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

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

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

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

2020-01-24 Thread tom

It affects disco. Was a fix released?

** Tags added: disco

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

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

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

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

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

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

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

2020-01-24 Thread Jeff Campbell

YEAH!!!

Finally Fixed!!!  I just tested the bluez proposed update and my
headphones connected in A2DP mode the first time (without having to go
through all the tricks of connecting/disconnecting bluetooth, etc, etc).
I did try powering off and on my headphones several times and it
continues to work as expected.

I'm a "good-to-go" for this fix.

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1860806] Re: Ubuntu 19.04 new ethernet problem

2020-01-24 Thread Paul White

Thank you for reporting this bug to Ubuntu.

Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020, (i.e.
yesterday).

You will need to install or upgrade to a supported release of Ubuntu. If
you then find that the problem is still present kindly upload the
debugging logs by running only once in a terminal:

apport-collect 1860806

and then change the status of the bug back to "New".

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

** Tags added: disco

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Ubuntu 19.04 new ethernet problem

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 (64 bit) on OptiPlex-7010
  On every power on I have no wired Ethernet connection or even an icon to 
enable it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1845046] Autopkgtest regression report (bluez/5.50-0ubuntu5)

All autopkgtests for the newly accepted bluez (5.50-0ubuntu5) for eoan have 
finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.20.4-2ubuntu2 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#bluez

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1765477] Re: 5s delay in AAAA dns resolving; artful and earlier is quick

2020-01-24 Thread Alberto Donato

I'm seeing this in eoan, too.

Whenever I try to access a host in my lan, host resolution takes 15s
(tried timing "ping -c 1" and "nslookup"

a "dig " query is immediate, but a "dig  " also takes
15s.

It seems it's trying 3 times, each with a 5s timeout before failing.

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

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765477/+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 1856703] Autopkgtest regression report (pam/1.3.1-5ubuntu1.19.10.1)

All autopkgtests for the newly accepted pam (1.3.1-5ubuntu1.19.10.1) for eoan 
have finished running.
The following regressions have been reported in tests triggered by the package:

openssh/1:8.0p1-6build1 (ppc64el, amd64, s390x, armhf, i386, arm64)
kscreenlocker/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#pam

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
   Return only PAM_IGNORE or error from pam_motd

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

Bug description:
  
  https://github.com/linux-pam/linux-pam/pull/157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1856703/+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 1765477] Re: 5s delay in AAAA dns resolving; artful and earlier is quick

2020-01-24 Thread Alberto Donato

** Tags added: 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/1765477

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765477/+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 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up

2020-01-24 Thread nimish

Came across this issue on a system I'm rebuilding and spun up a VM
running 18.04.3 to test. It seems like I got it working consistently on
every reboot. I'll try and breakdown what I've tried and what worked.
Everyone & Dev's can let me know if they see any issues of setting it up
the way it's working.

First made a backup of the file /etc/systemd/system/sshd.service just in
case even though you could use systemctl revert ssh.service to revert
any changes.

What I've tried:

editing /etc/systemd/system/sshd.service and changing the following
lines from:

After=network.target auditd.service

to:

After=network-online.target
Wants=network-online.target

or to:

Requires=network-online.target
After=network-online.target
Wants=network-online.target

or to:

Requires=network-online.target auditd.service
After=network-online.target auditd.service
Wants=network-online.target auditd.service

or to:

Requires=whoopsie.service
After=whoopsie.service
Wants=whoopsie.service

What I was trying to see is which service I could have ssh start after
seeing as using the various network.service/targets were just not
working or consistent. Using whoopsie.service worked the first time I
rebooted but each reboot after that ssh failed to start.

I tried the following as well:

systemctl edit ssh.service and putting the above variations in that file
and the ssh.service still failed to start.


When looking at:

systemctl show ssh or systemctl show ssh |grep -C 10 "After" to get the
data I wanted to see.

I see the following "Before=" argument which has multi-user.target
included. When you look at what's in /etc/systemd/system/multi-
user.target.wants/ it includes links to ssh.service, networkd-
dispatcher.service, networking.service & NetworkManager.service.

Names=ssh.service
Requires=sysinit.target system.slice -.mount
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=system.slice systemd-journald.socket network.target sysinit.target 
-.mount auditd.service basic.target

>From the above data it looks like ssh.service is set to start before
multi-user.target?

So I set out to change that behavior:

I tried putting the following in systemctl edit ssh.service which did
not work

Requires=multi-user.target
Before=shutdown.target
After=multi-user.target
Wants=multi-user.target

Did systemctl revert ssh.service to revert to the original configs


Then I tried systemctl edit --full ssh.service and put

Requires=multi-user.target
Before=shutdown.target
After=multi-user.target
Wants=multi-user.target

reloaded the daemons systemctl daemon-reload. I don't think it totally
necessary to do this if you're going to reboot anyway but why not, no
harm.

Rebooted multiple times and now ssh starts on every reboot/boot.

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

Title:
  sshd will not start at boot if ListenAddress is set, because network
  interface is not yet up

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: openssh-server

  The sshd will not start at boot if the ListenAddress option in
  /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 .

  I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the 
openssh-server package.
  I would expect that sshd is started after boot but it will not and I found 
this in /var/log/auth.log:

  sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign 
requested address.
  sshd[4527]: fatal: Cannot bind any address.

  Once the System is started you can start/stop the sshd with the
  /etc/init.d/ssh script without any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/216847/+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 1859031] Re: Cursor freezes with synergy software kvm

2020-01-24 Thread Launchpad Bug Tracker

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

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

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

Title:
  Cursor freezes with synergy software kvm

Status in libx11 package in Ubuntu:
  Confirmed

Bug description:
  I'm using the synergy software KVM to share a mouse and keyboard
  between two machines, with my Ubuntu workstation as the client.  When
  attempting to drag-and-drop within Qt apps, the mouse cursor will
  freeze for several seconds.  Cursor freezes also occur intermittently
  as well.  I have an issue report for synergy as well:
  https://github.com/symless/synergy-core/issues/6487

  This issue seems to be a regression related to update
  1.6.4-3ubuntu0.2.  The current workaround is to pin all libx11
  packages to the previous (0.1) versions.

  Release Version: Ubuntu 18.04.3 LTS
  Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libx11-6 2:1.6.4-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.33.01  Wed Nov 13 
00:00:22 UTC 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jan  9 09:13:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP104GLM [Quadro P5200 Mobile] [1028:1832]
  InstallationDate: Installed on 2018-07-30 (527 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Precision 7730
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=6599bc95-d2cf-4bb0-b32d-653b78ae0fe9 ro quiet splash acpi=force 
vt.handoff=1
  SourcePackage: libx11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0MG0JR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7730:pvr:rvnDellInc.:rn0MG0JR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7730
  dmi.product.sku: 0832
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1859031/+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 1860647] Re: block migration, removing unversioned packages

2020-01-24 Thread Matthias Klose

now migrated


** Changed in: python-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  block migration, removing unversioned packages

Status in python-defaults package in Ubuntu:
  Fix Released

Bug description:
  block migration, removing unversioned packages. Make the migration
  explicit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1860647/+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 1860806] [NEW] Ubuntu 19.04 new ethernet problem

2020-01-24 Thread JamesH

Public bug reported:

Ubuntu 19.04 (64 bit) on OptiPlex-7010
On every power on I have no wired Ethernet connection or even an icon to enable 
it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 19.04 new ethernet problem

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04 (64 bit) on OptiPlex-7010
  On every power on I have no wired Ethernet connection or even an icon to 
enable it. After a restart (soft boot) it comes back again. This appears to be 
different from another bug reported which states that the Ethernet cable has to 
be unplugged during power on. In my issue, I can leave the Ethernet cable 
plugged in and it works fine. It just doesn't work during first power on boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860544] Re: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1

2020-01-24 Thread geole0

Me also

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

Title:
  package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade:
  installed uuid-runtime package post-installation script subprocess
  returned error exit status 1

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  during update, the updater sent this message

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: uuid-runtime 2.34-0.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Jan 22 13:12:14 2020
  ErrorMessage: installed uuid-runtime package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-06-01 (964 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: util-linux
  Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: 
installed uuid-runtime package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (91 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1860544/+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 1859013] Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted openssh into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.6p1-4ubuntu0.4 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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: openssh (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1859013] Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted openssh into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.2p2-4ubuntu2.9 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

focal has -5 now

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

** Changed in: openssh (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1859013] Please test proposed package

Hello Dimitri, or anyone else affected,

Accepted openssh into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.0p1-6ubuntu0.1 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.

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

disco is EOL

** Changed in: openssh (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: openssh (Ubuntu Eoan)
   Status: New => 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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1859013

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1845046] Please test proposed package

Hello Nicholas, or anyone else affected,

Accepted bluez into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.3
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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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.

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

Hello Nicholas, or anyone else affected,

Accepted bluez into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.50-0ubuntu5 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.

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

** Tags added: verification-needed-bionic

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

2020-01-24 Thread Sean Feole

** Tags added: sru-20200106

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

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-01-24 Thread Paul Collinsworth

There seems to be some sort of problem with nouveau, too. Or it may just 
be a hardware issue.

On 1/24/20 2:54 AM, Timo Aaltonen wrote:
> don't try to install 304, it doesn't support the xserver in 18.04 which
> was one of the reasons it got dropped
>

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1856703] Re: Return only PAM_IGNORE or error from pam_motd

Hello Balint, or anyone else affected,

Accepted pam into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pam/1.3.1-5ubuntu1.19.10.1 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: pam (Ubuntu Eoan)
   Status: New => 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 pam in Ubuntu.
https://bugs.launchpad.net/bugs/1856703

Title:
   Return only PAM_IGNORE or error from pam_motd

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

Bug description:
  
  https://github.com/linux-pam/linux-pam/pull/157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1856703/+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 756317] Re: Captive portals may corrupt apt translation indices

2020-01-24 Thread Patrick Wigmore

Unfortunately, I cannot reproduce the bug by deliberately running apt
update while the captive portal is in effect.

I think I must have hit some obscure edge case that isn't covered by the
existing fix. Maybe something to do with switching networks during an
automatic update? Who knows. Clearly I haven't got enough information to
resolve this.

Unfortunately I did not retain a copy of the files I removed, so they
cannot be analysed, though I have saved a copy of the current captive
portal page if anyone wants me to upload it. (It might differ from the
one that triggered the bug for me though.)

Apologies for double comment.

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

Title:
  Captive portals may corrupt apt translation indices

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

Bug description:
  I have an adsl modem which returns an html page if the adsl link is
  broken. This page ends as the content of the apt cache files stored in
  /var/lib/apt/lists, which breaks apt.

  The only way to make apt work again is to delete all the files stored
  in /var/lib/apt/lists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/756317/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

Hello errors.ubuntu.com, or anyone else affected,

Accepted poppler into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/poppler/0.80.0-0ubuntu1.1 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: poppler (Ubuntu Eoan)
   Status: In Progress => 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 poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1849773

Title:
  
/usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

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

Bug description:
  [Impact]
  Selecting text in evince crashes for some files in eoan

  [Test case]

  Open the pdf in bug 1855596 and select some text.

  [Regression potential]
  This adds a check for a null pointer before using the pointer; it's limited 
to a small function checking if a font is glyphless so there is basically no 
risk for regressio

  [Error tracker]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evince.  This problem was most recently seen with package version 3.34.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1860647] Re: block migration, removing unversioned packages

2020-01-24 Thread Matthias Klose

unblocked

** Tags removed: block-proposed

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

Title:
  block migration, removing unversioned packages

Status in python-defaults package in Ubuntu:
  New

Bug description:
  block migration, removing unversioned packages. Make the migration
  explicit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1860647/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-01-24 Thread Paul Collinsworth

Perhaps I should just get a new GPU card. Or a new system.

In the meantime, at boot this morning, the first thing I tried to do 
after log-in was to access "Settings"; no response. After a few minutes 
of 'nothing happening', I clicked the e-mail ("Thunderbird") icon; no 
response there, as well. Went to the shutdown/restart panel (the 
pull-down at the upper right), clicked "Restart", the system reported 
that there was no response from "Thunderbird", switched to an 
unpopulated version (no desktop icons or tool bars) of my screen 
background image (with none of the corrupting artifact) and stalled.

Pushed the "big red reset" button (power), let it sit for a minute or 
two, booted, and after log-in, went straight to e-mail, which behaved 
more-or-less normally, accessed the 'net (no particular loss of browser 
functionality), and here I am.

Nvidia 304 is a familiar number. I had to re-install that thing several 
years ago; seems to me that it was pre-16.04, in fact. Took more than 
one iteration of the install process to get it functioning properly; 
recollection is that there was some issue with the digital video output. 
I did have to switch to the VGA output on the board a couple of years 
ago. Something finally got permanently hosed on the digital interface 
side, and that may be the root cause now - some sort of problem in the 
VGA interface.

On 1/24/20 12:46 AM, Daniel van Vugt wrote:
> Just checked the Nvidia web site and they recommend proprietary driver
> version 304 for your GPU (which also implies versions after 304 won't
> support it). It appears the reason why Software & Updates told you "No
> Additional Drivers Available" is because that's also older than any
> Nvidia shipped with Ubuntu 18.04.
>
> As a next step I would recommend you get the driver that Nvidia
> themselves recommend and manually install that:
> https://www.nvidia.com/Download/driverResults.aspx/123709/en-us
>
> Annoyingly, Ubuntu 16.04 does offer Nvidia driver version 304 but that
> Ubuntu release is older and did not ship with a version of Gnome Shell
> that we support.
>

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel:

[Touch-packages] [Bug 1308261]

2020-01-24 Thread Cvs-commit

The master branch has been updated by Jason Merrill :

https://gcc.gnu.org/g:ad09440a09597c34e0b93498aad9d6ef0b8ca9ae

commit r10-6121-gad09440a09597c34e0b93498aad9d6ef0b8ca9ae
Author: Jason Merrill 
Date:   Tue Jan 21 14:21:49 2020 -0500

PR c++/60855 - ICE with sizeof VLA capture.

For normal captures we usually look through them within unevaluated context,
but that doesn't work here; trying to take the sizeof of the array in the
enclosing scope tries and fails to evaluate a SAVE_EXPR from the enclosing
scope.

* lambda.c (is_lambda_ignored_entity): Don't look past VLA capture.

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

Title:
  ICE provoked by a lambda using the sizeof a captured stack-allocated
  array

Status in gcc:
  Fix Released
Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed

Bug description:
  See upstream report,
  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.

  $ cat gcc-bug.cpp
  int main() {
  unsigned count = 5;
  bool array[count];
  [] () {
array[0] = sizeof(array) > 5;
  }();
  return 0;
  }

  $ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp 
  gcc-bug.cpp: In lambda function:
  gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this 
function [-Wuninitialized]
   }();
   ^
  gcc-bug.cpp:3:21: note: ‘’ was declared here
   bool array[count];
   ^
  gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at 
expr.c:9363
   }();
   ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to 
your bugreport.

  $ g++ -v
  Using built-in specs.
  COLLECT_GCC=g++
  COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
  Target: x86_64-linux-gnu
  Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
  Thread model: posix
  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) 

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy gcc-4.8
  gcc-4.8:
Installed: 4.8.1-10ubuntu9
Candidate: 4.8.1-10ubuntu9
Version table:
   *** 4.8.1-10ubuntu9 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.8.1-10ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

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

2020-01-24 Thread Jason-gcc

*** Bug 86432 has been marked as a duplicate of this bug. ***

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

Title:
  ICE provoked by a lambda using the sizeof a captured stack-allocated
  array

Status in gcc:
  Fix Released
Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed

Bug description:
  See upstream report,
  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.

  $ cat gcc-bug.cpp
  int main() {
  unsigned count = 5;
  bool array[count];
  [] () {
array[0] = sizeof(array) > 5;
  }();
  return 0;
  }

  $ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp 
  gcc-bug.cpp: In lambda function:
  gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this 
function [-Wuninitialized]
   }();
   ^
  gcc-bug.cpp:3:21: note: ‘’ was declared here
   bool array[count];
   ^
  gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at 
expr.c:9363
   }();
   ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to 
your bugreport.

  $ g++ -v
  Using built-in specs.
  COLLECT_GCC=g++
  COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
  Target: x86_64-linux-gnu
  Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
  Thread model: posix
  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) 

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy gcc-4.8
  gcc-4.8:
Installed: 4.8.1-10ubuntu9
Candidate: 4.8.1-10ubuntu9
Version table:
   *** 4.8.1-10ubuntu9 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.8.1-10ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

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

2020-01-24 Thread Jason-gcc

Fixed for GCC 10.

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

Title:
  ICE provoked by a lambda using the sizeof a captured stack-allocated
  array

Status in gcc:
  Fix Released
Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed

Bug description:
  See upstream report,
  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.

  $ cat gcc-bug.cpp
  int main() {
  unsigned count = 5;
  bool array[count];
  [] () {
array[0] = sizeof(array) > 5;
  }();
  return 0;
  }

  $ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp 
  gcc-bug.cpp: In lambda function:
  gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this 
function [-Wuninitialized]
   }();
   ^
  gcc-bug.cpp:3:21: note: ‘’ was declared here
   bool array[count];
   ^
  gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at 
expr.c:9363
   }();
   ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to 
your bugreport.

  $ g++ -v
  Using built-in specs.
  COLLECT_GCC=g++
  COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
  Target: x86_64-linux-gnu
  Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
  Thread model: posix
  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) 

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy gcc-4.8
  gcc-4.8:
Installed: 4.8.1-10ubuntu9
Candidate: 4.8.1-10ubuntu9
Version table:
   *** 4.8.1-10ubuntu9 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.8.1-10ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1308261/+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 1308261] Re: ICE provoked by a lambda using the sizeof a captured stack-allocated array

** Changed in: gcc
   Status: Confirmed => Fix Released

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

Title:
  ICE provoked by a lambda using the sizeof a captured stack-allocated
  array

Status in gcc:
  Fix Released
Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed

Bug description:
  See upstream report,
  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.

  $ cat gcc-bug.cpp
  int main() {
  unsigned count = 5;
  bool array[count];
  [] () {
array[0] = sizeof(array) > 5;
  }();
  return 0;
  }

  $ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp 
  gcc-bug.cpp: In lambda function:
  gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this 
function [-Wuninitialized]
   }();
   ^
  gcc-bug.cpp:3:21: note: ‘’ was declared here
   bool array[count];
   ^
  gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at 
expr.c:9363
   }();
   ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to 
your bugreport.

  $ g++ -v
  Using built-in specs.
  COLLECT_GCC=g++
  COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
  Target: x86_64-linux-gnu
  Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
  Thread model: posix
  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) 

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy gcc-4.8
  gcc-4.8:
Installed: 4.8.1-10ubuntu9
Candidate: 4.8.1-10ubuntu9
Version table:
   *** 4.8.1-10ubuntu9 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.8.1-10ubuntu8 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1308261/+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 756317] Re: Captive portals may corrupt apt translation indices

2020-01-24 Thread Patrick Wigmore

I believe I have just experienced this bug in xenial with apt 1.2.32.
Files in /var/lib/apt/lists contained HTML from a captive portal, breaking apt 
until they were removed.

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

Title:
  Captive portals may corrupt apt translation indices

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

Bug description:
  I have an adsl modem which returns an html page if the adsl link is
  broken. This page ends as the content of the apt cache files stored in
  /var/lib/apt/lists, which breaks apt.

  The only way to make apt work again is to delete all the files stored
  in /var/lib/apt/lists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/756317/+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 1607845] Re: List of versioned kernels is not right for Ubuntu

2020-01-24 Thread Balint Reczey

Adding unattended-upgrades because it may remove kernel packages
accidentally and also it has autopkgtest to look for missed kernel
packages which is now failing.

** Tags added: update-excuse

** Also affects: unattended-upgrades (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/1607845

Title:
  List of versioned kernels is not right for Ubuntu

Status in apt package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The following command outputs the list:
  $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages'
  linux-image
  linux-headers
  linux-image-extra
  linux-signed-image
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel
  linux-backports-modules-.*
  linux-tools

  but the list does not 'contain linux-.*-tools' and 'linux-goldfish-
  headers', which are versioned kernel packages as well, if I have
  understood correctly.

  On the other hand are these values appropriate for Ubuntu?
  kfreebsd-image
  kfreebsd-headers
  gnumach-image
  .*-modules
  .*-kernel

  Same thing for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 29 18:55:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (250 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1607845/+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 1860683] Re: initramfs hang after today's updates

2020-01-24 Thread DLCBurggraaff

Closed as "user error" => "invalid"

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

Title:
  initramfs hang after today's updates

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 18.04.3 updated yesterday (Jan 22, 2020).
  Today's (Jan 23, 2020) updates cause initramfs to hang.
  Luckily I can restore my Jan 19, 2020 backup.
  I assume the ext{2,3,4} updates to be the culprit.
  Anyone else having this problem?
  :D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1860683/+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 1860683] Re: initramfs hang after today's updates

2020-01-24 Thread DLCBurggraaff

It definitely is the initramfs. After successfully mounting the root
filesystem (sda10) the following messages are displayed:

-- /scripts/init-bottom/udev: line 25: nuke: not found
-- done.
-- init: line 303: run-init: not found
-- Target filesystem does not have requested /sbin/init.
-- init: line 303: run-init: not found (5*)
-- No init found. Try passing init= bootarg.

Yesterday's ext?fs updates triggered an initramfs rebuild. After restoring my 
backup I reran those updates and had a good look at the initramfs rebuild 
messages. I saw a complaint about a missing /lib/klibc-*.so file. And indeed 
that file is missing.
I copied the /lib/klibc-wBFLvVtxy4xJqEadIBJMa78iJz8.so from an other Xubuntu 
installation and reran things: *problem resolved*.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  initramfs hang after today's updates

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 18.04.3 updated yesterday (Jan 22, 2020).
  Today's (Jan 23, 2020) updates cause initramfs to hang.
  Luckily I can restore my Jan 19, 2020 backup.
  I assume the ext{2,3,4} updates to be the culprit.
  Anyone else having this problem?
  :D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1860683/+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 1859963] Re: Info package on Ubuntu Focal comes preinstalled with desktop file

2020-01-24 Thread Sebastien Bacher

Seems like it would better if Debian reverted that change but meanwhile that 
will resolve the issue in our default sessions
https://launchpad.net/ubuntu/+source/ubuntu-settings/20.04.3

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

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  Info package on Ubuntu Focal comes preinstalled with desktop file

Status in One Hundred Papercuts:
  New
Status in texinfo package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The "info" package that is preinstalled on Ubuntu Focal ships with a
  "info.desktop" file that adds a "TeXInfo" desktop launcher displayed
  among other apps. The launcher opens a terminal application that is
  confusing and user unfriendly for many users. Users that actually want
  to use info can do it using a terminal. Please, consider removing the
  desktop file or at least set it to not show among other apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1859963/+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 1860683] Re: initramfs hang after today's updates

2020-01-24 Thread DLCBurggraaff

** Package changed: ubuntu => initramfs-tools (Ubuntu)

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

Title:
  initramfs hang after today's updates

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Xubuntu 18.04.3 updated yesterday (Jan 22, 2020).
  Today's (Jan 23, 2020) updates cause initramfs to hang.
  Luckily I can restore my Jan 19, 2020 backup.
  I assume the ext{2,3,4} updates to be the culprit.
  Anyone else having this problem?
  :D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1860683/+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 1860683] [NEW] initramfs hang after today's updates

2020-01-24 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Xubuntu 18.04.3 updated yesterday (Jan 22, 2020).
Today's (Jan 23, 2020) updates cause initramfs to hang.
Luckily I can restore my Jan 19, 2020 backup.
I assume the ext{2,3,4} updates to be the culprit.
Anyone else having this problem?
:D

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
initramfs hang after today's updates
https://bugs.launchpad.net/bugs/1860683
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools 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 1860770] Re: GDM fails to start at boot after removing LightDM

2020-01-24 Thread Chris Halse Rogers

debian/lightdm.prerm quite obviously attempts to remove itself from the
display manager set.

Also, “remove this non-default package and your system stops booting¹”
is a terrible experience.

¹: from an end-user perspective, booting to a black screen is the same
as not booting.

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

Title:
  GDM fails to start at boot after removing LightDM

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I removed LightDM on the 14th and then didn't reboot until after
  upgrading to Focal. The next reboot didn't launch a display manager at
  all, and we tracked this down to /etc/systemd/system/display-
  manager.service still pointing to lightdm.service. This is probably a
  bug in lightdm {pre,post}rm?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:18:25 2020
  InstallationDate: Installed on 2019-08-29 (148 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1849859] Re: smb printing fails

2020-01-24 Thread Mario

My machine also seems to be affected by this bug on Ubuntu 19.10. I filed some 
information here if it is of any help:
https://askubuntu.com/questions/1205208/how-to-fix-failing-connection-to-samba-print-share-ubuntu-19-10/1205397#1205397

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1860770] Re: GDM fails to start at boot after removing LightDM

2020-01-24 Thread Gunnar Hjalmarsson

On 2020-01-24 12:56, Chris Halse Rogers wrote:
> uninstalling lightdm should have done this automatically.

Can you point at some spot in the documentation where the behavior you
claim is correct has been documented? (If not, this may be considered a
feature request - importance "wishlist".)

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

Title:
  GDM fails to start at boot after removing LightDM

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I removed LightDM on the 14th and then didn't reboot until after
  upgrading to Focal. The next reboot didn't launch a display manager at
  all, and we tracked this down to /etc/systemd/system/display-
  manager.service still pointing to lightdm.service. This is probably a
  bug in lightdm {pre,post}rm?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:18:25 2020
  InstallationDate: Installed on 2019-08-29 (148 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1860770] Re: GDM fails to start at boot after removing LightDM

2020-01-24 Thread Chris Halse Rogers

I do not recall, but uninstalling lightdm should have done this
automatically.

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

Title:
  GDM fails to start at boot after removing LightDM

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I removed LightDM on the 14th and then didn't reboot until after
  upgrading to Focal. The next reboot didn't launch a display manager at
  all, and we tracked this down to /etc/systemd/system/display-
  manager.service still pointing to lightdm.service. This is probably a
  bug in lightdm {pre,post}rm?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:18:25 2020
  InstallationDate: Installed on 2019-08-29 (148 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1860770] Re: GDM fails to start at boot after removing LightDM

2020-01-24 Thread Gunnar Hjalmarsson

Did you forget to make gdm the default DM?

sudo dpkg-reconfigure gdm3

If you did, this does not sound as a bug to me.

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

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

Title:
  GDM fails to start at boot after removing LightDM

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I removed LightDM on the 14th and then didn't reboot until after
  upgrading to Focal. The next reboot didn't launch a display manager at
  all, and we tracked this down to /etc/systemd/system/display-
  manager.service still pointing to lightdm.service. This is probably a
  bug in lightdm {pre,post}rm?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:18:25 2020
  InstallationDate: Installed on 2019-08-29 (148 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2020-01-24 Thread Marek

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

Same with me, problem showed up after upgrading from 19.04 version.

Uncommenting lines mentioned in #13 did not work for me (ASUS UX301L).

Extremely annoying.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1475968] Re: match function hangs

2020-01-24 Thread Jarno Suni

mawk '{print match($0,/a*/)}' 
works, but
mawk '{print match($0,/a**/)}'
does not

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

Title:
  match function hangs

Status in mawk package in Ubuntu:
  New

Bug description:
  Testcase:
  mawk '{print match($0,/(a*)*/)}'
  hangs with any input. I expect it to print an integer number for each line in 
input and exit thereafter.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mawk 1.3.3-17ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-57.95-lowlatency 3.13.11-ckt21
  Uname: Linux 3.13.0-57-lowlatency x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul 19 12:00:02 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.6
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.6
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (301 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1475968/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

2020-01-24 Thread Dan Streetman

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

** Description changed:

+ Note: this bug touches on multiple packages:
+ - autopkgtest-cloud: merge request open to install 'modules-extra' package
+ - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
+ - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel
+ 
+ [SRU template for systemd]
+ 
  [impact]
  
  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*' deb
  which isn't installed by default, so the test always fails when doing a
  reverse-dep autopkgtest using such a kernel's meta pkg.
  
  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to load
  the scsi_debug module and the test should be skipped.
  
  [test case]
  
  run the 'storage' autopkgtest with a custom kernel that doesn't provide
  the scsi_debug module in the standard linux-modules deb, or check the
  autopkgtest.u.c history, for example:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
  
  [regression potential]
  
  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to install
  the proper linux-* debs.
  
  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid problems
  due to skipping the test.
  
  [scope]
  
  systemd in all releases needs to have its 'storage' test updated

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in linux-kvm source package in Disco:
  New
Status in systemd source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Note: this bug touches on multiple packages:
  - autopkgtest-cloud: merge request open to install 'modules-extra' package
  - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
  - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel

  [SRU template for systemd]

  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to
  install the proper linux-* debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

  [scope]

  systemd in all releases needs to have its 'storage' test updated

To manage notifications about this bug go

[Touch-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

2020-01-24 Thread Tobias Kuhn

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

It doesn't seem to me that this is really a duplicate of bug #1849859.
At least the reported symptoms are not identical.

In any case, has anybody found a workaround for this?

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  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.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1725306] Re: gnome-shell crashed with SIGSEGV in llvm_pipeline_generic() from llvm_middle_end_linear_run()

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

Title:
  gnome-shell crashed with SIGSEGV in llvm_pipeline_generic() from
  llvm_middle_end_linear_run()

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 17.10 updated from 17.04. System stuck in a loop on boot (after
  Ubuntu logo appears).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 16:18:48 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-09-19 (761 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x9586f257:movd   0x8(%ecx,%eax,1),%xmm3
   PC (0x9586f257) ok
   source "0x8(%ecx,%eax,1)" (0x0008) not located in a known VMA region 
(needed readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725306/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

** Tags removed: disco

** Tags removed: artful

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/gnome-shell/+bug/1727908/+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 1768609] Re: can't add KDE apps to GNOME dock

** Tags removed: disco

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

Title:
  can't add KDE apps to GNOME dock

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I clean installed Ubuntu 18.04 yesterday and noticed I couldn't add
  KDE apps to the GNOME dock. Basically, the "Add to Favorites" option
  is missing from the right-click menu of dock icons of currently-
  running KDE apps.

  If I search for a KDE app using the "Show Applications" button, and
  right-click on an app in the search results before running it, that
  menu does contain "Add to Favorites". However, if this is used, the
  added app behaves incorrectly, in that clicking on its icon in the
  dock always launches a new instance rather than bringing any existing
  instance to the front.

  Previously I used Ubuntu 14.04 (with Unity) and KDE apps could be
  added to the dock and managed as expected (i.e. clicking app icon when
  app is running brought it to the front).

  Some searching around suggests this might be related to missing
  StartWMClass fields in the .desktop files of the KDE apps. I added
  StartWMClass=kate to /usr/share/applications/org.kde.kate.desktop and
  that seemed to fix the problem. However this didn't work for Konsole,
  so there might be more to fixing this in general.

  I think this is probably either a KDE bug (they need to correct all
  their .desktop files?), a GNOME bug, or at the very least an Ubuntu-
  level regression in the Unity->GNOME transition that may justify
  taking action somewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768609/+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 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

don't try to install 304, it doesn't support the xserver in 18.04 which
was one of the reasons it got dropped

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

Title:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  My desktop has both it's usual items in place; toolbar on left and
  desktop icons distributed around the screen. Then there's what appears
  to be a bunch of scan line, raster line artifacts, in red, laid over
  my normal background, which is a star field photo on what is
  ordinarily a black field.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 21 13:04:20 2020
  DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
  InstallationDate: Installed on 2016-08-19 (1249 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 531
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
  dmi.bios.date: 11/09/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0RY206
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
  dmi.product.name: Inspiron 531
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct  3 10:41:28 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputLogitech USB Trackball MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+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 1738676] Re: With natural scrolling, horizontal sliders behave backwards

** Tags removed: disco

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1738676/+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 1860764] Re: problem after pulseaudio updating

2020-01-24 Thread Robert

after sleeping i can only one device 
hdmi .. and don't see Line out  Family 17...

** Attachment added: "Screenshot from 2020-01-24 12-41-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860764/+attachment/5322585/+files/Screenshot%20from%202020-01-24%2012-41-41.png

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

Title:
  problem after pulseaudio updating

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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/pulseaudio/+bug/1860764/+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 1583840] Re: pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer()

** Tags removed: disco

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

Title:
  pulseaudio crashed with SIGSEGV in avahi_client_get_state() from
  publish_service() from once_callback() from dispatch_defer()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e533a6f758cf595e0b31c717374dfed1acf6b2e9
  https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090

  ---
  Not sure error report popped up on reboot of system...

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
  Uname: Linux 4.4.0-23-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johndoe3047 F pulseaudio
    johndoe3120 F panel-6-mixer
  CurrentDesktop: XFCE
  Date: Thu May 19 18:39:25 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-03-04 (76 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   avahi_client_get_state () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/pulse-8.0/modules/module-zeroconf-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax kismet lpadmin plugdev 
pulse-access sambashare sudo video
  dmi.bios.date: 11/28/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583840/+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 1690026] Re: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_inf

** Tags removed: disco

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

Title:
  pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2()
  from convert_to_work_format() from pa_resampler_run() from
  pa_sink_input_peek() from fill_mix_info()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/09eaa7a762edd70e8a3d904cb32f366b3c3211a1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690026/+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 1821904] Re: Sound is muted by default after upgrading 18.04->18.10->19.04

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Sound is muted by default after upgrading 18.04->18.10->19.04

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+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 1631161] Re: Preferred output device is not remembered between logins

2020-01-24 Thread Robert

it seams like the proper device disappears

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

Title:
  Preferred output device is not remembered between logins

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I reboot anew, pulseaudio has forgotten the correct audio
  port which I have set using the kde pulseaudio tool.

  I use line out, but it defaults to headphones, which is incorrect for
  my current setup. I expect it to remember that I wanted line out every
  time.

  Once selected, everything runs fine for that session, but it doesn't
  get saved and defaults back to the wrong output every time.

  Guessing this is pulseaudio as it happens with the gnome tool also.

  Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04).

  Policy installed: 1:8.0-0ubuntu3

  Cheers
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   kvd1577 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kvd1577 F...m pulseaudio
   /dev/snd/controlC0:  kvd1577 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18
  InstallationDate: Installed on 2016-10-02 (5 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags: sarah third-party-packages
  Uname: Linux 4.4.0-38-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5f
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

** Tags removed: disco

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

Title:
  pulseaudio crashed during playback with SIGABRT in set_nonblock() from
  pa_make_fd_nonblock() from setup_stream() [bluez] from
  setup_transport_and_stream() [bluez]

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c
  https://errors.ubuntu.com/problem/36464ddf744c449f1480d3ec1746fa2ac4473f8d
  https://errors.ubuntu.com/problem/0c7f70ee57533aee145dad48aa05487de7da808d

  ---

  Pulseaudio crashed randomly while watching a YouTube video in
  fullscreen. When crashing the last 1 second or so of audio looped for
  a few seconds, then cut out. I am using PulseEffects as well, which
  crashed around the same time. Whether that was the cause or a result
  of the PulseAudio crash is unclear.

  I am using Bionic because the video drivers for my AMD Raven Ridge
  iGPU are not supported by earlier versions.

  ~ $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  ~ $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:11.1-1ubuntu7
    Candidate: 1:11.1-1ubuntu7
    Version table:
   *** 1:11.1-1ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ben3375 F pulseaudio
   /dev/snd/controlC0:  ben3375 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Apr  2 19:23:48 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2018-03-25 (8 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/pulse-11.1/modules/module-bluez5-device.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-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.:bvrF10:bd12/01/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1760729/+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 1836396] Re: Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Ubuntu 19.04 Bluetooth KaiOS phone file transfer issues

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu 19.04 on a Dell Inspiron Laptop that has Bluetooth
  enabled (visible, discoverable). Just bought a Tracfone MyFlip which
  uses KaiOS. Ideally, I should be able to transfer files back & forth.
  In fact, if a "send" a file from laptop to phone, I have no issues and
  the file appears. Means Bluetooth is more or less working ... devices
  are paired and some functionality.

  But if I try to send a file from phone to laptop - that does not work.
  There are messages on my phone, first: "File Transfer is Ready to
  Start". Then about 2 seconds latter: "File Transfer Fail." FYI: on
  KaiOS, via Files App... "Share" via "Bluetooth" and comes up with a
  list of paired devices, where my laptop is identified correctly.

  With laptop-->phone, phone bluetooth app displays messages and asks if OK to 
receive file.
  With phone-->laptop, no messages, nothing happens.

  Been knocking my head on this for two days now without resolution, so
  reaching out to community for help. Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836396/+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 1731699] Re: Unable to transfer files via bluetooth to paired android phone

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Unable to transfer files via bluetooth to paired android phone

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from
  Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's
  pairing in a way which permits file transfers. When I pair, my phone
  gives me a checkbox "Allow xx to access your contacts and call
  history", but there is no option to allow file transfers.

  Then, when I attempt to transfer a file via Bluetooth from Ubuntu the
  transfer fails and I get the message "There was an error". My phone
  doesn't seem to recognise there's been any attempt to send a file.

  Discussed at https://ubuntuforums.org/showthread.php?t=2377286

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+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 1843819] Re: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @
  0% where pulse volume @ 50%

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  When the volume is set to around 50% in PulseAudio (using the Ubuntu
  Sound preferences screen but cross-checked by simply viewing with
  pavucontrol) the alsamixer volume is set to 0%. I can see the volume
  rise quickly as the volume is raised past 50% in the Sound preferences
  screen.

  This occurs at least for the Logitech H600 USB device:
  Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset]

  The other audio devices behave "correctly" where 0% is silent and 100%
  is maximum volume.

  This confused me because the volume was set to 50% (I'll frequently
  reset headset volume to 30-50% to protect my ears) and thought audio
  was broken at first because I wasn't getting any sound at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1831074] Re: [JBL tune 160BT] In high fidelity playback, front right side of headset doesn't work

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [JBL tune 160BT] In high fidelity playback, front right side of
  headset  doesn't work

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  If i connect my jbl tune 160BT headset,then on high fidelity playback
  configuration right side of headset doesn't produce any sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 29 18:10:40 2019
  InstallationDate: Installed on 2019-05-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5577
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=84cfd91b-b197-4dea-8ed6-fe6f7cf2aade ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0MVD5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd08/16/2018:svnDellInc.:pnInspiron5577:pvr1.1.1:rvnDellInc.:rn0MVD5F:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 1.1.1
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: AC:ED:5C:49:18:75  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1391391 acl:103 sco:26301 events:5764 errors:0
TX bytes:4356927 acl:4943 sco:26284 commands:703 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831074/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

** Tags removed: disco

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1836809] Re: segfault when CCD are present in two different HOG services

** Changed in: bluez (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  segfault when CCD are present in two different HOG services

Status in Bluez Utilities:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hello everyone,

  We are currently developing a device that contains two HID services.
  That device, as it is right now, is properly functioning on Windows & Android.
  However, when pairing the device on Linux running bluez 5.50 we do get 
segfaults (see attached files).
  Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt 
services and 1 device information service.
  With trial and error, we managed to find that we wouldn't get any crash as 
long as only 1 HOG service was present.

  Here's the interesting part. The two HOG services are made as follows:
  - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / 
boot INPUT + OUTPUT / HID information / HID Control point
  - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID 
information / HID control point

  Looking at the write_ccc in the call stacks we wondered if the
  callbacks subscribing to notifications for the INPUT reports were
  causing this issue.

  We therefore changed the raw HID over gatt (and its report map) to
  remove the INPUT report and change it into 1 OUTPUT report (leading to
  2 OUTPUT reports): no crash.

  We therefore hypothesize that the segfault occurs when subscribing to
  notification on a second HOG service...

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1836809/+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 1631161] Re: Preferred output device is not remembered between logins

2020-01-24 Thread Robert

i added info log when i couldn't choose proper sound device after waking up to 
this thread https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860764
couldn't choose - it means i couldn't choose in settings->sounds

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

Title:
  Preferred output device is not remembered between logins

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I reboot anew, pulseaudio has forgotten the correct audio
  port which I have set using the kde pulseaudio tool.

  I use line out, but it defaults to headphones, which is incorrect for
  my current setup. I expect it to remember that I wanted line out every
  time.

  Once selected, everything runs fine for that session, but it doesn't
  get saved and defaults back to the wrong output every time.

  Guessing this is pulseaudio as it happens with the gnome tool also.

  Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04).

  Policy installed: 1:8.0-0ubuntu3

  Cheers
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   kvd1577 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kvd1577 F...m pulseaudio
   /dev/snd/controlC0:  kvd1577 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18
  InstallationDate: Installed on 2016-10-02 (5 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags: sarah third-party-packages
  Uname: Linux 4.4.0-38-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5f
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1 [Failed to restart bluetooth.service: Unit -.mount is
  masked.]

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  made upgrade using update-manager

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct  8 09:52:47 2019
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-05-18 (142 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 
rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" 
acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1.1
   apt  1.8.3
  SourcePackage: bluez
  Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14A1IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14A1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: GS40 6QE Phantom
  dmi.product.sku: Default string
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:0A:FA:40  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:775 acl:0 sco:0 events:59 errors:0
TX bytes:3668 acl:0 sco:0 commands:59 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1847201/+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 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device

** Tags removed: disco

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

Title:
  Default audio device changes on reboot; audio still outputs using my
  previously-selected device

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build.
  It was not present in Ubuntu 16.04.

  I have a USB microphone which also appears to pulse as a speaker.
  Pulse keeps picking it as the default audio device. I can switch audio
  devices to my analog line out, which works as expected until I reboot.

  After reboot, my audio device switches back to the USB "speaker", and
  Gnome shell / Gnome settings volume control adjusts the USB speaker
  volume. Despite  seeing the USB device as the current output device, I
  still hear sound from my line-out.

  In the interest of narrowing down this bug, I have found that
  disabling "module-switch-on-connect" fixes the problem (my line-out
  stays as the default audio device and I hear sound).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  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.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A: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/pulseaudio/+bug/1838577/+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 1860770] [NEW] GDM fails to start at boot after removing LightDM

2020-01-24 Thread Chris Halse Rogers

Public bug reported:

I removed LightDM on the 14th and then didn't reboot until after
upgrading to Focal. The next reboot didn't launch a display manager at
all, and we tracked this down to /etc/systemd/system/display-
manager.service still pointing to lightdm.service. This is probably a
bug in lightdm {pre,post}rm?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 11:18:25 2020
InstallationDate: Installed on 2019-08-29 (148 days ago)
InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  GDM fails to start at boot after removing LightDM

Status in lightdm package in Ubuntu:
  New

Bug description:
  I removed LightDM on the 14th and then didn't reboot until after
  upgrading to Focal. The next reboot didn't launch a display manager at
  all, and we tracked this down to /etc/systemd/system/display-
  manager.service still pointing to lightdm.service. This is probably a
  bug in lightdm {pre,post}rm?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:18:25 2020
  InstallationDate: Installed on 2019-08-29 (148 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1836809] Re: segfault when CCD are present in two different HOG services

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

Title:
  segfault when CCD are present in two different HOG services

Status in Bluez Utilities:
  Confirmed
Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Hello everyone,

  We are currently developing a device that contains two HID services.
  That device, as it is right now, is properly functioning on Windows & Android.
  However, when pairing the device on Linux running bluez 5.50 we do get 
segfaults (see attached files).
  Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt 
services and 1 device information service.
  With trial and error, we managed to find that we wouldn't get any crash as 
long as only 1 HOG service was present.

  Here's the interesting part. The two HOG services are made as follows:
  - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / 
boot INPUT + OUTPUT / HID information / HID Control point
  - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID 
information / HID control point

  Looking at the write_ccc in the call stacks we wondered if the
  callbacks subscribing to notifications for the INPUT reports were
  causing this issue.

  We therefore changed the raw HID over gatt (and its report map) to
  remove the INPUT report and change it into 1 OUTPUT report (leading to
  2 OUTPUT reports): no crash.

  We therefore hypothesize that the segfault occurs when subscribing to
  notification on a second HOG service...

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1836809/+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 1860764] Re: problem after pulseaudio updating

** Description changed:

  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
- maybe it depends on 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rob2511 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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.

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

Title:
  problem after pulseaudio updating

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  this problem happened after i updated system
  when i power on after sleeping i have problem with sounds. it doesn't work.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2511 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (362 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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/pulseaudio/+bug/1860764/+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 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: mutter (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Won't Fix
Status in ukwm package in Ubuntu:
  Fix Released

Bug description:
  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.

  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.

  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.

  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

  We could easily add a dummy key with the old name but I'm thinking the
  way forward is just to package the newer mutter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: mutter (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: mesa (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
  cursor.

  [  498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
  sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]

  Restarting gdm3 service results in the same trap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,gnomecompat,animation,vpswitch,grid,resize,imgpng,place,session,move,snap,unitymtgrabhandles,mousepoll,workarounds,expo,wall,ezoom,fade,scale,unityshell]
  Date: Tue Apr 23 09:56:22 2019
  DistUpgraded: 2019-04-22 15:16:02,086 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.18.0-13-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc MGA G200eW WPCM450 [15d9:0001]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3703]
  InstallationDate: Installed on 2012-02-14 (2625 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MachineType: Supermicro X8DT3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.2
  dmi.board.asset.tag: 1234567890
  dmi.board.name: X8DT3
  dmi.board.vendor: Supermicro
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: 1234567890
  dmi.product.name: X8DT3
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Apr 22 20:53:09 2019
  xserver.configfile:

[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

Status in alsa-driver package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  No Sound on laptop speaker after upgrading ubuntu 19.04 a few days
  ago. Soundcard is found in alsamixer but only "dummy" is available in
  gnome settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 20:18:10 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.sku: 1KT13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Laptop 13-ad1xx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13

[Touch-packages] [Bug 1855555] Re: CA0132: Only stereo with Creative Soundblaster ZxR

** Tags removed: disco

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

Title:
  CA0132: Only stereo with Creative Soundblaster ZxR

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a 5.1 sound system that is connected via three 3.5 mm audio
  cables with my Sound Blaster ZxR: Front Left, Center, Front Right,
  Rear Left, Rear Right, LFE

  I only get sound from "Front Left"/"Front Right". All other speakers
  don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro
  18.10, different Kernels and the Sound Blaster Patch from reddit,
  nothing helped. After all these tests, I started again with a fresh
  Ubuntu 19.10 installation with this output from "alsa information
  script": http://alsa-
  project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a

  Only thing that I did was changing the default audio device to my ZxR. 
Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc:
  defaults.ctl.!card "Creative"
  defaults.pcm.!card "Creative"
  defaults.timer.!card "Creative"

  Interestingly I decided to install Windows 10 on my second drive in dual boot 
mode.
  I noticed that when I start Windows all speakers are working. Then I reboot 
to Ubuntu and all speakers are working, too. This effect will vanish if I shut 
down my PC and start directly to Ubuntu.
  So something happens on Windows that is kept while rebooting to Ubuntu..

  I already reported this issue at bugzilla.kernel.org:
  https://bugzilla.kernel.org/show_bug.cgi?id=205315

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/185/+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 1860762] Re: Upgrade with zfs-on-root failures

I was able to fix this error:

 E: mkinitramfs failure cpio 141 lz4 -9 -l 24

by deleting the snapshots that sanoid made *during* the installation
process:

sarnold@millbarge:/boot$ sudo zfs destroy 
bpool@autosnap_2020-01-24_04:00:05_hourly%autosnap_2020-01-24_08:45:05_frequently
[sudo] password for sarnold: 
sarnold@millbarge:/boot$ sudo zfs destroy 
bpool/BOOT@autosnap_2020-01-24_04:00:05_hourly%autosnap_2020-01-24_08:45:05_frequently
sarnold@millbarge:/boot$ sudo zfs destroy 
bpool/BOOT/ubuntu@autosnap_2020-01-24_04:00:05_hourly%autosnap_2020-01-24_08:45:05_frequently
sarnold@millbarge:/boot$ df -h .
Filesystem Size  Used Avail Use% Mounted on
bpool/BOOT/ubuntu  365M  156M  210M  43% /boot
sarnold@millbarge:/boot$ sudo dpkg --configure -a
Setting up initramfs-tools (0.133ubuntu10) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133ubuntu10) ...
update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic
cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
cryptsetup: WARNING: Couldn't determine root device
sarnold@millbarge:/boot$ 


Considering sanoid is not packaged in Ubuntu, there may not be anything that 
do-release-upgrade or initramfs-tools can do differently.

Thanks

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

Title:
  Upgrade with zfs-on-root failures

Status in initramfs-tools package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I followed rlaager's howto for installing Ubuntu 18.04 LTS with ZFS
  root (but used disco). I've also set up sanoid to perform periodic
  snapshots of bpool (which stores /boot).

  The upgrade from disco to eoan didn't go well:

  [.. trimmed to fit in the comment box; more context in attachment ..]

  /ubuntu@autosnap_2020-01-24_04:00:05_frequently
  Found initrd image: initrd.img-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:00:05_frequently
  Found linux image: vmlinuz-5.0.0-39-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.0.0-39-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found linux image: vmlinuz-5.0.0-40-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.0.0-40-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found linux image: vmlinuz-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Found initrd image: initrd.img-5.3.0-29-generic in 
rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently
  Adding boot menu entry for EFI firmware configuration
  done
  Processing triggers for dbus (1.12.14-1ubuntu2) ...
  Processing triggers for initramfs-tools (0.133ubuntu10) ...
  update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic
  cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
  cryptsetup: WARNING: Couldn't determine root device
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for shim-signed (1.39+15+1533136590.3beb971-0ubuntu1) ...
  Nothing to do.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1build1) ...
  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A 
  recovery will run now (dpkg --configure -a). 

  Setting up initramfs-tools (0.133ubuntu10) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.133ubuntu10) ...
  update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/initramfs-tools.0.crash'
  cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
  cryptsetup: WARNING: Couldn't determine root device
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade 
  process. 

  To continue please press [ENTER]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10

[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.


** Tags removed: disco trusty

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

Title:
  Sound input settings not saved

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

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+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 1827691] Re: [ASUS X555YI] Speaker "Front right" do not have sound

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [ASUS X555YI] Speaker "Front right" do not have sound

Status in alsa-driver package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  My system is Ubuntu19.04
  I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test
  Front left have sound but front right have not sound
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon  7881 F pulseaudio
   /dev/snd/pcmC1D0p:   widon  7881 F...m pulseaudio
   /dev/snd/controlC0:  widon  7881 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-01 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:12.2-2ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

** Tags removed: disco

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

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

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

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193

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

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

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1838071] Re: Recording sound is impossible on Dell Latitude 7350 [broadwell-rt286]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Recording sound is impossible on Dell Latitude 7350 [broadwell-rt286]

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Since Ubuntu 16.04, it is impossible to use the microphone of headsets
  (those which come with 4 ring jack connector). The main microphone is
  sometimes usable (I think it's okay with Ubuntu 18.04). With Ubuntu
  19.04, neither the embedded (main) microphone nor those on headsets
  are functional, I thus cannot record any sound.

  I've read many things, tried many modifications of /etc/modprobe.d
  /alsa-base.conf in order to let the Internal Broadwell audio card be
  seen before HDMI audio, for example.

  Here is the Alsa diagnostic I ran : http://alsa-
  project.org/db/?f=06e98f49dcfaf88991b4a992e66409b71976f038

  I also verified everything was fine with alsamixer -c1 (broadwaell-
  rt286 is second by default). I also tried to use pavucontral, as under
  Ubuntu 18.04 it helped me to "start" the embedded microphone. With
  this tool, under Ubuntu 19.04, I see strange settings : there is an
  "internal audio main microphone + handset microphone" entry, there
  once were 2 entries. And the handset microphone is always "plugged in"
  and the "main microphone" is always unplugged.

  Here are logs from kern.log, audio-related :
  Jul 26 19:51:39 dell7350 kernel: [0.125327] ACPI: Added 
_OSI(Linux-Lenovo-NV-HDMI-Audio)
  Jul 26 19:51:39 dell7350 kernel: [5.426806] snd_hda_intel :00:03.0: 
bound :00:02.0 (ops i915_audio_component_bind_ops [i915])
  Jul 26 19:51:39 dell7350 kernel: [5.709584] haswell-pcm-audio 
haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with 
error -2
  Jul 26 19:51:39 dell7350 kernel: [5.709588] haswell-pcm-audio 
haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2)
  Jul 26 19:51:39 dell7350 kernel: [5.710201] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 19:51:39 dell7350 kernel: [5.730701] broadwell-audio 
broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok
  Jul 26 19:51:39 dell7350 kernel: [5.730753] broadwell-audio 
broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok
  Jul 26 19:51:39 dell7350 kernel: [5.730803] broadwell-audio 
broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok
  Jul 26 19:51:39 dell7350 kernel: [5.730852] broadwell-audio 
broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok
  Jul 26 19:51:39 dell7350 kernel: [5.733370] broadwell-audio 
broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok
  Jul 26 19:51:39 dell7350 kernel: [5.739468] input: broadwell-rt286 
Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input35
  Jul 26 19:51:43 dell7350 kernel: [   17.225240] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 19:52:04 dell7350 kernel: [   38.539888] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 19:54:28 dell7350 kernel: [  182.195082] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 19:54:46 dell7350 kernel: [  200.793924] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 17:58:48 dell7350 kernel: [  442.674338] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26 17:59:11 dell7350 kernel: [  466.144813] haswell-pcm-audio 
haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 
00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19
  Jul 26

[Touch-packages] [Bug 1827020] Re: [Z97X-UD3H, ATI R6xx HDMI, Digital Out, HDMI] Sound quality over HDMI very poor at times.

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
Status: New => Won't Fix

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

Title:
[Z97X-UD3H, ATI R6xx HDMI, Digital Out, HDMI] Sound quality over HDMI
very poor at times.

Status in alsa-driver package in Ubuntu:
Won't Fix

Bug description:
Frequently, I suffer from pops when playing audio over HDMI to my home
cinema receiver. Stereo or 5.1 output doesn't matter, the pops happen
regardless. The pops can go from a small one every few seconds, to
constant loud pops. At times, all sound can also become muffled and
have an unpleasant static tone. It's horrible, worse than the worst
popping. Other times sound can be fine, sometimes for hours, but the
pops always come back. I'm not experiencing any pops when switching to
line out, although my testing here is limited.

The problem started months ago, either in 18.10 or 18.04, and my
impression is that it's even worse in 19.04. Certainly, the complete
staticy mangling of all sound that occasionally happens is new. When
the sound starts acting up, it can fixed sometimes partially,
sometimes in whole, by switching between outputs and output
configurations, and then switching back. It is also my impression that
using multiple programs that play sound at the same time will have a
high risk of triggering, and worsening, the problem.

I don't think it's my home cinema receiver, as it works as it should
with my several video game consoles. It was also flawless in Ubuntu 6
months ago. It's not my GPU or its drivers, as I have had the same
problem with both Nvidia and AMD.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mattias 13111 F pulseaudio
/dev/snd/controlC1: mattias 13111 F pulseaudio
/dev/snd/pcmC1D7p: mattias 13111 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 10:50:11 2019
InstallationDate: Installed on 2019-04-26 (3 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [Z97X-UD3H, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-UD3H
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827020/+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 1834036] Re: [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded on TravelMate X514-51

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Only static noises are recorded
  on TravelMate X514-51

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  On TravelMate X514-51 the microphone is detected but only staticky
  noises are recorded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buo.ren.lin   7028 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jun 24 21:24:17 2019
  InstallationDate: Installed on 2019-05-08 (47 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_TW:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_TW.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: 內部音效 - HDA Intel PCH
  Symptom_Type: High background noise, or volume is too low
  Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.name: Crux_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd01/24/2019:svnAcer:pnTravelMateX514-51:pvrV1.04:rvnWL:rnCrux_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: TravelMate X5
  dmi.product.name: TravelMate X514-51
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834036/+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 1828718] Re: [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  sound is very low for videos both hevc and h264 . even with
  amplification.  and fine in youtube. overall sound is very much less
  than when i was in windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thanveer   1898 F pulseaudio
   /dev/snd/controlC0:  thanveer   1898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 14:45:17 2019
  InstallationDate: Installed on 2019-05-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.sku: W6T33PA#ACJ
  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/1828718/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1832128] Re: [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] volume slider problem

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI]
  volume slider problem

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  I upgraded my PC from 18.04 to 19.04. I have headphones using the
  clinch output and USB Audio Speakers. After I added the line "load-
  module module-udev-detect tsched=0" to /etc/pulse/default.pa, the
  speakers started working, but everytime I restart the computer the
  speakers need to be reselected. Also the volume slider does not seem
  to work.

  The Audiospeakers had trouble working since 18.04. Please fix that.

  Let me suggest a better way to allow controlling of the panel: Make the 
audiopanel a separate control panel.
  Show a list of devices to be selected. Then show another list of 
audiosources. Allow the control of each device separately with a Volumeslide 
and a Mute button.

  If you want to make it very fancy, then allow to each source to be
  directed to any output, so that I could send the output of one chrome
  tab to my headphones and the other one to the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ranju  1744 F pulseaudio
   /dev/snd/controlC2:  ranju  1744 F pulseaudio
   /dev/snd/controlC1:  ranju  1744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  9 13:22:25 2019
  InstallationDate: Installed on 2019-06-08 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: GF108 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   Jun 09 13:17:42 vikrant dbus-daemon[901]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.48' (uid=123 pid=1328 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
   Jun 09 13:17:46 vikrant pulseaudio[1328]: E: [pulseaudio] module.c: Module 
"module-udev-detect" should be loaded once at most. Refusing to load.
   Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.service: Succeeded.
   Jun 09 13:18:51 vikrant systemd[1129]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [To Be Filled By O.E.M., Nvidia GPU 14 HDMI/DP, Digital Out, HDMI] 
volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: N68C-GS FX
  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.:bvrP1.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX: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/1832128/+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 1836120] Re: [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback problem - System sounds work, but no media sound

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback
  problem - System sounds work, but no media sound

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  The system sound effects are working properly on my Corsair Void RGB
  Pro usb wired headset, but I cannot listen to audio in videos on
  Youtube via Chrome or Firefox. I cannot seem to get sound working in
  other apps as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 10 18:23:16 2019
  InstallationDate: Installed on 2019-07-09 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   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:Hea successful
  Symptom_Card: Corsair VOID RGB USB Gaming Headset  - Corsair VOID RGB USB 
Gaming Hea
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3P-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:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3P:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3P-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3P
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1836120/+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 1838048] Re: [chtrt5645 - chtrt5645, playback] Playback problem - Headphone jack inverted status as previously described 1824259 - hack quirk not fixing