date:20171215

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

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

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash
  package pre-installation script subprocess was killed by signal
  (Aborted), core dumped

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Installing 18.07 on WSL using do-distribution-upgrade -d

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Dec 14 17:46:10 2017
  Dmesg:
   
  ErrorMessage: new bash package pre-installation script subprocess was killed 
by signal (Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.2.24
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash 
package pre-installation script subprocess was killed by signal (Aborted), core 
dumped
  UpgradeStatus: Upgraded to xenial on 2017-12-14 (0 days ago)

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path

2017-12-15 Thread Martin Pitt

Thanks Christian! Indeed this is rather hard to reproduce locally, but
that PR seems to address this. I'll let you know if it doesn't after it
lands.

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

Title:
  [17.10 regression] AppArmor denial: Failed name lookup - disconnected
  path

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Artful:
  New
Status in ntp source package in Bionic:
  Triaged

Bug description:
  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  
  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  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
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

2017-12-15 Thread Waz

I was about to pass an exam, a powerpoint presentation, so the examiner
spelled me the wifi password and after pressing ok an other windows ask
for the wifi password! Quite embarrassing...

Is it a Kubuntu bug or Kde one ?

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Confirmed
Status in plasma-nm package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1738382] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-12-15 Thread Leonidas S. Barbosa

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1738382

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apport:
Installed: 2.20.1-0ubuntu2.13
Candidate: 2.20.1-0ubuntu2.14
Version table:
   2.20.1-0ubuntu2.14 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 2.20.1-0ubuntu2.13 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.1-0ubuntu2 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  
  The system reported this bug to me at start-up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Fri Dec 15 06:24:34 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.13
   Unpacking linux-headers-generic-hwe-16.04 (4.10.0.42.44) over (4.10.0.40.42) 
...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-28 (108 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1738382] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-12-15 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1738382

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apport:
Installed: 2.20.1-0ubuntu2.13
Candidate: 2.20.1-0ubuntu2.14
Version table:
   2.20.1-0ubuntu2.14 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 2.20.1-0ubuntu2.13 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.1-0ubuntu2 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  
  The system reported this bug to me at start-up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Fri Dec 15 06:24:34 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.13
   Unpacking linux-headers-generic-hwe-16.04 (4.10.0.42.44) over (4.10.0.40.42) 
...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-28 (108 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735960] Re: Merge avahi 0.7 with Debian

The merge would probably fix our FTBFS issue.

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

Title:
  Merge avahi 0.7 with Debian

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  avahi 0.7 is in Debian.

  This merge is blocked by this FTBFS issue:
  https://bugs.debian.org/878911
  https://bugs.debian.org/880036

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

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

[Touch-packages] [Bug 1735960] Re: Merge avahi 0.7 with Debian

Debian bug #878911 is marked as fixed ...

** Changed in: avahi (Ubuntu)
   Importance: Wishlist => High

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

Title:
  Merge avahi 0.7 with Debian

Status in avahi package in Ubuntu:
  Triaged

Bug description:
  avahi 0.7 is in Debian.

  This merge is blocked by this FTBFS issue:
  https://bugs.debian.org/878911
  https://bugs.debian.org/880036

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

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

[Touch-packages] [Bug 1738403] [NEW] iptables-save duplicates libvirt rules

2017-12-15 Thread jean-christophe manciot

Public bug reported:

Ubuntu 17.10
iptables 1.6.1-2ubuntu1

Before "iptables-save > /etc/iptables/rules.v4"
---
# cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
 14 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
 14 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
 14 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
 14 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
 14 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
 14 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
 14 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
 14 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
 14 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
 33 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
  1 -A ufw-user-input -i virbr0 -j ACCEPT
  1 -A ufw-user-output -o virbr0 -j ACCEPT

After "iptables-save > /etc/iptables/rules.v4"
--
# cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
 15 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
 15 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
 15 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
 15 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
 15 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
 15 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
 15 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
 15 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
 15 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
 34 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
  1 -A ufw-user-input -i virbr0 -j ACCEPT
  1 -A ufw-user-output -o virbr0 -j ACCEPT

It looks like iptables-save is confused by virbrn entries and duplicates
them each time it is run.

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

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

Title:
  iptables-save duplicates libvirt rules

Status in iptables package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10
  iptables 1.6.1-2ubuntu1

  Before "iptables-save > /etc/iptables/rules.v4"
  ---
  # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
   14 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
   14 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
   14 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
   14 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
   14 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
   14 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
   14 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
   14 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
   14 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
   14 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
   33 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
1 -A ufw-user-input -i virbr0 -j ACCEPT
1 -A ufw-user-output -o virbr0 -j ACCEPT

  After "iptables-save > /etc/iptables/rules.v4"
  --
  # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
   15 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
   15 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
   15 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
   15 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
   15 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
   15 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
   15 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
   15 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
   15 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
   15 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
   34 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
1 -A ufw-user-input -i virbr0 -j ACCEPT
1 -A ufw-user-output -o virbr0 -j ACCEPT

  It looks like iptables-save is confused by virbrn entries and
  duplicates them each time it is run.

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

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

[Touch-packages] [Bug 1738403] Re: iptables-save duplicates libvirt rules

2017-12-15 Thread jean-christophe manciot

It appears that this issue concerns all Linux bridges:

# cat iptables/rules.v4 | grep lxcbr0 | sort | uniq -c
  7 -A FORWARD -i lxcbr0 -j ACCEPT
  7 -A FORWARD -o lxcbr0 -j ACCEPT
  7 -A INPUT -i lxcbr0 -p tcp -m tcp --dport 53 -j ACCEPT
  7 -A INPUT -i lxcbr0 -p tcp -m tcp --dport 67 -j ACCEPT
  7 -A INPUT -i lxcbr0 -p udp -m udp --dport 53 -j ACCEPT
  7 -A INPUT -i lxcbr0 -p udp -m udp --dport 67 -j ACCEPT
 13 -A POSTROUTING -o lxcbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill

** Summary changed:

- iptables-save duplicates libvirt rules
+ iptables-save duplicates all rules related to Linux bridges

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

Title:
  iptables-save duplicates all rules related to Linux bridges

Status in iptables package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10
  iptables 1.6.1-2ubuntu1

  Before "iptables-save > /etc/iptables/rules.v4"
  ---
  # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
   14 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
   14 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
   14 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
   14 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
   14 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
   14 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
   14 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
   14 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
   14 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
   14 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
   33 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
1 -A ufw-user-input -i virbr0 -j ACCEPT
1 -A ufw-user-output -o virbr0 -j ACCEPT

  After "iptables-save > /etc/iptables/rules.v4"
  --
  # cat iptables/rules.v4 | grep virbr0 | sort | uniq -c
   15 -A FORWARD -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate 
RELATED,ESTABLISHED -j ACCEPT
   15 -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
   15 -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
   15 -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
   15 -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
   15 -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
   15 -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
   15 -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
   15 -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
   15 -A OUTPUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
   34 -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM 
--checksum-fill
1 -A ufw-user-input -i virbr0 -j ACCEPT
1 -A ufw-user-output -o virbr0 -j ACCEPT

  It looks like iptables-save is confused by virbrn entries and
  duplicates them each time it is run.

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

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

[Touch-packages] [Bug 1723956] Re: busybox-static: several network applets segfaulting

2017-12-15 Thread Simon Rettberg

Pretty much every single one that would do a hostname lookup it seems.
Tried ping, ping6, nc, wget; they all crash.

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

Title:
  busybox-static: several network applets segfaulting

Status in busybox package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  On a fully up-to-date Ubuntu 17.04, running most applets from busybox-
  static that are network-related lead to a segfault. Example:

  $ busybox nslookup google.com 8.8.8.8
  Server:8.8.8.8
  Segmentation fault

  $ busybox
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary.
  [...]

  $ apt-cache policy busybox
  busybox:
Installed: (none)
Candidate: 1:1.22.0-19ubuntu2
Version table:
   1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages

  $ dpkg -S /bin/busybox 
  busybox-static: /bin/busybox

  $ apt-cache policy busybox-static
  busybox-static:
Installed: 1:1.22.0-19ubuntu2
Candidate: 1:1.22.0-19ubuntu2
Version table:
   *** 1:1.22.0-19ubuntu2 500
  500 http://ftp.fau.de/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status


  This even happens when passing invalid domains or DNS servers to use
  that don't actually run any DNS service. (like "busybox nslookup
  google.com 1.2.3.4" or "busybox nslookup bar.foof00 8.8.8.8"), so it
  seems to be early in the network setup.

  I could not reproduce the problem on the very same system when compiling 
stock busybox 1.22.1 (why even? we're at 1.27.x!) myself, neither with a recent 
git clone. Also two VMs I had at hand running Ubuntu 14.04 and 16.04 didn't 
show this problem with busybox-static. Installing the package "busybox" (which 
removes busybox-static) fixes the problem on 17.04.
  The only thing that might be related in any way about my system is that it 
has no IPv6 connectivity (apart from the link-local address).

  I also sent a crash report when the apport window popped up, but I
  have no idea where this ends up and how to add further information,
  hence this report here. Please let me know if this seemingly trivial
  bug cannot be reproduced instantly, so I can try to assist with
  further information.

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

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

[Touch-packages] [Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe

2017-12-15 Thread Loïc Minier

Could you describe the minimal steps to reproduce the issue on top of a
standard 16.04?

NB: /sys is not read-only on official images and deployments, and this
doesn't seem to affect official images.

** Description changed:

  Dear all,
  
- Following up the bug report #1713674, when executing systemd in a
- hardened LXC context, it might not be suitable to reexec systemd daemon,
- that would not be able to perform.
+ Following up the bug #1713674, when executing systemd in a hardened LXC
+ context, it might not be suitable to reexec systemd daemon, that would
+ not be able to perform.
  
  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find its
  cgroups). This means, systemd cannot be reexecuted, it will fail to
  restart and will freeze (properly) at restart making the LXC container
  in frozen state (still working, but no new services startable, no
  interaction with systemd possible anymore).
  
  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in a
  degraded state.
  
  It would likely be appropriate the check whether the reexecute can work
  will before performing it: checking capabilities, sys mount point perms,
  etc. If not applicable, not performing a reexucte and possibly print a
  message to the user.
  
  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.
  
  Cheers

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

Status in lxc package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Dear all,

  Following up the bug #1713674, when executing systemd in a hardened
  LXC context, it might not be suitable to reexec systemd daemon, that
  would not be able to perform.

  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find
  its cgroups). This means, systemd cannot be reexecuted, it will fail
  to restart and will freeze (properly) at restart making the LXC
  container in frozen state (still working, but no new services
  startable, no interaction with systemd possible anymore).

  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in
  a degraded state.

  It would likely be appropriate the check whether the reexecute can
  work will before performing it: checking capabilities, sys mount point
  perms, etc. If not applicable, not performing a reexucte and possibly
  print a message to the user.

  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

  Cheers

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

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

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

2017-12-15 Thread Robie Basak

Thanks. I'm happy with the additional information provided.

autopkgtests are still failing on this, including the amd64 one for
systemd which seems somewhat essential and has failed on retry, so right
now this is blocked on those.

If the autopkgtests failures can be resolved (fix or confirm not a
problem) then I'd be happy to release this.

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

Title:
systemd-rfkill service times out when a new rfkill device is added

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

Bug description:
[Impact]

The following issue was observed while running network-
manager=1.8.4-1ubuntu3 autopkgtest on Artful with
systemd=234-2ubuntu12.1:

---
Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start
operation timed out. Terminating.
Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill
Switch Status.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered
failed state.
Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with
result 'timeout'.
---

This happens after the testcase inserts the fake-rfkill module (a
module shipped with network-manager tests that registers a new fake
device with the rfkill subsystem).

On Artful, it causes the network-manager autopkgtest killswitches-no-
urfkill to fail (see bug 1733321). The testcase reveals that when
running network-manager cli to query the status of a WiFi interface
('nmcli radio wifi') it can report the wrong state of the device after
'rfkill block/unblock' is run to change the device 'Soft blocked'
state. This can affect the state of the device presented to the user.

[Fix]

The issue is fixed by the following systemd upstream patches:

---

https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
Author: S. Fan
Date: Mon Jul 31 05:10:10 2017 -0500

rfkill: fix erroneous behavior when polling the udev monitor
(#6489)

Comparing udev_device_get_sysname(device) and sysname will always return
true. We need to check the device received from udev monitor instead.

Also, fd_wait_for_event() sometimes never exits. Better set a timeout
here.
---

---

https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

commit c7f6ca9379279affa8f22d15fa13063491f86a49
Author: Xiang Fan
Date: Wed Aug 9 05:51:53 2017 -0500

rfkill: fix typo (#6574)
---

With the fixes, the output from systemd-rfkill is:

---
Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch
Status...
Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev
monitor.
Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch
Status.
---

The patches are needed to fix the ADT tests observed with Artful tests on
ppc64el architecture:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

[Test Case]

2.1. Download network-manager package source code
$ apt-get source network-manager

2.2. Run killswitches-no-urfkill testcase
$ cd network-manager-1.8.4
$ sudo ./debian/tests/killswitches-no-urfkill

[Regression Potential]

Most of the network-manager and rfkill functionalities that can be
affected by this change are tested by killswitches-no-urfkill
testcase. It covers querying the WiFi device state using nmcli and the
following rfkill commands: list, block and unblock. These have been
verified to be either fixed or not having regressions.

The only rfkill command that is not covered by the testcase is
'event', which listens to rfkill events and display them. I have run
tests manually and verified that it's not affected by these changes.
These are the outputs from the unpatched and patched systemd versions
while running the killswitches-no-urfkill testcase, which adds the
rfkill device, blocks and unbloks it and removes the device (the idx
value is expected to be different):

system

[Touch-packages] [Bug 1738427] [NEW] Segfault if crontab is owned by a user who cannot be found?

2017-12-15 Thread Sitsofe Wheeler

Public bug reported:

Description of the problem
It appears that cron will go on to crash if it finds a crontab owned by uid who 
does not map to a valid user.

Steps to reproduce:
1. Create a crontab with an Active Directory user set up via SSSD?
2. Switch AD domains so user's uid is entirely different?
3. Wait for cron to try and run the old user's crontab?

Expected result:
Error in the journal?

Actual result:
Error in the log file and cron segfault?

How reproducible is the issue?
It has happened twice so far before the crontab was removed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cron 3.0pl1-128ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
Date: Fri Dec 15 14:33:45 2017
InstallationDate: Installed on 2017-03-09 (280 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Segfault if crontab is owned by a user who cannot be found?

Status in cron package in Ubuntu:
  New

Bug description:
  Description of the problem
  It appears that cron will go on to crash if it finds a crontab owned by uid 
who does not map to a valid user.

  Steps to reproduce:
  1. Create a crontab with an Active Directory user set up via SSSD?
  2. Switch AD domains so user's uid is entirely different?
  3. Wait for cron to try and run the old user's crontab?

  Expected result:
  Error in the journal?

  Actual result:
  Error in the log file and cron segfault?

  How reproducible is the issue?
  It has happened twice so far before the crontab was removed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Fri Dec 15 14:33:45 2017
  InstallationDate: Installed on 2017-03-09 (280 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

shemgp, unfortunately, your newest patch still does not solve the
problem for me.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-15 Thread Didier Raboud

It's fine to have root as member of the lpadmin group. BUT… it's not
fine to have cups-pk-helper run as root and allow unauthorized users (in
CUPS' eyes) cancel other user's jobs.

This should be fixed in cups-pk-helper through making it interact with
CUPS using the requesting user's user. This would ensure that CUPS's
authorizations are respected.

I don't want to see a situation where "any GNOME user" accesses "cups-
pk-helper which runs as root" and can then "manipulate CUPS as if it
were a member of lpadmin".

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Touch-packages] [Bug 1738432] [NEW] Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

2017-12-15 Thread Sergio Callegari

Public bug reported:

Recently, my print dialogs have started to include network discoverd
printers in addition to those configured in cups even if the cups-
browsed service is disabled and the BrowseRemoteProtocols option is set
to none.

There does not seem to be any way to disable this behavior apart from
disabling avahi or its ability to talk to dbus, which causes side
effects on the system.

Yet, in some environments this behavior is a definite regression over
the old one and leads to an extremely poor user experience.

On some networks:

- The print dialogs takes 3-10 sec to open which is a huge amount of
time for an action that is expected to be instantaneous and for which
there is no visual feedback.

- The print dialog contains many tens of printer entries, all identified
by weird hex strings that cannot be related to any useful location, that
do not help identifying which entry corresponds to which printer and
that only mess up the list making it hard to find the printers that are
actually useful.

For instance, suppose that you work at some office that has recently
purchased a batch of new printers all the same model. In the print
dialog you may get many entries like:

HP_Laserjet_Pro_Mxxxdw_21ACF2

which only vary in the final hex string. How is one suppose to know what
is where?

Please make it possible to disable this driverless printer madness.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libcups2 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
CurrentDesktop: KDE
Date: Fri Dec 15 16:22:07 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1463 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Notebook W740SU
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W740SU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug artful

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  New

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [1

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-12-15 Thread Scott Moser

I've verified zesty with the script that is attached.
Output is shown here.


** Attachment added: "verification log of zesty"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5023065/+files/zesty.log

** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-donezesty

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in resolvconf source package in Zesty:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
    trusty uses 'running-in-container' to determine this.
    xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x

Re: [Touch-packages] [Bug 1737657] Re: Failure to be root is repored in a misleading message

2017-12-15 Thread Kevin O'Gorman

On Tue, Dec 12, 2017 at 6:17 PM, Paul Gear 
wrote:

> Hi @kogorman-pacbell,
>
> Can you explain what you think should be happening here?  Running
> ntpdate from sudo or a root shell gives exactly the same behaviour -
> ntpdate requires a list of servers to be provided on the command line,
> and it is simply indicating that this has not been provided.
>

It is indicating in a round-about way.  It should do so directly: "no
servers provided on the command line, or they are not usable".
That would be more clear, and for the clueless (like me) provide a clue as
to what is expected.


>
> In addition, it's completely legitimate to run ntpdate as a non-root
> user in order to see the offset from a remote server without setting the
> time (see the man page for details on the -d option).
>
> ** Changed in: ntp (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737657
>
> Title:
>   Failure to be root is repored in a misleading message
>
> Status in ntp package in Ubuntu:
>   Incomplete
>
> Bug description:
>   This is a feature request.
>
>   When solving a problem or in a rush, I don't necessarily remember
>   everything from a man page, or even think to read it.  This is what
>   happened with ntpdate(8)
>
>   $ ntpdate
>   11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
>   $
>
>   Of course, I should have used sudo.  And it's documented.  But as I
>   pointed out that doesn't help much when in a hurry or stressed.  My
>   bad, so I usually wouldn't mention it.  But the fix is so simple I
>   hope it appeals to you.
>
>   -> test the permissions and if they are missing, make that message
>
>   11 Dec 20:08:12 ntpdate[13930]: insufficient permissions (suggestion:
>   use sudo)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5.7
>   ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
>   Uname: Linux 4.4.0-103-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.1-0ubuntu2.14
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Mon Dec 11 17:53:23 2017
>   InstallationDate: Installed on 2016-08-08 (490 days ago)
>   InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   SourcePackage: ntp
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737657/+subscriptions
>


-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


** Attachment added: "unnamed"
   https://bugs.launchpad.net/bugs/1737657/+attachment/5023085/+files/unnamed

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

Title:
  Failure to be root is repored in a misleading message

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  This is a feature request.

  When solving a problem or in a rush, I don't necessarily remember
  everything from a man page, or even think to read it.  This is what
  happened with ntpdate(8)

  $ ntpdate
  11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
  $

  Of course, I should have used sudo.  And it's documented.  But as I
  pointed out that doesn't help much when in a hurry or stressed.  My
  bad, so I usually wouldn't mention it.  But the fix is so simple I
  hope it appeals to you.

  -> test the permissions and if they are missing, make that message

  11 Dec 20:08:12 ntpdate[13930]: insufficient permissions (suggestion:
  use sudo)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5.7
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Dec 11 17:53:23 2017
  InstallationDate: Installed on 2016-08-08 (490 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

Do you actually have no cups-browsed process running at all?
In which print dialogs do the driverless extra printers appear? Of which 
applications?
Please also run the commands

avahi-browse -v -t -r --all
lpstat -e
lpstat -v

and post the output here.


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

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
  CurrentDesktop: KDE
  Date: Fri Dec 15 16:22:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1463 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook W740SU
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1738448] [NEW] gnome-online-accounts should recommend dleyna-server for Media Server support

Public bug reported:

Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
cannot recommend it like the Debian package does. I have pushed a hack
to Debian to allow us to sync gnome-online-accounts and for the
dependencies to be handled correctly.

I am filing this as an informational bug since this issue will now be
less visible than if there was a persistent diff with Debian.

I think this will make the Media Server option in Settings > Online
Accounts not work, but I don't have a Media Server here to test right
now. This issue affects Ubuntu 17.10 and newer.

Ideally, the Media Server account type should be hidden if it doesn't
work, or modified to allow a user to easily install dleyna-server via
PackageKit.

Or we could try to get dleyna-server in to Ubuntu main.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
  cannot recommend it like the Debian package does. I have pushed a hack
  to Debian to allow us to sync gnome-online-accounts and for the
  dependencies to be handled correctly.

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1738448/+subscriptions

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

[Touch-packages] [Bug 1738448] Re: gnome-online-accounts should recommend dleyna-server for Media Server support

** Description changed:

- Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
- cannot recommend it like the Debian package does. I have pushed a hack
- to Debian to allow us to sync gnome-online-accounts and for the
- dependencies to be handled correctly.
+ Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
+ 
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639
  
  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.
  
  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.
  
  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.
  
  Or we could try to get dleyna-server in to Ubuntu main.

** Tags added: artful bionic gnome-17.10

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
  
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1738448/+subscriptions

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

[Touch-packages] [Bug 1683990] Re: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all. Resets to mute. No 'Play Sound Through' options

2017-12-15 Thread Clare

the bug is fixed! today I have sound. I would close this if I could see
how.

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

Title:
  [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all.
  Resets to mute. No 'Play Sound Through' options

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Edit 11-Dec-2017

  attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer indicates that the speaker keeps 
getting reset to mute after each re-start.
  -

  Edit 05-Nov-2017
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed

  and when I ran gnome-control-center at the command line recently I
  saw:

  (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
  the tree, so cannot set the active output

  (gnome-control-center:8955): Gvc-WARNING **: Couldn't match the
  portless stream (with card) - 'Built-in Audio Analog Stereo' is it an
  input ? -> 1, streams card id -> 0

  (gnome-control-center:8955): Gvc-CRITICAL **:
  gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE
  (device)' failed

  (gnome-control-center:8955): sound-cc-panel-WARNING **:
  on_control_active_input_update - tried to fetch an input of id 0 but
  got nothing

  -original text of bug--

  I have had no sound since original (fairly recent) purchase. I
  purchased online from Dell.

  Sound preferences were originally showing in upper right hand corner
  of the screen, but the sliders for changing volume were grayed out,
  and choosing sound test had no audible or visual result.

  Now sound preferences are not showing in upper right corner at all,
  and system preferences --> sound no longer shows 'sound test' as an
  option.

  I tried to fix original problem myself by killing then re-starting pulseaudio
  No effect. Also I tried commands

  apt-get purge pulseaudio
  and then later
  apt-get install pulseaudio

  it seemed to be after that when the sound preferences stopped showing
  in upper right corner, but I also did a general ubuntu update at the
  same time (and there is still a restart required for update for
  'Latitude E5X60 System Update' 68614)

  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 0FFPFD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1738404] [NEW] Bluetooth sound extreme low quality

You have been subscribed to a public bug:

I upgraded today from ubuntu 17.04 to ubuntu 17.10.

I use 3 different bluetooth audio devices ( BT earphones, BT speaker, BT
BOSE Soundlink speaker) , all of them worked properly on 17.04.

Since the upgrade, the sound gets continuous interruptions/cracking. 
These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
I could relate this to the fact that a new BT stack has replaced the former in 
Ubuntu.

If I use wired devices (hdmi connected screen+audio, the sound quality is good 
and as before) so the issue is related to the use of the new Bluetooth stack.
I have not found a way to parameterise it neither.

I have not found any similar report. "apport" seems not ot exist in
thise version, I cannot find and execute it.

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


** Tags: bot-comment
-- 
Bluetooth sound extreme low quality
https://bugs.launchpad.net/bugs/1738404
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

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

[Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality

2017-12-15 Thread Paul White

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

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

Title:
  Bluetooth sound extreme low quality

Status in bluez package in Ubuntu:
  New

Bug description:
  I upgraded today from ubuntu 17.04 to ubuntu 17.10.

  I use 3 different bluetooth audio devices ( BT earphones, BT speaker,
  BT BOSE Soundlink speaker) , all of them worked properly on 17.04.

  Since the upgrade, the sound gets continuous interruptions/cracking. 
  These sound interruptions and cracking are so annoying that I cannot keep on 
listening to music.
  I could relate this to the fact that a new BT stack has replaced the former 
in Ubuntu.

  If I use wired devices (hdmi connected screen+audio, the sound quality is 
good and as before) so the issue is related to the use of the new Bluetooth 
stack.
  I have not found a way to parameterise it neither.

  I have not found any similar report. "apport" seems not ot exist in
  thise version, I cannot find and execute it.

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

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

[Touch-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserG

[Touch-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

2017-12-15 Thread Adam Hulin

I'm also affected of this issue.

I found this partial(?) solution to this on github:
https://gist.github.com/kevinlekiller/f533f4d1f7318a7cf81a

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-15 Thread NoOne

@Thanks Gunnar, it worked like you said.

Can confirm that the fix works !

Finally!  Very happy.  :-)

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

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

[Touch-packages] [Bug 1424768] Re: Consider switching to path based activation

I think this will require more than just switching how the systemd
service runs as whoopsie is currently designed to run in the background
so will need to exit after submitting the crash reports.

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

Title:
  Consider switching to path based activation

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Bionic:
  Confirmed

Bug description:
  1)  Ubuntu 15.04
  2) 0.2.46
  3) Whoopsie to only run when it is needed.
  4) Instead it runs constantly, using network activity, l
  See bug (there are more..):
  https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481
  also try: sudo fnotifystat -p whoopsie

  Instead whoopsie should use path based activation to only run when
  /var/crash has changed.

  http://www.freedesktop.org/software/systemd/man/systemd.path.html

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

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-12-15 Thread William Ivanski

Workaround in #4 works for me, but only for the computer-integrated
speaker. Integrated microphone and also headsets don't work any more.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  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:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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.

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

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

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-15 Thread Gunnar Hjalmarsson

Thank *you*, NoOne, both for reporting the issue and for confirming the
fix.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

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

[Touch-packages] [Bug 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

I was unable to recreate this given the test case you've provided.
Here's the end of my unattended-upgrade dry-run with --verbose:

thunderbird-gnome-support:amd64 thunderbird-locale-en-us:all xserver-common:all 
xserver-xorg-core:amd64 xul-ext-ubufox:all liblouis-data:all liblouis9:amd64 
python3-louis:all
/usr/bin/dpkg --status-fd 73 --configure --pending
All upgrades installed

The last line is a lie.

bdmurray@clean-xenial-amd64:~$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.90ubuntu0.8
  Candidate: 0.90ubuntu0.8
  Version table:
 *** 0.90ubuntu0.8 500
500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial-updates/main i386 Packages
100 /var/lib/dpkg/status
 0.90ubuntu0.1 500
500 http://192.168.10.7/ubuntu xenial-security/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial-security/main i386 Packages
 0.90 500
500 http://192.168.10.7/ubuntu xenial/main amd64 Packages
500 http://192.168.10.7/ubuntu xenial/main i386 Packages
N: Ignoring file '50unattended-upgrades.ucf-dist' in directory 
'/etc/apt/apt.conf.d/' as it has an invalid filename extension
bdmurray@clean-xenial-amd64:~$ grep Automatic-Reboot 
/etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Automatic-Reboot "true";
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";
bdmurray@clean-xenial-amd64:~$ file /var/run/reboot-required
/var/run/reboot-required: empty

Can you provide any more details about how this happened? Does your
unattended-upgrades log file include information about the reboot?

>From the code:
# reboot at the specified time
when = apt_pkg.config.find(
"Unattended-Upgrade::Automatic-Reboot-Time", "now")
if shutdown_lock > 0:
os.close(shutdown_lock)
logging.warning("Found %s, rebooting" % REBOOT_REQUIRED_FILE)
subprocess.call(["/sbin/shutdown", "-r", when])

Thanks in advance!

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+subscriptions

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2017-12-15 Thread LETHRITZAKIS LEONIDAS

** Changed in: initramfs-tools
   Status: Confirmed => Incomplete

** Changed in: initramfs-tools
   Status: Incomplete => Opinion

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1711760] Reminder of SRU verification policy change

2017-12-15 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in resolvconf source package in Zesty:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
    trusty uses 'running-in-container' to determine this.
    xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (

[Touch-packages] [Bug 1738479] [NEW] libimobile device doesn't see device and device reboots when I'm disconnecting it from computer device doesn't see device, device reboots when I'm disconnecting it

2017-12-15 Thread Evgeny

Public bug reported:

Hi.

My computer: 
(Lubuntu):
evg@evg-Parallels-Virtual-Platform:$ uname -a
Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
(Ubuntu):
Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 
2017 i686 i686 i686 GNU/Linux

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken

I've successfully installed all libs from this document
https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc .
And device isn't visible when I'm trying to pair it using idevicepair
pair command, but it appears in all connected device list.

evg@evg-Parallels-Virtual-Platform:$ lsusb
Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1
Bus 001 Device 002: ID 203a:fff9
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
evg@evg-Parallels-Virtual-Platform:$ idevicepair pair
No device found, is it plugged in?
I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on Ubuntu 
(16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my ipad 
reboots when I disconnecting it from computer.

video with reboot (Reboot appears only on Ubuntu, not Lubuntu):
https://youtu.be/8expDYVAW4o

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

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

Title:
  libimobile device doesn't see device and device reboots when I'm
  disconnecting it from computer device doesn't see device, device
  reboots when I'm disconnecting it from computer

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Hi.

  My computer: 
  (Lubuntu):
  evg@evg-Parallels-Virtual-Platform:$ uname -a
  Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
  (Ubuntu):
  Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 
2017 i686 i686 i686 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken

  I've successfully installed all libs from this document
  https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc
  . And device isn't visible when I'm trying to pair it using
  idevicepair pair command, but it appears in all connected device list.

  evg@evg-Parallels-Virtual-Platform:$ lsusb
  Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1
  Bus 001 Device 002: ID 203a:fff9
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  evg@evg-Parallels-Virtual-Platform:$ idevicepair pair
  No device found, is it plugged in?
  I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on 
Ubuntu (16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my 
ipad reboots when I disconnecting it from computer.

  video with reboot (Reboot appears only on Ubuntu, not Lubuntu):
  https://youtu.be/8expDYVAW4o

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

2017-12-15 Thread Colin Watson

** Changed in: initramfs-tools
   Status: Opinion => Confirmed

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

2017-12-15 Thread Sergio Callegari

Don't know what I did, but finally I have succeeded disabling the
display of the driverless network printers.

Right before systemd reported cups-browsed as stopped.

Can it be the case that you need /both/ the process stopped /and/ the
BrowseRemoteProtocols in its conf file set to none /at the same time/
plus a restart of the desktop environment?

In case, I would change the bug title to "please document how to disable
the display of the driverless network printers" in the print dialog. It
can be a handy feature in places with just a couple of printers of
different brands, but in some environments it needs to be off.

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
  CurrentDesktop: KDE
  Date: Fri Dec 15 16:22:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1463 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook W740SU
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

2017-12-15 Thread NoOne

Now, if someone could ever fix that bug, I would be free of any
annoyance in Ubuntu. :-)

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724105

Let's hope for 18.04.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

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

[Touch-packages] [Bug 1728329] Re: Update freetype to 2.8.1

2017-12-15 Thread Adolfo Jayme

https://launchpad.net/ubuntu/+source/freetype/2.8.1-0.1ubuntu2

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

Title:
  Update freetype to 2.8.1

Status in freetype package in Ubuntu:
  Triaged

Bug description:
  We should merge freetype 2.8.1 from Debian Testing.

  freetype (2.8.1-0.1) unstable; urgency=medium

* Non-maintainer upload.
* New upstream release (Closes: #876132)
  - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
partially fixed upstream
  - debian/libfreetype6.symbols: Add newly export symbol

  
  However, there is a regression in Electron apps.

  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737

  https://github.com/electron/electron/pull/10213

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

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

[Touch-packages] [Bug 1738487] [NEW] Shell crashes with JS ERROR: TypeError: monitor is null

2017-12-15 Thread Laura Dietz

Public bug reported:

Periodically when I suspend my computer and resume it I find that my
session is gone. The following is logged in the journal after such an
event,

Dec 15 16:20:35 jam gnome-shell[1501]: JS ERROR: TypeError: monitor is null
   
BoxPointer<._reposition@resource:///org/gnome/shell/ui/boxpointer.js:507:13
   
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
   
BoxPointer<._allocate@resource:///org/gnome/shell/ui/boxpointer.js:234:13
   
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
   
LayoutManager<._init/<@resource:///org/gnome/shell/ui/layout.js:208:33
Dec 15 16:20:36 jam org.gnome.Shell.desktop[1501]: == Stack trace for context 
0x564daca8d000 ==

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 16:29:40 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Iris Graphics 540 [1028:06dc]
InstallationDate: Installed on 2017-11-24 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Latitude E7470
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic.efi.signed 
root=UUID=68384484-a30e-4aa4-990d-3727f8967b40 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.5
dmi.board.name: 0YDW8F
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.5:bd07/11/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0YDW8F:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful crash ubuntu wayland-session

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

Title:
  Shell crashes with JS ERROR: TypeError: monitor is null

Status in xorg package in Ubuntu:
  New

Bug description:
  Periodically when I suspend my computer and resume it I find that my
  session is gone. The following is logged in the journal after such an
  event,

  Dec 15 16:20:35 jam gnome-shell[1501]: JS ERROR: TypeError: monitor is null
 
BoxPointer<._reposition@resource:///org/gnome/shell/ui/boxpointer.js:507:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
BoxPointer<._allocate@resource:///org/gnome/shell/ui/boxpointer.js:234:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
LayoutManager<._init/<@resource:///org/gnome/shell/ui/layout.js:208:33
  Dec 15 16:20:36 jam org.gnome.Shell.desktop[1501]: == Stack trace for context 
0x564daca8d000 ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 16:29:40 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a)

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

2017-12-15 Thread Treviño

Adding Qt for historic reasons...

Fixed in commit
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9067a7f59c54a3dfab914b842b009b8346ae384c

See https://bugreports.qt.io/browse/QTBUG-63065

** Also affects: qt
   Importance: Undecided
   Status: New

** No longer affects: qt

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions

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

[Touch-packages] [Bug 1728329] Re: Update freetype to 2.8.1

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

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

Title:
  Update freetype to 2.8.1

Status in freetype package in Ubuntu:
  Fix Committed

Bug description:
  We should merge freetype 2.8.1 from Debian Testing.

  freetype (2.8.1-0.1) unstable; urgency=medium

    * Non-maintainer upload.
    * New upstream release (Closes: #876132)
  - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
    partially fixed upstream
  - debian/libfreetype6.symbols: Add newly export symbol

  However, there is a regression in Electron apps. It looks like we'll
  need to wait for Electron 1.9 for the regression to be fixed.

  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737

  https://github.com/electron/electron/pull/10213

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

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

[Touch-packages] [Bug 1728329] Re: Update freetype to 2.8.1

** Description changed:

  We should merge freetype 2.8.1 from Debian Testing.
  
  freetype (2.8.1-0.1) unstable; urgency=medium
  
-   * Non-maintainer upload.
-   * New upstream release (Closes: #876132)
- - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
-   partially fixed upstream
- - debian/libfreetype6.symbols: Add newly export symbol
+   * Non-maintainer upload.
+   * New upstream release (Closes: #876132)
+ - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
+   partially fixed upstream
+ - debian/libfreetype6.symbols: Add newly export symbol
  
- 
- However, there is a regression in Electron apps.
+ However, there is a regression in Electron apps. It looks like we'll
+ need to wait for Electron 1.9 for the regression to be fixed.
  
  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737
  
  https://github.com/electron/electron/pull/10213

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

Title:
  Update freetype to 2.8.1

Status in freetype package in Ubuntu:
  Fix Committed

Bug description:
  We should merge freetype 2.8.1 from Debian Testing.

  freetype (2.8.1-0.1) unstable; urgency=medium

    * Non-maintainer upload.
    * New upstream release (Closes: #876132)
  - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
    partially fixed upstream
  - debian/libfreetype6.symbols: Add newly export symbol

  However, there is a regression in Electron apps. It looks like we'll
  need to wait for Electron 1.9 for the regression to be fixed.

  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737

  https://github.com/electron/electron/pull/10213

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

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

[Touch-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

2017-12-15 Thread Scott Moser

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   Status: Fix Committed => Fix Released

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

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Released
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Fix Released
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)

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

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

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

Here's an improved artful debdiff taking into account Seth's comments.

** Patch removed: "bug-1733366-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022276/+files/bug-1733366-artful.debdiff

** Patch removed: "bug-1733366-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022277/+files/bug-1733366-zesty.debdiff

** Patch removed: "bug-1733366-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022278/+files/bug-1733366-xenial.debdiff

** Patch added: "bug-1733366-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5023241/+files/bug-1733366-artful.debdiff

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

2017-12-15 Thread Faron Anslow

I still have this problem. When I disconnect from a VPN, the various
resolv files retain a search line and DNS lookup fails for the domain
associated with the VPN (in this case, my university). Luckily, this is
fairly easy to work around (I no longer reboot to try to fix my
network). Did I miss something? Or has the fix been committed, but not
yet propagated out into a new systemd package in the repos? The post
above seems to indicate that the version 234-2ubuntu12 and above would
have the fix. I have 234-2ubuntu12.2 which I presume is newer.

here's output from dpkg-query -s systemd:

fanslow@sano:~$ dpkg-query -s systemd
Package: systemd
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 11704
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: foreign
Version: 234-2ubuntu12.2
Replaces: udev (<< 228-5)
Depends: libacl1 (>= 2.2.51-8), libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 
1:2.2.1), libblkid1 (>= 2.19.1), libc6 (>= 2.25), libcap2 (>= 1:2.10), 
libcryptsetup4 (>= 2:1.4.3), libgcrypt20 (>= 1.7.0), libgpg-error0 (>= 1.14), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), libkmod2 (>= 5~), 
liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libmount1 (>= 
2.26.2), libpam0g (>= 0.99.7.1), libseccomp2 (>= 2.3.1), libselinux1 (>= 
2.1.9), libsystemd0 (= 234-2ubuntu12.2), util-linux (>= 2.27.1), mount (>= 
2.26), adduser, procps
Pre-Depends: libc6 (>= 2.8)
Recommends: libpam-systemd, dbus
Suggests: systemd-container, policykit-1
Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
Conffiles:
 /etc/dhcp/dhclient-enter-hooks.d/resolved 17323c120a8bb9f8453c24b43d900203
 /etc/dhcp/dhclient-exit-hooks.d/timesyncd a891f21f45b0648b7082d999bf424591
 /etc/pam.d/systemd-user 3d97692a0125712fcfbd7ddf756f7696
 /etc/systemd/journald.conf b89a22c219efce8b3700feafc61e0c18
 /etc/systemd/logind.conf aeeac805b4bfb7450183ce346999dd38
 /etc/systemd/resolved.conf cda783b1a7bc2e01f2268b9df3c71934
 /etc/systemd/system.conf adc308320471c75a60e07184cf2ebb05
 /etc/systemd/timesyncd.conf 4e1cf2b5f85dff6c1f186135b9f66a85
 /etc/systemd/user.conf 675370e2d80a4ad957202e68c1b4aaee
Description: system and service manager
 systemd is a system and service manager for Linux. It provides aggressive
 parallelization capabilities, uses socket and D-Bus activation for starting
 services, offers on-demand starting of daemons, keeps track of processes using
 Linux control groups, maintains mount and automount points and implements an
 elaborate transactional dependency-based service control logic.
 .
 systemd is compatible with SysV and LSB init scripts and can work as a
 drop-in replacement for sysvinit.
 .
 Installing the systemd package will not switch your init system unless you
 boot with init=/bin/systemd or install systemd-sysv in addition.
Homepage: https://www.freedesktop.org/wiki/Software/systemd
Original-Maintainer: Debian systemd Maintainers 


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

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3)

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

And the xenial one.

** Patch added: "bug-1733366-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5023243/+files/bug-1733366-xenial.debdiff

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'

Here's a zesty debdiff.

** Patch added: "bug-1733366-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5023242/+files/bug-1733366-zesty.debdiff

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

Title:
  apport crashed with FileNotFoundError in is_container_pid(): [Errno 2]
  No such file or directory: '/proc/11102/ns/pid'

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Zesty:
  Confirmed
Status in apport source package in Artful:
  Confirmed
Status in apport source package in Bionic:
  Fix Released

Bug description:
  It appears that after login this was the first action performed by the
  system which resulted in the generation of the crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 
01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash
  Date: Mon Nov 20 01:59:46 2017
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2017-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop 
Experience Bionic Beaver"
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102']
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] 
No such file or directory: '/proc/11102/ns/pid'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 242533] Re: weather applet beaufort scale should use descriptions and not numbers.

2017-12-15 Thread Bug Watch Updater

** Changed in: libgweather
   Status: New => Won't Fix

** Changed in: libgweather
   Importance: Medium => Wishlist

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

Title:
  weather applet beaufort scale should use descriptions and not numbers.

Status in libgweather:
  Won't Fix
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-applets

  The weather applet, when set to use the Beaufort scale, should at least have 
an option to present descriptions instead of numbers.  Descriptions may be 
found at http://en.wikipedia.org/wiki/Beaufort_scale#The_modern_scale (accessed 
June 23, 2008, permalink:
  http://en.wikipedia.org/w/index.php?title=Beaufort_scale&oldid=220195075): 
look in the table under the "Description" column.  
  To reproduce:
  1. set the weather applet to use the Beaufort scale: right click on it and 
choose preferences, from there set the wind speed unit
  2. view the weather (you may have to hit update to see it using the Beaufort 
scale).
  This is a wishlist bug/enhancement

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

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-12-15 Thread José Manuel

I experienced this bug too. #2 fixes the problem but also removes
plasma-pa. When plasma-pa is reinstalled it breaks pulseaudio again.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  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:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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.

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

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

[Touch-packages] [Bug 1738515] [NEW] [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at all after plugging in headphones

2017-12-15 Thread Paul Williams

Public bug reported:

Sound worked before, but after plugging in headphones, sound does not work 
through either headphones or internal speakers. Sound continues not to work 
after unplugging headphones.
I tried:
1. killall pulseaudio; rm -r ~/.config/pulse/* ; rm -r ~/.pulse*
2. wait 10 seconds 
3. reboot

Then sound worked in internal speakers, but when I plugged in
headphones, I got the same result. I tested the sound using "Test
Speakers" in Settings, and by playing youtube videos in Firefox.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
 /dev/snd/controlC0:  paul   1374 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 22:15:26 2017
InstallationDate: Installed on 2017-12-08 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
 /dev/snd/controlC0:  gdm1055 F pulseaudio
  paul   1374 F pulseaudio
Symptom_Jack: Black Speaker, Internal
Symptom_Type: No sound at all
Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0WVDX2
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd08/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at
  all after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound worked before, but after plugging in headphones, sound does not work 
through either headphones or internal speakers. Sound continues not to work 
after unplugging headphones.
  I tried:
  1. killall pulseaudio; rm -r ~/.config/pulse/* ; rm -r ~/.pulse*
  2. wait 10 seconds 
  3. reboot

  Then sound worked in internal speakers, but when I plugged in
  headphones, I got the same result. I tested the sound using "Test
  Speakers" in Settings, and by playing youtube videos in Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
   /dev/snd/controlC0:  paul   1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 22:15:26 2017
  InstallationDate: Installed on 2017-12-08 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
paul   1374 F pulseaudio
  Symptom_Jack: Black Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0WVDX2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd08/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.produc

[Touch-packages] [Bug 1724079] Re: bluetooth applet hangs - 17.10 artful