[Touch-packages] [Bug 1692437] Re: Monitors on second GPU not working after upgrade to zesty

[Richard Eames]

lspci and lshw show 2 GPUs. The builtin one, and the actual card, but
xrandr only lists one provider.

$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 
associated providers: 0 name:KAVERI @ pci::00:01.0


Might be a bug in the radeon driver?

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

** Also affects: xserver-xorg-driver-radeonhd
   Importance: Undecided
   Status: New

** Attachment added: "lspci -vvv"
   
https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1692437/+attachment/4881502/+files/lspci.txt

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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

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

[Touch-packages] [Bug 1692582] Re: RFE: dbus AppArmor mediation matching by message type

[Simon McVittie]

If I'm reading the AppArmor user-space source code correctly, if
backwards compatibility wasn't a concern then this could be achieved by
adding an additional user-defined field to vec in
dbus_rule::gen_policy_re(Profile&) and passing the new number of fields
to add_rule_vec(), then adding that same field to the queries built by
dbus-daemon in bus/apparmor.c build_message_query().

Unfortunately, again if I'm reading correctly, the query works by
building a long string with embedded \0 bytes, then matching it against
a DFA representing a single long regular expression that also has
embedded \0 bytes - if true, this would mean the number of fields can't
usefully be varied.

If extensibility is desired, I think the ideal thing might be if extra
fields in the query were ignored (always match) and extra fields in the
rule were compared as though the query had an empty string at that point
in the vector, but I don't know how feasible that would be.

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

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 1692582] Re: RFE: dbus AppArmor mediation matching by message type

[John Johansen]

There are actually a couple of ways to add it, and still keep userspace
compatibility. Kernel side we are actually often checking partial
matches, and due is a permission but AA_CONTINUE to indicate that if
permissions aren't satisfied to continue the match.

This could be emulated in userspace a couple different ways, either by
the dbus pulling the policy it needs and doing the match entirely in
userspace (currently this would be the entire policy but the way things
are setup this could be split out so dbus could request on the dbus
relevant bits), ideally all this would just be a couple of calls into
libapparmor. Or the code could use the current interface and round trip
the kernel a couple of times (not ideal), though this approach becomes
less and less serviceable long term).

A third approach would be to tack the type field onto the larger match
string and do it as a single match.

Another approach would be to improve the kernel interfaces and update
the dbus code to the improved query/matching.

All of these of course rely on the policy being able to carry some
information to dbus to allow it to know if it should use the newer
policy, do the extra match, what ever approach is chosen. AppArmor
already has support for a key/value pair storage (its even in the
upstream kernel) in policy that could be leveraged to do this.

So there are lots of options available, its a matter of choosing a
design and doing the work.

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

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 1669270] Re: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

[Steve Langasek]

An error code of '10' from debconf generically means that wrong
arguments have been passed.

Please show the output of 'debconf-show ucf'

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

Title:
  package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 10

Status in ucf package in Ubuntu:
  New

Bug description:
  When I start my screen, a blue screen appears with 2 options,
  1. GNU/grub-pc
  2. Advanced options for ubuntu.

  And I have to always click on 1 to get my PC started(or it
  automatically chooses 1).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-pc 2.02~beta2-36ubuntu3.7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Mar  2 10:55:13 2017
  DpkgHistoryLog:
   Start-Date: 2017-03-02  10:55:02
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libgd3:amd64 (2.1.1-4ubuntu0.16.04.5, 2.1.1-4ubuntu0.16.04.6), 
libtiff5:amd64 (4.0.6-1, 4.0.6-1ubuntu0.1)
  DuplicateSignature:
   package:grub-pc:2.02~beta2-36ubuntu3.7
   Setting up unattended-upgrades (0.90ubuntu0.3) ...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2017-02-16 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InvalidGrubScript: /etc/default/grub
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=3cfa4b16-e389-41c3-a5c6-98add8a87218 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: grub2
  Title: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692582] Re: RFE: dbus AppArmor mediation matching by message type

[John Johansen]

@Simmon,

You are right, that will require extending what is supported in the
mediation, beyond even landing support for #2. It will take a bit of
work, but we can definitely do it. My preferred solution is more work
than the quickest/easiest solution, as it requires landing a few things
that haven't landed yet or are in the process of landing, but overall I
would rather go with the best long term solution.

What time frame are you looking for to land fixes for this. Earliest
possible for the userspace mediation would be the next apparmor release
in the fall. The dbus code changes could be done off of development
trees, and as long as care is taken to maintain backwards compatibility,
along with a few build conditionals, it could land any time that is
suitable for dbus.

A going with a solution that uses the current interfaces and doesn't
have any build deps could potentially be added to an apparmor point
release, and land a bit sooner.

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

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.5p1-3ubuntu1

---
openssh (1:7.5p1-3ubuntu1) artful; urgency=medium

  * On s390x, allow geteuid syscall in the sandbox, to allow openssh
connections to work when hw accelerated cryptography is enabled. This
patch is to be replaced by the one accepted upstream, when
reviewed. LP: #1686618

 -- Dimitri John Ledkov   Mon, 22 May 2017 13:13:59
+0100

** Changed in: openssh (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  In Progress
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 

[Touch-packages] [Bug 1692671] [NEW] intel driver fails to reenable display

[Alejandro Mery]

Public bug reported:

if the display is sent to sleep it won't wake up. If I go to tty1 or
tty2 I'm pulled back to tty7 (?) within seconds.

sometimes if I ctrl-alt-del I'm sent back to the login screen and from
there I can resume the session.

everything was working fine with my previous (1920x1080) display, but
since I switched to a 3840x2160 display the only reliable solution to
get the computer back from blanking is pressing the power button. I can
then see the shutdown "splash" and after powering it back again
everything is back to normal. until it blanks the screen again obviusly

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon May 22 19:16:43 2017
InstallationDate: Installed on 2015-12-27 (512 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

** Affects: xorg (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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1692671

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "sudo get-edid | parse-edid"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881543/+files/edid.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

[Dimitri John Ledkov]

** Changed in: ifupdown (Ubuntu)
   Importance: Medium => High

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown source package in Xenial:
  New

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1692582] Re: RFE: dbus AppArmor mediation matching by message type

[John Johansen]

The message type certain could be added. However it is not the only way
this separation can be achieved.

The label in particular should be able to be used without tying it to a
specific service. Admittedly this is somewhat limited atm.

1. the label name on a service does not have to match its executable
name so an executable could be labeled with a more generic profile. This
however will not work in cases where an executable maybe servicing
multiple service end points that want different labels, and would be
require #2.

2. while conceptually apparmor supports having none application (domain)
labels on objects, the support for enabling a service to provide a
different label while creating sockets has not landed yet, so until it
does, apparmor policy currently is tying the service confinement and
policy tighter than it should.

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

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 1692594] Re: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1692594

Title:
  package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I always get system error during system start-up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgail-3-0:amd64 3.18.9-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 15 23:25:21 2017
  DuplicateSignature:
   package:libgail-3-0:amd64:3.18.9-1ubuntu3.3
   Setting up libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ...
   dpkg: error processing package libgail-3-0:amd64 (--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 2015-01-29 (844 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gtk+3.0
  Title: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (294 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1692594/+subscriptions

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

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692561] Re: Version 4.5 has been released

[Nikita Yerenkov-Scott]

** Summary changed:

- Version 4.5 has beel released
+ Version 4.5 has been released

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

Title:
  Version 4.5 has been released

Status in shadow package in Ubuntu:
  New

Bug description:
  Version 4.5 has just been released so it would be nice to get it into
  the repositories some time soon: https://github.com/shadow-
  maint/shadow/releases/tag/4.5

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

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

[Touch-packages] [Bug 1613043] Re: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1682934
   python3 in /usr/local/bin can cause python3 packages to fail to install

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

Title:
  package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to
  install/upgrade: подпроцесс установлен сценарий pre-removal возвратил
  код ошибки 1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.1-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 13 13:53:39 2016
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2015-08-12 (367 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.1-1~ubuntu16.04.1 failed to 
install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код 
ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1613043/+subscriptions

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

[Touch-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Balint Reczey]

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

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in apparmor package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  In Progress

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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

Re: [Touch-packages] [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')

[Robin Smith]

From: Serhiy Zahoriya <1383...@bugs.launchpad.net>
Subject: [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v 
-t')
Date: Mon, 22 May 2017 10:51:47 -

> I've found a clue. It's a server with limited bandwidth and it's
> currently using all of it. Not sure how the limit works, but I'm sure
> that's the problem: something is placing nginx traffic above scp traffic
> and the latter waits for hours.

Thanks for this.  Since the time of this initial report, I've changed
server. At that time, I was on a DSL (!) connection, which of course
had limited bandwidth, since fiber wasn't available at my location.
However, I have seen an occasional long hang on scp and also on ssh
since then, so the issue is perhaps still around (it was ATT in both
cases, though now it's "Uverse", which does have a known problem with
periodic drops on ssh connections, though ATT doesn't provide any help
about this). 

> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1383470
> 
> Title:
>   scp does not work (fails at 'Sending command scp -v -t')
> 
> Status in openssh package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   Following the last update of Ubuntu 14.02, scp (in the default system) has 
> ceased working. It hangs after authentication at the point where it wold 
> start an interactive session.  I've verified that the problem is in my 
> system: scp still works at the target machine and scp won't work on my 
> machine to various hosts.  Output below.
>   rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org:
>   Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), 
> command scp -v -t .
>   OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
>   debug1: Reading configuration data /home/rasmith/.ssh/config
>   debug1: /home/rasmith/.ssh/config line 17: Applying options for *
>   debug1: /home/rasmith/.ssh/config line 20: Deprecated option 
> "rhostsauthentication"
>   debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh"
>   debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh"
>   debug1: Reading configuration data /etc/ssh/ssh_config
>   debug1: /etc/ssh/ssh_config line 19: Applying options for *
>   debug1: Connecting to apacentral.org [65.19.130.61] port 22.
>   debug1: Connection established.
>   debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or 
> directory
>   debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such 
> file or directory
>   debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission 
> denied
>   debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such 
> file or directory
>   debug1: identity file /home/rasmith/.ssh/identity type 0
>   debug1: identity file /home/rasmith/.ssh/identity-cert type -1
>   debug1: Remote protocol version 2.0, remote software version 
> OpenSSH_6.4_hpn13v11 FreeBSD-2013
>   debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 
> 0x0400
>   debug1: Enabling compatibility mode for protocol 2.0
>   debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
>   debug1: SSH2_MSG_KEXINIT sent
>   debug1: SSH2_MSG_KEXINIT received
>   debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none
>   debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none
>   debug1: sending SSH2_MSG_KEX_ECDH_INIT
>   debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
>   debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae
>   debug1: Host 'apacentral.org' is known and matches the RSA host key.
>   debug1: Found key in /home/rasmith/.ssh/known_hosts:26
>   debug1: ssh_rsa_verify: signature correct
>   debug1: SSH2_MSG_NEWKEYS sent
>   debug1: expecting SSH2_MSG_NEWKEYS
>   debug1: SSH2_MSG_NEWKEYS received
>   debug1: Roaming not allowed by server
>   debug1: SSH2_MSG_SERVICE_REQUEST sent
>   debug1: SSH2_MSG_SERVICE_ACCEPT received
>   debug1: Authentications that can continue: publickey,keyboard-interactive
>   debug1: Next authentication method: publickey
>   debug1: Offering DSA public key: rasm...@aristotle.tamu.edu
>   debug1: Server accepts key: pkalg ssh-dss blen 433
>   debug1: Authentication succeeded (publickey).
>   Authenticated to apacentral.org ([65.19.130.61]:22).
>   debug1: channel 0: new [client-session]
>   debug1: Requesting no-more-sessi...@openssh.com
>   debug1: Entering interactive session.
>   debug1: Sending environment.
>   debug1: Sending env LANG = 

[Touch-packages] [Bug 1692594] [NEW] package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Arun Joshi]

Public bug reported:

I always get system error during system start-up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgail-3-0:amd64 3.18.9-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 15 23:25:21 2017
DuplicateSignature:
 package:libgail-3-0:amd64:3.18.9-1ubuntu3.3
 Setting up libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ...
 dpkg: error processing package libgail-3-0:amd64 (--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 2015-01-29 (844 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gtk+3.0
Title: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-07-31 (294 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I always get system error during system start-up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgail-3-0:amd64 3.18.9-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 15 23:25:21 2017
  DuplicateSignature:
   package:libgail-3-0:amd64:3.18.9-1ubuntu3.3
   Setting up libgtk-3-0:amd64 (3.18.9-1ubuntu3.3) ...
   dpkg: error processing package libgail-3-0:amd64 (--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 2015-01-29 (844 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gtk+3.0
  Title: package libgail-3-0:amd64 3.18.9-1ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (294 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1692594/+subscriptions

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

[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "lspci -v"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881544/+files/lspci.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Touch-packages] [Bug 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881545/+files/dmesg.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 233-6ubuntu3

---
systemd (233-6ubuntu3) artful; urgency=medium

  * resolved: fix null pointer dereference crash (LP: #1621396)

 -- Dimitri John Ledkov   Mon, 22 May 2017 09:29:22
+0100

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

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1692718] [NEW] /lib/systemd/systemd-resolved:11:dns_packet_is_reply_for:dns_transaction_process_reply:on_dns_packet:source_dispatch:sd_event_dispatch

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

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


** Tags: artful xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
resolved:11:dns_packet_is_reply_for:dns_transaction_process_reply:on_dns_packet:source_dispatch:sd_event_dispatch

Status in systemd package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

[spike speigel]

Here's an earlier bug report (~Dec 2015):

http://lkml.iu.edu/hypermail/linux/kernel/1512.1/02819.html

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

Title:
  XPS 13 9360, Realtek ALC3246, Headphone audio hiss

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

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

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

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

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Jean-Pol Landrain]

Seeing this after upgrade from 16.04 to 16.10

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

** Description changed:

  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space in
  /boot temporarily. But there is no space left, if /boot is full.
  
  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".
  
  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.
  
  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
+ That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.
  
  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692705] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1692705

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  no idea just reporting this error i get on startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 03:51:46 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-05-19 (734 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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

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

[Touch-packages] [Bug 1692710] [NEW] [System Product Name, Realtek ALC1200, Green Line Out, Rear] Pulseaudio, Jack and ALSA seem to work, but there's no sound output

[Paul van Leeuwen]

Public bug reported:

I've got Ubuntu 17.04 installed with KXStudio on top of that.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
Uname: Linux 4.10.0-21-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon May 22 22:29:46 2017
InstallationDate: Installed on 2017-05-21 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA ATI SB
Symptom_Jack: Green Line Out, Rear
Title: [System Product Name, Realtek ALC1200, Green Line Out, Rear] Pulseaudio 
fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78 PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd01/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  [System Product Name, Realtek ALC1200, Green Line Out, Rear]
  Pulseaudio, Jack and ALSA seem to work, but there's no sound output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I've got Ubuntu 17.04 installed with KXStudio on top of that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 22:29:46 2017
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Title: [System Product Name, Realtek ALC1200, Green Line Out, Rear] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78 PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0801:bd01/05/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1692718] Re: /lib/systemd/systemd-resolved:11:dns_packet_is_reply_for:dns_transaction_process_reply:on_dns_packet:source_dispatch:sd_event_dispatch

[Dimitri John Ledkov]

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

** This bug has been marked a duplicate of bug 1621396
   systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

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

Title:
  /lib/systemd/systemd-
  
resolved:11:dns_packet_is_reply_for:dns_transaction_process_reply:on_dns_packet:source_dispatch:sd_event_dispatch

Status in systemd package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1665785] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise or low volume

[Launchpad Bug Tracker]

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise
  or low volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  There is a background hissing/squeaking noise in my headphones every time I 
resume suspend.
  Speakers and HDMI audio are not affected.
  I've tried many solutions to fix it (alsa force-reload etc.), but none of 
them worked well.
  More detailes you can find here:
  
http://askubuntu.com/questions/884051/constant-hissing-sound-after-suspend-asus-zenbook-ux501-vw

  
  Standard four questions:
  1) Ubuntu 16.04.1 LTS
  2) Kernel 4.8.17-040817-generic (also tried 4.4.0 and 4.3.5)
  3) When I resume suspend I hear no noise unless I play something
  4) Right after suspend resume there is a background noise

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.8.17-040817-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   firesword   3563 F...m pulseaudio
   /dev/snd/pcmC0D0p:   firesword   3563 F...m pulseaudio
   /dev/snd/controlC0:  firesword   3563 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 17 23:54:52 2017
  InstallationDate: Installed on 2017-02-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-17T21:26:16.180413

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

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

[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

In Artful, we have (running with -proposed for open-iscsi and lvm2):

● snapd.service loaded failed failed Snappy daemon 
● snapd.socket  loaded failed failed Socket activation for snapp
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

snapd team probably need to fix the first two.

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  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
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692714] [NEW] Unstable Wifi: re-Authentication fails after wifi drops and reconnects

[Laurens Kils-Hütten]

Public bug reported:

I see frequent disconnects due to reason=4, which would be o.k. if
reconnects worked fine. However often on reconnects 4-way handshake
times out and I'm prompted to re-enter our wifi pass-phrase, sometimes
as frequent as every few minutes - a major annoyance :-(

Problem seems to depend a bit on network traffic. However only my
notebook with ubuntu 17.04. seems to be affected. Two iphones, an
android phone and a chromebook seem to have no wifi problems at all.

Also, when I set up wls2 manually in /etc/network/interfaces I haven't
seen failed reconnects so far.

I have had this problem since 16.04. Various work arounds suggested on
the web like changing wifi channel, disabling IPv6, or disabling DHCP
haven't affected this problem.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May 22 22:34:01 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-08-28 (267 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
IpRoute:
 default via 192.168.2.1 dev wls2 proto static metric 600 
 169.254.0.0/16 dev wls2 scope link metric 1000 
 192.168.2.0/24 dev wls2 proto kernel scope link src 192.168.2.129 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-14 (38 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug zesty

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

Title:
  Unstable Wifi: re-Authentication fails after wifi drops and reconnects

Status in network-manager package in Ubuntu:
  New

Bug description:
  I see frequent disconnects due to reason=4, which would be o.k. if
  reconnects worked fine. However often on reconnects 4-way handshake
  times out and I'm prompted to re-enter our wifi pass-phrase, sometimes
  as frequent as every few minutes - a major annoyance :-(

  Problem seems to depend a bit on network traffic. However only my
  notebook with ubuntu 17.04. seems to be affected. Two iphones, an
  android phone and a chromebook seem to have no wifi problems at all.

  Also, when I set up wls2 manually in /etc/network/interfaces I haven't
  seen failed reconnects so far.

  I have had this problem since 16.04. Various work arounds suggested on
  the web like changing wifi channel, disabling IPv6, or disabling DHCP
  haven't affected this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 22:34:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-28 (267 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  IpRoute:
   default via 192.168.2.1 dev wls2 proto static metric 600 
   169.254.0.0/16 dev wls2 scope link metric 1000 
   192.168.2.0/24 dev wls2 proto kernel scope link src 192.168.2.129 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (38 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

[John Johansen]

This is caused do a change made upstream in the 4.11 kernel, which
forbids writing the buffer size parameter after boot. The change to boot
time preallocated work buffers made this parameter useless, but 4.11
only partially merged that work, making writing the buffer size an
attack vector on the kernel memory and with user namespaces enabled any
user could exploit it. Hence a follow-on patch to make the buffer size
read-only after boot.

We have 2 choices for dealing with this, either fix the regression tests
OR we can virtualize the buffer size parameter per namespace, capping
the virtualized size by what was allocated at boot.

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

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

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

[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas H. Silva]

** Description changed:

+ THE ISSUE:
+ The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
+ 
  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
- THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
- 
  It can always be reproduced. I can record a video of the issue if
  needed.

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

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+subscriptions

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

[Touch-packages] [Bug 1692705] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Dino]

Public bug reported:

no idea just reporting this error i get on startup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue May 23 03:51:46 2017
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-05-19 (734 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  no idea just reporting this error i get on startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 03:51:46 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-05-19 (734 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Dimitri John Ledkov]

** Description changed:

- This is one of background errors that happens without any active app being 
involved. 
+ This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal
+ 
+ [Testcase]
+ Notice the dropoff rate of the crash report on errors:
+ 
+ The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd. This problem was most recently seen with package version 233-6ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
+ If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
-  ?? ()
-  ?? ()
-  ?? () from /lib/systemd/libsystemd-shared-231.so
-  sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
-  sd_event_run () from /lib/systemd/libsystemd-shared-231.so
+  ?? ()
+  ?? ()
+  ?? () from /lib/systemd/libsystemd-shared-231.so
+  sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
+  sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  [Testcase]
  Notice the dropoff rate of the crash report on errors:

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

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
 

[Touch-packages] [Bug 1692152] Re: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** 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/1692152

Title:
  package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  i am getting following error: when i am trying to install anything

  ubuntu@ubuntu:~$ sudo apt install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
apport
  The following packages will be upgraded:
apport
  1 upgraded, 0 newly installed, 0 to remove and 410 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/121 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 291353 files and directories currently installed.)
  Preparing to unpack .../apport_2.20.4-0ubuntu4_all.deb ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.4-0ubuntu4_all.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1
  Error: Timeout was reached
  E: Sub-process /usr/bin/dpkg exited unexpectedly

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.3-0ubuntu8.2
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   apport:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   644:0:116:0:2017-05-20 07:24:12.658019135 +0530:2017-05-20 
07:24:12.658019135 +0530:/var/crash/_usr_bin_pyclean.0.upload
   640:0:116:60537:2017-05-20 07:24:09.354035139 +0530:2017-05-20 
07:24:10.354035139 +0530:/var/crash/_usr_bin_pyclean.0.crash
   600:0:116:1700582:2017-05-20 07:23:00.490636348 +0530:2017-05-20 
07:23:01.490636348 +0530:/var/crash/apport.0.crash
   640:0:116:14562:2017-05-20 07:23:00.998641622 +0530:2017-05-20 
07:23:00.998641622 +0530:/var/crash/_usr_bin_pycompile.0.crash
  Date: Sat May 20 07:23:00 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-05 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-05-18 (1 days ago)

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

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

[Touch-packages] [Bug 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')

[Seth Arnold]

Hello Senad, try:

sudo apt-get update
sudo apt-get -f install
sudo dpkg --configure -a

Thanks

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

Title:
  package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade:
  package iproute2 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  I dont know anything. I just try to instal some programs on my comp,
  and when i try to start virtualbox it cant.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   iproute2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 20 16:22:19 2017
  DpkgTerminalLog:
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-20 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
package iproute2 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade:
  package iproute2 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  I dont know anything. I just try to instal some programs on my comp,
  and when i try to start virtualbox it cant.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   iproute2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 20 16:22:19 2017
  DpkgTerminalLog:
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-20 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
package iproute2 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692748] [NEW] el equipo no puede actulizarce

[jose cordova]

Public bug reported:

El equipo no puede actualizar ya que hubo un error , el sistema me dice
que active el gestor de paquetes pero tampoco puedo activarlo ya que el
sistema no me lo permite por favor necesito ayuda, saludos.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon May 22 21:07:51 2017
DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0936]
InstallationDate: Installed on 2017-04-03 (50 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
MachineType: Acer Aspire ES1-512
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago)
dmi.bios.date: 08/11/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-512
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2014:svnAcer:pnAspireES1-512:pvrV1.06:rvnAcer:rnAspireES1-512:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.name: Aspire ES1-512
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1
xserver.bootTime: Mon May 22 19:57:24 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


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

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

Title:
  el equipo no puede actulizarce

Status in xorg package in Ubuntu:
  New

Bug description:
  El equipo no puede actualizar ya que hubo un error , el sistema me
  dice que active el gestor de paquetes pero tampoco puedo activarlo ya
  que el sistema no me lo permite por favor necesito ayuda, saludos.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon May 22 21:07:51 2017
  DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0936]
  InstallationDate: Installed on 2017-04-03 (50 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: Acer Aspire ES1-512
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  

[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

[Steve Langasek]

I've adjusted the bug description to match my understanding of the
actual problem.

AIUI this does not happen on a disconnected system; if motd.ubuntu.com
cannot resolve or returns ECONNREFUSED or EHOSTUNREACH, there should be
no 5-second delay.  The error only happens on a system which has routes,
but has a firewall that drops packets instead of responding to the
request.  (Or when motd.u.c is actually down.)

So, what you appear to be describing here is a deliberate design
tradeoff.  Unless you are recommending a different timeout (if so, what
value?) or asking for this to be disabled altogether (in which case I
will refer you to Dustin), I think the only solution here is for your
lab to have suitable firewall+proxy settings.

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  New

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+subscriptions

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

[Touch-packages] [Bug 124743] Re: Sony Sixaxis Controller does not work over bluetooth

[Daniel van Vugt]

dandart, all: If you continue to have issues then please log a new bug using 
this command:
   ubuntu-bug bluez

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

Title:
  Sony Sixaxis Controller does not work over bluetooth

Status in Ubuntu PS3 Port:
  New
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Sixaxis controller has limited functionality as a USB device (no
  motion sensor axis support) but is not able to pair and be recognized
  from Feisty install.  External tools are needed to allow it to pair,
  but kernel support may also be required.

  Please see:
  http://ubuntuforums.org/showthread.php?p=2983423#post2983423

  tools and patch available here:
  http://www.pabr.org/sixlinux/sixlinux.en.html

  Bluetooth packet log from attempt on OS X:
  
http://mt.creativepony.com/drop-box/PacketLogger%20Sixaxis%20Bluetooth.pklg.zip

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ps3-port/+bug/124743/+subscriptions

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

[Touch-packages] [Bug 997331] Re: Some ALSA applications play bad sound

[Daniel van Vugt]

** Summary changed:

- Some alsa applications play bad sound
+ Some ALSA applications play bad sound

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

Title:
  Some ALSA applications play bad sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Some applications using ALSA plays bad sound. One is WINE
  applications. Winecfg test sound is distorted (sounds awful). Spotify
  running WINE plays songs way too fast. A flash based program play
  distorted sound. The common thing for all of them is that under
  Applications in Sound settings it says alsa-plugin and it flashes very
  rapidly between "No application is currently playing" and alsa-plugin.
  It almost looks like flickering. I've testet a normal wave file using
  aplay and that was okey, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC0:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC1:  oeriksen   3299 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 41
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at 
usb-:00:1d.0-1.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:4083'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 48
 Mono: Capture 45 [94%] [18.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Wed May  9 22:41:04 2012
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback 
problem
  UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago)
  dmi.bios.date: 02/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 REV 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1692782] [NEW] package libharfbuzz0b:amd64 1.0.1-1build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Shardul Bankar]

Public bug reported:

The error came while performing the following operation:
sudo apt-get install git-core gnupg flex bison gperf build-essential   zip curl 
zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386   lib32ncurses5-dev 
x11proto-core-dev libx11-dev lib32z-dev ccache   libgl1-mesa-dev libxml2-utils 
xsltproc unzip

This was the message on the console:

The following package was automatically installed and is no longer required:
  libpango1.0-0
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
14 not fully installed or removed.
Need to get 140 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 libharfbuzz0b amd64 
1.0.1-1build2 [140 kB]
Fetched 140 kB in 1s (111 kB/s)   
dpkg: error processing package libharfbuzz0b:amd64 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
No apport report written because the error message indicates its a followup 
error from a previous failure.
  E: Sub-process /usr/bin/dpkg returned an error code 
(1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libharfbuzz0b:amd64 1.0.1-1build2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue May 23 09:42:55 2017
DpkgTerminalLog:
 dpkg: error processing package libharfbuzz0b:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-19 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: harfbuzz
Title: package libharfbuzz0b:amd64 1.0.1-1build2 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)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libharfbuzz0b:amd64 1.0.1-1build2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  The error came while performing the following operation:
  sudo apt-get install git-core gnupg flex bison gperf build-essential   zip 
curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386   lib32ncurses5-dev 
x11proto-core-dev libx11-dev lib32z-dev ccache   libgl1-mesa-dev libxml2-utils 
xsltproc unzip

  This was the message on the console:

  The following package was automatically installed and is no longer required:
libpango1.0-0
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
  14 not fully installed or removed.
  Need to get 140 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 libharfbuzz0b 
amd64 1.0.1-1build2 [140 kB]
  Fetched 140 kB in 1s (111 kB/s)   
  dpkg: error processing package libharfbuzz0b:amd64 (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  No apport report written because the error message indicates its a followup 
error from a previous failure.
E: Sub-process /usr/bin/dpkg returned an error code 
(1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libharfbuzz0b:amd64 1.0.1-1build2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue May 23 09:42:55 2017
  DpkgTerminalLog:
   dpkg: error processing package libharfbuzz0b:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: harfbuzz
  Title: package libharfbuzz0b:amd64 1.0.1-1build2 failed to install/upgrade: 

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Ancell]

All current duplicates are for Zesty, except for bug 1691599 (Artful)
and bug 1692344 (Yakkety).

** Also affects: gconf (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Fix Released

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

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

** Changed in: gnome-software (Ubuntu Zesty)
   Importance: Undecided => High

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1652148] Re: I am not able to print on my new canon laser shot LBP2900B printer

[Launchpad Bug Tracker]

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

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

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

Title:
  I am not able to print on my new canon laser shot LBP2900B printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  i am able to find the printer on the system but it is not able to print...
  in the status of printer it shows "idle:sending file to printer"
  or "sending file to printer" or "Idle - Sending data to printer. "but the 
printer doesnt prints

  output of lpusb commmand
  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 004: ID 8087:0a2a Intel Corp. 
  Bus 002 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd 
  Bus 002 Device 012: ID 04a9:2676 Canon, Inc. CAPT Device
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  printer :canon laser shot LBP2900B printer
   driver downloaded from : 
http://gdlp01.c-wss.com/gds/6/014596/04/Linux_CAPT_PrinterDriver_V270_uk_EN.tar.gz
   Tried x64 bit drivers

  expected: printer to print

  happened : no response from printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 23 00:26:32 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for CanonLBP2900B: usb://Canon/LBP2900?serial=C1G97FQN
  MachineType: FUJITSU LIFEBOOK A555
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CanonLBP2900B.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CanonLBP2900B.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=94e9467b-205b-43c4-b1ca-7f285806bdba ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: 1.21
  dmi.board.name: FJNBB3E
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A555
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Ancell]

Using the purge technique I can also reproduce in Xenial. I suspect this
problem isn't being seen much pre-Zesty because gconf is already
installed (pulled in by aisleriot and probably other older pacakges).

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in gconf source package in Xenial:
  New
Status in gnome-software source package in Xenial:
  New
Status in gconf source package in Yakkety:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New
Status in gconf source package in Artful:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Ancell]

By purging gconf2-common, I can reproduce in Artful.

i.e.
$ sudo apt purge gconf2-common
$ gnome-software --local-filename 
~/Downloads/google-chrome-stable_current_amd64.deb 


** Changed in: gnome-software (Ubuntu)
   Status: Fix Released => New

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

** Also affects: gconf (Ubuntu Artful)
   Importance: High
   Status: New

** Also affects: gnome-software (Ubuntu Artful)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: New

** Also affects: gconf (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Changed in: gnome-software (Ubuntu Yakkety)
   Importance: Undecided => High

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in gconf source package in Xenial:
  New
Status in gnome-software source package in Xenial:
  New
Status in gconf source package in Yakkety:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New
Status in gconf source package in Artful:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Robert Ancell]

I could reproduce in Zesty, but not Artful or Xenial.

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS

[Launchpad Bug Tracker]

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

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

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

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: 

[Touch-packages] [Bug 1663647] Re: cannot add printer

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot add printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  Terminal log follows

  neil@neil-Latitude-D630:~$ lsmod | grep usb
  usbhid 49152  0
  hid   118784  2 hid_generic,usbhid
  neil@neil-Latitude-D630:~$ tail -f /var/log/syslog
  Feb 10 15:02:17 neil-Latitude-D630 avahi-daemon[960]: Registering new address 
record for fe80::221:5cff:fe6f:bbe5 on wlp12s0.*.
  Feb 10 15:03:08 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:03:16 neil-Latitude-D630 systemd-timesyncd[463]: Synchronized to 
time server 91.189.94.4:123 (ntp.ubuntu.com).
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1581]: Time has been changed
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: Time has been changed
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: snapd.refresh.timer: Adding 5h 
11min 5.412159s random time.
  Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: apt-daily.timer: Adding 50min 
41.219140s random time.
  Feb 10 15:13:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:17:01 neil-Latitude-D630 CRON[15040]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
  Feb 10 15:23:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.068213] usb 2-4: new 
high-speed USB device number 4 using ehci-pci
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202919] usb 2-4: New USB 
device found, idVendor=04a9, idProduct=10d3
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202928] usb 2-4: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202934] usb 2-4: Product: 
iP2700 series
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202938] usb 2-4: 
Manufacturer: Canon
  Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202943] usb 2-4: 
SerialNumber: 234517
  Feb 10 15:33:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
  Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: checking bus 2, device 4: 
"/sys/devices/pci:00/:00:1d.7/usb2/2-4"
  Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: bus: 2, device: 4 was not an 
MTP device
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Starting Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4)...
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Started CUPS Scheduler.
  Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Reached target Printer.
  Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076606] usblp 2-4:1.0: 
usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10D3
  Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076648] usbcore: registered 
new interface driver usblp
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: add 
/devices/pci:00/:00:1d.7/usb2/2-4
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: device 
devpath is /devices/pci:00/:00:1d.7/usb2/2-4
  Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: MFG:Canon 
MDL:iP2700 series SERN:- serial:234517
  Feb 10 15:41:12 neil-Latitude-D630 kernel: [17269.577898] audit: type=1400 
audit(1486741272.103:36): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=15225 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Unit entered 
failed state.
  Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Failed with 
result 'exit-code'.
  Feb 10 15:41:17 neil-Latitude-D630 udev-configure-printer[15223]: failed to 
connect to CUPS server; giving up
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Control process exited, code=exited status=1
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4).
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Unit entered failed state.
  Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 

[Touch-packages] [Bug 1675527] Re: Caliu FTP server in Debian.mirrors

[Launchpad Bug Tracker]

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

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

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

Title:
  Caliu FTP server in Debian.mirrors

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  Hello!
  I am a sysadmin of the ftp.caliu.cat mirror of Ubuntu and Debian in 
Catalonia. I've noticed that in the list of Software Sources in the System 
Settings both ftp://ftp.caliu.cat and http://ftp.caliu.cat appear, but only the 
second one is working. Checking the Debian.mirrors in 
/usr/share/python-apt/templates ftp:// also appears there, and it should be 
removed. Only the http:// version should be there. For the Ubuntu.mirrors it is 
ok.

  Thank you!

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

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

[Touch-packages] [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')

[Seth Arnold]

Serhiy, Robin, I suggest investing traffic shaping / QoS solutions such
as http://lartc.org/wondershaper/ (packaged as 'wondershaper' in Ubuntu)
-- back when I had limited bandwidth this utility was quite wonderful.
You can of course achieve similar things without this specific tool.

Perhaps the more modern approach is to try the codel or fq_codel traffic
shaping tools; see https://www.bufferbloat.net/projects/ for more
information.

Thanks

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

Title:
  scp does not work (fails at 'Sending command scp -v -t')

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Following the last update of Ubuntu 14.02, scp (in the default system) has 
ceased working. It hangs after authentication at the point where it wold start 
an interactive session.  I've verified that the problem is in my system: scp 
still works at the target machine and scp won't work on my machine to various 
hosts.  Output below.
  rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org:
  Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), 
command scp -v -t .
  OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /home/rasmith/.ssh/config
  debug1: /home/rasmith/.ssh/config line 17: Applying options for *
  debug1: /home/rasmith/.ssh/config line 20: Deprecated option 
"rhostsauthentication"
  debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh"
  debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh"
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to apacentral.org [65.19.130.61] port 22.
  debug1: Connection established.
  debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or 
directory
  debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
denied
  debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file 
or directory
  debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
denied
  debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file 
or directory
  debug1: identity file /home/rasmith/.ssh/identity type 0
  debug1: identity file /home/rasmith/.ssh/identity-cert type -1
  debug1: Remote protocol version 2.0, remote software version 
OpenSSH_6.4_hpn13v11 FreeBSD-2013
  debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 
0x0400
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none
  debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae
  debug1: Host 'apacentral.org' is known and matches the RSA host key.
  debug1: Found key in /home/rasmith/.ssh/known_hosts:26
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: Roaming not allowed by server
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,keyboard-interactive
  debug1: Next authentication method: publickey
  debug1: Offering DSA public key: rasm...@aristotle.tamu.edu
  debug1: Server accepts key: pkalg ssh-dss blen 433
  debug1: Authentication succeeded (publickey).
  Authenticated to apacentral.org ([65.19.130.61]:22).
  debug1: channel 0: new [client-session]
  debug1: Requesting no-more-sessi...@openssh.com
  debug1: Entering interactive session.
  debug1: Sending environment.
  debug1: Sending env LANG = en_US.UTF-8
  debug1: Sending command: scp -v -t .

  (at this point, the command hangs more or less indefinitely until
  killed with Ctrl-C)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 15:25:14 2014
  InstallationDate: Installed on 2012-10-18 (732 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  

[Touch-packages] [Bug 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

[Steve Langasek]

** Summary changed:

- 50-motd-news costs 5 seconds every login on disconnected systems
+ 50-motd-news costs 5 seconds every login on firewalled systems

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  New

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+subscriptions

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

[Touch-packages] [Bug 1692454] Re: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

[Daniel van Vugt]

** Tags added: nosound vm

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  no audio at all

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 14:08:44 2017
  InstallationDate: Installed on 2017-05-17 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Touch-packages] [Bug 1692582] [NEW] RFE: dbus AppArmor mediation matching by message type

[Simon McVittie]

Public bug reported:

Suppose you're writing an AppArmor profile for a D-Bus service like
Tracker. The service might get compromised (perhaps it's network-facing)
so you don't want it to be able to act as a client of privileged
processes like systemd --user. However, imagine you do want arbitrary
third-party "apps" to be allowed to use the service if they have
appropriate rules in their own AppArmor profiles.

One reasonably natural way to encode this without tightly coupling the
service and its clients would be:

profile /usr/bin/my-service {
  ...
  dbus send bus=session type=signal,
  dbus receive bus=session type=method_call,
}

profile /usr/bin/my-client-app {
  ...
  dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
}

However, the AppArmor integration in src:dbus and the rule parser in
src:apparmor don't allow this: they match fine-grained information like
the method name and object path, but have no concept of message types.
This seems backwards: I only expect the object path to be useful in very
rare/niche cases, but the message type is "larger" and more important
than anything else from the message payload.

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

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

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Steve Langasek]

** Changed in: aptdaemon
 Assignee: aden iwa rante (radeniw) => (unassigned)

** Changed in: aptdaemon (Ubuntu)
   Status: New => Triaged

** Changed in: debconf (Ubuntu)
   Status: New => Triaged

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1692793] [NEW] [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

[Ram Mandal]

Public bug reported:

I recently upgraded my system from 14.04LTS to 16.04LTS. 
But now I cannot hear any sound from any player or youtube.

executing the command

aplay -l

I get the harware information like

 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
 /dev/snd/controlC0:  ronem  1986 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 23 10:54:00 2017
InstallationDate: Installed on 2016-01-05 (503 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
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/pcmC0D0p:   ronem  1986 F...m pulseaudio
 /dev/snd/controlC0:  ronem  1986 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)
dmi.bios.date: 01/10/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-P20 (G3) (MS-7788)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd01/10/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P20(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7788
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1692793

Title:
  [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I recently upgraded my system from 14.04LTS to 16.04LTS. 
  But now I cannot hear any sound from any player or youtube.

  executing the command

  aplay -l

  I get the harware information like

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 23 10:54:00 2017
  InstallationDate: Installed on 2016-01-05 (503 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  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/pcmC0D0p:   ronem  1986 F...m pulseaudio
   /dev/snd/controlC0:  ronem  1986 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [MS-7788, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (0 days ago)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P20 (G3) (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd01/10/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P20(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

backtrace by apport-retrace

crash buntu:/var/crash# apport-retrace --stdout 
/var/crash/_usr_lib_xorg_Xorg.0.c
gpgv: Signature made Tue 01 Nov 2016 04:15:19 PM CST using RSA key ID A88984DC
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on 
./xorg-server_1.18.4-0ubuntu0.2.dsc
dpkg-source: info: extracting xorg-server in xorg-server-1.18.4
dpkg-source: info: unpacking xorg-server_1.18.4.orig.tar.gz
dpkg-source: info: applying xorg-server_1.18.4-0ubuntu0.2.diff.gz
dpkg-source: info: upstream files that have been modified: 
 xorg-server-1.18.4/.dir-locals.el
 xorg-server-1.18.4/ChangeLog
 xorg-server-1.18.4/config/dbus-api
 xorg-server-1.18.4/damageext/damageext.h
 xorg-server-1.18.4/doc/c-extensions
 xorg-server-1.18.4/dri3/dri3int.h
 xorg-server-1.18.4/fix-miregion
 xorg-server-1.18.4/fix-miregion-private
 xorg-server-1.18.4/fix-patch-whitespace
 xorg-server-1.18.4/fix-region
 xorg-server-1.18.4/hw/kdrive/Xkdrive.man
 xorg-server-1.18.4/hw/kdrive/fbdev/Xfbdev.man
 xorg-server-1.18.4/hw/xfree86/os-support/shared/platform_noop.c
 xorg-server-1.18.4/hw/xquartz/GL/glcontextmodes.c
 xorg-server-1.18.4/hw/xquartz/GL/glcontextmodes.h
 xorg-server-1.18.4/hw/xwin/winclipboard/internal.h
 xorg-server-1.18.4/xkb/XKM_file_format.txt
W: Can't drop privileges for downloading as file 
'xorg-server_1.18.4-0ubuntu0.2.dsc' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
--- stack trace ---
#0  0x9220b528 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
_sys_result = 0
pd = 0x91fa7000
pid = 7478
selftid = 7478
#1  0x9220c9e0 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0xa6530de4, 
sa_sigaction = 0xa6530de4}, sa_mask = {__val = {2676586395008836901, 
2676586395008836901, 2594, 6730122966621824347, 32, 2910292295676945778, 
18446744073709486080, 0, 18446744073709551360, 0, 4616194021471027200, 1024, 
4616194021471028224, 0, 4616194021471028225, 4616194021471028225}}, sa_flags = 
-1054354032, sa_restorer = 0xc122fa28 }
sigs = {__val = {32, 0 }}
#2  0xc122fa28 in OsAbort () at ../../os/utils.c:1408
No locals.
#3  0xc1116364 in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1102
i = 
#4  0xc111643c in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1146
i = 
#5  0xc12358e0 in AbortServer () at ../../os/log.c:874
No locals.
#6  0xc1236624 in FatalError (f=f@entry=0xc1266988 "Caught signal 
%d (%s). Server aborting\n") at ../../os/log.c:1015
args = {__stack = 0xd085b680, __gr_top = 0xd085b680, __vr_top = 
0xd085b640, __gr_offs = -56, __vr_offs = -128}
args2 = {__stack = 0xd085b680, __gr_top = 0xd085b680, __vr_top 
= 0xd085b640, __gr_offs = -56, __vr_offs = -128}
beenhere = 1
#7  0xc122d294 in OsSigHandler (signo=11, sip=0xd085b6a0, 
unused=) at ../../os/osinit.c:150
unused = 
sip = 0xd085b6a0
signo = 11
#8  
No symbol table info available.
#9  0xc1192254 in RRSetChanged (pScreen=) at 
../../randr/randr.c:562
master = 
mastersp = 0x0
#10 0xc119654c in RRScreenSetSizeRange 
(pScreen=pScreen@entry=0xaaab00cd7860, minWidth=, 
minHeight=, maxWidth=, maxHeight=) 
at ../../randr/rrinfo.c:228
No locals.
#11 0xc11510d4 in xf86RandR12CreateScreenResources12 
(pScreen=0xaaab00cd7860) at ../../../../hw/xfree86/modes/xf86RandR12.c:1649
c = 
pScrn = 
config = 0xaaab00d02f50
#12 xf86RandR12CreateScreenResources (pScreen=pScreen@entry=0xaaab00cd7860) at 
../../../../hw/xfree86/modes/xf86RandR12.c:833
pScrn = 0xaaab00cd0fd0
config = 
c = 
width = 
height = 
mmWidth = 
mmHeight = 
#13 0xc1144bbc in xf86CrtcCreateScreenResources (screen=0xaaab00cd7860) 
at ../../../../hw/xfree86/modes/xf86Crtc.c:719
screen = 0xaaab00cd7860
scrn = 
#14 0xc10d5cf0 in dix_main (argc=1, argv=0xd085cbb8, 
envp=) at ../../dix/main.c:215
pScreen = 0xaaab00cd7860
i = 0
alwaysCheckForInput = {0, 1}
#15 0x921f98a0 in __libc_start_main (main=0x0, argc=0, argv=0x0, 
init=, fini=, rtld_fini=, 
stack_end=) at libc-start.c:291
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {187650361516128, 0, 0, 0, 
0, 0, 0, 0, 0, 0, 281474180172400, 3655814494272476266, 129, 
3655814493156378226, 0, 0, 0, 0, 0, 0, 0, 0}, mask_was_saved = 0}}, priv = {pad 
= {0x0, 0x0, 0xc127d120, 0xc10bfce8 <_start+52>}, data = {prev = 0x0, 
cleanup = 0x0, canceltype = -1054355168}}}
not_first_call = 
#16 0xc10bfce8 in _start ()
No symbol table info available.
Backtrace stopped: previous frame 

[Touch-packages] [Bug 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit

[Hans Deragon]

ChristianEhrhardt (paelzer) and John Johansen (jjohansen), I tried your
sha1sum checks and all looks good, but the problem still persists.
Nothing suggested in this bug reports works for me.  Luckily, on my
system where it fails, I do not make use of libvirt; this issue is just
an annoying error message when I upgrade my system.  My server does not
suffer from this problem; wonder why only some system suffer from this
problem suddenly.

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

Title:
  Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04
  64-bit

Status in apparmor package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  Output from 'apt-get upgrade':
  Setting up libvirt-bin (1.3.1-1ubuntu10.1) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'screen-cleanup' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`screen-cleanup'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`screen-cleanup'
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  insserv: warning: script 'binfmt-support' missing LSB tags and overrides
  insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`binfmt-support'
  insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`binfmt-support'
  Job for libvirt-bin.service failed because the control process exited with 
error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript libvirt-bin, action "restart" failed.
  dpkg: error processing package libvirt-bin (--configure):
   subprocess installed post-installation script returned error exit status 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Output from 'systemctl status libvirt-bin.service':
  ● libvirt-bin.service - Virtualization daemon
 Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 
BST; 4min 52s ago
   Docs: man:libvirtd(8)
 http://libvirt.org
Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, 
status=6)
   Main PID: 2984 (code=exited, status=6)

  Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon.
  Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed 
state.
  Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 
'exit-code'.
  Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time 
over, scheduling restart.
  Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon.
  Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated 
too quickly.
  Jun 21 17:55:16 lydia systemd[1]: Failed to start Virtualization daemon.

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

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

[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

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

Bug description:
  Bluetooth device doesn't play any sound in A2DP mode unless set to
  HSP/HFP first

  ---

  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1692437] [NEW] Monitors on second GPU not working after upgrade to zesty

[Richard Eames]

Public bug reported:

I'm not 100% sure this is the right package to file the bug against, but
since upgrading to zesty the two monitors on my second GPU are no longer
detected once I reach the greeter screen at login time. However, both of
them display information during boot.

Let me know how I can narrow down the bug report.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: lightdm 1.22.0-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon May 22 01:42:58 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-29 (388 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lightdm
UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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

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

[Touch-packages] [Bug 1692437] Re: Monitors on second GPU not working after upgrade to zesty

[Richard Eames]

** Attachment added: "lshw output"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/4881175/+files/lshw.txt

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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

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

[Touch-packages] [Bug 1362313] Re: a2dp bluetooth music playback broken after bluetooth device reconnect

[Daniel van Vugt]

** Tags added: a2dp

** Summary changed:

- a2dp bluetooth music playback broken after bluetooth device reconnect
+ PulseAudio can't find Bluetooth device after reconnecting

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

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

Title:
  PulseAudio can't find Bluetooth device after reconnecting

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

Bug description:
  What happens?
  1. connct a2dp device
  2. start playback
  3. reconnect a2dp device from remote
  4. ubuntu reports device is connected
  5. a2dp device does not show up in pulseaudio nor does music playback work 
(via a2dp device). sometimes there are "timeout" error messages in kde.
  6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio 
daemon. it all does not help.
  7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then 
connect the device (if not already auto-connected)

  After step 3, there is the following error message in syslog (no other
  errors in syslog or dmesg):

  pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release
  transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method
  "Release" with signature "s" on interface "org.bluez.MediaTransport"
  doesn't exist

  What I expected to happen?
  After the device reconnect, the music playback switches playback back to the 
bluetooth device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluetooth 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Wed Aug 27 21:41:34 2014
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: bluez
  UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: B85 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CC:E6:D5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:100536 acl:18 sco:0 events:14179 errors:0
TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0
  syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: 
/org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready

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

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

[Touch-packages] [Bug 1692448] [NEW] Bluetooth speaker fails to reconnect when turned on (but it tries)

[Daniel van Vugt]

Public bug reported:

Bluetooth speaker fails to reconnect when turned on. Watching the
Bluetooth icon in the Unity panel I can see it is trying (B icon briefly
gets the expected padlock and then loses it). The speaker doesn't
reconnect then unless initiated by the laptop (set Connection = ON in
the panel).

Sounds like of like this (which is fixed in newer releases than xenial, but not 
in xenial):
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed

Note this bug is only about the Bluetooth connection, and not about
audio problems (of which there are a few).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 22 16:28:37 2017
InstallationDate: Installed on 2017-05-19 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20CM0010AU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET45W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CM0010AU
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CM0010AU
dmi.product.version: ThinkPad X250
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 34:02:86:EE:0F:47  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0
TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1692448

Title:
  Bluetooth speaker fails to reconnect when turned on (but it tries)

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth speaker fails to reconnect when turned on. Watching the
  Bluetooth icon in the Unity panel I can see it is trying (B icon
  briefly gets the expected padlock and then loses it). The speaker
  doesn't reconnect then unless initiated by the laptop (set Connection
  = ON in the panel).

  Sounds like of like this (which is fixed in newer releases than xenial, but 
not in xenial):
  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed

  Note this bug is only about the Bluetooth connection, and not about
  audio problems (of which there are a few).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 16:28:37 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20CM0010AU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM0010AU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM0010AU
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 34:02:86:EE:0F:47  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0
TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0

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

-- 
Mailing list: 

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Daniel van Vugt]

Lev: The problem you describe in comment #69 sounds like it might be
fixed by this (which is missing from xenial AFAIK):

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

[Daniel van Vugt]

** Summary changed:

- [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 
16.10 yakkety
+ [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

** Tags added: a2dp

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Touch-packages] [Bug 1692510] [NEW] package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/l

[shikhertiwari]

Public bug reported:

This is occur while installing openastro.org

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 22 17:04:26 2017
DuplicateSignature:
 package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package iproute2 (--configure):
  package iproute2 is not ready for configuration
ErrorMessage: package iproute2 is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-05-11 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: iproute2
Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed 
to install/upgrade: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge
  sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat
  usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl
  usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
  failed to install/upgrade: package iproute2 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  This is occur while installing openastro.org

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:04:26 2017
  DuplicateSignature:
   package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-11 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed 
to install/upgrade: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692510] Re: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib

[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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1692510

Title:
  package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge
  sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat
  usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl
  usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
  failed to install/upgrade: package iproute2 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  This is occur while installing openastro.org

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:04:26 2017
  DuplicateSignature:
   package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz]
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-11 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge 
sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat 
usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl 
usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed 
to install/upgrade: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Dimitri John Ledkov]

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

** Changed in: openssh (Ubuntu Zesty)
   Status: Fix Committed => In Progress

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh source package in Zesty:
  In Progress
Status in openssh source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: 

[Touch-packages] [Bug 1692517] [NEW] crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgra

[Lionel Rioche]

Public bug reported:

Maybe a conflict with the ubuntu softwares library.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon 
sbin/tc sbin/tipc usr/sbin/genl]
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17
Uname: Linux 4.8.0-52-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 synaptic: Install
 iproute2: Configure
 synaptic: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon May 22 14:19:11 2017
DuplicateSignature:
 package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon 
sbin/tc sbin/tipc usr/sbin/genl]
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package iproute2 (--configure):
  package iproute2 is not ready for configuration
ErrorMessage: package iproute2 is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-05-13 (9 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: iproute2
Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package 
iproute2 is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  crash on install new package package iproute2 4.3.0-1ubuntu3
  [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc
  usr/sbin/genl] failed to install/upgrade: package iproute2 is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Maybe a conflict with the ubuntu softwares library.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl]
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-52-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   synaptic: Install
   iproute2: Configure
   synaptic: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 14:19:11 2017
  DuplicateSignature:
   package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl]
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-13 (9 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package 
iproute2 is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

[haozi]

i met this error too.anyone know where to get the patch???

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

Title:
  newusers error adding more than one user

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

[Dimitri John Ledkov]

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

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Yakkety:
  Triaged
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts

[Chris J Arges]

** Patch added: "init-system-helpers-zesty-1691474.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881359/+files/init-system-helpers-zesty-1691474.debdiff

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

Title:
  invoke-rc.d service start fails on services with upstart-only scripts

Status in init-system-helpers package in Ubuntu:
  In Progress
Status in init-system-helpers source package in Xenial:
  New
Status in init-system-helpers source package in Yakkety:
  New
Status in init-system-helpers source package in Zesty:
  New

Bug description:
  [Impact]
  On 16.04+ if you using upstart as your primary init system "enabled" services 
that _only_ have upstart scripts fail to start with invoke-rc.d (with a default 
policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on 
invoke-rc.d to start/stop services and fail to start services on installation.

  [Test Case]
  Boot into affected system with upstart as default init.
  Try starting an 'upstart only' service with 'invoke-rc.d service start'.
  It is expected this should work.

  [Regression Potential]
  14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has 
invoke-rc.d start working with enabled services and default policy. 
16.04/upstart should be the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+subscriptions

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

[Touch-packages] [Bug 1692494] Re: klibc does not support reboot arguments

[Ubuntu Foundations Team Bug Bot]

The attachment "add-reboot-argument-support.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  klibc does not support reboot arguments

Status in klibc package in Ubuntu:
  New

Bug description:
  ... so we cannot do things like "reboot recovery" in devices that
  follow the Android partitions conventions.

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

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

[Touch-packages] [Bug 1692517] Re: crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade

[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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1692517

Title:
  crash on install new package package iproute2 4.3.0-1ubuntu3
  [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc
  usr/sbin/genl] failed to install/upgrade: package iproute2 is not
  ready for configuration  cannot configure (current status 'half-
  installed')

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Maybe a conflict with the ubuntu softwares library.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl]
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17
  Uname: Linux 4.8.0-52-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   synaptic: Install
   iproute2: Configure
   synaptic: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 14:19:11 2017
  DuplicateSignature:
   package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl]
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-13 (9 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct 
sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package 
iproute2 is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts

[Chris J Arges]

** Patch added: "init-system-helpers-yakkety-lp1691474.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881367/+files/init-system-helpers-yakkety-lp1691474.debdiff

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

Title:
  invoke-rc.d service start fails on services with upstart-only scripts

Status in init-system-helpers package in Ubuntu:
  In Progress
Status in init-system-helpers source package in Xenial:
  New
Status in init-system-helpers source package in Yakkety:
  New
Status in init-system-helpers source package in Zesty:
  New

Bug description:
  [Impact]
  On 16.04+ if you using upstart as your primary init system "enabled" services 
that _only_ have upstart scripts fail to start with invoke-rc.d (with a default 
policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on 
invoke-rc.d to start/stop services and fail to start services on installation.

  [Test Case]
  Boot into affected system with upstart as default init.
  Try starting an 'upstart only' service with 'invoke-rc.d service start'.
  It is expected this should work.

  [Regression Potential]
  14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has 
invoke-rc.d start working with enabled services and default policy. 
16.04/upstart should be the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+subscriptions

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Dimitri John Ledkov]

** Information type changed from Private Security to Public Security

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Dimitri John Ledkov]

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

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 997331] Re: Some alsa applications play bad sound

[Valentin Leclere]

Same bug here on a 16.04, agw3's workaround doesn't fix the issue for me.
It occurs when my browser (firefox 53.0.2 64b) display a google research with 
google translate content.

The way I fix it is:
pulseaudio -k && sudo alsa force-reload
It's a bit annoying, I would like to fix it permanently.

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

Title:
  Some alsa applications play bad sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Some applications using ALSA plays bad sound. One is WINE
  applications. Winecfg test sound is distorted (sounds awful). Spotify
  running WINE plays songs way too fast. A flash based program play
  distorted sound. The common thing for all of them is that under
  Applications in Sound settings it says alsa-plugin and it flashes very
  rapidly between "No application is currently playing" and alsa-plugin.
  It almost looks like flickering. I've testet a normal wave file using
  aplay and that was okey, no problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC0:  oeriksen   3299 F pulseaudio
   /dev/snd/controlC1:  oeriksen   3299 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 41
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at 
usb-:00:1d.0-1.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:4083'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 48
 Mono: Capture 45 [94%] [18.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
 Mixer name : 'Nvidia GPU 16 HDMI/DP'
 Components : 'HDA:10de0016,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  Date: Wed May  9 22:41:04 2012
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback 
problem
  UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago)
  dmi.bios.date: 02/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 REV 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Daniel van Vugt]

Confirmed on xenial, exactly how hife describes it.

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

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

Bug description:
  Bluetooth device doesn't play any sound in A2DP mode unless set to
  HSP/HFP first

  ---

  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1692474] [NEW] Sound settings don't remember my preferred audio output device

[Daniel van Vugt]

Public bug reported:

Sound settings don't remember my preferred audio output device.

Every time I (manage to) connect a bluetooth audio device, the default
output remains the built-in PC speaker. Same when I connect USB audio
devices... Ubuntu sticks to the built-in speakers until manually set
otherwise.

This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
  1. Prefer what the user manually selected last; or
  2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
  3. Prefer what audio device appeared in the list most recently.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center (not installed)
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May 22 17:23:59 2017
InstallationDate: Installed on 2017-05-19 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug xenial

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

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

Title:
  Sound settings don't remember my preferred audio output device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound settings don't remember my preferred audio output device.

  Every time I (manage to) connect a bluetooth audio device, the default
  output remains the built-in PC speaker. Same when I connect USB audio
  devices... Ubuntu sticks to the built-in speakers until manually set
  otherwise.

  This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
1. Prefer what the user manually selected last; or
2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
3. Prefer what audio device appeared in the list most recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:23:59 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

[Dimitri John Ledkov]

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

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

** Changed in: systemd (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on
  armhf

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

  root-unittests fails:

-> Unit a.service:
Description: a.service
Instance: n/a
Unit Load State: not-found
Unit Active State: inactive
State Change Timestamp: n/a
Inactive Exit Timestamp: n/a
Active Enter Timestamp: n/a
Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit 
c.service not found.
  Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
   Exit Timestamp: n/a

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

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

[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line

[Dimitri John Ledkov]

Just did a release to artful; I will do this one in the next update
after this one.

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.06

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates

** Changed in: systemd (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  loginctl ignoring user given sessions IDs at command-line

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Zesty:
  Triaged

Bug description:
  Kubuntu zesty, 232-21ubuntu2

  See upstream bug https://github.com/systemd/systemd/issues/5733 with
  patch attached.

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

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

[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.
  
  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.
  
  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.
  
  [Regression Risk]
- TBD - depends on the proposed solution.
+ Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

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

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

** Changed in: systemd (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates

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

Title:
  no predictable names for platform (non-PCI) NICs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems may have NICs attached to the "platform" bus. These are NICs that are 
onboard, but not attached to a PCI(-like) bus. Rather, they are described by 
firmware directly. None of the naming policies enabled by Ubuntu by default 
matches these NICs, so they end up having unpredictable names. In the case 
where other NICs are attached (e.g. PCIe cards), the ethN enumeration race 
occurs, making it impossible to have an interface name that is persistent 
across reboots. That is, if you do a network install over "eth0", on reboot 
that NIC now maybe "eth3", which causes it to fail to start the network on boot.

  The HiSilicon D05 boards are an example of this. It has 4 onboard NICs
  that are described by ACPI directly, and may also have other PCIe NICs
  plugged in.

  [Test Case]
  Boot a system with the characteristics described above, and check to see if 
any "ethN" interfaces exist.

  [Regression Risk]
  Unless one fixed the names locally with .netlink / .rules files the interface 
names will change for the ACPI/platform bus network interfaces, from random 
ethX names to stable names named like enaVENDORMODELiX. Thus we should check 
that this update doesn't negatively break certified ARM64 platforms with: ARM, 
NVIDIA, HISILICON platform bus ethernet devices.

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

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

[Touch-packages] [Bug 1629226] Re: systemd's service killed by cgroup controller pids

[Balint Reczey]

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

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

Title:
  systemd's service killed by cgroup controller pids

Status in The Ubuntu-power-systems project:
  New
Status in bash package in Ubuntu:
  In Progress

Bug description:
  Problem Description
  ===
  I write a simple systemd service which will fork child processes fiercely. 
But quickly the service failed:

  % sudo systemctl status reproducer.service
  ? reproducer.service - Reproducer of systemd services killed by ips
 Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2016-03-18 06:58:37 CDT; 2min 
43s ago
Process: 5103 ExecStart=/home/hpt/reproducer/reproducer.sh (code=exited, 
status=0/SUCCESS)
   Main PID: 5105 (code=exited, status=254)

  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Main process exited, 
code=exited, status=254/n/a
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Unit entered failed 
state.
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Failed with result 
'exit-code'.

  The default task limit of systemd services is 512. Looks like the
  service is terminated by the kernel's ips cgroup controller. I think
  this isn't correct. Child processes cannot be forked shouldn't cause
  parent to die.

  
  % cat /etc/systemd/system/reproducer.service 
  [Unit]
  Description=Reproducer of systemd services killed by ips
  After=multi-user.target

  [Service]
  ExecStart=/home/hpt/reproducer/reproducer.sh
  Type=forking

  [Install]
  WantedBy=multi-user.target

  % cat /home/hpt/reproducer/reproducer.sh
  #!/bin/bash

  foo()
  {
  #exec sh -c "echo $1: \$\$;sleep 60"
  echo $1: 
  sleep 60
  }

  bar()
  {
  c=1
  while true
  do
  for ((i=1;i<=2048;i++))
  do
  foo $c &
  ((c++))
  done

  wait
  c=1
  done
  }

  # main
  bar &

  disown -a

  exit 0

  
  ---uname output---
  Linux pinelp3 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8408-E8E,lpar 

  Steps to Reproduce
  
  1. install the simple service in "Problem description"
  2. sudo systemctl start reproducer.service
  3. wait 2~3 minutes
   
  == Comment: #3 - Vaishnavi Bhat  - 2016-03-22 11:21:55 ==
  From the machine,
  root@pinelp3:~# ulimit -a
  core file size  (blocks, -c) 0
  data seg size   (kbytes, -d) unlimited
  scheduling priority (-e) 0
  file size   (blocks, -f) unlimited
  pending signals (-i) 48192
  max locked memory   (kbytes, -l) 64
  max memory size (kbytes, -m) unlimited
  open files  (-n) 1024
  pipe size(512 bytes, -p) 8
  POSIX message queues (bytes, -q) 819200
  real-time priority  (-r) 0
  stack size  (kbytes, -s) 8192
  cpu time   (seconds, -t) unlimited
  max user processes  (-u) 48192
  virtual memory  (kbytes, -v) unlimited
  file locks  (-x) unlimited

  root@pinelp3:~# ps aux | wc -l  ->While the service is 
running 
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l-->While the service is not 
running. 
  572

  root@pinelp3:~# free -m   --> While service is running
totalusedfree  shared  buff/cache   
available
  Mem:  12117 628 459  22   11029

[Touch-packages] [Bug 1692496] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1688721, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  after cancel download

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 22 12:51:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Dimitri John Ledkov]

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

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  This is one of background errors that happens without any active app being 
involved. 
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1692454] [NEW] [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

[hari]

Public bug reported:

no audio at all

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hariharan   1985 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon May 22 14:08:44 2017
InstallationDate: Installed on 2017-05-17 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful
Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hariharan   1985 F pulseaudio
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug zesty

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

Title:
  [ENS1371 - Ensoniq AudioPCI, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  no audio at all

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon May 22 14:08:44 2017
  InstallationDate: Installed on 2017-05-17 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI 
successful
  Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / 
Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hariharan   1985 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[aden iwa rante]

** Changed in: aptdaemon
 Assignee: (unassigned) => aden iwa rante (radeniw)

** Changed in: debconf (Ubuntu)
   Status: Triaged => New

** Changed in: aptdaemon (Ubuntu)
   Status: Triaged => New

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  New
Status in debconf package in Ubuntu:
  New

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1692474] Re: Sound settings don't remember my preferred audio output device

[Daniel van Vugt]

** Package changed: gnome-control-center (Ubuntu) => unity-control-
center (Ubuntu)

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

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

Title:
  Sound settings don't remember my preferred audio output device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Sound settings don't remember my preferred audio output device.

  Every time I (manage to) connect a bluetooth audio device, the default
  output remains the built-in PC speaker. Same when I connect USB audio
  devices... Ubuntu sticks to the built-in speakers until manually set
  otherwise.

  This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
1. Prefer what the user manually selected last; or
2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
3. Prefer what audio device appeared in the list most recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:23:59 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

[Dimitri John Ledkov]

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

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

** Changed in: systemd (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Zesty)
Milestone: None => zesty-updates

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Zesty)
   Status: Confirmed => Fix Committed

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on
  armhf

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

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

  root-unittests fails:

-> Unit a.service:
Description: a.service
Instance: n/a
Unit Load State: not-found
Unit Active State: inactive
State Change Timestamp: n/a
Inactive Exit Timestamp: n/a
Active Enter Timestamp: n/a
Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit 
c.service not found.
  Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
   Exit Timestamp: n/a

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

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Sandeep]

About Vulkan package:

Vulkan loader (libvulkan) has moved to newer version and that is needed
to make use of all the recently proposed vulkan extensions in the
application.

The main application that doesn't work currently is with Vulkan CTS:
https://github.com/KhronosGroup/VK-GL-CTS

Vulkan CTS passing is required for a device to be called as Vulkan
compatible.

We support only LTS releases on our devices so need latest version on
16.04. Can you please upgrade the libvulkan.so version to 1.0.42 for
Xenial?

This version is already available for latest ubuntu version (17.04).

Thanks.

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1692496] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[ali]

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

Public bug reported:

after cancel download

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon May 22 12:51:01 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-18 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  after cancel download

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 22 12:51:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692494] [NEW] klibc does not support reboot arguments

[Alfonso Sanchez-Beato]

Public bug reported:

... so we cannot do things like "reboot recovery" in devices that follow
the Android partitions conventions.

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

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

Title:
  klibc does not support reboot arguments

Status in klibc package in Ubuntu:
  New

Bug description:
  ... so we cannot do things like "reboot recovery" in devices that
  follow the Android partitions conventions.

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

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

[Touch-packages] [Bug 1692492] [NEW] package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Richard Scott]

Public bug reported:

No further information to provide, this bug report was submitted
automatically.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 19 08:43:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-09-08 (255 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "1";
 APT::Periodic::AutocleanInterval "7";
 APT::Periodic::Unattended-Upgrade "1";
modified.conffile..etc.apt.apt.conf.d.99update-notifier:
 #DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch 
/var/lib/update-notifier/dpkg-run-stamp; fi; 
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
 #APT::Update::Post-Invoke-Success 
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
mtime.conffile..etc.apt.apt.conf.d.99update-notifier: 2016-11-16T17:39:04.061871

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  No further information to provide, this bug report was submitted
  automatically.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 19 08:43:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-08 (255 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "7";
   APT::Periodic::Unattended-Upgrade "1";
  modified.conffile..etc.apt.apt.conf.d.99update-notifier:
   #DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch 
/var/lib/update-notifier/dpkg-run-stamp; fi; 
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
   #APT::Update::Post-Invoke-Success 
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
  mtime.conffile..etc.apt.apt.conf.d.99update-notifier: 
2016-11-16T17:39:04.061871

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

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

[Touch-packages] [Bug 1692492] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1692492

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  No further information to provide, this bug report was submitted
  automatically.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 19 08:43:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-08 (255 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "7";
   APT::Periodic::Unattended-Upgrade "1";
  modified.conffile..etc.apt.apt.conf.d.99update-notifier:
   #DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch 
/var/lib/update-notifier/dpkg-run-stamp; fi; 
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
   #APT::Update::Post-Invoke-Success 
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
  mtime.conffile..etc.apt.apt.conf.d.99update-notifier: 
2016-11-16T17:39:04.061871

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

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

[Touch-packages] [Bug 1692494] Re: klibc does not support reboot arguments

[Alfonso Sanchez-Beato]

** Patch added: "add-reboot-argument-support.patch"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4881283/+files/add-reboot-argument-support.patch

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

Title:
  klibc does not support reboot arguments

Status in klibc package in Ubuntu:
  New

Bug description:
  ... so we cannot do things like "reboot recovery" in devices that
  follow the Android partitions conventions.

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

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

[Touch-packages] [Bug 1692448] Re: Bluetooth speaker fails to reconnect when turned on (but it tries)

[Daniel van Vugt]

** Description changed:

  Bluetooth speaker fails to reconnect when turned on. Watching the
  Bluetooth icon in the Unity panel I can see it is trying (B icon briefly
  gets the expected padlock and then loses it). The speaker doesn't
  reconnect then unless initiated by the laptop (set Connection = ON in
  the panel).
  
- Sounds like of like this (which is fixed in newer releases than xenial, but 
not in xenial):
+ Sounds kind of like this (which is fixed in newer releases than xenial, but 
not in xenial):
  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed
  
  Note this bug is only about the Bluetooth connection, and not about
  audio problems (of which there are a few).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 16:28:37 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20CM0010AU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM0010AU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM0010AU
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  hciconfig:
-  hci0:Type: BR/EDR  Bus: USB
-   BD Address: 34:02:86:EE:0F:47  ACL MTU: 1021:5  SCO MTU: 96:6
-   UP RUNNING 
-   RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0
-   TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0
+  hci0:Type: BR/EDR  Bus: USB
+   BD Address: 34:02:86:EE:0F:47  ACL MTU: 1021:5  SCO MTU: 96:6
+   UP RUNNING
+   RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0
+   TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0

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

Title:
  Bluetooth speaker fails to reconnect when turned on (but it tries)

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth speaker fails to reconnect when turned on. Watching the
  Bluetooth icon in the Unity panel I can see it is trying (B icon
  briefly gets the expected padlock and then loses it). The speaker
  doesn't reconnect then unless initiated by the laptop (set Connection
  = ON in the panel).

  Sounds kind of like this (which is fixed in newer releases than xenial, but 
not in xenial):
  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed

  Note this bug is only about the Bluetooth connection, and not about
  audio problems (of which there are a few).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 16:28:37 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20CM0010AU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM0010AU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM0010AU
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 34:02:86:EE:0F:47  ACL MTU: