date:20181217

@Ben

patch_realtek.c is missing under
/lib/modules/4.20.0-042000rc7-generic/kernel/sound/pci/hda/ after
installing 4.20.0-rc7 kernel.

Can't find it elsewhere either.

How do you properly applied those 3 patches?

And the proper command is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
ALC294_FIXUP_ASUS_SPK)

You forgot to close the brackets.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1764628] Comment bridged from LTC Bugzilla

2018-12-17 Thread bugproxy

--- Comment From bssrika...@in.ibm.com 2018-12-18 01:25 EDT---
(In reply to comment #18)
> IBM, Xenial-updates is currently on version
> (https://packages.ubuntu.com/xenial-updates/util-linux) util-linux
> (2.27.1-6ubuntu3.6) could you please retest and confirm that this is now
> fixed ?

No. Issue still present:

root@guest:~# dpkg -l | grep util-linux
ii  util-linux2.27.1-6ubuntu3.6 
 ppc64el  miscellaneous system utilities
root@guest:~# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):64
On-line CPU(s) list:   0-63
Thread(s) per core:4
Core(s) per socket:8
Socket(s): 2
NUMA node(s):  1
Model: 2.0 (pvr 004d 0200)
Model name:POWER8 (architected), altivec supported
Hypervisor vendor: horizontal
Virtualization type:   full
L1d cache: 64K
L1i cache: 32K
NUMA node0 CPU(s): 0-63

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

2018-12-17 Thread maria smith

In both cases, no network, no static IP address, .. however, restarting 
systemd-networkd instantly brings the configuration up, and communication on 
the desired IP address starts.
If anyone face laptop problem gets help from this http://lenovotechsupport.com

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1808493] Re: Let's Encrypt CA Root Certificates missing

2018-12-17 Thread Oliver

looks now working :(

openssl s_client -connect letsencrypt.org:443

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

Title:
  Let's Encrypt CA Root Certificates missing

Status in ca-certificates package in Ubuntu:
  Incomplete

Bug description:
  Please add the Chain of trust for the Let's Encrypt CA to the ubuntu
  ca-certificates

  https://letsencrypt.org/certificates/


  we have to add them always manually and i think it's time to accept,
  that let's encrypt is now one of the bigger CA.

  
  Missing in releases 16.04  LTS / 18.04 LTS

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

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

[Touch-packages] [Bug 1623383] Re: Some restarts fail due to missing base devices

2018-12-17 Thread maria smith

The system LPAR this was seen first was an upgrade from Xenial but since then 
has been freshly installed with Yakkety. The same behaviour is seen on a zVM 
guest running  Yakkety.
If anyone face printer issue click here http://canonprintersupport247.com

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

Title:
  Some restarts fail due to missing base devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Arch: s390x
  Release: Yakkety / 16.10

  This happens on some (but not all) system starts with Yakkety. In
  Xenial (which is using the same 4.4 kernel version the Yakkety systems
  were using when the problem was first observed) this did not happen.
  The system (LPAR) this was seen first was an upgrade from Xenial but
  since then has been freshly installed with Yakkety. The same behaviour
  is seen on a zVM guest running Yakkety.

  The attached syslog shows a failed boot, followed by one that did work. Note 
the "Found device .*(sclp|encc00).*" messages in the good boot. Those are 
missing in the bad attempt and as a result networking and console fail to be 
usable. Also note, those boots were 4.8 kernels but we saw this with 4.4 
kernels, too.
  This might be a systemd problem / race, I just filed it into udev for now as 
that better matches the not finding basic devices symptom.

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

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

[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

2018-12-17 Thread hackel

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

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1808909] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-12-17 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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808909

Title:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  I am trying to upgrade 16.04 to 18.04, but I am encountering the
  errors as below

  insserv: warning: script is corrupt or invalid: 
/etc/init.d/../rc2.d/S01shm_load
  insserv: Script oracle-xe is broken: missing end of LSB comment

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   util-linux: Configure
   mysql-server-5.7: Configure
   mysql-server: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec 17 22:00:50 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-24 (814 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.19
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-12-18 (0 days ago)

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

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

[Touch-packages] [Bug 1808909] [NEW] package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-12-17 Thread Karthikeyan Ponnusamy

Public bug reported:

I am trying to upgrade 16.04 to 18.04, but I am encountering the errors
as below

insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S01shm_load
insserv: Script oracle-xe is broken: missing end of LSB comment

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.6
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 util-linux: Configure
 mysql-server-5.7: Configure
 mysql-server: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Dec 17 22:00:50 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-09-24 (814 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.19
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-12-18 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  I am trying to upgrade 16.04 to 18.04, but I am encountering the
  errors as below

  insserv: warning: script is corrupt or invalid: 
/etc/init.d/../rc2.d/S01shm_load
  insserv: Script oracle-xe is broken: missing end of LSB comment

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   util-linux: Configure
   mysql-server-5.7: Configure
   mysql-server: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec 17 22:00:50 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-24 (814 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.19
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-12-18 (0 days ago)

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

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

[Touch-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911

[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/1713448

Title:
  Adobe Reader doesn't print on OKI C911

Status in cups package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Out and over.
  I tried whatever I could think of, but whatever I send there, anything will 
make the printer blink, 'processing', forever, until I cancel the job. 
  The printer, however, prints the same files from okular, and from all other 
applications that I have tried so far. This would clearly point to acroread. 
  However, acroread prints to all other printers that we have standing about 
without any problem. 

  Logically, from what I could state so far, we have an AND-combination:
  everything works, except I print a file from acroread through OKI
  C911.

  Since I have other printers and other PDF-software, it is minor. And yet, I 
wouldn't mind helping to debug this thing.
  I'm using the OKI-provided ppd with cups. 

  adobereader-enu:i386 9.5.5
  cups 2.1.3-4
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of 
/var/cache/cups/job.cache.
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of 
/var/cache/cups/job.cache.
   E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of 
/var/cache/cups/job.cache.
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-04-01 (1247 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  Lpstat:
   device for BrotherColourMFC9970: socket://134.91.100.26:9100
   device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: 
dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/
   device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/
   device for Samsung_M262x_282x_Series: 
dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/
  MachineType: LENOVO 2924WEG
  Package: linux
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', 
'/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', 
'/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: 
Permission denied
   grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied
   grep: 
/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Tags:  xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924WEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2924WEG
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

2018-12-17 Thread maria smith

you can Add a device, and assign two IPv4 addresses. First one, with a short
lease time. Second one, with a different ip and a longer lease time.
If anyone face printer issue click here http://HPsupport365.com

** Attachment added: "printer.png"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721223/+attachment/5223123/+files/printer.png

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

Title:
Networkd fail to set ip address between leases if ip address changes
on UbuntuCore

Status in Snappy:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Zesty:
Won't Fix
Status in systemd source package in Artful:
Fix Released

Bug description:
[Impact]

* networkd fails to renew a lease, specifically it fails to change IPv4
address via DHCP renew/rebind.
* networkd relies on a kernel feature to promote secondary IPv4 address to
primary, upon primary address lease expiry.
* this sysctl tunable was not enabled by default in systemd.

[Test Case]

Add a device, and assign two IPv4 addresses. First one, with a short
lease time. Second one, with a different ip and a longer lease time.
Second one should be treated as secondary ip address, and upon expiry
of the first one, should be promoted and become primary ip address.
The below scripted instructions simulate this:

sudo ip link add name testleases type dummy

sudo ip address add 192.0.2.10/27 dev testleases \
valid_lft 5 preferred_lft 5

sudo ip address add 192.0.2.11/27 dev testleases \
valid_lft 11 preferred_lft 11

ip address list dev testleases | \
grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
&& echo ok || echo not ok

ip address list dev testleases | \
grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
&& echo ok || echo not ok

sleep 6

ip address list dev testleases | \
grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
&& echo ok || echo not ok

sudo ip link del dev testleases

[Regression Potential]

* This changes the default kernel behaviour, previously upon expiry
of the primary address, secondary addresses were removed as well.
Which is imho silly.

* comparing networkd renewal with isc-dhcp renewal the semantics are
quite different. Upon acquiring new ip address, isc-dhcp would
instantly flush existing ip address, and add a new one. Networkd add
the new address as secondary, and waits for old one to expire first
before promoting / switching to using the new ip address. IMHO kernel
should have an API to promote secondary ip address to a primary one.

* This update also applies other safe-looking options, which are
currently also already applied via sysctls shipped in other packages

# Source route verification
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1

# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0

# Enable hard and soft link protection
fs.protected_hardlinks = 1
fs.protected_symlinks = 1

* This update also applies the following upstream/bufferbloat.net
recommended setting

# Fair Queue CoDel packet scheduler to fight bufferbloat
net.core.default_qdisc = fq_codel

* [~racb] There are complex network setups out there, such as HA with
corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
fix were SRU'd, will all of these things in the wild cope with this
sysctl change?

[Other Info]

* Original bug report

Hi there,
we found a replicable issue that involves the Ubuntu Core networking and
causes complete loss of connectivity.
We run a custom board with ubuntu core: the architecure is amrhf.
We replicated this issue with an official Ubuntu Core image on a Raspberry
Pi: other platform was been tested.
It shows that it is a snap core problem which interests networkd: we use the
default network stack based on networkd + netplan.

Below steps to replicate the issue.

1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes).
2)Boot the board and wait for get an ip from dhcp server
3)Before the lease expires, set a reservation for a different ip address

Depending on lease duration before the lease expires( for 10 minute we have 2
minutes before ), networkd configure the new address in addition to the
previous one.
When the lease expire both ip address ( the prevoius and the new one )
disappear from the interested network interface.
Depending on lease duration before the second lease expires ( for 10 minure
we have 2 minutes before ) networkd configure only the new ip address on the
network interface and the ping toward an outside host work properly.

During

[Touch-packages] [Bug 1808806] Re: ????

2018-12-17 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  

Status in xorg package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec 17 13:48:00 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:078c]
  InstallationDate: Installed on 2018-11-16 (30 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
   LANGUAGE=fr_LU:fr
   PATH=(custom, no user)
   LANG=fr_LU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed 
root=UUID=12ce8976-9f9f-49bf-ae0c-ba49a024ad56 ro locale=fr_FR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.1
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.1:bd04/20/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Dec 17 10:02:54 2018
  xserver.configfile: default
  xserver.errors:
   evdev: "USB OPTICAL MOUSE ": Unable to open evdev device "/dev/input/event7".
   PreInit returned 2 for ""USB OPTICAL MOUSE ""
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5595 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1808493] Re: Let's Encrypt CA Root Certificates missing

2018-12-17 Thread Seth Arnold

Hello Oliver, could you please run the following?

ls -l /etc/ssl/certs/ISRG_Root_X1.pem /usr/share/ca-
certificates/mozilla/ISRG_Root_X1.crt

(The first file should be a symbolic link to the second file.)

I find the version on my system is identical to the version on the
letsencrypt website, with a bit of mangling:

sarnold@hunt:/tmp$ tr -d '\r' < isrgrootx1.pem.txt | sha256sum
22b557a27055b33606b6559f37703928d3e4ad79f110b407d04986e1843543d1  -
sarnold@hunt:/tmp$ tr -d '\r' < /etc/ssl/certs/ISRG_Root_X1.pem | sha256sum
22b557a27055b33606b6559f37703928d3e4ad79f110b407d04986e1843543d1  -

Thanks

** Changed in: ca-certificates (Ubuntu)
   Status: New => Incomplete

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

Title:
  Let's Encrypt CA Root Certificates missing

Status in ca-certificates package in Ubuntu:
  Incomplete

Bug description:
  Please add the Chain of trust for the Let's Encrypt CA to the ubuntu
  ca-certificates

  https://letsencrypt.org/certificates/


  we have to add them always manually and i think it's time to accept,
  that let's encrypt is now one of the bigger CA.

  
  Missing in releases 16.04  LTS / 18.04 LTS

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

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

[Touch-packages] [Bug 1808826] Re: install intel draphic drivers

Ubuntu already comes with Intel graphics drivers and your logs seem to
show they are working.

What is the problem you are reporting?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  install intel draphic drivers

Status in Ubuntu:
  Incomplete

Bug description:
  for Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 17 07:16:01 2018
  DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:170b]
  InstallationDate: Installed on 2018-11-26 (20 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: Hewlett-Packard HP Z200 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic 
root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago)
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786H3 v01.13
  dmi.board.asset.tag: 2UA12218BX
  dmi.board.name: 0B40h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA12218BX
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786H3v01.13:bd03/09/2011:svnHewlett-Packard:pnHPZ200Workstation:pvr:rvnHewlett-Packard:rn0B40h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z200 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Dec 17 06:37:20 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1808873] [NEW] gdm3 no greeter with two monitors

2018-12-17 Thread Mike

Public bug reported:

Hello,

Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector 
connected by HDMI.
While all the boot messages appear on both devices (if they are turned on) the 
gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a virtual 
console and back (Ctrl+Alt+F2, Ctrl+Alt+F1).

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

** Attachment added: "apport-bug info"
   https://bugs.launchpad.net/bugs/1808873/+attachment/5223090/+files/gdm3bug

** Package changed: console-setup (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  gdm3 no greeter with two monitors

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Hello,

  Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector 
connected by HDMI.
  While all the boot messages appear on both devices (if they are turned on) 
the gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a 
virtual console and back (Ctrl+Alt+F2, Ctrl+Alt+F1).

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

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

[Touch-packages] [Bug 1165014] Re: libsdl1.2-dev:i386 cannot be installed on 64-bit systems

2018-12-17 Thread Juhani Numminen

** Package changed: apt (Ubuntu) => libsdl1.2 (Ubuntu)

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

Title:
  libsdl1.2-dev:i386 cannot be installed on 64-bit systems

Status in libsdl1.2 package in Ubuntu:
  Confirmed

Bug description:
  Platform:
  Ubuntu Precise 12.04.2 LTS 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 
00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  Reference:
  I also refer you to bug #1068374 which is very similar in behaviour.

  Behaviour:
  When I try to bring in libsdl1.2-dev:i386, apt wants to uninstall half my 
system!

  Expectation:
  I would expect the library to be installed seamlessly along with the other 
i386 libraries I had already obtained.

  Detail:
  I was in the throes of installing Neverwinter Nights game natively under 
linux using instructions found on 
"http://ubuntuforums.org/showthread.php?t=113259; and on
  
"http://social.bioware.com/forum/Neverwinter-Nights-1/NwN-1-Technical-Support-Self-help-for-all-versions-and-expansions/nwmouse-and-friends-64bit-linux-5212955-1.html;.
  
  I wanted this package to cross-compile the nwmouse.so component to assist 
with the installation of a hardware mouse within the game.

  Additional:
  Using the instructions for further information requested in bug #1068374 I've 
already attached the output for further analysis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1165014/+subscriptions

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

[Touch-packages] [Bug 1200955] Re: apt-get update fails to fetch http://ppa.launchpad.net

2018-12-17 Thread Juhani Numminen

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

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

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

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

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

Title:
  apt-get update fails to fetch http://ppa.launchpad.net

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu Release 12.04 (precise) 64-bit, Kernel Linux
  3.2.0-49-generic, GNOME 3.4.2

  Failure occurs on any ppa I've tested so far.
  Sample: W: Failed to fetch 
http://ppa.launchpad.net/team-xbmc/ppa/ubuntu/dists/precise/main/binary-amd64/Packages
  403  Forbidden

  I can successfully ping/resolve ppa.launchpad.net

  bug: #1185159 Failing to fetch https sources with apt-get update
  appears to be very similar

  apt:
Installed: 0.8.16~exp12ubuntu10.10
Candidate: 0.8.16~exp12ubuntu10.10
Version table:
   *** 0.8.16~exp12ubuntu10.10 0
  500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.8.16~exp12ubuntu10 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

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

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

[Touch-packages] [Bug 1314428] Re: apt is not essential anymore

2018-12-17 Thread Juhani Numminen

Hi,

Please describe why you've filed this bug. What is the buggy behavior?

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

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

Title:
  apt is not essential anymore

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 14.10 dev with apt 1.0.2ubuntu2 and apt has no
  Essential flag anymore:

  root@ubuntu:~# apt-cache show apt | grep Essential
  Build-Essential: yes

  
  But interestingly if I'm trying to remove apt it claims that it is still 
essential:

  root@ubuntu:~# apt-get remove apt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
apt
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
apt
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 3673 kB disk space will be freed.
  You are about to do something potentially harmful.
  To continue type in the phrase 'Yes, do as I say!'
   ?] 
  Abort.

  
  I don't know what Build-Essential will do here (maybe some sort of 
replacement?) but it is not known to the manual page of deb-src-control and the 
debian documentation: 
https://www.debian.org/doc/debian-policy/ch-controlfields.html

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

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

[Touch-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

2018-12-17 Thread m...@papersolve.com

Just hit me, kernel 4.19.8-liquorix-amd64, Ubuntu 18.10.   I was running
with modesetting, but decided to change to intel driver (freshly
compiled from git) to see if I run into it again (it seems pretty rare
though so will probably be tough to hit).  Has anyone definitely hit it
on xf86-video-intel or only modesetting?

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Incomplete

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Touch-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

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

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

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Incomplete

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-17 Thread Ben

The fixes in the 4.20-rc kernels are for other laptops, not the UX391UA.
You'll need to add:

SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK

to /sound/pci/hda/patch_realtek.c

to get sound working on this laptop.

I used the 4.19.9 kernel, applied the 3 linked patches and added the
line above.  If you're using 4.20-rc6 / 7, you may only need to add the
line to patch_realtek.c

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1808864] [NEW] Poor translation of zh_CN gpasswd(1) man page

2018-12-17 Thread LYF

Public bug reported:

man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

The zh_CN version of gpasswd(1) not only is partially done, but also
contains an error in the first sentence. The translator confused the
verb "administer" with the person "administrator." The section heading,
originally "Notes (noun) about group passwords," was translated as
"Please note (verb) the group passwords." Even Google translate does
better!

Translation errors
==
gpasswd - administer /etc/group and /etc/gshadow
gpasswd - 管理员 /etc/group 和 /etc/gshadow
  ^^ 管理员 -- administrator
 管理 -- administer

Notes about group passwords
请注意组密码
^^ 请注意…… -- please note (v.)
   关于……的说明 -- notes (n.) about

Typos
=
-h, --help
Display help message and exit.

-h, --help
现实帮助信息并退出。
 显示 Xiǎnshì -- display
 现实 Xiànshí -- reality

Correct Google translate results (this but unironically)

"gpasswd - administer /etc/group and /etc/gshadow"
"gpasswd - 管理 /etc/group 和 /etc/gshadow"

"Notes about group passwords"
"关于组密码的说明"

"Display help message and exit."
"显示帮助消息并退出。"

Notes about my system
=
$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
$ apt-cache policy passwd
passwd:
  Installed: 1:4.5-1ubuntu1
  Candidate: 1:4.5-1ubuntu1
  Version table:
 *** 1:4.5-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

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


** Tags: manpage

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

Title:
  Poor translation of zh_CN gpasswd(1) man page

Status in shadow package in Ubuntu:
  New

Bug description:
  man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

  The zh_CN version of gpasswd(1) not only is partially done, but also
  contains an error in the first sentence. The translator confused the
  verb "administer" with the person "administrator." The section
  heading, originally "Notes (noun) about group passwords," was
  translated as "Please note (verb) the group passwords." Even Google
  translate does better!

  Translation errors
  ==
  gpasswd - administer /etc/group and /etc/gshadow
  gpasswd - 管理员 /etc/group 和 /etc/gshadow
^^ 管理员 -- administrator
   管理 -- administer

  Notes about group passwords
  请注意组密码
  ^^ 请注意…… -- please note (v.)
 关于……的说明 -- notes (n.) about

  Typos
  =
  -h, --help
  Display help message and exit.

  -h, --help
  现实帮助信息并退出。
   显示 Xiǎnshì -- display
   现实 Xiànshí -- reality

  Correct Google translate results (this but unironically)
  
  "gpasswd - administer /etc/group and /etc/gshadow"
  "gpasswd - 管理 /etc/group 和 /etc/gshadow"

  "Notes about group passwords"
  "关于组密码的说明"

  "Display help message and exit."
  "显示帮助消息并退出。"

  Notes about my system
  =
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy passwd
  passwd:
Installed: 1:4.5-1ubuntu1
Candidate: 1:4.5-1ubuntu1
Version table:
   *** 1:4.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-17 Thread spm2011

** Description changed:

  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).
  
+ UnreportableReason:
+  Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
+  warning: core file may not match specified executable file.
+ 
+ 
  Expected: able to report ?
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
-  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
-  ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
+  ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
+  ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  UnreportableReason:
   Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: 
expected core file size >= 1245646848, found: 760283136
   warning: core file may not match specified executable file.

  
  Expected: able to report ?

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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

[Touch-packages] [Bug 1808861] [NEW] chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated

2018-12-17 Thread spm2011

Public bug reported:

Trying to report a crash in chromium-browser, get Unreportable reason
Invalid core dump: BFD: warning apport_core is truncated (see
screenshot, can't copy message from apport dialog - bug # 1273752).

Expected: able to report ?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.5
ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportLog:
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 17 15:30:28 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-09-12 (96 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "chromium-browser_invalid_core_dump.png"
   
https://bugs.launchpad.net/bugs/1808861/+attachment/5223066/+files/chromium-browser_invalid_core_dump.png

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  chromium-browser crash Unreportable - Invalid core dump: BFD: warning:
  apport_core is truncated

Status in apport package in Ubuntu:
  New
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Trying to report a crash in chromium-browser, get Unreportable reason
  Invalid core dump: BFD: warning apport_core is truncated (see
  screenshot, can't copy message from apport dialog - bug # 1273752).

  Expected: able to report ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.5
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportLog:
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, 
signal 5, core limit 0, dump mode 1
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: 
/usr/lib/chromium-browser/chromium-browser (command line 
"/usr/lib/chromium-browser/chromium-browser\ --enable-pinch")
   ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report 
/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 15:30:28 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (96 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago)

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

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

[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-17 Thread Brian Murray

** Changed in: software-properties (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: software-properties (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  In Progress
Status in software-properties source package in Bionic:
  In Progress
Status in software-properties source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

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

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Installed 4.20.0-rc7 kernel through UKUU, but still no sound on ASUS
UX391U :/

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-17 Thread Brian Murray

** Description changed:

+ [Impact]
+ software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.
+ 
+ [Test Case]
+ We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.
+ 
+ [Regression Potential]
+ We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.
+ 
+ [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Also affects: software-properties (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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1807373

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  In Progress
Status in software-properties source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

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

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

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

[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-17 Thread Brian Murray

** Changed in: software-properties (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: software-properties (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  In Progress
Status in software-properties source package in Cosmic:
  In Progress

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

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

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

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

2018-12-17 Thread David Coronel

I tested the systemd 229-4ubuntu21.11 package from xenial-proposed in
Ubuntu 16.04 in KVM and also confirm I cannot reproduce the issue with
this updated package:

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial

# dpkg -l | grep 229-4ubuntu21.11
ii  libpam-systemd:amd64 229-4ubuntu21.11   
amd64system and service manager - PAM module
ii  libsystemd0:amd64229-4ubuntu21.11   
amd64systemd utility library
ii  systemd  229-4ubuntu21.11   
amd64system and service manager

# mkdir -p bind-test/abc 
# mount --bind bind-test bind-test 
# mount -t tmpfs tmpfs bind-test/abc 
# umount bind-test/abc 
# systemctl list-units --all | grep bind-test 
  root-bind\x2dtest.mount 
loadedactive   mounted   /root/bind-test

+1, LGTM

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

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

Bug description:
  [Impact]

  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345

  [Test Case]

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  Expected outcome (w/ the fix) :

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  [Regression Potential]

  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is
  easily adaptable because the current function mount_setup_unit() is
  dealing with both of at the moment instead of being individually
  separate in two distinct function.

  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()

  This patch changes mount_setup_unit() to prevent the just_mounted
  mount setup flag from being overwritten if it is set to true. This
  will allow all mount units created from /proc/self/mountinfo entries
  to be initialised properly.

  Additionally, the patch got the blessing of 'xnox' who looked at it
  and mention it looks fine to him.

  [Pending SRU]

  Note: No autopkgtests has been reported since systemd (21.5) ...
  between 21.5 and now (21.11) everything released has been about
  security fixes :

  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU

  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz

  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic

  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.

  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.

  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz

  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could
  not create NMClient object: Cannot invoke method; proxy is for a well-
  known name without an owner and

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-17 Thread VanVan

Audio fixes start with Linux 4.20-rc6, not 4.19

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

@Greg (buchovagabond)

Without adding those 3 patches and the SND_PCI_QUIRK(0x1043, 0x10a1,
"ASUS UX391UA", ALC294_FIXUP_ASUS_SPK) tweak to to
/sound/pci/hda/patch_realtek.c ?

So only updating with UKUU will work?

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-17 Thread chovy

Confirmed 4.19 fixes audio! Excellent work guys!

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

[VERIFICATION XENIAL]

I confirm that this specific bug is now fix with that proposed package.


# Confirmation of the use of proposed systemd packages:

ii  libpam-systemd:amd64229-4ubuntu21.11
   amd64system and service manager - PAM module
ii  libsystemd0:amd64   229-4ubuntu21.11
   amd64systemd utility library
ii  libudev1:amd64  229-4ubuntu21.11
   amd64libudev shared library
ii  systemd 229-4ubuntu21.11
   amd64system and service manager
ii  systemd-sysv229-4ubuntu21.11
   amd64system and service manager - SysV links
ii  udev229-4ubuntu21.11
   amd64/dev/ and hotplug management daemon


# Confirmation that I ran the test on xenial

root@ubuntu:/tmp# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"


# Reproducer as describe in upstream bug and above in the SRU tmpl:

root@ubuntu:/tmp# mkdir -p bind-test/abc
root@ubuntu:/tmp# mount --bind bind-test bind-test
root@ubuntu:/tmp# mount -t tmpfs tmpfs bind-test/abc
root@ubuntu:/tmp# umount bind-test/abc
root@ubuntu:/tmp# systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loadedactive   mounted   /tmp/bind-test
 


I also did some dogfooding here and there, BUT, since systemd is a pretty 
critical piece, I would appreciate more feedback from other impacted users 
before I can proceed with the release in xenial-updates. 

Meaning I won't change this bug to "verification-done-xenial" until
then. I'll return from vacation on the week of January 7th (mid-week)
which will give us a reasonable amount of time for impacted users and
other volunteers to test this new proposed package.

- Eric

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

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

Bug description:
  [Impact]

  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345

  [Test Case]

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  Expected outcome (w/ the fix) :

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  [Regression Potential]

  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is
  easily adaptable because the current function mount_setup_unit() is
  dealing with both of at the moment instead of being individually
  separate in two distinct function.

  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()

  This patch changes mount_setup_unit() to prevent the just_mounted
  mount setup flag from being overwritten if it is set to true. This
  will allow all mount units created from /proc/self/mountinfo entries
  to be initialised properly.

  Additionally, the patch got the blessing of 'xnox' who looked at it
  and mention it looks fine to him.

  [Pending SRU]

  Note: No autopkgtests has been reported since systemd (21.5) ...
  between 21.5 and now (21.11) everything released has been about
  security fixes :

  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU

  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz

  Error:
  modprobe: FATAL: Module cfg80211 not found in

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-17 Thread Greg

I just saw that the fix is included in the new 4.19.10 kernel. You can
use UKUU to install.

---
Jian-Hong Pan (2):
  ALSA: hda/realtek: Enable audio jacks of ASUS UX533FD with ALC294
  ALSA: hda/realtek: Enable audio jacks of ASUS UX433FN/UX333FA with ALC294

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1808836] [NEW] Adding 64-bit libs for Skype rendered Lenovo G50 laptop unbootable

2018-12-17 Thread Silas S. Brown

Public bug reported:

I used a standard Lubuntu 18.04 LTS i386-destkop live CD to install on a
Lenovo G50 laptop, the install went well and booted into the new system
nicely, but then I remembered this user might want Skype, so I
downloaded the Skype deb and found it was amd64-only.  The laptop was
64-bit capable but I had only brought an i386 CD.

So I did a "dpkg --add-architecture amd64" and an "apt-get update" and
"apt-get install linux-image-generic:amd64" (and reboot) and then tried
to apt-get the libraries that dpkg was complaining about when I'd tried
to install the Skype deb.  This caused apt-get to cascade into changing
half the system to amd64 and I had to do "apt-get -f install" a few
times, one of which told me I was about to remove essential packages,
which I thought was OK because it was going to replace them with the
amd64 versions.  But it turned out the replacement process involved
removing all old packages before installing all new ones, which is not
so good when one of those packages is dpkg itself: I ended up with the
"cannot exec dpkg" error.  So I manually replaced dpkg (using "ar" and
"tar" to extract the deb) and carried on (and it reinstalled dpkg from
amd64 over the top of my manual replacement), and then I thought
everything was OK, but I was getting a few "timeout" and "dpkg
unexpected number of operations" errors (sorry I don't recall the exact
wording), and then when I rebooted I found the initrd was in an
inconsistent state and the system couldn't boot.  (Editing the GRUB
command to boot single-user and without the "splash" or "quiet" options
showed it didn't get any further than initrd-unpack.)

Worse, I couldn't even boot off the CD again, because the Lenovo G50
folks put the CD-booting code on the hard disk.  If you elect to replace
the existing Windows 8 system with Linux (wiping the hard disk and
installing afresh), as I had, the laptop ends up not being able to give
you the option to boot a CD-ROM or USB stick, because the menu to do
that lived on the hard disk and was wiped by the Linux install.  I tried
going into GRUB's command mode (hold Shift on boot and then press C in
GRUB), but GRUB's "ls" could not see the CD-ROM drive.

Thankfully GRUB could still see USB media, so I took the laptop home and
used UNetbootin to put a 64-bit Lubuntu image onto a memory card and put
in the standard Grub2 commands "insmod chain", "set root=(hd1)",
"chainloader +1" and "boot", then copied off the home directory and made
a clean reinstall on amd64.  So all is well.  But I thought a report of
what happened might still be useful.

Perhaps this bug is Lubuntu-related (as the main Ubuntu is no longer
shipping a 32-bit installer with 18.04, but Lubuntu is).  I first tried
to report at https://bugs.launchpad.net/lubuntu/+filebug but that form
gave me a choice of "LxFind or LxScreenshot" and nothing else.  I am
therefore filing it as a general Ubuntu bug in the hope that somebody
can refile as appropriate.

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

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

Title:
  Adding 64-bit libs for Skype rendered Lenovo G50 laptop unbootable

Status in apt package in Ubuntu:
  New

Bug description:
  I used a standard Lubuntu 18.04 LTS i386-destkop live CD to install on
  a Lenovo G50 laptop, the install went well and booted into the new
  system nicely, but then I remembered this user might want Skype, so I
  downloaded the Skype deb and found it was amd64-only.  The laptop was
  64-bit capable but I had only brought an i386 CD.

  So I did a "dpkg --add-architecture amd64" and an "apt-get update" and
  "apt-get install linux-image-generic:amd64" (and reboot) and then
  tried to apt-get the libraries that dpkg was complaining about when
  I'd tried to install the Skype deb.  This caused apt-get to cascade
  into changing half the system to amd64 and I had to do "apt-get -f
  install" a few times, one of which told me I was about to remove
  essential packages, which I thought was OK because it was going to
  replace them with the amd64 versions.  But it turned out the
  replacement process involved removing all old packages before
  installing all new ones, which is not so good when one of those
  packages is dpkg itself: I ended up with the "cannot exec dpkg" error.
  So I manually replaced dpkg (using "ar" and "tar" to extract the deb)
  and carried on (and it reinstalled dpkg from amd64 over the top of my
  manual replacement), and then I thought everything was OK, but I was
  getting a few "timeout" and "dpkg unexpected number of operations"
  errors (sorry I don't recall the exact wording), and then when I
  rebooted I found the initrd was in an inconsistent state and the
  system couldn't boot.  (Editing the GRUB command to boot single-user
  and without the "splash" or "quiet" options showed it

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

** Description changed:

  [Impact]
  
  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345
  
  [Test Case]
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  Expected outcome (w/ the fix) :
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  [Regression Potential]
  
  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is easily
  adaptable because the current function mount_setup_unit() is dealing
  with both of at the moment instead of being individually separate in two
  distinct function.
  
  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()
  
  This patch changes mount_setup_unit() to prevent the just_mounted mount
  setup flag from being overwritten if it is set to true. This will allow
  all mount units created from /proc/self/mountinfo entries to be
  initialised properly.
  
  Additionally, the patch got the blessing of 'xnox' who looked at it and
  mention it looks fine to him.
  
  [Pending SRU]
  
  Note: No autopkgtests has been reported since systemd (21.5) ... between
  21.5 and now (21.11) everything released has been about security fixes :
  
  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU
  
- Unless security team has some autopkgtests reports elsewhere, the only
- data available I have (to compare) is if the autopkgtests were
- "failling" or "passing" when 21.5 has been pushed. Since then quite a
- few release has been uploaded with no autopkgtests report.
  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz
  
  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic
  
  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.
  
  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.
  
  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz
  
  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not
  create NMClient object: Cannot invoke method; proxy is for a well-known
  name without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
  NMClient object: Cannot invoke method; proxy is for a well-known name
  without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  Justification:
  
  The test are "passing" if ran manually in my own HW :
  
  autopkgtest [15:29:15]: host ; command line: 
/usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file 
/tmp/adt-proposed.out --- qemu 
/var/lib/libvirt/images/autopkgtest-xenial-amd64.img
  .
  Setting up systemd (229-4ubuntu21.11) ...
  Setting up nplan (0.32~16.04.6) ...
  Setting up network-manager (1.2.6-0ubuntu0.16.04.3) ...
  
  test_dhcp6 (__main__.TestNetworkManager) ... ok
  test_bridge_priority (__main__.TestNetworkManager) ... ok
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... ok
  
  I *think* that these test may eventually works, but is it really worth
  it to retry them until success if it works fine outside the

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

Regression in autopkgtest for nplan (amd64): test log

It's failling in the Ubuntu infra but passing when ran manually in my
own HW, here's the full output in attachment: autopkgtest_result.txt

- Eric

** Attachment added: "autopkgtest_result.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795764/+attachment/5223032/+files/autopkgtest_result.txt

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

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

Bug description:
  [Impact]

  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345

  [Test Case]

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  Expected outcome (w/ the fix) :

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  [Regression Potential]

  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is
  easily adaptable because the current function mount_setup_unit() is
  dealing with both of at the moment instead of being individually
  separate in two distinct function.

  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()

  This patch changes mount_setup_unit() to prevent the just_mounted
  mount setup flag from being overwritten if it is set to true. This
  will allow all mount units created from /proc/self/mountinfo entries
  to be initialised properly.

  Additionally, the patch got the blessing of 'xnox' who looked at it
  and mention it looks fine to him.

  [Pending SRU]

  Note: No autopkgtests has been reported since systemd (21.5) ...
  between 21.5 and now (21.11) everything released has been about
  security fixes :

  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU

  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz

  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic

  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.

  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.

  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz

  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could
  not create NMClient object: Cannot invoke method; proxy is for a well-
  known name without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
  NMClient object: Cannot invoke method; proxy is for a well-known name
  without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  Justification:

  The test are "passing" if ran manually in my own HW :

  autopkgtest [15:29:15]: host ; command line: 
/usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file 
/tmp/adt-proposed.out --- qemu 
/var/lib/libvirt/images/autopkgtest-xenial-amd64.img
  .
  Setting up systemd (229-4ubuntu21.11) ...
  Setting

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

Regression in autopkgtest for nplan (amd64): test log

It's failling in the Ubuntu infra but passing when ran manually in my
own HW, here's the full output in attachment: autopkgtest_result.txt

- Eric


** Description changed:

  [Impact]
  
  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345
  
  [Test Case]
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  Expected outcome (w/ the fix) :
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  [Regression Potential]
  
  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is easily
  adaptable because the current function mount_setup_unit() is dealing
  with both of at the moment instead of being individually separate in two
  distinct function.
  
  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()
  
  This patch changes mount_setup_unit() to prevent the just_mounted mount
  setup flag from being overwritten if it is set to true. This will allow
  all mount units created from /proc/self/mountinfo entries to be
  initialised properly.
  
  Additionally, the patch got the blessing of 'xnox' who looked at it and
  mention it looks fine to him.
  
  [Pending SRU]
  
  Note: No autopkgtests has been reported since systemd (21.5) ... between
  21.5 and now (21.11) everything released has been about security fixes :
  
  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU
  
  Unless security team has some autopkgtests reports elsewhere, the only
  data available I have (to compare) is if the autopkgtests were
  "failling" or "passing" when 21.5 has been pushed. Since then quite a
  few release has been uploaded with no autopkgtests report.
  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz
  
  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic
  
  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.
  
  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.
  
  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz
  
  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not
  create NMClient object: Cannot invoke method; proxy is for a well-known
  name without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
  NMClient object: Cannot invoke method; proxy is for a well-known name
  without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  Justification:
  
  The test are "passing" if ran manually in my own HW :
  
  autopkgtest [15:29:15]: host ; command line: 
/usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file 
/tmp/adt-proposed.out --- qemu 
/var/lib/libvirt/images/autopkgtest-xenial-amd64.img
  .
  Setting up systemd (229-4ubuntu21.11) ...
  Setting up nplan (0.32~16.04.6) ...
  Setting up network-manager (1.2.6-0ubuntu0.16.04.3) ...
  
  test_dhcp6 (__main__.TestNetworkManager) ... ok
  test_bridge_priority (__main__.TestNetworkManager) ... ok

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

I have a ASUS UX391UA and finally want to get the sound working.

Is it theoretically possible to apply the above mentioned fix using the
Kernel Update Utility for Ubuntu (https://github.com/teejee2008/ukuu)?

What's the proper way to apply the following patches afterwards?

https://lkml.org/lkml/2018/12/7/158
https://lkml.org/lkml/2018/12/7/160
https://lkml.org/lkml/2018/12/7/159

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

2018-12-17 Thread Jamie Strandboge

@Matt you have both ufw and firewalld installed and running. You should
disable/remove firewalld. Marking this as 'Invalid' for now, but please
feel free to report back if you still see a bug in ufw after addressing
firewalld.

** Changed in: ufw
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Disco)
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Cosmic)
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Bionic)
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Xenial)
   Status: Incomplete => Invalid

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Invalid
Status in ufw source package in Xenial:
  Invalid
Status in ufw source package in Bionic:
  Invalid
Status in ufw source package in Cosmic:
  Invalid
Status in ufw source package in Disco:
  Invalid

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

** Description changed:

  [Impact]
  
  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345
  
  [Test Case]
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  Expected outcome (w/ the fix) :
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  [Regression Potential]
  
  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is easily
  adaptable because the current function mount_setup_unit() is dealing
  with both of at the moment instead of being individually separate in two
  distinct function.
  
  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()
  
  This patch changes mount_setup_unit() to prevent the just_mounted mount
  setup flag from being overwritten if it is set to true. This will allow
  all mount units created from /proc/self/mountinfo entries to be
  initialised properly.
  
  Additionally, the patch got the blessing of 'xnox' who looked at it and
  mention it looks fine to him.
  
  [Pending SRU]
  
  Note: No autopkgtests has been reported since systemd (21.5) ... between
  21.5 and now (21.11) everything released has been about security fixes :
  
  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU
  
  Unless security team has some autopkgtests reports elsewhere, the only
  data available I have (to compare) is if the autopkgtests were
  "failling" or "passing" when 21.5 has been pushed. Since then quite a
  few release has been uploaded with no autopkgtests report.
  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz
  
  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic
  
  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.
  
  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.
  
  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz
  
  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not
  create NMClient object: Cannot invoke method; proxy is for a well-known
  name without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
  NMClient object: Cannot invoke method; proxy is for a well-known name
  without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
  
  Justification:
  
+ The test are "passing" if ran manually in my own HW :
+ 
+ autopkgtest [15:29:15]: host ; command line: 
/usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file 
/tmp/proposed2.out --- qemu /var/lib/libvirt/images/autopkgtest-xenial-amd64.img
+ .
+ Setting up systemd (229-4ubuntu21.11) ...
+ Setting up nplan (0.32~16.04.6) ...
+ Setting up network-manager (1.2.6-0ubuntu0.16.04.3) ...
+ 
+ test_dhcp6 (__main__.TestNetworkManager) ... ok
+ test_bridge_priority (__main__.TestNetworkManager) ... ok
+ test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... ok
+ 
+ 
  * Regression in autopkgtest for nplan (armhf): test log

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

** Also affects: gnome-control-center (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Bionic:
  New
Status in gnome-shell source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   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: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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

[Touch-packages] [Bug 1661809] Re: failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-12-17 Thread Jamie Strandboge

This looks to be a local issue:

insserv: warning: script 'K20.depend.boot' missing LSB tags and overrides
insserv: warning: script 'K20.depend.start' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop between service .depend.boot and plymouth if started
insserv:  loop involving service plymouth at depth 2
insserv:  loop involving service .depend.boot at depth 1
insserv:  loop involving service rsyslog at depth 1
insserv: Starting .depend.boot depends on plymouth and therefore on system 
facility `$all' which can not be true!
...
insserv: Max recursions depth 99 reached
insserv:  loop involving service networking at depth 4
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service .depend.boot and mountkernfs if started
insserv:  loop involving service mountkernfs at depth 1
insserv: There is a loop between service .depend.boot and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package ufw (--purge):
 subprocess installed post-removal script returned error exit status 1

This loop doesn't seem to have anything to do with ufw. Closing for now,
but feel free to reopen if you have specific instructions on how to
reproduce with the ufw deb.

Thanks!

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

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

Title:
  failed to install/upgrade: subprocess installed post-removal script
  returned error exit status 1

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  I purged ufw from the system. systemctl list-unit-files showed UFW
  enabled.

  
  The reason I noticed was firewalld is not starting on boot, firewalld.service 
is running and it loads inactive.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   ufw: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Feb  4 00:04:25 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ufw
  Title: package ufw (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

** Description changed:

  [Impact]
  
  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345
  
  [Test Case]
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  Expected outcome (w/ the fix) :
  
  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
  
  [Regression Potential]
  
  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is easily
  adaptable because the current function mount_setup_unit() is dealing
  with both of at the moment instead of being individually separate in two
  distinct function.
  
  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()
  
  This patch changes mount_setup_unit() to prevent the just_mounted mount
  setup flag from being overwritten if it is set to true. This will allow
  all mount units created from /proc/self/mountinfo entries to be
  initialised properly.
  
  Additionally, the patch got the blessing of 'xnox' who looked at it and
  mention it looks fine to him.
  
  [Pending SRU]
  
  Note: No autopkgtests has been reported since systemd (21.5) ... between
  21.5 and now (21.11) everything released has been about security fixes :
  
  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU
  
  Unless security team has some autopkgtests reports elsewhere, the only
  data available I have (to compare) is if the autopkgtests were
  "failling" or "passing" when 21.5 has been pushed. Since then quite a
  few release has been uploaded with no autopkgtests report.
  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz
  
  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic
  
  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.
  
  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.
  
+ * Regression in autopkgtest for nplan (amd64): test log
+ 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz
+ 
+ Error: (Ran on autopkgtest Ubuntu infra)
+ test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
+ 
+ test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not
+ create NMClient object: Cannot invoke method; proxy is for a well-known
+ name without an owner and proxy was constructed with the
+ G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
+ 
+ test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
+ NMClient object: Cannot invoke method; proxy is for a well-known name
+ without an owner and proxy was constructed with the
+ G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL
+ 
+ Justification:
+ 
+ * Regression in autopkgtest for nplan (armhf): test log
+ 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/n/nplan/20181217_132248_e07e2@/log.gz
+ 
+ Error:
+ Traceback (most recent call last):
+   File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
+ command()
+   File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 646, in command
+ r = f(c, ce)
+   File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 342, in cmd_reboot
+ caller.hook_wait_reboot()
+   File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-lxd", line 230, in 
hook_wait_reboot
+ wait_booted()
+   File

[Touch-packages] [Bug 1808826] [NEW] install intel draphic drivers

2018-12-17 Thread app

Public bug reported:

for Ubuntu 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
Uname: Linux 4.4.0-140-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Dec 17 07:16:01 2018
DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:170b]
InstallationDate: Installed on 2018-11-26 (20 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
MachineType: Hewlett-Packard HP Z200 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic 
root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago)
dmi.bios.date: 03/09/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786H3 v01.13
dmi.board.asset.tag: 2UA12218BX
dmi.board.name: 0B40h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA12218BX
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786H3v01.13:bd03/09/2011:svnHewlett-Packard:pnHPZ200Workstation:pvr:rvnHewlett-Packard:rn0B40h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z200 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Dec 17 06:37:20 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  install intel draphic drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  for Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 17 07:16:01 2018
  DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:170b]
  InstallationDate: Installed on 2018-11-26 (20 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: Hewlett-Packard HP Z200 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic 
root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago)
  dmi.bios.date: 03/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786H3 v01.13
  dmi.board.asset.tag: 2UA12218BX
  dmi.board.name: 0B40h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA12218BX
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-12-17 Thread emarkay

Bug #1761003 also may be related.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2018-12-17 Thread Jim Campbell

I'm still on 18.04, but this problem remains for me, as well.

Grub with noresume doesn't work
RESUME=none doesn't work
RESUME=/dev/mapper/ubuntu-root doesn't work
RESUME=/dev/mapper/ubuntu-swap doesn't work

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

2018-12-17 Thread emarkay

Yes, may be related to Bug #1748839 reported by Petr Michalec on
2018-02-12!  Almost a year ago!

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Hello,

  since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS 
network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the 
dual boot Windows 10 environment it is still working with the same certificates.
  It is a hidden network, adding it by "connect to a hidden network" entering 
SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate 
password.
  Tried a lot not getting it working. The password entry dialog for the network 
is always popping up upon connection trials. The password is for sure the 
correct one, checked it very often.
  If I'm able to I'll attach a syslog and kern.log of error occurense.

  Thanks for investigation and inputs.

  Best regards

  Kitsab

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  3 23:52:23 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-02-14 (1144 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2018-12-17 Thread emarkay

OK, how'd this slip through?  No WPA options anywhere? Only 2 WEP
options.  2 new installs, on different machines, I can not connect to my
WPA (TKIP+AES) network wirelessly!!!

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

Sorry you are right. I'm not really familiar with alsa much but triaged
a few similar issues recently and tried to help a bit.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/tree/sound/pci/hda/patch_realtek.c has mention of hacks with
the ALC256 but for asus configs, unsure they would adapt well.

https://bugzilla.kernel.org/show_bug.cgi?id=201251 is an upstream kernel
bug that mentions swift configurations so maybe it's worth
following/commenting there

** Bug watch added: Linux Kernel Bug Tracker #201251
   https://bugzilla.kernel.org/show_bug.cgi?id=201251

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1784485] Missing required logs.

2018-12-17 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1784485

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1808674] Re: software-properties-gtk should have --disable-component to disable specified component of the distro's repositories

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  software-properties-gtk should have --disable-component to disable
  specified component of the distro's repositories

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties-gtk already has

-e ENABLE_COMPONENT, --enable-component=ENABLE_COMPONENT
  Enable the specified component of the distro's
  repositories

  but do not have option to disable specified component of the distro's
  repositories.

  Consider to add such functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 16 13:09:39 2018
  InstallationDate: Installed on 2018-08-07 (130 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1808676] Re: Ubuntu needs console alternative for software-properties-gtk / software-properties-kde

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Ubuntu needs console alternative for software-properties-gtk /
  software-properties-kde

Status in software-properties package in Ubuntu:
  New

Bug description:
  Currently Ubuntu provides only GUI versions of software-properties.

  
  Console version for software-properties-gtk / software-properties-kde is 
needed.

  ---

  You can follow the discussion on https://community.ubuntu.com/t/does-
  ubuntu-need-console-alternative-for-software-properties-gtk-software-
  properties-kde/8763 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 16 13:15:11 2018
  InstallationDate: Installed on 2018-08-07 (130 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-17 Thread Tomasz Przybył

I booted **manjaro-kde-18.0-stable-x86_64.iso** nd sounds works (internal 
speakers) like a charm.
Sound details:
```
[manjaro@manjaro ~]$ sudo hwinfo --sound
20: PCI 1f.3: 0403 Audio device 
  [Created at pci.378]
  Unique ID: nS1_.b28td23g3aB
  SysFS ID: /devices/pci:00/:00:1f.3
  SysFS BusID: :00:1f.3
  Hardware Class: sound
  Model: "Intel Audio device"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x9d71 
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x1a00 
  Revision: 0x21
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable)
  Memory Range: 0xef50-0xef50 (rw,non-prefetchable)
  IRQ: 130 (615 events)
  Module Alias: "pci:v8086d9D71sv1043sd1A00bc04sc03i00"
  Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
  Driver Info #1:
Driver Status: snd_soc_skl is active
Driver Activation Cmd: "modprobe snd_soc_skl"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
```

This ISO included patches for ALSA, 
Patches for ASUS sound issues was applied in **4.19.8-2** release via this 
commit > 
https://gitlab.manjaro.org/packages/core/linux419/commit/ef116a4b40754fa3f08e605c9e30fca35f0d6f03
Naming taken from this:
https://gitlab.manjaro.org/packages/core/linux419/commit/082db04a3e3d904e13e1550ae80f553dd1a0cba6

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

2018-12-17 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-12-17 Thread Ubuntu Foundations Team Bug Bot

The attachment "disco-stop-mount-error-propagation.debdiff" seems to be
a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1755863

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")

[Touch-packages] [Bug 1802525] Re: (s)ata disks do not have /dev/disk/by-path links created

This bug was fixed in the package systemd - 204-5ubuntu20.29

---
systemd (204-5ubuntu20.29) trusty; urgency=medium

  * d/p/0001-udev-build-by-path-identifiers-for-ATA-devices.patch
create /dev/disk/by-path/ symlinks for (s)ata disks
(LP: #1802525)

 -- Dan Streetman   Fri, 09 Nov 2018 10:16:27
-0500

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

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

  [other info]

  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.

  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
  even upstream.  However, since Xenial and later currently do have udev
  code that creates ata by-path symlinks, that is a separate issue and
  not a reason for keeping ata by-path symlinks about of trusty udev.

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

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

[Touch-packages] [Bug 1802525] Update Released

2018-12-17 Thread Łukasz Zemczak

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

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

  [other info]

  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.

  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
  even upstream.  However, since Xenial and later currently do have udev
  code that creates ata by-path symlinks, that is a separate issue and
  not a reason for keeping ata by-path symlinks about of trusty udev.

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

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

[Touch-packages] [Bug 1807134] Re: lxc 3.0.2/3 - cannot create root password in privileged container

2018-12-17 Thread km

The issue is due to the lxc logic of applying in deploying in
default.conf

lxc.idmap = u 0 10 65536
lxc.idmap = g 0 10 65536

in which case the container is ultimately constructed as unprivileged
container and such cannot be reverted with a the container specific
config.

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

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

Title:
  lxc 3.0.2/3  - cannot create root password in privileged container

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Prior filing this as potential bug help was sought but did not yield a
  remedy

  https://discuss.linuxcontainers.org/t/3-0-2-bug-cannot-create-root-
  password-in-privileged-container/3425

  host - ubuntu cosmic with kernel 4.18.0-12 / systemd 239-7 / apparmor
  2.12

  Whilst there is no issue with creating a root password via lxc-attach
  and passwd in an unprivileged container it is however not possible to
  create a password the same way for a privileged container (tried
  centos 7 and ubuntu cosmic).

  Error reported from within the containers:

  passwd: System error
  passwd: Authentication token manipulation error

  Error reported at the host:

  passwd: PAM audit_log_acct_message() failed: Operation not permitted

  Next tried with:

  chroot /container/path/rootfs passwd

  but that produced the same error.

  Next tried with:

  lxc.cap.keep = CAP_AUDIT_WRITE

  but the container would not boot.

  Next tried with:

  lxc.apparmor.profile = unconfined

  but no remedy.

  Next switched the kernel to 4.19.7 but no dice either.

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

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

[Touch-packages] [Bug 1799251] Re: mount options for /run should be the same as initramfs tools

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360989

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

Title:
  mount options for /run should be the same as initramfs tools

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

Bug description:
  mount options for /run should be the same as initramfs tools

  [Impact]

   * /run is mounted with different options on initrd boots, and initrd-
  less boots. For consistency it should be the same

   * In particular, this causes overuse of RAM on hosts with dense
  deployment of containers. Specifically, runtime journald takes up at
  most 10% or /run, which is capped at 10% of ram, thus 1% of total RAM.
  However, on initrd-less boots (like lxd launch ubuntu-daily:foo), /run
  takes up all of RAM, and thus run-time journal is now capped at 10% of
  RAM. Which is really bad when one deploys more than 10 containers...

  [Test Case]

   * Check total RAM on the host with `free -h`
   * lxd launch ubuntu-daily:release
   * In that container check the size of /run with `df -h | grep '/run$'`
   * /run should roughly be 1/10th of the total RAM.

  [Regression Potential]

   * /run is meant to be small, and it is small on systems booted with
  initrd and everything works fine there. Reducing the default size of
  /run in the containers should not have averse impacts. The most
  notable change is that runtime journald is now capped 10x smaller in
  the containers, to the same size as on the hosts. If that is not
  enough, one should $ sudo mkdir /var/log/journal to have a larger
  persistent journal.

  [Other Info]
   
   * This issue got escalated as affecting production deployments in the 
Canonical datacentre.

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

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

[Touch-packages] [Bug 1805358] Re: autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360989

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

Title:
  autopkgtest boot-and-services fails on many architectures very often
  since systemd/239-7ubuntu12

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

Bug description:
  [Impact]

   * Boot and services autopkgtest case has become flakey, especially on
  ppc64el but other architectures too.

  [Test Case]

   * Check that boot-and-services passes more reliably

  [Regression Potential]

   * this is a test change only

  [Other Info]
   
   * gdm3 used to start reliably, in nested qemu, with dummy xorg, but it 
doesn't anymore. Thus stop testing gdm3 coming up as part of the systemd 
autopkgtest. Mostly, because in realisty it's not that interesting to see if 
gdm3 works with dummy xorg, as we mostly care about gdm3 working on bare-metal 
with proper graphics cards intel/amd/nvidia/etc.

  I appreciate that some old known issues on 'upstream' are fixed.
  But looking at the current tests I see that often on amd64 (2/3 and very 
often on ppc64le (4/4 since ubuntu12 and 11/11 before that version).

  Looking at the list of people hitting retry and the list of packages
  blocked that seems an issue that must be checked.

  See current head of tests at:
  amd64: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/amd64
  ppc64el: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/ppc64el

  One example log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20181126_074048_cb8d2@/log.gz

  Example of the error that one can see in the log:
  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service user@118.service 
---
  -- Logs begin at Tue 2018-10-30 09:54:39 UTC, end at Mon 2018-11-26 07:05:17 
UTC. --
  Nov 26 07:05:09 autopkgtest systemd[1]: Starting User Manager for UID 118...
  Nov 26 07:05:10 autopkgtest systemd[1292]: pam_unix(systemd-user:session): 
session opened for user gdm by (uid=0)
  Nov 26 07:05:10 autopkgtest systemd[1292]: Failed to fully start up daemon: 
Permission denied
  Nov 26 07:05:10 autopkgtest systemd[1]: user@118.service: Failed with result 
'protocol'.
  Nov 26 07:05:10 autopkgtest systemd[1]: Failed to start User Manager for UID 
118.
  FAIL

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.Xm5RBa/build.JSa/src/debian/tests/boot-and-services", line 
62, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['user@118.service loaded failed failed User 
Manager for UID 118'] != []

  First list contains 1 additional elements.
  First extra element 0:
  'user@118.service loaded failed failed User Manager for UID 118'

  - ['user@118.service loaded failed failed User Manager for UID 118']
  + []

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

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

[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360989

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

Title:
  systemd-resolved has issues when the answer is over 512 bytes with
  EDNS disabled

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  TCP stub is cutting down the payload to 512 bytes when EDNS is
  disabled. This makes non-EDNS clients (nslookup) receive a "shortened"
  answer even when UDP returns a truncated reply for a new TCP query.
  For instance,

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  In the second case, no-EDNS, TCP should provide the complete answer,
  but it's capped at UDP's size.

  [Test Case]

  Query systemd-resolved with a domain name that resolves to multiple
  (lots.. 30+) A records. A client with EDNS support (dig) will receive
  all of them, a client without support (nslookup or dig +noedns) will
  have a truncated list. Using the example above:

  EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 
| wc -l

  [Regression potential]

  Minimal. This change only affects TCP requests, and the new size is
  already used in the code for other requests.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10816
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce

  [Original Description]

  Querying a domain name that has >512 bytes in records (e.g. 30+ A
  records), the number of results depends on the DNS client used:

  - If the client supports EDNS:

  $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  30

  - If the client does not support EDNS:

  $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
  29

  Normally a client that doesn't support EDNS would receive a truncated
  reply from the initial UDP connection (limited by the spec to 512
  bytes) and a second query would be established via TCP to receive the
  complete results. In this case, the number of results is the same
  regardless of the protocol used (29).

  Upstream bug: https://github.com/systemd/systemd/issues/10816

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

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

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360989

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/systemd/+git/systemd/+merge/360990

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2018-12-17 Thread Michał Sawicz

lsusb says "Bus 002 Device 003: ID 8087:07dc Intel Corp." here.

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost

2018-12-17 Thread Kai-Heng Feng

Would it be possible to try older kernel releases like v4.4.X [1]?

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.167/

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

Title:
  Intel I219-V ethernet connection lost

Status in systemd package in Ubuntu:
  New

Bug description:
  Ethernet connection id dropped randomly, sometimes works fine for the whole 
day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this 
bug being unable to add usable info to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar.
  I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with 
standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel.
  When the connection drops i can restart it just closing and restarting the 
net.
  Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm 
forced to do reconnect to send the doc.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 239-7ubuntu14
  Uname: Linux 4.20.0-042000rc4-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 18:33:12 2018
  InstallationDate: Installed on 2018-11-07 (26 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic 
root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-07 (26 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 239-7ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Tags:  wayland-session disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2018-12-17 Thread Kai-Heng Feng

Michał, does this happen to intel Bluetooth USB controller?

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap

2018-12-17 Thread Mantas Kriaučiūnas

** Tags added: rls-bb-incoming

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

Title:
  [SRU] Slow startup with zram-config installed (/dev/zram0) or
  encrypted swap

Status in Default settings and artwork for Baltix OS:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zram-config package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled 
(for example zram-config installed) or swap is encrypted.
  Today lots of users have SSD instead of HDD disk drives and use zram swap 
instead of swap partition or swap file, but if initrd is generated when zram 
swap is enabled then system can become "unbootable" from the user's perspective 
(Users with SSD storage doesn't wait 2 or more minutes...)

  This bug is already fixed in Debian initramfs-tools ver 0.132, please accept 
this simple 3 lines patch from Debian into Ubuntu 18.04 LTS
  
https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d

  [Test Case]
  Install zram-config package and regenerate and initrd, for example with 
  sudo update-initramfs -u

  When generating initrd I get this message in terminal:

  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
  I: Set the RESUME variable to override 
this.###.]

  So the local-premount script in initramfs was waiting for a swap
  device that was not available, until it timed out. The relevant
  message was gave up waiting for suspend/resume device.

  [Regression Potential]

  None, patch simply adds case for /dev/zram*:

  60case "$resume_auto" in
  61/dev/zram*)
  62ephemeral=true
  63;;
  64esac

  
  [Other Info]
  Manual method to disable this (as resuming from swap is not possible with an 
encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add 
(or change) line
  RESUME=none
  (instead of the UUID that was here) will disable waiting for a resume device.
  and run sudo update-initramfs -u to apply the changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+subscriptions

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

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

2018-12-17 Thread Julian Andres Klode

If we want to backport this to stable releases, we need a test case.
What I came up with, as I was not able to simulate dhcp lease refreshes,
is:


(1) Append make_resolv_conf to the end of the file, so it gets executed
(2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings change.


** Description changed:

- If a cloud server is upgraded from Xenial to Bionic, the dhclient system
- remains in place and any DHCP lease refreshes cause a needless restart
- of the system-resolved daemon
+ [Impact]
+ Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?
  
+ [Test case]
+ (1) Append make_resolv_conf to the end of the file, so it gets executed
+ (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings change.
+ 
+ [Regression potential]
+ The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.
+ 
+ [Original bug report]
+ If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon
  
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?
  
  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
- (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings change.
+ (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:
+ 
+ sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
+ sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
+ => no restart
+ sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
+ => should restart
+ sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
+ => no restart
+ sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
+ => should restart
  
  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.
  
  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

2018-12-17 Thread Julian Andres Klode

Here's a patch while the git branch is pushing.

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

** Patch added: 
"0001-Only-restart-resolved-on-changes-in-dhclient-enter-h.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+attachment/5222922/+files/0001-Only-restart-resolved-on-changes-in-dhclient-enter-h.patch

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test

2018-12-17 Thread Trent Lloyd

** Bug watch added: github.com/lathiat/avahi/issues #2
   https://github.com/lathiat/avahi/issues/2

** Also affects: avahi via
   https://github.com/lathiat/avahi/issues/2
   Importance: Unknown
   Status: Unknown

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

Title:
  avahi-0.6.31 doesn't pass Apple conformance test

Status in Avahi:
  Unknown
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  We are working on to support Apple bonjour conformance test-1.3.0 and
  test fails with avahi version 0.6.31 for test case - SRV
  PROBING/ANNOUNCEMENTS. This test fails both on IPV4 and IPV6. And the
  configured network package - dhcpcd-6.6.4.

  After parsing all logs(wireshark, apple PC and linux PC syslogs), and
  looks like avahi does not support a particular scenario in which Apple
  bonjour conformance test looks for. And also confirmed Apple test is
  inline with the RFC 6762 document for a special use-case(resolving SRV
  names on power up).

  Below is the bug description,

  setup:
  Apple MAC with Bonjour conformance test - 1.3.0 (latest OS x)
  Apple airport  (latest version)
  Linux device(PC) (ubuntu 14.04)

  Configure all above devices to communicate on link local mode.

  1) Start avahi bonjour conformance test on APPLE PC and Power ON linux
  device with avahi-0.6.31 and with _ssh._tcp.local service file

  2) First Linux device sends SRV initial probe message on link and followed by 
apple test sends same SRV (Linux device) question on link,
 example:(commands on wire shark)
  Linux Device sends ->  Who has "SSH" SRV QM question?
  Apple Bonjour Conformance Test -> Who has "SSH" SRV QM question?

  3) Then after this there is no message from Linux device on network and Apple 
test expecting new SRV probe message from device.
And so conformance test failed, since device couldn't able to send new 
SRV probe message with new name for service "SSH"

  4) After parsing log files found that,
 avahi-daemon logged service with new name ("SSH #2") in log file and could 
not publish/probe SRV message on network.

Linux device syslog messages,
Loading service file /etc/avahi/services/ssh.service
Service name conflict for "SSH" (/etc/avahi/services/ssh.service), 
retrying with "SSH #2).

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

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

[Touch-packages] [Bug 1799265] Re: avahi-daemon high cpu, unusable networking

2018-12-17 Thread Trent Lloyd

** Changed in: avahi (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: avahi (Ubuntu)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

** Bug watch added: github.com/lathiat/avahi/issues #210
   https://github.com/lathiat/avahi/issues/210

** Also affects: avahi via
   https://github.com/lathiat/avahi/issues/210
   Importance: Unknown
   Status: Unknown

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  Unknown
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  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: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-12-17 Thread Victor Tapia

** Patch added: "disco-stop-mount-error-propagation.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1755863/+attachment/5222912/+files/disco-stop-mount-error-propagation.debdiff

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]:

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-12-17 Thread Victor Tapia

Hi,

I'm working on the patches for Disco, Cosmic, Bionic and Xenial. It's
not in Disco yet, but the fix process will be tracked in this bug.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Mounting manually a network share (NFS) and masking it breaks the state of 
other units (and their dependencies).
  Casper is masking a mounted NFS share, blocking the normal boot process as 
described in the original description, but the issue comes from systemd.

  [Test Case]

  - NFS mount point at /media
  root@iscsi-bionic:/home/ubuntu# mount | grep media
  10.230.56.72:/tmp/mnt on /media type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72)

  - Test mount point (/test) defined in /etc/fstab:
  root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test
  tmpfs /test tmpfs nosuid,nodev 0 0

  1. If media.mount is not masked, everything works fine:

  root@iscsi-bionic:/home/ubuntu# mount | grep test
  root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active
 Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days 
ago
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test

  2. If media.mount is masked, other mounts are failing:

  root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount
  Created symlink /etc/systemd/system/media.mount → /dev/null.
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active
 Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s 
ago
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl start test.mount
  Job for test.mount failed.
  See "systemctl status test.mount" and "journalctl -xe" for details.
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount
  root@iscsi-bionic:/home/ubuntu# mount | grep test
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
  tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)

  [Regression potential]

  Minimal. Originally, one failing mount point blocked the processing of
  the rest due to how the return codes were handled for every line in
  /proc/self/mountinfo. This patch removes this "dependency" and keeps
  the failure local to the affected mount point, allowing the rest to be
  processed normally.

  [Other Info]

  Upstream bug: https://github.com/systemd/systemd/issues/10874
  Fixed upstream with commit: 
https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3

  [Original Description]

  
  netbooting the bionic live CD[1] over NFS goes straight to maintenance mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service

[Touch-packages] [Bug 1781440] Update Released

2018-12-17 Thread Łukasz Zemczak

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

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

Title:
  package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which
  is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1

Status in wayland package in Ubuntu:
  Fix Released
Status in wayland source package in Bionic:
  Fix Committed
Status in wayland source package in Cosmic:
  Fix Released

Bug description:
  [impact]

  upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was
  installed

  [test case]

  install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic

  [regression potential]

  none, the fix only changes the version numbers in Breaks/Replaces

  
  --

  Occured when upgrading from Bionic to Cosmic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-dev 1.15.0-2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jul 12 18:41:26 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package 
libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:224e]
  InstallationDate: Installed on 2018-02-07 (155 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  MachineType: LENOVO 20JDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= 
vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha2
  SourcePackage: wayland
  Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also 
in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET33W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 2nd
  dmi.product.name: 20JDCTO1WW
  dmi.product.version: ThinkPad X1 Yoga 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

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

[Touch-packages] [Bug 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1

This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1

---
wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium

  * control: Bump Breaks/Replaces again to match reality. (LP: #1781440)

 -- Timo Aaltonen   Tue, 27 Nov 2018 21:41:23 +0200

** Changed in: wayland (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which
  is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1

Status in wayland package in Ubuntu:
  Fix Released
Status in wayland source package in Bionic:
  Fix Committed
Status in wayland source package in Cosmic:
  Fix Released

Bug description:
  [impact]

  upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was
  installed

  [test case]

  install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic

  [regression potential]

  none, the fix only changes the version numbers in Breaks/Replaces

  
  --

  Occured when upgrading from Bionic to Cosmic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-dev 1.15.0-2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jul 12 18:41:26 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package 
libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:224e]
  InstallationDate: Installed on 2018-02-07 (155 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  MachineType: LENOVO 20JDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= 
vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha2
  SourcePackage: wayland
  Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also 
in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET33W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 2nd
  dmi.product.name: 20JDCTO1WW
  dmi.product.version: ThinkPad X1 Yoga 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

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

[Touch-packages] [Bug 1799394] Re: [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out, Front] no audio from front headphone

** Tags added: bionic

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

Title:
  [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out,
  Front] no audio from front headphone

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  no audio from front headphone

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omkar  2871 F...m pulseaudio
   /dev/snd/controlC0:  omkar  2871 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 23 15:12:18 2018
  InstallationDate: Installed on 2018-07-06 (108 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omkar  2871 F...m pulseaudio
   /dev/snd/controlC0:  omkar  2871 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out, 
Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.10
  dmi.board.name: H110M-HDV R3.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd07/18/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDVR3.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-13T11:41:09.962499

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

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

[Touch-packages] [Bug 1799394] Re: [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out, Front] no audio from front headphone

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

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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out,
  Front] no audio from front headphone

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  no audio from front headphone

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omkar  2871 F...m pulseaudio
   /dev/snd/controlC0:  omkar  2871 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 23 15:12:18 2018
  InstallationDate: Installed on 2018-07-06 (108 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   omkar  2871 F...m pulseaudio
   /dev/snd/controlC0:  omkar  2871 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out, 
Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.10
  dmi.board.name: H110M-HDV R3.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd07/18/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDVR3.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-08-13T11:41:09.962499

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

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

[Touch-packages] [Bug 1808757] Re: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

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

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


** This bug has been marked a duplicate of bug 1799394
   [To Be Filled By O.E.M., Realtek ALC887-VD, Green Headphone Out, Front] no 
audio from front headphone

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

Title:
  [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound from headphones from ubuntu desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cosmadrian   1251 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 10:35:18 2018
  InstallationDate: Installed on 2018-08-08 (131 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 924 F pulseaudio
cosmadrian   1251 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M PRO-VD (MS-7B53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd02/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360MPRO-VD(MS-7B53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B53
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1808757] [NEW] [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

2018-12-17 Thread Adrian Cosma

Public bug reported:

No sound from headphones from ubuntu desktop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cosmadrian   1251 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 17 10:35:18 2018
InstallationDate: Installed on 2018-08-08 (131 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 924 F pulseaudio
  cosmadrian   1251 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.10
dmi.board.asset.tag: Default string
dmi.board.name: B360M PRO-VD (MS-7B53)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd02/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360MPRO-VD(MS-7B53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B53
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound from headphones from ubuntu desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cosmadrian   1251 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 10:35:18 2018
  InstallationDate: Installed on 2018-08-08 (131 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 924 F pulseaudio
cosmadrian   1251 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [MS-7B53, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M PRO-VD (MS-7B53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd02/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360MPRO-VD(MS-7B53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B53
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-12-17 Thread Kai-Heng Feng

Florian,
So it works in udev-232 but not udev-233? Sounds like a regression.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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

[Touch-packages] [Bug 1607677] Re: Set default mouse acceleration profile to none/flat