date:20190628

[Touch-packages] [Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames

2019-06-28 Thread ironstorm

Thanks Martin, your solution to disable systemd-resolve allowed me to
finally resolve hosts on my local network again...  I was using a
temporary workaround of replacing "echo 'nameserver 192.168.1.1' >
/etc/resolv.conf", however that doesn't survive reboots.

This issue should be addressed by Ubuntu devs, systemd is pretty
seriously f-ing up a basic form of usability in being able to resolve
machines (and devices) by name on a local home network.

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

Title:
  systemd-resolve breaks resolution of local network hostnames

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.04 (zesty), resolution of my local
  network's host names is completely broken.  Apparently the upgrade
  replaced my existing resolver with systemd-resolve, which deliberately
  refuses to pass "single-label" domain names to my domain name server.
  That is the server where all my network's host names are kept, so I
  can no longer resolve any of them.

  Apparently, this is yet another example of Poettering's upstream decisions 
causing denial of service to people who have been saddled with his malware.
  https://github.com/systemd/systemd/issues/2514#issuecomment-179203186

  Would someone sensible please put a stop to this forced breakage
  during upgrade, and advise on how to fix it now that the damage has
  been done?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+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 1826648] Re: cupds crashes with core dump

2019-06-28 Thread Launchpad Bug Tracker

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

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

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

Title:
  cupds crashes with core dump

Status in cups package in Ubuntu:
  Expired

Bug description:
  At home my cupsd daemon crashes all the time.

  Sometimes I'm able to print a few pages but in most cases it ends-up
  restarting and sending tons of crap to my printer resulting in
  multiple wasted pages with non-sense characters printed on it.

  I ended-up manually creating a core dump by launching it from root with:
  # cupsd -f -c /etc/cups/cupsd.conf
  (will attach core in post)

  I tried using the default drivers for my printer then using the
  Samsung provided ones with same result.  My printer is a Samsung
  C460W.

  Here is the systemd status:
  $ sudo systemctl status cups
  ● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 
12min ago
   Docs: man:cupsd(8)
Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT)
   Main PID: 15292 (code=dumped, signal=ABRT)

  avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler.
  avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer
  avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, 
code=dumped, status=6/ABRT
  avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 
'core-dump'.
  avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler.

  I wasn't able to find the core dump it refers to so that's why I
  ended-up generating one by invoking cupsd manually then launching
  ubuntu-bug against the cups package.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4
  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
  Date: Sat Apr 27 09:54:21 2019
  InstallationDate: Installed on 2019-04-05 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO 20L6SF1000
  Papersize: letter
  PpdFiles:
   Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS
   Samsung-C460: Samsung C460 Series PS
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago)
  dmi.bios.date: 02/20/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET48W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6SF1000
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6SF1000
  dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826648/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-28 Thread Book 'em Dano

Per instructions listed @
https://wiki.ubuntu.com/DebuggingPrintingProblems

** Attachment added: "troubleshoot-again.txt"
   
https://bugs.launchpad.net/hplip/+bug/1834400/+attachment/5274052/+files/troubleshoot-again.txt

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-28 Thread Book 'em Dano

I upgraded from hplip 3.19.5 to 3.19.6 and still not able to print to
network printer. Followed debugging instructions @
https://wiki.ubuntu.com/DebuggingPrintingProblems

** Attachment added: "error_log"
   
https://bugs.launchpad.net/hplip/+bug/1834400/+attachment/5274051/+files/error_log

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-28 Thread Book 'em Dano

I don't believe that the issues in LP:934669 are related to the issues I
have experienced, but I could be wrong.

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1777094] Re: dnsmasq started too early, not getting all interfaces

2019-06-28 Thread Terrence Houlahan

The problem lives in the [Unit] section in the After= directive which
when modified as follows raises dnsmasq.service unbroken on boot:

sed -i 's/After=network.target/After=NetworkManager-wait-
online.service/' /etc/systemd/system/multi-
user.target.wants/dnsmasq.service

That's a fairly tidy, and *reproducible* fix which works on successive
reboots.


** Changed in: dnsmasq (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Expired

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

2019-06-28 Thread Manoj Iyer

== Regression test on PPC64EL ==

ubuntu@tiselius:~$ uname -a 
Linux tiselius 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@tiselius:~$ 

ubuntu@tiselius:~$ apt policy gdb
gdb:
  Installed: 8.1-0ubuntu4
  Candidate: 8.1-0ubuntu4
  Version table:
 *** 8.1-0ubuntu4 500
500 http://ppa.launchpad.net/manjo/gdb-lp1830796/ubuntu bionic/main 
ppc64el Packages
100 /var/lib/dpkg/status
 8.1-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages
ubuntu@tiselius:~$ 


root@tiselius:/home/ubuntu# gdb /usr/lib/debug/boot/vmlinux-4.15.0-20-generic 
/proc/kcore 
GNU gdb (Ubuntu 8.1-0ubuntu4) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc64le-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/debug/boot/vmlinux-4.15.0-20-generic...done.

warning: core file may not match specified executable file.
[New process 1]
Core was generated by `root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro 
console=hvc0'.
#0  0x in ?? ()
(gdb) p jiffies_64
$1 = 4294952364
(gdb)

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  In Progress

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+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 1798313] Re: traceoute6 gives error sendto: Invalid argument

2019-06-28 Thread Sebastien Bacher

(the ppa build has been deleted since replaced by the SRU)

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in iputils package in Debian:
  Fix Released

Bug description:
  * Impact
  Using IPv6 the routing command returns Invalid argument errors

  * Test case
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument

  * Regression potential
  Check that the command behave correclty on IPv4 and IP6 Ips

  --

  
  This seems like a regression of Debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

2019-06-28 Thread Andreas Hasenack

The PPA has cosmic and bionic packages. I tested with the prefork,
worked and event MPMs, and also ran the apache DEP8 tests. All passed.

I'll prepare MPs, update this bug with the SRU template and testing
instructions, and get ready to release this early next week.

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Incomplete
Status in apache2 source package in Bionic:
  Confirmed
Status in apache2 source package in Cosmic:
  Confirmed

Bug description:
  I am using Apache2 with client certificate authentication.
  Since recently (last week) and without any configuration changes, the 
following errors occur frequently:

  AH02042: rejecting client initiated renegotiation

  Client connections are very slow and sometimes it takes more than a minute 
until a weg page can be opened in the browser.
  Before installation of the latest security fixes last week, this error did 
not occur.

  Could it be related to
  https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689?

  
  System information:

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apache2:
Installiert:   2.4.29-1ubuntu4.6
Installationskandidat: 2.4.29-1ubuntu4.6
Versionstabelle:
   *** 2.4.29-1ubuntu4.6 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  openssl:
Installiert:   1.1.1-1ubuntu2.1~18.04.2
Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2
Versionstabelle:
   *** 1.1.1-1ubuntu2.1~18.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.0g-2ubuntu4.3 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.1.0g-2ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1798313] Re: traceoute6 gives error sendto: Invalid argument

2019-06-28 Thread Sebastien Bacher

The issue is fixed in the current version, a SRU has been uploaded to
bionic now

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

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

** Description changed:

+ * Impact
+ Using IPv6 the routing command returns Invalid argument errors
+ 
+ * Test case
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
-  1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
-  *sendto: Invalid argument
- traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
-  *sendto: Invalid argument
- traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
-  *
  
- This seems like a regression of Debian bug https://bugs.debian.org/cgi-
- bin/bugreport.cgi?bug=843264
+ * Regression potential
+ Check that the command behave correclty on IPv4 and IP6 Ips
+ 
+ --
+ 
+ 
+ This seems like a regression of Debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264
  
  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64
  
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in iputils package in Debian:
  Fix Released

Bug description:
  * Impact
  Using IPv6 the routing command returns Invalid argument errors

  * Test case
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument

  * Regression potential
  Check that the command behave correclty on IPv4 and IP6 Ips

  --

  
  This seems like a regression of Debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

2019-06-28 Thread Sebastien Bacher

Thank you for your bug report, marking the bug as fixed since the issue
is resolved in the current version.

We are doing a SRU backport to Bionic as well (the corresponding line
will be added to the report)

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

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

** Description changed:

- The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is the
- only version that presents the problem. This version has a known problem
- when reading file entries in ZIP files, where it incorrectly identifies
- directories and files entries.
+ * Impact
+ The bionic version has a known problem when reading file entries in ZIP 
files, where it incorrectly identifies directories and files entries.
+ 
+ * Test case
+ $ wget 
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip
+ $ bsdtar -vxf example.zip
+ $ ls -l
+ 
+ The 'ABCD_1234' and 'empty' entries should be directories
+ 
+ * Regression potential
+ Check that extracting zips from bsdtar or nautilus work without issue
+ 
+ 
  
  It has been confirmed that the previous and following versions (3.3.1+)
  do not have this problem and the library handles the ZIP files
  correctly.
  
  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?
  
  This problem is seriously affecting some of our systems.

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  The bionic version has a known problem when reading file entries in ZIP 
files, where it incorrectly identifies directories and files entries.

  * Test case
  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip
  $ bsdtar -vxf example.zip
  $ ls -l

  The 'ABCD_1234' and 'empty' entries should be directories

  * Regression potential
  Check that extracting zips from bsdtar or nautilus work without issue

  

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-28 Thread brian_p

> io/hpmud/jd.c 373: unable to connect to print port 9100: Connection
> refused   hp:/net/HP_OfficeJet_Pro_8710?ip=192.168.0.17

Not very encouraging. Does any of

https://bugs.launchpad.net/hplip/+bug/934669

or its associated bugs fit your situation?

-- 
Brian.

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

2019-06-28 Thread Andreas Hasenack

** Also affects: apache2 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: openssl (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** No longer affects: openssl (Ubuntu Bionic)

** No longer affects: openssl (Ubuntu Cosmic)

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

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

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Incomplete
Status in apache2 source package in Bionic:
  Confirmed
Status in apache2 source package in Cosmic:
  Confirmed

Bug description:
  I am using Apache2 with client certificate authentication.
  Since recently (last week) and without any configuration changes, the 
following errors occur frequently:

  AH02042: rejecting client initiated renegotiation

  Client connections are very slow and sometimes it takes more than a minute 
until a weg page can be opened in the browser.
  Before installation of the latest security fixes last week, this error did 
not occur.

  Could it be related to
  https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689?

  
  System information:

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apache2:
Installiert:   2.4.29-1ubuntu4.6
Installationskandidat: 2.4.29-1ubuntu4.6
Versionstabelle:
   *** 2.4.29-1ubuntu4.6 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  openssl:
Installiert:   1.1.1-1ubuntu2.1~18.04.2
Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2
Versionstabelle:
   *** 1.1.1-1ubuntu2.1~18.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.0g-2ubuntu4.3 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.1.0g-2ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Dan Streetman

Opened MR to blacklist TEST-15 and TEST-22:

https://salsa.debian.org/systemd-team/systemd/merge_requests/35

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |
  | updated  | 2019-05-16T07:00:42Z 
  |
  | user_id  | 8524250971084851b3792a68fbc398dd 
  |

[Touch-packages] [Bug 1834666] [NEW] X didn't use hardware acceleration for your system

2019-06-28 Thread juan david linares santana

Public bug reported:

Your system is providing 3D via software rendering rather than hardware
rendering.  This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor.  If the problem
you're reporting is related to graphics performance, your real question
may be why X didn't use hardware acceleration for your system.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Jun 28 16:28:41 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=4e297ab3-b0cc-4dcf-ac56-953597c77fa0 ro
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: Default string
dmi.board.name: TUF B360-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB360-PLUSGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  X didn't use hardware acceleration for your system

Status in xorg package in Ubuntu:
  New

Bug description:
  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Jun 28 16:28:41 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=4e297ab3-b0cc-4dcf-ac56-953597c77fa0 ro
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF B360-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets

2019-06-28 Thread Kostas Papadopoulos

Most reports mention ALC1220, but the same bug occurs in older AMD
systems also.

E.g. it occurs on a 2014 system by Dell, AMD chipset, AMD G-T48E CPU, ALC269VB, 
with Linux 4.19.
Whereas the microphone of that system works OK with Windows 10.


 List of PLAYBACK Hardware Devices 
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

 List of CAPTURE Hardware Devices 
card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Ubuntu Foundations Team Bug Bot

The attachment "Proposed workaround. Still under analysis. Testing
appreciated." seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Mark J. Wielaard

** Patch added: "Proposed workaround. Still under analysis. Testing 
appreciated."
   
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+attachment/5274014/+files/0001-Be-more-liberal-in-the-number-of-selectors-we-accept.patch

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Mark J. Wielaard

Please see the discussion and analysis of the issue on the bzip2-devel
mailinglist: https://sourceware.org/ml/bzip2-devel/2019-q2/msg00024.html

There is a proposed workaround patch for decompression of the (buggy lbzip2 
compressed) files:
https://sourceware.org/ml/bzip2-devel/2019-q2/msg00031.html

Testing of that patch is highly appreciated.

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets

2019-06-28 Thread Kostas Papadopoulos

Bug 195303 (ALC1220 snd_hda_intel Sound capture is crackled / distorted)
is the most detailed and active of several open bug reports about this.

** Changed in: linux
   Importance: Medium => Unknown

** Changed in: linux
   Status: Confirmed => Unknown

** Changed in: linux
 Remote watch: Linux Kernel Bug Tracker #201613 => Linux Kernel Bug Tracker 
#195303

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

2019-06-28 Thread Brian Murray

Actually the version number used in the debdiff (8.1-0ubuntu4) had
already been uploaded to the archive and so it was rejected. This is
part of why
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
recommends appending a .1 to the package version number, which is what I
did.

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  In Progress

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+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 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

2019-06-28 Thread Brian Murray

I've uploaded this to the SRU queue for Ubuntu 18.04 so it can be
reviewed by the SRU team.

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  In Progress

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Dan Streetman

> right now the upstream test timeouts on i386

ah, ok - so I did look into this, or at least some failures really
similar to this, a while back, for bug 1831468.  As far as I could tell,
the problem in those cases was that the test was starting a service and
waiting for notification of its completion; but for some reason, dbus
seemed to be crashing/dying/exiting, and the notification of the
completed service never actually reached the test suite, so it just
waited forever until timeout.  I do see in the logs for the test you
referenced:

[0;38;5;245mUnable to add match 
type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.7',
 failing connection: Method call timed out[0m
[0;38;5;245mBus bus-api-system: changing state RUNNING → CLOSING[0m
[0;38;5;245mUnable to add match 
type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.7',
 failing connection: Connection terminated[0m
[0;38;5;245mBus bus-api-system: changing state CLOSING → CLOSED[0m
[0;38;5;245msystemd-rfkill.socket: Changed dead -> listening[0m
[0;38;5;245msystemd-rfkill.socket: Job 364 systemd-rfkill.socket/start 
finished, result=done[0m
[[0;32m  OK  [0m] Listening on [0;1;39mLoad/Save RF …itch Status /dev/rfkill 
Watch[0m.
[0;38;5;245mBus bus-api-system: changing state UNSET → OPENING[0m
[0;38;5;245mBus bus-api-system: changing state OPENING → AUTHENTICATING[0m

that's quite similar to what i saw before.  I never had a chance to get
farther than that, but I can try to look more into it soon.  Let me know
if that sounds familiar or if you have any debugging suggestions.

> Plus, in https://github.com/systemd/systemd/pull/12861#issuecomment-506556062 
> the
> test is completely broken on Ubuntu CI and I have no idea why.

ugh, yeah TEST-15 and TEST-22 aren't giving any clues at all in the log
to why they failed.

> As far as I can tell, it has been abandoned since then. If you're ready to 
> keep
> the list up to date by visiting PRs where Ubuntu CI fails I'm of course all 
> for it.

Let's add TEST-15 and TEST-22 for now, and I'll see if I can both keep
up with other flaky tests, and also try to figure out why they're being
flaky in ubuntu-ci.

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive

[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Evgeny Vereshchagin

Just to clarify, I think that it would be better to turn off the test
globally because we know it's flaky and unstable and we generally never
roll out globally flaky tests so as not to annoy contributors (I'm not
sure why Ubuntu CI should be different from any other CI system we use
upstream). And then, it should be possible to run the test over and over
again somewhere to see what fails updating the list along the way.

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |

[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Marc Deslauriers

** Information type changed from Public to Public Security

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

2019-06-28 Thread Andreas Hasenack

I think this patch worked:
https://github.com/apache/httpd/commit/bbedd8b80e50647e09f2937455cc57565d94a844

Could you please try the build from my ppa:
https://launchpad.net/~ahasenack/+archive/ubuntu/apache2-client-cert-1833039

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I am using Apache2 with client certificate authentication.
  Since recently (last week) and without any configuration changes, the 
following errors occur frequently:

  AH02042: rejecting client initiated renegotiation

  Client connections are very slow and sometimes it takes more than a minute 
until a weg page can be opened in the browser.
  Before installation of the latest security fixes last week, this error did 
not occur.

  Could it be related to
  https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689?

  
  System information:

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apache2:
Installiert:   2.4.29-1ubuntu4.6
Installationskandidat: 2.4.29-1ubuntu4.6
Versionstabelle:
   *** 2.4.29-1ubuntu4.6 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  openssl:
Installiert:   1.1.1-1ubuntu2.1~18.04.2
Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2
Versionstabelle:
   *** 1.1.1-1ubuntu2.1~18.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.0g-2ubuntu4.3 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.1.0g-2ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

2019-06-28 Thread Andreas Hasenack

https://bz.apache.org/bugzilla/show_bug.cgi?id=62691#c5
"Moving "SSLVerifyClient require" outside of the  block instantly 
returns the document.  So it does appear to be ONLY the renegotiation case.
"

That works here too, in my simple test case. I had this location directive:

SSLVerifyClient require
Require ssl-verify-client


By moving SSLVerifyClient to the vhost level, i.e., the whole site
requires it, then re-negotiation isn't triggered and access works
without a timeout.

** Bug watch added: bz.apache.org/bugzilla/ #62691
   https://bz.apache.org/bugzilla/show_bug.cgi?id=62691

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I am using Apache2 with client certificate authentication.
  Since recently (last week) and without any configuration changes, the 
following errors occur frequently:

  AH02042: rejecting client initiated renegotiation

  Client connections are very slow and sometimes it takes more than a minute 
until a weg page can be opened in the browser.
  Before installation of the latest security fixes last week, this error did 
not occur.

  Could it be related to
  https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689?

  
  System information:

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apache2:
Installiert:   2.4.29-1ubuntu4.6
Installationskandidat: 2.4.29-1ubuntu4.6
Versionstabelle:
   *** 2.4.29-1ubuntu4.6 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  openssl:
Installiert:   1.1.1-1ubuntu2.1~18.04.2
Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2
Versionstabelle:
   *** 1.1.1-1ubuntu2.1~18.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.0g-2ubuntu4.3 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.1.0g-2ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Evgeny Vereshchagin

Regarding the blacklist, we started to work on it in
https://github.com/systemd/systemd/issues/11195 (which was initially
about merging PRs where bugs were caught by Travis CI but ignored
because everybody was used to Ubuntu CI failing more often than not) and
ended up with a list of test I suggested because I more or less knew
what was flaky at the time and kept monitoring Ubuntu CI for a couple of
days. As far as I can tell, it has been abandoned since then. If you're
ready to keep the list up to date by visiting PRs where Ubuntu CI fails
I'm of course all for it.

Other than that, right now the upstream test timeouts on i386, which has
been on for just two days:
https://github.com/systemd/systemd/pull/12901#issuecomment-506646998.
I'm not sure how turning off some tests will help there (because
generally I don't understand why it fails).

Plus, in
https://github.com/systemd/systemd/pull/12861#issuecomment-506556062 the
test is completely broken on Ubuntu CI and I have no idea why.


** Bug watch added: github.com/systemd/systemd/issues #11195
   https://github.com/systemd/systemd/issues/11195

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13

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

2019-06-28 Thread pgfan92

It is NOT the hardware!  After wasting hours trying to get a Windows 10
disc to install so I can update the BIOS, I put the Ubuntu install disc
back in and clicked to install rather than try.  When the install page
loaded up, I decided to try the sound to see if it worked, and it did
work!  If you can give me something to try to fix it before I have
everything backed up for reinstallation, I would appreciate it.
Otherwise, I'm going forward with reinstallation.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I don't have any sound.  I have followed some online instructions that
  have not worked.  Please help me.  My laptop was working just fine
  until today.  I opened it up and there was no sound.  If you need
  further information from me, please provide instructions on how to
  obtain it.  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 25 18:29:31 2019
  InstallationDate: Installed on 2019-02-18 (127 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8364
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc0xx
  dmi.product.sku: 1KU13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa

** Also affects: bzip2 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Dan Streetman

> Even if I'm totally wrong and someone is interested in getting it to
work on Ubuntu CI

I'll work on this; I would like it to work correctly.

> it should be possible to turn it off globally so as not to annoy
contributors with known issues

I agree about doing *something* for flaky tests - it makes the entire
test suite unreliable if you can't trust the end result.

There is an existing upstream test blacklist:
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/tests/upstream#L11

how about if we keep that up to date with any upstream tests that are
flaky in ubuntu ci?

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE

[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa

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

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1832882] Re: libcurl-gnutls segfaults spotify client

2019-06-28 Thread Francis Ginther

** Tags added: id-5d14f42606a1fc59984d531b

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

Title:
  libcurl-gnutls segfaults spotify client

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Disco:
  Confirmed

Bug description:
  The latest release of Spotify client segfaults in libcurl-gnutls as can be 
read in this thread on spotify support forum:
  
https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479

  According to one participant the work-around is to install debian
  packages libgnutls30_3.6.8-1_amd64.deb and
  libcurl3-gnutls_7.64.0-3_amd64.deb

  Ubuntu 19.04 version of the packages:
  libgnutls30 3.6.5-2ubuntu1.1
  libcurl3-gnutls 7.64.0-2ubuntu1.1

  As the bug can be resolved by installing debian packages, I assume
  Ubuntu's version of the packages is at fault and should be upgraded to
  match debian's level as soon as possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-28 Thread Erik Sax

Did a PS on one of these systems this morning. Found some shenanigans.
root  3380 1  0 08:25 ?00:00:00 /bin/sh 
/usr/lib/apt/apt.systemd.daily install
root  3384  3380  0 08:25 ?00:00:00 /bin/sh 
/usr/lib/apt/apt.systemd.daily lock_is_held install
root  3415  3384 99 08:25 ?00:00:09 /usr/bin/python3 
/usr/bin/unattended-upgrade

Grep for "updates" yielded this:
$ ps -ef | grep upgrade
root  1182 1  0 08:22 ?00:00:00 /usr/bin/python3 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
root  3415  3384 14 08:25 ?00:00:22 /usr/bin/python3 
/usr/bin/unattended-upgrade
root  5356  3415  1 08:27 ?00:00:00 /usr/bin/python3 
/usr/bin/unattended-upgrade

After I killed 3415 I was able to get the apt lock and proceed with a
manual `sudo apt-get upgrade`

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

Title:
  update-notifier doesn't respect "automatically check for updates:
  Never"

Status in software-properties package in Ubuntu:
  New

Bug description:
  This has been a long-standing problem with various ubuntu
  installations, and I'm sensing some reticence in doing anything about
  it. This attitude also seems to be purposeful to try to cajole updates
  on people who make bad choices due to confusion/fud/paranoia.

  apt install fails due to:

  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  A great deal of networking is taking place despite setting automatic
  upgrades to "never". Cycling this doesn't seem to do anything. This
  action is hostile to programmers and the setting should be respected.

  Wisdom on threads is to let it update until it's out of updates, and
  then it supposedly respects the "never" flag, but the experience I'm
  having is much more non-deterministic. have been using 19.04 for weeks
  now and still get the background notifier using data and getting in
  the way of aptitude package installations. I prefer manual update &&
  upgrade once my code is ready to push.

  Is there another way around this or are people just living with it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Bug Watch Updater

** Changed in: bzip2
   Status: Unknown => New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa

** Also affects: bzip2 (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  Unknown
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1830477] Re: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

2019-06-28 Thread Dan Streetman

re: autopkgtests, a few failed, but I re-ran them and they passed on the
re-run.

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

Title:
  systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [impact]

  these tests require, and modify, grub.  That fails on s390x on xenial
  because it does not use grub.

  [test case]

  run the autopkgtests for xenial on s390x

  [regression potential]

  low; only skipping test cases on s390x.

  [other info]

  in bionic and later, systemd-fsckd has support for zipl (s390x
  bootloader) and cmdline-upstart-boot is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+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 1798313] Re: traceoute6 gives error sendto: Invalid argument

2019-06-28 Thread Sebastien Bacher

Could those having the issue try if the deb on https://launchpad.net
/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/10307594/+listing-
archive-extra fixes their issue (I don't know enough ab out IPv6 to have
those commands return something else than 'network unreachable')

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1830477] Re: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

2019-06-28 Thread Dan Streetman

autopkgtests on s390x now all pass

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

** Tags removed: ddstreet-next

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

Title:
  systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [impact]

  these tests require, and modify, grub.  That fails on s390x on xenial
  because it does not use grub.

  [test case]

  run the autopkgtests for xenial on s390x

  [regression potential]

  low; only skipping test cases on s390x.

  [other info]

  in bionic and later, systemd-fsckd has support for zipl (s390x
  bootloader) and cmdline-upstart-boot is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Evgeny Vereshchagin

I agree ideally the test should be fixed but it's been flaky for a
couple of years and I didn't notice anyone who would be willing to try
to figure it out. I think it's time to admit nobody cares. Even if I'm
totally wrong and someone is interested in getting it to work on Ubuntu
CI, it should be possible to turn it off globally so as not to annoy
contributors with known issues they shouldn't even have to care about
and keep trying to reproduce it "locally" (as we do on CentOS CI, Travis
CI, Azure Pipelines and so on and so forth).

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-28 Thread Dan Streetman

re: autopkgtests, a few failed, but I re-ran them and they passed on the
re-run.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in snapd source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

   * When a generator started to be provided by systemd, it was
  recognized that $PATH is not correctly set, nonetheless, due to an
  environment bug that systemd generators run in.

  [Testcase]

  # make snapd-env-generator executable if it is not
  $ sudo chmod +x 
/usr/lib/systemd/system-environment-generators/snapd-env-generator

  # reboot, then test the effect of the fix
  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

  Output should contain a complete and a valid PATH, i.e.
  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" 
or similar.

  [Regression Potential]

   * snapd generator was already fixed separately to cause no harm, when
  running under a broken systemd. With the corrected environment,
  generators will now run with a correct PATH out of the box. A slight
  change of PATH will be observed by all generators, when running in
  containers/initramfs-less boots. However most generators will not be
  affected as they typically do not execute external binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-06-28 Thread Dan Streetman

storage test passed for all archs

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

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  Fix Committed

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-06-28 Thread Dan Streetman

re: autopkgtests, a few failed, but I re-ran them and they passed on the
re-run.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in systemd package in Debian:
  Fix Committed

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1828892] Re: systemctl - alias service reports inactive while aliased is active

2019-06-28 Thread Dan Streetman

re: autopkgtests, a few failed, but I re-ran them and they passed on the
re-run.

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

Title:
  systemctl - alias service reports inactive while aliased is active

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  'systemctl is-active' command reports an alias service as inactive even 
though the aliased service
  is active.
  Currently the 'systemctl is-active' command does not load units to minimise 
its effect on the system (i.e. that a monitoring command does not itself alter 
the state of the system).
  However, this behaviour leads to inconsistencies when services are aliased.

  [Test case]

  - Test case 1 - libvirtd

  alias service : libvirtd
  aliased service : libvirt-bin

  /etc/systemd/system$ ls -la libvirtd.service 
  lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> 
/lib/systemd/system/libvirt-bin.service

  $ systemctl is-active libvirtd
  inactive

  $ systemctl is-active libvirt-bin
  active

  
  - Test case 2 - sshd

  alias service : sshd
  aliased service : ssh

  /ect/systemd/system$ ls -la sshd.service 
  lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> 
/lib/systemd/system/ssh.service

  $ systemctl is-active sshd
  inactive

  $ systemctl is-active ssh
  active

  
  [Regression Potential]

  This fix may result into systemctl reporting inconsistent information
  concerning the status of a service.

  [Other]

  Upstream issue : https://github.com/systemd/systemd/issues/7875
  Upstream fix : https://github.com/systemd/systemd/pull/7997

  Xenial is affected, fix exists on Bionic onward.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu21.21
Candidate: 229-4ubuntu21.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Marc Deslauriers

** Bug watch added: gitlab.com/federicomenaquintero/bzip2/issues #24
   https://gitlab.com/federicomenaquintero/bzip2/issues/24

** Also affects: bzip2 via
   https://gitlab.com/federicomenaquintero/bzip2/issues/24
   Importance: Unknown
   Status: Unknown

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  Unknown
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-28 Thread Dan Streetman

> Would it also be possible to mark the "upstream" test "flaky" or turn
it off altogether

I'll have to defer to @xnox on that...personally I would prefer to leave
it on and try to fix whatever is causing the test(s) to be flaky, and/or
disable only individual upstream tests instead of marking all of them
flaky.

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |
  | updated  | 2019-05-16T07:00:42Z

[Touch-packages] [Bug 1833013] Re: Interactive prompt during non-interactive install

2019-06-28 Thread Robie Basak

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

> `apt-get install -y -qq ansible`

This does not guarantee a non-interactive run. If you want a non-
interactive run, you must use all the necessary parameters. For example:

UCF_FORCE_CONFOLD=1 DEBIAN_FRONTEND=noninteractive apt-get -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
-qq -y install ansible

See the dpkg and ucf documentation to set the default behaviour as you
actually want it.

Perhaps this could be better documented in apt-get(8). The -y option
there refers to apt-get itself only and does not apply to underlying
dpkg behaviour and debconf and ucf calls that might be called from
maintainer scripts that need to interact with the user.

Unfortunately my example above isn't a complete answer either, since
there is no unified "must run non-interactively" directive that
individual package maintainer scripts must follow. In general though
they tend to use dpkg's built-in handling, debconf and ucf when
prompting the user is required, so this should cover most (99%+?) cases.

It's valid to say that we could do with a better unified way of
achieving non-interactivity. However, in today's current design, if
you're not calling apt-get with the appropriate parameters as in my
example above, then it's your script that isn't correctly calling for
non-interactivity. All configuration management tooling that expects
non-interactivity needs to be doing this, and this isn't a workaround -
it's the official CLI interface.

Bug 1747464 is related, though that relates to the default conffile
state in our cloud images, so is a more specific instance of the problem
where _interactive_ use causes unnecessary prompts.

This bug is not valid for openssl, because it isn't a bug for it to
prompt in itself. It is perhaps valid for ansible if ansible itself
incorrectly assumes non-interactivity without requesting it correctly -
I don't if that's the case specifically with Ubuntu's ansible package;
if it is, please describe the detail and change that bug status back to
New.

It would be a valid feature request for Ubuntu to request a more unified
way of requesting non-interactivity, though that would be a major effort
as it would require changes across the stack, and wouldn't be of
particularly high priority as we have a good enough (if non-obvious) way
of achieving the same thing today (my example above). Specific requests
to make this clear in documentation would also be valid. Please file
separate bugs for those if you wish. I hope though that I've described
adequately above why the behaviour you describe isn't itself a bug in
the base packages.


** Changed in: openssl (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Interactive prompt during non-interactive install

Status in ansible package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  `apt-get install -y -qq ansible` runs `whiptail --backtitle Package
  configuration --title Configuring libssl1.1:amd64 --output-fd 11
  --defaultno --yesno -- There are services installed on your system
  which need to be restarted  when certain libraries, such as libpam,
  libc, and libssl, are upgraded.  Since these restarts may cause
  interruptions of service for the system,  you will normally be
  prompted on each upgrade for the list of services  you wish to
  restart.  You can choose this option to avoid being  prompted;
  instead, all necessary restarts will be done for you  automatically so
  you can avoid being asked questions on each library  upgrade.  Restart
  services during package upgrades without asking? 16 77`, causing a
  non-interactive installation to be impossible.

  Also reported to the Ansible Local Vagrant provisioner because they
  will probably have to work around this in the short term:
  https://github.com/hashicorp/vagrant/issues/10914

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+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 1832458] Re: [SRU] 2.60.3

2019-06-28 Thread Iain Lane

I verified 2.60.3-1~ubuntu19.04.1 according to the first post.

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

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

Title:
  [SRU] 2.60.3

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  Upstream have release 2.60.3 in the 2.60 series

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure no autopkgtests are regressed by this upload. Suggestion for
  something explicit to test would be epiphany on secure websites.

  [ Regression potential ]

  A broken glib-networking could affect various applications' ability to
  use networking properly, particularly TLS.

  [ Upstream NEWS ]

  2.60.3 - June 9, 2019
  =

  - Fix clobbering of the thread-default main context after certificate
verification failure during async handshakes since 2.60.1 (#85)
  - Fix GTlsDatabase initialization failures in OpenSSL backend due to
uninitialized memory use
  - Fix minor leak of ALPN protocols

  2.60.2 - May 2, 2019
  

  - OpenSSL backend now defaults to system trust store (#62)
  - Fix client auth failure error with GnuTLS 3.6.7 (#70)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

2019-06-28 Thread Sebastien Bacher

Thanks, I can't confirm those problems but the patch seems indeed a distro 
divergence we don't need, remove it now in the packaging vcs
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?id=227d3ade 

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1833013] Re: Interactive prompt during non-interactive install

2019-06-28 Thread Dmitrii Shcherbakov

Looks like it was introduced by this:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832522

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

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

Title:
  Interactive prompt during non-interactive install

Status in ansible package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  New

Bug description:
  `apt-get install -y -qq ansible` runs `whiptail --backtitle Package
  configuration --title Configuring libssl1.1:amd64 --output-fd 11
  --defaultno --yesno -- There are services installed on your system
  which need to be restarted  when certain libraries, such as libpam,
  libc, and libssl, are upgraded.  Since these restarts may cause
  interruptions of service for the system,  you will normally be
  prompted on each upgrade for the list of services  you wish to
  restart.  You can choose this option to avoid being  prompted;
  instead, all necessary restarts will be done for you  automatically so
  you can avoid being asked questions on each library  upgrade.  Restart
  services during package upgrades without asking? 16 77`, causing a
  non-interactive installation to be impossible.

  Also reported to the Ansible Local Vagrant provisioner because they
  will probably have to work around this in the short term:
  https://github.com/hashicorp/vagrant/issues/10914

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+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 1834622] Re: package console-setup 1.178ubuntu2.9 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 10

2019-06-28 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package console-setup 1.178ubuntu2.9 failed to install/upgrade:
  installed console-setup package post-installation script subprocess
  returned error exit status 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  the upgrade fails

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.178ubuntu2.9
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Fri Jun 28 10:38:20 2019
  ErrorMessage: installed console-setup package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-09-03 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.11
  SourcePackage: console-setup
  Title: package console-setup 1.178ubuntu2.9 failed to install/upgrade: 
installed console-setup package post-installation script subprocess 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/console-setup/+bug/1834622/+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 1834622] [NEW] package console-setup 1.178ubuntu2.9 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 10

2019-06-28 Thread KORiNEZA

Public bug reported:

the upgrade fails

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: console-setup 1.178ubuntu2.9
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Fri Jun 28 10:38:20 2019
ErrorMessage: installed console-setup package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2018-09-03 (297 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.11
SourcePackage: console-setup
Title: package console-setup 1.178ubuntu2.9 failed to install/upgrade: 
installed console-setup package post-installation script subprocess returned 
error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package console-setup 1.178ubuntu2.9 failed to install/upgrade:
  installed console-setup package post-installation script subprocess
  returned error exit status 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  the upgrade fails

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.178ubuntu2.9
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Fri Jun 28 10:38:20 2019
  ErrorMessage: installed console-setup package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-09-03 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.11
  SourcePackage: console-setup
  Title: package console-setup 1.178ubuntu2.9 failed to install/upgrade: 
installed console-setup package post-installation script subprocess 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/console-setup/+bug/1834622/+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 1834606] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-06-28 Thread Jorma Hytonen

Public bug reported:


sudo apt install --reinstall avahi-daemon

invoke-rc.d: initscript avahi-daemon, action "restart" failed.
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since pe 2019-06-28 11:54:00 EEST; 29ms 
ago
  Process: 3812 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
 Main PID: 3812 (code=exited, status=255)
   Status: "avahi-daemon 0.6.32-rc starting up."

kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc starting up.
kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully called chroot().
kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully dropped remaining 
capabilities.
kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Loading service file 
/services/udisks.service.
kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Failed to create server: Invalid 
domain name
kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc exiting.
kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Main process exited, 
code=exited, status=255/n/a
kesä 28 11:54:00 dv5000 systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Unit entered failed 
state.
kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Failed with result 
'exit-code'.
dpkg: error processing package avahi-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 avahi-daemon

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 avahi-daemon: Install
 avahi-daemon: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jun 28 11:54:00 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-01-23 (1251 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: avahi
Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.avahi-daemon:
 # 1 = Try to detect unicast dns servers that serve .local and disable avahi in
 # that case, 0 = Don't try to detect .local unicast dns servers, can cause
 # troubles on misconfigured networks
 AVAHI_DAEMON_DETECT_LOCAL=0
mtime.conffile..etc.avahi.avahi-daemon.conf: 2016-01-23T18:21:30.589405
mtime.conffile..etc.default.avahi-daemon: 2016-01-24T19:26:59.568985

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


** Tags: amd64 apport-package xenial

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  
  sudo apt install --reinstall avahi-daemon

  invoke-rc.d: initscript avahi-daemon, action "restart" failed.
  ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
 Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since pe 2019-06-28 11:54:00 EEST; 29ms 
ago
Process: 3812 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
   Main PID: 3812 (code=exited, status=255)
 Status: "avahi-daemon 0.6.32-rc starting up."

  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc starting 
up.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully called chroot().
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully dropped remaining 
capabilities.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Loading service file 
/services/udisks.service.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Failed to create server: Invalid 
domain name
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc exiting.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Main process 
exited, code=exited, status=255/n/a
  kesä 28 11:54:00 dv5000 systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Unit entered failed 
state.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Failed with result 
'exit-code'.
  dpkg: error processing package avahi-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:

[Touch-packages] [Bug 1834606] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-06-28 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  
  sudo apt install --reinstall avahi-daemon

  invoke-rc.d: initscript avahi-daemon, action "restart" failed.
  ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
 Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since pe 2019-06-28 11:54:00 EEST; 29ms 
ago
Process: 3812 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
   Main PID: 3812 (code=exited, status=255)
 Status: "avahi-daemon 0.6.32-rc starting up."

  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc starting 
up.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully called chroot().
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Successfully dropped remaining 
capabilities.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Loading service file 
/services/udisks.service.
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: Failed to create server: Invalid 
domain name
  kesä 28 11:54:00 dv5000 avahi-daemon[3812]: avahi-daemon 0.6.32-rc exiting.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Main process 
exited, code=exited, status=255/n/a
  kesä 28 11:54:00 dv5000 systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Unit entered failed 
state.
  kesä 28 11:54:00 dv5000 systemd[1]: avahi-daemon.service: Failed with result 
'exit-code'.
  dpkg: error processing package avahi-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   avahi-daemon

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
  Uname: Linux 4.4.0-154-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   avahi-daemon: Install
   avahi-daemon: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun 28 11:54:00 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-23 (1251 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.avahi-daemon:
   # 1 = Try to detect unicast dns servers that serve .local and disable avahi 
in
   # that case, 0 = Don't try to detect .local unicast dns servers, can cause
   # troubles on misconfigured networks
   AVAHI_DAEMON_DETECT_LOCAL=0
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2016-01-23T18:21:30.589405
  mtime.conffile..etc.default.avahi-daemon: 2016-01-24T19:26:59.568985

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1834606/+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 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2019-06-28 Thread Vlad Orlov

No, Debian package doesn't have this change. As for the bug reports, I
only found a mention of this issue in a report for dpkg:
https://bugs.debian.org/774794

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

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers

2019-06-28 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Fix Released => Confirmed

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

Title:
  The wlan/bt hotkey doesn't work for all Dell Latitude and Precision
  computers

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * All Dell Latitude and Precision computer users can not use the
  wlan/bt hotkey.

  [Test Case]

   * Use any Dell Latitude and Precision computer to check the wlan/bt
  hotkey.

   * If you don't have the computer above, you can use the following
  command to check, and the expected output is "KEYBOARD_KEY_88=!wlan"
  instead of "KEYBOARD_KEY_88=!".

   `systemd-hwdb query
  
evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  | grep KEYBOARD_KEY_88`

  [Regression Potential]

   * No regression

  [Other Info]

   * None

  Just install the official Ubuntu 18.10 on any Dell Latitude or
  Precision computer and press wlan/bt hotkey on the keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 15:37:41 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  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:5520 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.0.24
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1834578] Re: Mouse stop working

2019-06-28 Thread Daniel van Vugt

Your kernel log shows it is having trouble with the mouse. This might be
a fault with the mouse or the USB port. It might also be a kernel bug,
but that's less likely...

[  551.252894] usb 1-6: reset low-speed USB device number 3 using xhci_hcd
[  551.520701] usb 1-6: device descriptor read/64, error -71
[  556.957250] usb 1-6: reset low-speed USB device number 3 using xhci_hcd
[  557.733478] usb 1-6: USB disconnect, device number 3
[  558.061164] usb 1-6: new low-speed USB device number 4 using xhci_hcd
[  558.212826] usb 1-6: New USB device found, idVendor=046d, idProduct=c05a
[  558.212832] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  558.212837] usb 1-6: Product: USB Optical Mouse
[  558.212841] usb 1-6: Manufacturer: Logitech
[  558.215745] input: Logitech USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:046D:C05A.0005/input/input15
[  558.216101] hid-generic 0003:046D:C05A.0005: input,hidraw3: USB HID v1.11 
Mouse [Logitech USB Optical Mouse] on usb-:00:14.0-6/input0
[  687.645465] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[  777.148862] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[  777.417072] usb 1-6: Device not responding to setup address.
[  777.625107] usb 1-6: Device not responding to setup address.
[  777.832620] usb 1-6: device not accepting address 4, error -71
[  778.100621] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[ 1095.999728] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[ 1096.267472] usb 1-6: device descriptor read/64, error -71
[ 1096.643504] usb 1-6: device descriptor read/64, error -71
[ 1097.019526] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[ 1097.287539] usb 1-6: device descriptor read/64, error -71
[ 1097.663495] usb 1-6: device descriptor read/64, error -71
[ 1098.039490] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[ 1098.039923] usb 1-6: Device not responding to setup address.
[ 1098.247947] usb 1-6: Device not responding to setup address.
[ 1098.455509] usb 1-6: device not accepting address 4, error -71
[ 1098.723506] usb 1-6: reset low-speed USB device number 4 using xhci_hcd
[ 1098.723945] usb 1-6: Device not responding to setup address.
[ 1098.931938] usb 1-6: Device not responding to setup address.
[ 1099.139470] usb 1-6: device not accepting address 4, error -71
[ 1099.139617] usb 1-6: USB disconnect, device number 4
[ 1099.327521] usb 1-6: new low-speed USB device number 5 using xhci_hcd
[ 1099.455500] usb 1-6: device descriptor read/64, error -71
[ 1099.691465] usb 1-6: device descriptor read/64, error -71
[ 1099.927528] usb 1-6: new low-speed USB device number 6 using xhci_hcd
[ 1100.055542] usb 1-6: device descriptor read/64, error -71
[ 1100.291539] usb 1-6: device descriptor read/64, error -71
[ 1100.399599] usb usb1-port6: attempt power cycle
[ 1101.055512] usb 1-6: new low-speed USB device number 7 using xhci_hcd
[ 1101.055908] usb 1-6: Device not responding to setup address.
[ 1101.263962] usb 1-6: Device not responding to setup address.
[ 1101.471513] usb 1-6: device not accepting address 7, error -71
[ 1101.599512] usb 1-6: new low-speed USB device number 8 using xhci_hcd
[ 1101.599924] usb 1-6: Device not responding to setup address.
[ 1101.807962] usb 1-6: Device not responding to setup address.
[ 1102.015541] usb 1-6: device not accepting address 8, error -71
[ 1102.015632] usb usb1-port6: unable to enumerate USB device
[ 1143.931796] usb 1-6: new low-speed USB device number 9 using xhci_hcd
[ 1144.083477] usb 1-6: New USB device found, idVendor=046d, idProduct=c05a
[ 1144.083483] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1144.083487] usb 1-6: Product: USB Optical Mouse

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

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

Title:
  Mouse stop working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB mouse stop working randomly

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
  Uname: Linux 4.15.0-53-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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 28 10:24:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant:

[Touch-packages] [Bug 1834578] [NEW] Mouse stop working

2019-06-28 Thread Mehmet Dayıpoğlu

Public bug reported:

USB mouse stop working randomly

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
Uname: Linux 4.15.0-53-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.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 28 10:24:54 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 4.15.0-52-generic, x86_64: installed
 nvidia, 390.116, 4.15.0-53-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d3]
InstallationDate: Installed on 2018-09-21 (280 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 009: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
 Bus 001 Device 002: ID 0518:5111 EzKEY Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic 
root=UUID=8e5738ba-3515-4603-abfb-a837482ef7ba ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0809
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B250M-K
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.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  Mouse stop working

Status in xorg package in Ubuntu:
  New

Bug description:
  USB mouse stop working randomly

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
  Uname: Linux 4.15.0-53-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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 28 10:24:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-52-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-53-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA

[Touch-packages] [Bug 1834566] [NEW] Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2019-06-28 Thread Robert Davenport

Public bug reported:

Unable to get system speakers working running 19.04.  At max volume,
sound is barely perceptible through headphones.  Pavucontrol shows
sounds is present, but no amount of adjustments makes a difference.

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
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  robert 3355 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jun 28 00:44:13 2019
InstallationDate: Installed on 2019-06-05 (22 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
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_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02AHK.029.190425.PS
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP930MBE-K04US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
dmi.product.family: Notebook 9 Series
dmi.product.name: 930MBE
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
dmi.product.version: P02AHK
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug 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/1834566

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  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
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+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

59 matches

Mail list logo