[Touch-packages] [Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container

[ChristianEhrhardt]

I used this in the past:
lxc config set  raw.lxc lxc.aa_profile=unconfined

I can confirm that after this the conf contains both lines as you
outlined, but for me it worked to unconfine it. I had to restart the
container to pick up the new profile thou - so maybe that applies to you
as well?

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

Title:
  Can't install kernel-nfs-server inside lxc container

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to virtualize a package that depends on NFS by installing
  it in an LXC container.

  The commands

  sudo apt-get install nfs-kernel-server
  sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64
  sudo lxc-start -n nfstest
  sudo lxc-attach -n nfstest apt-get update
  sudo lxc-attach -n nfstest apt-get install nfs-kernel-server

  should install NFS server software inside the container, but instead
  fail with

  ...
  Not creating home directory `/var/lib/nfs'.
  nfs-utils.service is a disabled or a static unit, not starting it.
  Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ...
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  nfs-server.service couldn't start.
  Creating config file /etc/exports with new version
  Creating config file /etc/default/nfs-kernel-server with new version
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
  dpkg: error processing package nfs-kernel-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu4) ...
  Errors were encountered while processing:
   nfs-kernel-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  sudo lxc-attach -n nfstest journalctl -xe reports:

  Apr 27 15:42:59 nfstest systemd[1]: Failed to mount NFSD configuration 
filesystem
  -- Subject: Unit proc-fs-nfsd.mount has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- Unit proc-fs-nfsd.mount has failed.
  -- The result is failed.

  Presumably this is intended, and there is a way to configure lxc to allow
  running nfs servers inside it (there are rumors of success on the web), but 
  https://help.ubuntu.com/lts/serverguide/lxc.html  is silent on the issue,
  and doesn't even mention the word nfs.
  Likewise, https://help.ubuntu.com/lts/serverguide/network-file-system.html
  doesn't even mention lxc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 27 08:19:41 2016
  InstallationDate: Installed on 2016-03-26 (32 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1649453] Re: systemd starts postfix before resolver

[Greg Black]

OK. Thanks for the update.

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

Title:
  systemd starts postfix before resolver

Status in postfix package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Postfix starts before systemd-resolved.service, resulting in postfix
  reporting that it can't find MX records for outgoing mail, as shown in
  the trace below:

  $ systemd-analyze critical-chain postfix.service systemd-resolved.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  postfix.service +1ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms
  systemd-resolved.service +268ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms

  The postfix service needs to start after systemd-resolved.service.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive 
yakkety-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages

  $ apt-cache policy postfix
  postfix:
Installed: 3.1.0-5
Candidate: 3.1.0-5
Version table:
   *** 3.1.0-5 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1649453] Re: systemd starts postfix before resolver

[Scott Kitterman]

On Tuesday, January 03, 2017 12:34:12 AM you wrote:
> Any idea when the fix will appear in updates for yakkety?

We plan on an upload to Debian in the next day or two.  It'll follow into 
Ubuntu shortly there after.  A Yakkety SRU is work for someone involved in 
Ubuntu to do, so no.

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

Title:
  systemd starts postfix before resolver

Status in postfix package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Postfix starts before systemd-resolved.service, resulting in postfix
  reporting that it can't find MX records for outgoing mail, as shown in
  the trace below:

  $ systemd-analyze critical-chain postfix.service systemd-resolved.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  postfix.service +1ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms
  systemd-resolved.service +268ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms

  The postfix service needs to start after systemd-resolved.service.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive 
yakkety-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages

  $ apt-cache policy postfix
  postfix:
Installed: 3.1.0-5
Candidate: 3.1.0-5
Version table:
   *** 3.1.0-5 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

[Bin Li]

@themuso,

 Done, I'd updated the description with the template of SRU. Thanks a
lot!

** Description changed:

+ [Impact]
+ 
+  * When plug in headset jack, you can't view any item in unity-control-
+ center, so you can't change the volume.
+ 
+  * For the situation of one pulseaudio port has 2 or more jacks, it will
+ bring some change, in the past, if one of the jacks is plugged and other
+ jacks are not plugged, the pulseaudio will print out "Availability of
+ port '%s' is inconsistent!" and will not set this pulseaudio port to
+ available, this is a bug for pulseaudio.
+ 
+  * After applying this patch, this issue can be addressed by this patch.
+ 
+ [Test Case]
+ 
+  * Reproduce steps:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.
  
- The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1
+ [Regression Potential]
+ 
+  *  For most of the situations like one pulseaudio port only has one
+ jack, this patch will not bring any change. So there is no potential
+ regression.
+ 
+ [Other Info]
+  
+  * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

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

Title:
  There is no entry in 'Play sound through' list when plug in headset
  jack [8086:9d70].

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Trusty:
  New

Bug description:
  [Impact]

   * When plug in headset jack, you can't view any item in unity-
  control-center, so you can't change the volume.

   * For the situation of one pulseaudio port has 2 or more jacks, it
  will bring some change, in the past, if one of the jacks is plugged
  and other jacks are not plugged, the pulseaudio will print out
  "Availability of port '%s' is inconsistent!" and will not set this
  pulseaudio port to available, this is a bug for pulseaudio.

   * After applying this patch, this issue can be addressed by this
  patch.

  [Test Case]

   * Reproduce steps:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.

  [Regression Potential]

   *  For most of the situations like one pulseaudio port only has one
  jack, this patch will not bring any change. So there is no potential
  regression.

  [Other Info]
   
   * The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1643812/+subscriptions

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

[Touch-packages] [Bug 1291373] Re: wget. memory leaks

[Jes Bodi Klinke]

fd_read_body() seems to be riddled with memory leaks.

Below is output of running a wget -c -r, fetching a total of a few
hundred files, all of which were already found on local disk, and thus
not actually fetched.

I am using 1.13.4-2ubuntu1.4 on Linux 2.6.32-042stab117.14 x86_64

==26452== 2,082 bytes in 347 blocks are definitely lost in loss record 810 of 
839
==26452==at 0x4C2B6CD: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26452==by 0x430348: xmalloc (xmalloc.c:43)
==26452==by 0x428464: strdupdelim (utils.c:224)
==26452==by 0x42BD94: parse_charset (iri.c:72)
==26452==by 0x41ACBC: gethttp (http.c:2287)
==26452==by 0x41B622: http_loop (http.c:2769)
==26452==by 0x4249AD: retrieve_url (retr.c:736)
==26452==by 0x422894: retrieve_tree (recur.c:283)
==26452==by 0x40541A: main (main.c:1388)
==26452==
==26452== 38,400 bytes in 300 blocks are definitely lost in loss record 834 of 
839
==26452==at 0x4C2B6CD: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26452==by 0x430348: xmalloc (xmalloc.c:43)
==26452==by 0x423DB6: fd_read_hunk (retr.c:451)
==26452==by 0x424573: fd_read_body (retr.c:295)
==26452==by 0x41A962: gethttp (http.c:2588)
==26452==by 0x41B622: http_loop (http.c:2769)
==26452==by 0x4249AD: retrieve_url (retr.c:736)
==26452==by 0x422894: retrieve_tree (recur.c:283)
==26452==by 0x40541A: main (main.c:1388)
==26452==
==26452== 147,712 bytes in 1,154 blocks are definitely lost in loss record 835 
of 839
==26452==at 0x4C2B6CD: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26452==by 0x430348: xmalloc (xmalloc.c:43)
==26452==by 0x423DB6: fd_read_hunk (retr.c:451)
==26452==by 0x4245A8: fd_read_body (retr.c:355)
==26452==by 0x41A962: gethttp (http.c:2588)
==26452==by 0x41B622: http_loop (http.c:2769)
==26452==by 0x4249AD: retrieve_url (retr.c:736)
==26452==by 0x422894: retrieve_tree (recur.c:283)
==26452==by 0x40541A: main (main.c:1388)
==26452==
==26452== 186,112 bytes in 1,454 blocks are definitely lost in loss record 837 
of 839
==26452==at 0x4C2B6CD: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26452==by 0x430348: xmalloc (xmalloc.c:43)
==26452==by 0x423DB6: fd_read_hunk (retr.c:451)
==26452==by 0x42453E: fd_read_body (retr.c:283)
==26452==by 0x41A962: gethttp (http.c:2588)
==26452==by 0x41B622: http_loop (http.c:2769)
==26452==by 0x4249AD: retrieve_url (retr.c:736)
==26452==by 0x422894: retrieve_tree (recur.c:283)
==26452==by 0x40541A: main (main.c:1388)
==26452==
==26452== 540,606 (144,384 direct, 396,222 indirect) bytes in 9,024 blocks are 
definitely lost in loss record 839 of 839
==26452==at 0x4C2B6CD: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26452==by 0x50F21B3: CRYPTO_malloc (in 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x519CCB6: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x519FB8C: ASN1_item_ex_d2i (in 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x519FE70: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x51A021B: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x519F86C: ASN1_item_ex_d2i (in 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x51A0353: ASN1_item_d2i (in 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x51BD606: X509V3_EXT_d2i (in 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0)
==26452==by 0x42D09A: ssl_check_certificate (openssl.c:590)
==26452==by 0x41908B: gethttp (http.c:1917)
==26452==by 0x41B622: http_loop (http.c:2769)
==26452==
==26452== LEAK SUMMARY:
==26452==definitely lost: 518,690 bytes in 12,279 blocks
==26452==indirectly lost: 396,222 bytes in 18,047 blocks
==26452==  possibly lost: 20 bytes in 1 blocks
==26452==still reachable: 395,620 bytes in 6,051 blocks
==26452== suppressed: 0 bytes in 0 blocks

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

Title:
  wget. memory leaks

Status in wget package in Ubuntu:
  New

Bug description:
  Wget eats RAM when downloading big website. To reproduce run these on slow 
internet connection:
  bash$ wget -r -k -p -l inf -U 'Mozilla/5.0 (compatible; Googlebot/2.1; 
+http://www.google.com/bot.html)' 'http://bigwebsite.com/' 2> stderr.txt
  After one ~6 hours wget eats 1.5 GiB of RAM.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: wget 1.13.4-2ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14
  Uname: Linux 3.8.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Mar 12 15:29:05 2014
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  SourcePackage: wget
  UpgradeStatus: 

[Touch-packages] [Bug 1652032] Re: ambiguous config file

[ChristianEhrhardt]

Network Manager does: --conf-file=/dev/null 
--conf-dir=/etc/NetworkManager/dnsmasq.d
and might therefore be an example of those that call it - as you mentioned it 
can be discussed if it would have to add the,*.conf or anything like it.

An example of a program not calling with --conf-dir=/etc/dnsmasq.d might be 
libvirt.
But then it explicitly wants no other config at all to influence it and in 
terms of the interface exceptions and such it is correct as it explicitly 
states the interface to bind to.
Call:
--conf-file=/var/lib/libvirt/dnsmasq/default.conf
But in there:
interface=virbr0
So instead of using exclusions it it very specific where to bind to.
Maybe that and similar cases are a reason why it should not always pull in the 
dnsmasq.d dir - not sure?

Could you list the other examples you found - as I assume to get an idea
of potential side effects we would have to collect as much as possible.

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

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

Title:
  ambiguous config file

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm currently hunting some problems caused by some ambiguity in the
  dnsmasq config.

  There's a directory /etc/dnsmasq.d, where some packages put files with
  except-interface=... clauses, telling other instances of dnsmasq to
  "Keep your fingers from my interface". Good practice.

  But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
  commented out, so actually the /etc/dnsmasq.d directory is not read by
  default.

  Some packages that use dnsmasq therefore give it a --conf-
  dir=/etc/dnsmasq.d command line parameter to make it read all those
  config snippets.

  This causes two problems:

  - Not all packages give their dnsmasq this additional parameter, and
  therefore not all dnsmasq instances obey those config. E.g.
  NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt
  does not read it either.

  
  - Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


  So it is quite unclear how these things should work together cleanly.
  Since the details are left to both the user's arbitrary configuration
  of /etc/dnsmasq.conf and every single package maintainer how he would
  prefer to use it, there's just a heap of confusion.

  In my eyes the best way would be to just use

  conf-dir=/etc/dnsmasq.d/,*.conf

  
  in the /etc/dnsmasq.conf and have this as a default, and that's it. 


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 22 12:55:33 2016
  InstallationDate: Installed on 2016-04-22 (243 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

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

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

[Touch-packages] [Bug 1652032] Re: ambiguous config file

[ChristianEhrhardt]

** Changed in: dnsmasq (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ambiguous config file

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm currently hunting some problems caused by some ambiguity in the
  dnsmasq config.

  There's a directory /etc/dnsmasq.d, where some packages put files with
  except-interface=... clauses, telling other instances of dnsmasq to
  "Keep your fingers from my interface". Good practice.

  But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
  commented out, so actually the /etc/dnsmasq.d directory is not read by
  default.

  Some packages that use dnsmasq therefore give it a --conf-
  dir=/etc/dnsmasq.d command line parameter to make it read all those
  config snippets.

  This causes two problems:

  - Not all packages give their dnsmasq this additional parameter, and
  therefore not all dnsmasq instances obey those config. E.g.
  NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt
  does not read it either.

  
  - Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


  So it is quite unclear how these things should work together cleanly.
  Since the details are left to both the user's arbitrary configuration
  of /etc/dnsmasq.conf and every single package maintainer how he would
  prefer to use it, there's just a heap of confusion.

  In my eyes the best way would be to just use

  conf-dir=/etc/dnsmasq.d/,*.conf

  
  in the /etc/dnsmasq.conf and have this as a default, and that's it. 


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 22 12:55:33 2016
  InstallationDate: Installed on 2016-04-22 (243 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

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

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

[Touch-packages] [Bug 1653593] Re: 'unity-system-compositor --debug-without-dm' fails to start: 'std::exception::what: dbus_request_name: Failed to become primary owner'

[Daniel van Vugt]

Workaround:  systemctl stop lightdm

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

Title:
  'unity-system-compositor --debug-without-dm' fails to start:
  'std::exception::what: dbus_request_name: Failed to become primary
  owner'

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor --debug-without-dm

  fails to start due to:

  ERROR: 
/build/unity-system-compositor-Z26sU0/unity-system-compositor-0.8.0+17.04.20161206/src/dbus_connection_handle.cpp(66):
 Throw in function void usc::DBusConnectionHandle::request_name(const char*) 
const
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: dbus_request_name: Failed to become primary owner

  I would have thought that's what the debug option is there to work
  around.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1653593/+subscriptions

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

[Touch-packages] [Bug 1653593] [NEW] 'unity-system-compositor --debug-without-dm' fails to start: 'std::exception::what: dbus_request_name: Failed to become primary owner'

[Daniel van Vugt]

Public bug reported:

unity-system-compositor --debug-without-dm

fails to start due to:

ERROR: 
/build/unity-system-compositor-Z26sU0/unity-system-compositor-0.8.0+17.04.20161206/src/dbus_connection_handle.cpp(66):
 Throw in function void usc::DBusConnectionHandle::request_name(const char*) 
const
Dynamic exception type: 
boost::exception_detail::clone_impl
std::exception::what: dbus_request_name: Failed to become primary owner

I would have thought that's what the debug option is there to work
around.

** Affects: unity-system-compositor
 Importance: Undecided
 Status: New

** Affects: unity-system-compositor (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  'unity-system-compositor --debug-without-dm' fails to start:
  'std::exception::what: dbus_request_name: Failed to become primary
  owner'

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor --debug-without-dm

  fails to start due to:

  ERROR: 
/build/unity-system-compositor-Z26sU0/unity-system-compositor-0.8.0+17.04.20161206/src/dbus_connection_handle.cpp(66):
 Throw in function void usc::DBusConnectionHandle::request_name(const char*) 
const
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: dbus_request_name: Failed to become primary owner

  I would have thought that's what the debug option is there to work
  around.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1653593/+subscriptions

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

[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

[Luke Yelavich]

The upload was rejected due to lack of SRU information. Could you please add 
that according to 
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Thanks.

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

Title:
  There is no entry in 'Play sound through' list when plug in headset
  jack [8086:9d70].

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Trusty:
  New

Bug description:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.

  The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1643812/+subscriptions

-- 
Mailing list: https://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 1384503] Re: rsync fails on large files with compression

[Robie Basak]

On Tue, Jan 03, 2017 at 05:00:09AM -, Haw Loeung wrote:
> rsync shipped in Xenial builds with the included zlib (--with-included-
> zlib=yes and -Izlib). Couldn't we SRU a fix doing the same thing as per
> https://bugs.launchpad.net/rsync/+bug/1300367/comments/6?

I am -1 on any SRU that does not come with a comprehensive regression
risk analysis. It's not the patch that is the problem; it is the
consideration of all interoperability permutations that needs to be made
if behaviour in this area is to be changed.

I'm not saying we can't do it; just that we need to carefully consider
what behaviour in what parts of the interoperability matrix we'd be
changing, what the regression risk is for each of those permutations,
and how to mitigate that.

It's not sufficient to say "we did it in Xenial so we can do the same in
Trusty". For example: without testing or analysis, I don't know if your
proposal breaks interoperability between Precise and Trusty when perhaps
that combination works today, or between non-updated Trusty and updated
Trusty.

My example is not exhaustive (testing just my example is not enough).

Remember also that each version combination has two directions, further
exploding the number of permutations to check. It would be OK if an
analysis convincingly collapses some of the permutations, but no such
analysis currently exists, AFAIK.

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Triaged

Bug description:
  [Status]
  This issue is currently Incomplete.

  We're currently blocked on obtaining access to a reliable, and publicly 
  available dataset that can be shared to reproduce the issue.  The test
  is critical to being able to evaluate the impact of the change on other
  users when assessing if the fix can be SRU'ed to trusty.

  If you are affected by this bug and can reliably reproduce the issue
  with a specific dataset that you are willing and permitted to share please
  comment and specify the dataset location, and how you reproduce the issue.

  
  [Original Description]
  Copying large (>10GB) files with rsync -z (compression) leads to a long hang 
and eventual error after transferring part of the file.  The error is 
consistent.  The file copies at normal speed until it reaches its maximum size 
(1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another).  Then nothing 
happens for a while (many minutes).  Finally, there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

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

[Touch-packages] [Bug 1384503] Re: rsync fails on large files with compression

[Haw Loeung]

Search for --with-included-zlib in the following build logs:

Zesty - 
https://launchpadlibrarian.net/293687018/buildlog_ubuntu-zesty-amd64.rsync_3.1.2-1_BUILDING.txt.gz
Xenial - 
https://launchpadlibrarian.net/234647228/buildlog_ubuntu-xenial-amd64.rsync_3.1.1-3ubuntu1_BUILDING.txt.gz
Vivid - 
https://launchpadlibrarian.net/234714800/buildlog_ubuntu-vivid-amd64.rsync_3.1.1-3ubuntu0.15.04.1_BUILDING.txt.gz
Trusty - 
https://launchpadlibrarian.net/156027313/buildlog_ubuntu-trusty-amd64.rsync_3.1.0-2_UPLOADING.txt.gz

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Triaged

Bug description:
  [Status]
  This issue is currently Incomplete.

  We're currently blocked on obtaining access to a reliable, and publicly 
  available dataset that can be shared to reproduce the issue.  The test
  is critical to being able to evaluate the impact of the change on other
  users when assessing if the fix can be SRU'ed to trusty.

  If you are affected by this bug and can reliably reproduce the issue
  with a specific dataset that you are willing and permitted to share please
  comment and specify the dataset location, and how you reproduce the issue.

  
  [Original Description]
  Copying large (>10GB) files with rsync -z (compression) leads to a long hang 
and eventual error after transferring part of the file.  The error is 
consistent.  The file copies at normal speed until it reaches its maximum size 
(1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another).  Then nothing 
happens for a while (many minutes).  Finally, there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

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

[Touch-packages] [Bug 1384503] Re: rsync fails on large files with compression

[Haw Loeung]

rsync shipped in Xenial builds with the included zlib (--with-included-
zlib=yes and -Izlib). Couldn't we SRU a fix doing the same thing as per
https://bugs.launchpad.net/rsync/+bug/1300367/comments/6?

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Triaged

Bug description:
  [Status]
  This issue is currently Incomplete.

  We're currently blocked on obtaining access to a reliable, and publicly 
  available dataset that can be shared to reproduce the issue.  The test
  is critical to being able to evaluate the impact of the change on other
  users when assessing if the fix can be SRU'ed to trusty.

  If you are affected by this bug and can reliably reproduce the issue
  with a specific dataset that you are willing and permitted to share please
  comment and specify the dataset location, and how you reproduce the issue.

  
  [Original Description]
  Copying large (>10GB) files with rsync -z (compression) leads to a long hang 
and eventual error after transferring part of the file.  The error is 
consistent.  The file copies at normal speed until it reaches its maximum size 
(1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another).  Then nothing 
happens for a while (many minutes).  Finally, there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

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

[Touch-packages] [Bug 1384503] Re: rsync fails on large files with compression

[Robie Basak]

Thank you for the test case. Unfortunately Ryan is no longer available
to work on this, so I'll unassign him.

Fixing this is non-trivial. I think any fix has a high risk of
regression, particularly with the permutations of rsync versions that
must interoperate. The full matrix needs to be considered and each
permutation tested. Given that this is a significant amount of work, the
compatibility issue with older versions will die over time, and 16.04
exists, I'm not sure it's worth our time.

This does not preclude any volunteer from taking this on, however.

** Changed in: rsync (Ubuntu Trusty)
 Assignee: Ryan Harper (raharper) => (unassigned)

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Triaged

Bug description:
  [Status]
  This issue is currently Incomplete.

  We're currently blocked on obtaining access to a reliable, and publicly 
  available dataset that can be shared to reproduce the issue.  The test
  is critical to being able to evaluate the impact of the change on other
  users when assessing if the fix can be SRU'ed to trusty.

  If you are affected by this bug and can reliably reproduce the issue
  with a specific dataset that you are willing and permitted to share please
  comment and specify the dataset location, and how you reproduce the issue.

  
  [Original Description]
  Copying large (>10GB) files with rsync -z (compression) leads to a long hang 
and eventual error after transferring part of the file.  The error is 
consistent.  The file copies at normal speed until it reaches its maximum size 
(1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another).  Then nothing 
happens for a while (many minutes).  Finally, there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

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

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

[Touch-packages] [Bug 1232788] Re: Software demo clients either hang or crash [MirSurface::get_cpu_region()] with unity-system-compositor. Not so with mir_demo_server_*

[Launchpad Bug Tracker]

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  Software demo clients either hang or crash
  [MirSurface::get_cpu_region()] with unity-system-compositor. Not so
  with mir_demo_server_*

Status in Mir:
  Expired
Status in Unity System Compositor:
  Expired
Status in mir package in Ubuntu:
  Expired

Bug description:
  i was testing mir using the mir_demo_client_flicker demo mir client

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: mir-demos 0.0.12+13.10.20130926.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sun Sep 29 15:07:57 2013
  ExecutablePath: /usr/bin/mir_demo_client_flicker
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: mir_demo_client_flicker
  SegvAnalysis:
   Segfault happened at: 0x7fe04195ef74 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7fe04195ef74) ok
   source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: mir
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x7fe0421389f0 <_IO_stdfile_1_lock>) at 
pthread_mutex_lock.c:50
   MirSurface::get_cpu_region(MirGraphicsRegion&) () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.3
   main ()
  Title: mir_demo_client_flicker crashed with SIGSEGV in 
__GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1232788] Re: Software demo clients either hang or crash [MirSurface::get_cpu_region()] with unity-system-compositor. Not so with mir_demo_server_*

[Launchpad Bug Tracker]

[Expired for Unity System Compositor because there has been no activity
for 60 days.]

** Changed in: unity-system-compositor
   Status: Incomplete => Expired

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

Title:
  Software demo clients either hang or crash
  [MirSurface::get_cpu_region()] with unity-system-compositor. Not so
  with mir_demo_server_*

Status in Mir:
  Expired
Status in Unity System Compositor:
  Expired
Status in mir package in Ubuntu:
  Expired

Bug description:
  i was testing mir using the mir_demo_client_flicker demo mir client

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: mir-demos 0.0.12+13.10.20130926.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sun Sep 29 15:07:57 2013
  ExecutablePath: /usr/bin/mir_demo_client_flicker
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: mir_demo_client_flicker
  SegvAnalysis:
   Segfault happened at: 0x7fe04195ef74 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7fe04195ef74) ok
   source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: mir
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x7fe0421389f0 <_IO_stdfile_1_lock>) at 
pthread_mutex_lock.c:50
   MirSurface::get_cpu_region(MirGraphicsRegion&) () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.3
   main ()
  Title: mir_demo_client_flicker crashed with SIGSEGV in 
__GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1232788] Re: Software demo clients either hang or crash [MirSurface::get_cpu_region()] with unity-system-compositor. Not so with mir_demo_server_*

[Launchpad Bug Tracker]

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

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

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

Title:
  Software demo clients either hang or crash
  [MirSurface::get_cpu_region()] with unity-system-compositor. Not so
  with mir_demo_server_*

Status in Mir:
  Expired
Status in Unity System Compositor:
  Expired
Status in mir package in Ubuntu:
  Expired

Bug description:
  i was testing mir using the mir_demo_client_flicker demo mir client

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: mir-demos 0.0.12+13.10.20130926.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Sun Sep 29 15:07:57 2013
  ExecutablePath: /usr/bin/mir_demo_client_flicker
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: mir_demo_client_flicker
  SegvAnalysis:
   Segfault happened at: 0x7fe04195ef74 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7fe04195ef74) ok
   source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: mir
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x7fe0421389f0 <_IO_stdfile_1_lock>) at 
pthread_mutex_lock.c:50
   MirSurface::get_cpu_region(MirGraphicsRegion&) () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.3
   main ()
  Title: mir_demo_client_flicker crashed with SIGSEGV in 
__GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1502704] Re: Cannot get source packages without root privileges

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot get source packages without root privileges

Status in apt package in Ubuntu:
  Expired

Bug description:
  When I try
  apt-get source coreutils
  as standard user I get
  Error: You must put some 'source' URIs in your sources.list
  With sudo apt-get source works as expected.
  Remove please the need of root privileges to download source packages.
  I have deb-src lines in /etc/apt/sources.list.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.10
  ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25
  Uname: Linux 3.13.0-63-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  Date: Sun Oct  4 22:27:55 2015
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-04 (548 days ago)

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

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

[Touch-packages] [Bug 1549645] Re: powerpc-linux-gnu-ld.bfd crashed with SIGSEGV in bfd_perform_relocation()

[Launchpad Bug Tracker]

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

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

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

Title:
  powerpc-linux-gnu-ld.bfd crashed with SIGSEGV in
  bfd_perform_relocation()

Status in binutils package in Ubuntu:
  Expired

Bug description:
  Building opal-prd as part of skiboot:

   git clone https://github.com/open-power/skiboot
   cd external/opal-prd
   CROSS_COMPILE=powerpc-linux-gnu- make

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: binutils-powerpc-linux-gnu 2.26-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Feb 25 15:25:32 2016
  Dependencies:
   binutils 2.26-4ubuntu1
   gcc-6-base 6-20160220-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160220-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  ExecutablePath: /usr/bin/powerpc-linux-gnu-ld.bfd
  SegvAnalysis:
   Segfault happened at: 0x7f38186b1df7:mov0xf8(%rdx),%rax
   PC (0x7f38186b1df7) ok
   source "0xf8(%rdx)" (0x00f8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: binutils
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libbfd-2.26-powerpc.so
   bfd_perform_relocation () from 
/usr/lib/x86_64-linux-gnu/libbfd-2.26-powerpc.so
   bfd_generic_get_relocated_section_contents () from 
/usr/lib/x86_64-linux-gnu/libbfd-2.26-powerpc.so
   ?? () from /usr/lib/x86_64-linux-gnu/libbfd-2.26-powerpc.so
   bfd_elf_final_link () from /usr/lib/x86_64-linux-gnu/libbfd-2.26-powerpc.so
  Title: powerpc-linux-gnu-ld.bfd crashed with SIGSEGV in 
bfd_perform_relocation()
  UpgradeStatus: Upgraded to xenial on 2015-03-05 (356 days ago)
  UserGroups: adm cdrom dialout dip docker kvm libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Olaf Waszkewitz]

It started with the 16.04 upgrade. I noticed that the mouse cursor works
a few seconds after login but after my Psensor (temperature display)
started up, the mouse cursor jumps. Wonder what library Psensor is
using.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1652695] Re: GCE default NTP configuration uses both leap-smeared and true UTC sources

[Robie Basak]

> However, we may want to consider changing the default ntp
configuration to use 'server' rather than 'pool' for ntp.ubuntu.com, to
ensure that it is included in the configuration at least once.

Why is this necessary? AIUI, ntp.ubuntu.com exists as a backup in case
pool.ntp.org (an externally managed domain) fails to resolve or is
otherwise down. Will this not work right now? If it does not, that's
really a separate bug (that we should fix).

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

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

Title:
  GCE default NTP configuration uses both leap-smeared and true UTC
  sources

Status in cloud-images:
  New
Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  A default install of cloud images on GCE results in a configuration of
  NTP which will likely be problematic during leap seconds, because it
  uses both Google's leap-smeared time source, and the public pool,
  which uses true UTC.  These should not be combined in the default
  configuration.

  The principle of least astonishment would suggest that a non-standard
  feature like leap smearing should be disabled by default.

  This behaviour has been consistent in the 3 different GCE regions in
  which I've recently created instances.

  
  root@instance-4:~# cat /etc/cloud/build.info 
  build_name: server
  serial: 20161221

  
  root@instance-4:~# cat /etc/ntp.conf
  # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

  driftfile /var/lib/ntp/ntp.drift

  # Enable this if you want statistics to be logged.
  #statsdir /var/log/ntpstats/

  statistics loopstats peerstats clockstats
  filegen loopstats file loopstats type day enable
  filegen peerstats file peerstats type day enable
  filegen clockstats file clockstats type day enable

  # Specify one or more NTP #servers.

  # Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
  # on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
  # more information.
  pool 0.ubuntu.pool.ntp.org iburst
  pool 1.ubuntu.pool.ntp.org iburst
  pool 2.ubuntu.pool.ntp.org iburst
  pool 3.ubuntu.pool.ntp.org iburst

  # Use Ubuntu's ntp #server as a fallback.
  pool ntp.ubuntu.com

  # ... comments snipped ...

  # By default, exchange time with everybody, but don't allow configuration.
  restrict -4 default kod notrap nomodify nopeer noquery limited
  restrict -6 default kod notrap nomodify nopeer noquery limited

  # Local users may interrogate the ntp #server more closely.
  restrict 127.0.0.1
  restrict ::1

  # Needed for adding pool entries
  restrict source notrap nomodify noquery

  # ... comments snipped ...

  # Google NTP source. This was added as part of the gce-cloud-config package.
  server metadata.google.internal

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1652695/+subscriptions

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

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

[e b]

Hi,

I don't know if it can help but I've a similar bug which involves restarting 
Rsyslog.
I use Ubuntu 16.04 LTS 64bits with Rsyslog 8.16-0-1ubuntu3 on two kind of 
hardware:

  - docker-machine
  - AWS EC2

I noticed that on servers that don't use systemd -- in this case docker-
machine -- using the sysV init script doesn't work.

The reason:

L 54 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5
--pidfile $PIDFILE --exec $DAEMON

If you remove the --quiet:
 /etc/init.d/rsyslog stop
 * Stopping enhanced syslogd rsyslogd
No /usr/sbin/rsyslogd found running; none killed.
   ...done.

Then if you remove --exec $DAEMON it works.

I have the same behavior when I use the init script on a systemd based
ubuntu. But the systemd job seems to work fine.

And of course, /etc/init.d/rsyslog rotate doesn't work either.

I'm currently debating with my self on how I'm going to handle that..

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

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com;] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  

[Touch-packages] [Bug 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

[Lee moonhyoung]

** Changed in: vim (Ubuntu)
 Assignee: (unassigned) => Lee moonhyoung (eobeauti2)

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

Title:
  Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in vim package in Ubuntu:
  Confirmed

Bug description:
  When launched from a terminal the widely used text editor gvim
  displays lots WARNING and CRITICAL messages such as:

  ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu-
  shell.c:176):unity_gtk_menu_shell_show_item: code should not be
  reached

  ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify:
  assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed

  This did not happen in 15.04. It is a most embarrassing bug. Gvim is
  an essential tool for many users.

  I am using Ubuntu 15.10 Beta 2.

  $ lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  $ apt-cache policy vim-gnome
  vim-gnome:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy vim-gtk
  vim-gtk:
Installed: 2:7.4.712-2ubuntu3
Candidate: 2:7.4.712-2ubuntu3
Version table:
   *** 2:7.4.712-2ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  I expected to be able to use Gvim. Now Gvim pollutes the terminal with
  scary messages, and disturbs the messages shown by other programs
  running in the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: vim-gnome 2:7.4.712-2ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 26 00:40:37 2015
  InstallationDate: Installed on 2015-09-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1653571] [NEW] package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[giezel]

Public bug reported:

a

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python2.7 2.7.6-8ubuntu0.3
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Tue Jan  3 08:59:18 2017
DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2016-01-07 (361 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python2.7
Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in python2.7 package in Ubuntu:
  New

Bug description:
  a

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python2.7 2.7.6-8ubuntu0.3
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Tue Jan  3 08:59:18 2017
  DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-01-07 (361 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python2.7
  Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1653571/+subscriptions

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

[Touch-packages] [Bug 1649453] Re: systemd starts postfix before resolver

[Greg Black]

Any idea when the fix will appear in updates for yakkety?

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

Title:
  systemd starts postfix before resolver

Status in postfix package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Postfix starts before systemd-resolved.service, resulting in postfix
  reporting that it can't find MX records for outgoing mail, as shown in
  the trace below:

  $ systemd-analyze critical-chain postfix.service systemd-resolved.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  postfix.service +1ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms
  systemd-resolved.service +268ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms

  The postfix service needs to start after systemd-resolved.service.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive 
yakkety-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages

  $ apt-cache policy postfix
  postfix:
Installed: 3.1.0-5
Candidate: 3.1.0-5
Version table:
   *** 3.1.0-5 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1570749] Re: Upgrade to 11.7 from May 2016

[Pander]

any progress on this bug that was set to 'critical'? Thanks.

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

Title:
  Upgrade to 11.7 from May 2016

Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 11.6 from February 2016, see https://libav.org/ and
  https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.6

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

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

[Touch-packages] [Bug 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering

[Andrew La Russa]

Post 10 did work with directory by creating the jabra.conf in
/usr/share/X11/xorg.conf.d/

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I switch the primary sound device to a USB headset connected to
  my laptop, mouse click events no longer work except in the Sound
  Settings window.  This does not seem to occur when the device is
  connected, only when it is made the default audio device.

  Once this occurs, the mouse events do not work until the device is
  disconnected.  Clicks inside the Sound Settings window are registered
  (including buttons and other tabs inside the System Settings window,
  but not the titlebar or close/minimize/maximize buttons.)  Focus can
  be given to other windows via alt-tab and keyboard input continues to
  function, but mouse events do not register on windows focused in this
  way.

  This is *deeply* weird, BTW.

  Hardware:
  Jabra EVOLVE 80 headset
  lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom 

  Steps to reproduce:
  1. Connect the device to a USB port.
  2. Open Sound Settings window.
  3. Select the Jabra USB device as the primary sound device.
  4. Observe that mouse clicks no longer register outside of the System 
Settings window.

  dmesg shows the following during this process:

  [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using 
xhci_hcd
  [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, 
idProduct=0305
  [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
  [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
  [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007
  [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as 
/devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
  [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB 
HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on 
usb-:00:14.0-2.1.1/input3
  [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130177.637403] usb 2-2.1.1: USB disconnect, device number 22

  
  This appears to possibly be related to bug #1371853.

  I'm happy to provide more information, try custom kernels, etc. as
  needed.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 13:00:25 2016
  DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-10-03 (222 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=21920f07-2445-42e9-82fe-5d6b209d8688 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  

[Touch-packages] [Bug 1653566] [NEW] package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Herman Heunis]

Public bug reported:

after installing libguestfs-tools

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.7
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
Date: Tue Jan  3 01:11:46 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-22 (11 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  after installing libguestfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.7
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Tue Jan  3 01:11:46 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-22 (11 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1581626] Re: Switching to USB sound device stops USB mouse clicks from registering

[Andrew La Russa]

This bug also affect me as well. I have a similar model, Jabra EVOLVE
40. If the device is connected during startup I have no issue, but if
its connected once logged in or subsequently disconnected/connected, I
have a similar issue to the OP, though it's regardless if I set the
device as the default.

lsusb:

Bus 002 Device 008: ID 0b0e:0306 GN Netcom

dmesg:

[  +0.018675] input: GN Netcom A/S Jabra EVOLVE LINK as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6.1/2-1.6.1:1.3/0003:0B0E:0306.0007/input/input24
[  +0.052471] hid-generic 0003:0B0E:0306.0007: input,hiddev0,hidraw4: USB HID 
v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK] on usb-:00:1d.0-1.6.1/input3
[  +0.025352] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.000515] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.003624] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[  +0.000626] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[  +0.001736] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.000497] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.019249] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[  +0.000646] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[  +0.003870] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.000623] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[  +0.374731] retire_capture_urb: 915 callbacks suppressed
[ +22.492209] usb 2-1.6.1: USB disconnect, device number 9

I'm not using an xorg config file, so not sure how to apply the fix from
post 10.

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

Title:
  Switching to USB sound device stops USB mouse clicks from registering

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I switch the primary sound device to a USB headset connected to
  my laptop, mouse click events no longer work except in the Sound
  Settings window.  This does not seem to occur when the device is
  connected, only when it is made the default audio device.

  Once this occurs, the mouse events do not work until the device is
  disconnected.  Clicks inside the Sound Settings window are registered
  (including buttons and other tabs inside the System Settings window,
  but not the titlebar or close/minimize/maximize buttons.)  Focus can
  be given to other windows via alt-tab and keyboard input continues to
  function, but mouse events do not register on windows focused in this
  way.

  This is *deeply* weird, BTW.

  Hardware:
  Jabra EVOLVE 80 headset
  lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom 

  Steps to reproduce:
  1. Connect the device to a USB port.
  2. Open Sound Settings window.
  3. Select the Jabra USB device as the primary sound device.
  4. Observe that mouse clicks no longer register outside of the System 
Settings window.

  dmesg shows the following during this process:

  [130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using 
xhci_hcd
  [130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, 
idProduct=0305
  [130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
  [130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
  [130169.223038] usb 2-2.1.1: SerialNumber: 51E7669007
  [130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as 
/devices/pci:00/:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
  [130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB 
HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on 
usb-:00:14.0-2.1.1/input3
  [130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
  [130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
  [130177.637403] usb 2-2.1.1: USB disconnect, device number 22

  
  This appears to possibly be related to bug #1371853.

  I'm happy to provide more information, try custom kernels, etc. as
  needed.  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 

[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

[Adam Szmigin]

In case this helps the non-gurus, I needed to do a fraction more than
Brad Lucier's suggestions, but a lot less than samrocketman's
suggestions, in order to get things working with my wife's iOS 10.2
device on Linux Mint 18:

1) Install dependencies for compilation
$ sudo apt install build-essential git
$ sudo apt install automake libtool pkg-config libplist-dev libplist++-dev 
python-dev libssl-dev libusb-1.0-0-dev libfuse-dev

2) Clone libimobiledevice, build, install
$ cd ~/path/to/my/build/dir
$ git clone https://github.com/libimobiledevice/libimobiledevice.git
$ cd libimobiledevice
$ ./autogen.sh --prefix=/usr/local/libimobiledevice
$ make
$ sudo make install

3) Configure the dynamic linker
$ echo "/usr/local/libimobiledevice/lib" | sudo tee 
/etc/ld.so.conf.d/000-libimobiledevice.conf
$ sudo ldconfig

Just cloning and compiling libimobiledevice from the git sources will
not build tools like ifuse, and it seems it is not necessary to do so,
provided the dynamic linker is set up correctly.  Apparently, using
ldconfig is preferred to setting LD_LIBRARY_PATH on Ubuntu and LM, so I
hear.  You can see if it's doing the right thing by looking at ldd.

It should show something like this:
$ ldd `which ifuse` | grep libimobiledevice
  libimobiledevice.so.6 => /usr/local/libimobiledevice/lib/libimobiledevice.so.6

If ldd shows something like this, the linker is not finding your rebuilt libs:
$ ldd `which ifuse` | grep libimobiledevice
  libimobiledevice.so.6 => /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6

Hope this helps until a strategic solution is in place.

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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

[Touch-packages] [Bug 1651041] Re: package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Scott Kitterman]

Looks like a upower bug:

dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 36944 
package 'libupower-glib3:amd64':
 'Recommends' field, reference to 'upower':
 '>' is obsolete, use '>=' or '>>' instead
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 36944 
package 'libupower-glib3:amd64':
 'Recommends' field, reference to 'upower':
 version value starts with non-alphanumeric, suggest adding a space
dpkg-query: error: parsing file '/var/lib/dpkg/status' near line 36944 package 
'libupower-glib3:amd64':
 'Recommends' field, reference to 'upower': version contains ' '
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 289, in 
main()
  File "/usr/bin/pycompile", line 262, in main
options.force, options.optimize, e_patterns)
  File "/usr/bin/pycompile", line 154, in compile
for fn, versions_to_compile in filter_files(files, e_patterns, versions):
  File "/usr/bin/pycompile", line 109, in filter_files
for fn in files:
  File "/usr/share/python/debpython/files.py", line 77, in filter_out_ext
for fn in files:
  File "/usr/share/python/debpython/namespace.py", line 77, in 
add_namespace_files
for fn in files:
  File "/usr/share/python/debpython/files.py", line 69, in filter_public
for fn in files:
  File "/usr/share/python/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of python-httplib2
dpkg: error processing package python-httplib2 (--configure):
 subprocess installed post-installation script returned error exit status 1


** Package changed: python-httplib2 (Ubuntu) => upower (Ubuntu)

** Summary changed:

- package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ Bad version in Recommends

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

Title:
  Bad version in Recommends

Status in upower package in Ubuntu:
  New

Bug description:
  not really sure what to say am a novice

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-httplib2 0.9.1+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sun Dec 18 23:25:18 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-14 (4 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: python-httplib2
  Title: package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-19 (0 days ago)

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

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

[Touch-packages] [Bug 1651041] [NEW] package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

not really sure what to say am a novice

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-httplib2 0.9.1+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sun Dec 18 23:25:18 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-14 (4 days ago)
InstallationMedia:
 
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: python-httplib2
Title: package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-12-19 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check xenial
-- 
package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1651041
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

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

[Touch-packages] [Bug 1620118] Re: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am new with ubuntu, I bought a new laptop it came with ubuntu 14.04
  LTs installed on it and I decided to use it like that. Initially it
  was working correctly, but later I realized there is no sound when
  using any browser or playing video. So I upgraded to ubuntu 16.04 and
  the sound is working with firefox browser, but if I plug speaker it
  stop. Then I opened the sound setting and click output and there is
  mode of sound and I try to select so mode but then the tab disappeared
  and there is no sound at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhashim4153 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep  4 23:19:46 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-02-11 (206 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhashim4153 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (0 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 05T1GT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn05T1GT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1653554] [NEW] Unread messages counter requires viewing actual message before decrementing

[Joe Liau]

Public bug reported:

Mako
Rc-proposed

Issue:
Viewing and responding to message from quick settings doesn't mark message as 
read.
Furthermore, if viewing message in messaging app, you must scroll up to that 
message in order to decrement the unread message counter.

This feature makes a lot of sense as is, but some people send flurries
of messages and it is often that some messages get pushed up beyond
conviences of viewing them. As a result, there is always an inread
message counter.

A few things could be considered:
- mark message(s) read if replied to from quick settings
- mark all messages read when conversation is opened in messaging app*
-* option to mark all messages as read or jump to the oldest unread message

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unread messages counter requires viewing actual message before
  decrementing

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Mako
  Rc-proposed

  Issue:
  Viewing and responding to message from quick settings doesn't mark message as 
read.
  Furthermore, if viewing message in messaging app, you must scroll up to that 
message in order to decrement the unread message counter.

  This feature makes a lot of sense as is, but some people send flurries
  of messages and it is often that some messages get pushed up beyond
  conviences of viewing them. As a result, there is always an inread
  message counter.

  A few things could be considered:
  - mark message(s) read if replied to from quick settings
  - mark all messages read when conversation is opened in messaging app*
  -* option to mark all messages as read or jump to the oldest unread message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1653554/+subscriptions

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

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

[NetForHack]

Actual for xenial too

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

Title:
  secret-tool does not run on headless system

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  libsecret-tools:
Installed: 0.16-0ubuntu1
Candidate: 0.16-0ubuntu1
Version table:
   *** 0.16-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  I expected to be able to run secret-tool on a headless sytem, but got
  this message after running it.

  secret-tool store ...

  (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY

  # didn't expect thisto work, but thought I'd give it a try.
  export DISPLAY=:0
  secret-tool store ...

  (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Error spawning command line 'dbus-launch 
--autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': 
Child process exited with code 1

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Crimbo]

Scrap that... I realised it was because I had the 'indicator-datetime-
service' package set to 'stop' in the system monitor (which is a great
temporary fix if anyone is having this same issue).

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

[Crimbo]

Scrap that... I realised it was because I had the 'indicator-datetime-
service' package set to 'stop' in the system monitor (which is a great
temporary fix if anyone is having this same issue).

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

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

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

[Touch-packages] [Bug 1652789] Re: indicator-datetime-service using high volumes of ram/memory

[Crimbo]

Scrap that... I realised it was because I had the 'indicator-datetime-
service' package set to 'stop' in the system monitor (which is a great
temporary fix if anyone is having this same issue).

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

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

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

[Touch-packages] [Bug 1582068] Re: Can't create GPG key - it stop before asking for passphrase

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't create GPG key - it stop before asking for passphrase

Status in gnupg package in Ubuntu:
  Confirmed

Bug description:
  My distribution: lubuntu 16.04
  environment: encrypted home drive

  I have run the following to create the key for signing

  gnu --gen-key

  The program interactively asks for information and it was provided
  accordingly.

  at the end I receive

  Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
  You need a Passphrase to protect your secret key.

  It doesn't ask for passphrase and appears to be hung.
  pressing -C I get the following

  gpg: Interrupt caught ... exiting

  I tried to look for the log and there seems to be non.

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

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Melvin Hausmann]

I got the same problem, hibernation working fine with Ubuntu 16.04 and
now (still) not working after upgrade to 16.10 (running Linux version
4.8.0-32-generic (buildd@lcy01-34) (gcc version 6.2.0 20161005 (Ubuntu
6.2.0-5ubuntu12) ) #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 (Ubuntu
4.8.0-32.34-generic 4.8.11)) / Kubuntu 16.10

Even more vexing is that when I tell my system to hibernate it gets
stuck somewhere, not writing anything to the disk anymore. When running
sudo pm-hibernate in tty1 I get kernel messages saying that the system
has lost the synchronization with my EXT4 partitions and that journaling
would be disabled therefore.

Afterwards I can only turn my Laptop off via the power button and boot
again.


The last lines from /var/log/pm-hibernbate.log
Running hook /etc/pm/sleep.d/novatel_3g_suspend hibernate hibernate:
/etc/pm/sleep.d/novatel_3g_suspend hibernate hibernate: success.

Mo 2. Jan 17:24:11 CET 2017: performing hibernate


[END_OF_FILE]


Syslog extract from /var/log/syslog.1

Jan  2 17:23:34 MH4Linux systemd[1]: Starting Stop ureadahead data collection...
Jan  2 17:23:34 MH4Linux systemd[1]: Started Stop ureadahead data collection.
Jan  2 17:24:11 MH4Linux kernel: [  119.501530] bbswitch: enabling discrete 
graphics
Jan  2 17:28:24 MH4Linux rsyslogd: [origin software="rsyslogd" 
swVersion="8.16.0" x-pid="784" x-info="http://www.rsyslog.com;] start
Jan  2 17:28:24 MH4Linux rsyslogd: rsyslogd's groupid changed to 108

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1641919/+subscriptions

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Melvin Hausmann]

** Attachment added: "dmesg output after (another) dead start."
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1641919/+attachment/4799134/+files/dmesg.log

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1641919/+subscriptions

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

[Touch-packages] [Bug 1627919] Re: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1

[Alberto Salvia Novella]

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

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

Title:
  package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el
  subproceso instalado el script pre-removal devolvió el código de
  salida de error 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  me encontraba instalando un paquete .deb descargado de la página
  oficial de mysongbook, similar a lo que sería guitar pro... y el
  instalador de paquetes dpkg estalló

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 26 22:49:04 2016
  ErrorMessage: el subproceso instalado el script pre-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-02-11 (228 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el 
subproceso instalado el script pre-removal devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

[Alberto Salvia Novella]

** Changed in: hicolor-icon-theme (Ubuntu)
   Importance: Undecided => High

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

Title:
  package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade
  triggers looping

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04
  something like a post-install hook apparently triggered looping.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Aug  6 11:48:42 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-02-24 (893 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1610517/+subscriptions

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

[Touch-packages] [Bug 1609891] Re: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

[Alberto Salvia Novella]

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

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

Title:
  package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess
  new pre-installation script returned error exit status 2

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from 14.04.3 to 16.04.1

  Noted during install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Aug  4 09:10:47 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2015-08-19 (351 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: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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

[Touch-packages] [Bug 1622730] Re: No sound on headphones after suspend

[Alberto Salvia Novella]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  No sound on headphones after suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a common problem on XMG Clevo W230SS there is no
  output on the headphone jack after suspend. The headphones are
  detected and the speakers are muted, but there is no output to the
  headphones. Init-headphones does not help:

  sudo init-headphone 
  WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax
  WARNING:root:Module is not loaded: i2c_dev
  ERROR:root:Can't find i2c bus
  ERROR:root:Operation failed

  Any workaround beside reboot?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  pia   23276 F pulseaudio
   /dev/snd/controlC0:  pia   23276 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Sep 12 21:56:08 2016
  InstallationDate: Installed on 2015-11-05 (312 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815

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

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

[Touch-packages] [Bug 1605941] Re: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  NOT SURE WHAT IT IS  SORRY

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 15:50:43 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-27 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651082] Re: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

@ Murilla Clinton

You can join at
https://launchpad.net/~ubuntu-testing

:P

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

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  "there was an error installing package" that is the massage i receive
  every time i install a package using terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Dec 19 13:13:39 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-15 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

[per]

This will work with LinuxMint18,1 and iOS 10.2 I just follow the
instructions
https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc
now I can access my folders on my Iphone ;-) Thank you Sam

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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

[Touch-packages] [Bug 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

[Alberto Salvia Novella]

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop

Status in xorg package in Ubuntu:
  Confirmed

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
  ---
  For Roll-Back:
  > Terminal >
  sudo apt install systemd-sysv
  sudo update-initramfs -u
  sudo shutdown -r now
  --
  Sorry, don't know, what to try next 

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Alberto Salvia Novella]

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1613078] Re: package console-setup 1.108ubuntu15.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

[Alberto Salvia Novella]

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => High

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

Title:
  package console-setup 1.108ubuntu15.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 10

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  
  _
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-35.54-generic 4.4.16
  Uname: Linux 4.4.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 14 17:10:19 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2015-12-01 (257 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup 1.108ubuntu15.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
  UpgradeStatus: Upgraded to xenial on 2016-08-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1613078/+subscriptions

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Launchpad Bug Tracker]

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

** Changed in: pm-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1641919/+subscriptions

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

[Launchpad Bug Tracker]

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

** Changed in: nouveau-firmware (Ubuntu)
   Status: New => Confirmed

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1641919/+subscriptions

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

[Touch-packages] [Bug 1653540] [NEW] Using Processor microcode firmware for intel CPUs from intel-microcode(proprietary)

[mohamed]

Public bug reported:

I have installed Ubuntu 16-04-1 update it many times on Hp Compaq Elite 8100 
SFF.
On a details setting, on overview, I have this configuration:
The device name, memory, Processor Intel i5 cpu 650 @ 3,5 GHz X 4
Graphics intel Ironlake desktop
Os type 64.
I have an issue with my display monitor: 
I have Unknown display
Cannot change the resolution of my screen 1024:768(4:3) to higher.

Under Software & update I have these messages:
Unknown: Unknown (this device is using an alternative driver)
Using Processor microcode firmware for intel CPUs from 
intel-microcode(proprietary)
my product hp machine is: AY032AV: HP Compaq 8100 SFF

mohamed@HP-Cpq-PC:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

mohamed@HP-Cpq-PC:~$ apt-cache policy pkgname
N: Unable to locate package pkgname

Of course I have tried most of answer in every website.

Thank you for your help

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
Uname: Linux 4.4.0-58-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
 [  OK  ] Started LSB: daemon to balance interrupts for SMP systems.
 [  OK  ] Started Raise network interfaces.
 [  OK  ] Reached target Network.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jan  2 18:19:21 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:304a]
InstallationDate: Installed on 2017-01-01 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP Compaq 8100 Elite SFF PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic 
root=UUID=e4b57f22-d72d-441a-9f95-637a0d130be8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option 
"AccelMethod" "sna" EndSection
dmi.bios.date: 06/09/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786H1 v01.05
dmi.board.asset.tag: CZC1326QPX
dmi.board.name: 304Ah
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC1326QPX
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786H1v01.05:bd06/09/2010:svnHewlett-Packard:pnHPCompaq8100EliteSFFPC:pvr:rvnHewlett-Packard:rn304Ah:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq 8100 Elite SFF PC
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jan  2 18:05:38 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  Using Processor microcode firmware for intel CPUs from intel-
  microcode(proprietary)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed Ubuntu 16-04-1 update it many times on Hp Compaq Elite 8100 
SFF.
  On a details setting, on overview, I have this configuration:
  The device name, memory, Processor Intel i5 cpu 650 @ 3,5 GHz X 4
  Graphics intel Ironlake desktop
  Os type 64.
  I have an issue with my display monitor: 
  I have Unknown display
  Cannot change the resolution of my screen 1024:768(4:3) to higher.

  Under Software & update I have these messages:
  Unknown: Unknown (this device is using an alternative driver)
  Using Processor 

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Crimbo]

This seems to have been resolved now, since running a system update on
Yakkety via 'Ubuntu Software'. Can anyone else confirm the same?

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

[Crimbo]

This seems to have been resolved now, since running a system update on
Yakkety via 'Ubuntu Software'. Can anyone else confirm the same?

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

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

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

[Touch-packages] [Bug 1652789] Re: indicator-datetime-service using high volumes of ram/memory

[Crimbo]

This seems to have been resolved now, since running a system update.

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

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

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

[Touch-packages] [Bug 1573856] Re: NetworkManager resets spoofed mac address to physical mac

[Sebastien Bacher]

Looking upstream it seems similar to
https://bugzilla.gnome.org/show_bug.cgi?id=770611

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

Title:
  NetworkManager resets spoofed mac address to physical mac

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 bumped NetworkManager to version 1.1.93. Unlike 15.10
  (with v1.0.4) and earlier NetworkManager now resets temporary mac of
  an interface to actual physical mac effectively disabling typical wifi
  anonymization technics.

  Same issue is present in just released NetworkManager 1.2.

  It appears that sometime between 1.0.10 and 1.1.93 there was a change
  in src/devices/wifi/nm-device-wifi.c from

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   if (cloned_mac)
    nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);
  to

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);

  cloned_mac is NULL if not specified in NetworkManager GUI. When called
  with NULL nm_device_set_hw_addr sets the mac to physical mac of the
  interface.

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

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

[Touch-packages] [Bug 1573856] Re: NetworkManager resets spoofed mac address to physical mac

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Bug watch added: GNOME Bug Tracker #770611
   https://bugzilla.gnome.org/show_bug.cgi?id=770611

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

Title:
  NetworkManager resets spoofed mac address to physical mac

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 bumped NetworkManager to version 1.1.93. Unlike 15.10
  (with v1.0.4) and earlier NetworkManager now resets temporary mac of
  an interface to actual physical mac effectively disabling typical wifi
  anonymization technics.

  Same issue is present in just released NetworkManager 1.2.

  It appears that sometime between 1.0.10 and 1.1.93 there was a change
  in src/devices/wifi/nm-device-wifi.c from

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   if (cloned_mac)
    nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);
  to

   /* Set spoof MAC to the interface */
   cloned_mac = nm_setting_wireless_get_cloned_mac_address (s_wireless);
   nm_device_set_hw_addr (device, cloned_mac, "set", LOGD_WIFI);

  cloned_mac is NULL if not specified in NetworkManager GUI. When called
  with NULL nm_device_set_hw_addr sets the mac to physical mac of the
  interface.

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

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

[Touch-packages] [Bug 1652791] Re: Evince PDF doesn't print, yet Writer prints just fine

[Sebastien Bacher]

Seems like it was an user config error then (or a printer driver one for
allowing setting an option that makes the printer bug)

** Changed in: ubuntu
   Importance: Undecided => Low

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

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

Title:
  Evince PDF doesn't print, yet Writer prints just fine

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  I have the Canon PIXMA IP7250 printer installed. When I plug it via
  the USB cable, the printer driver seems autodetected incorrectly:
  Canon iP7200 series - CUPS+Gutenprint v5.2.11 , however printing of
  the test page succeeds and the test page is printed successfully.
  Writer is also able to print the documents correctly. However printing
  PDFs via Evince does absolutely nothing - the printing job seems to
  get executed correctly, however the printer power led just blinks two
  times and that's it - no error message is produced, no segfault, no
  feedback, nothing.

  The really interesting thing is that on another laptop with Ubuntu
  16.10 the printer works correctly and prints the PDF without any
  problem. I am totally at loss what to google for or where to search
  for possible solutions as there is no error message :(

  Thanks for any tip.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 27 16:08:05 2016
  Lpstat: device for iP7200-series: usb://Canon/iP7200%20series?serial=0100CA
  MachineType: Hewlett-Packard HP EliteBook 8460p
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iP7200-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/iP7200-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=20d1b3dc-793d-4f98-b4b4-b9d6e062c35a ro nosplash
  SourcePackage: cups
  UpgradeStatus: Upgraded to yakkety on 2016-12-27 (0 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.50
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4D
  dmi.chassis.asset.tag: CZC23317TB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1652791] [NEW] Evince PDF doesn't print, yet Writer prints just fine

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have the Canon PIXMA IP7250 printer installed. When I plug it via the
USB cable, the printer driver seems autodetected incorrectly: Canon
iP7200 series - CUPS+Gutenprint v5.2.11 , however printing of the test
page succeeds and the test page is printed successfully. Writer is also
able to print the documents correctly. However printing PDFs via Evince
does absolutely nothing - the printing job seems to get executed
correctly, however the printer power led just blinks two times and
that's it - no error message is produced, no segfault, no feedback,
nothing.

The really interesting thing is that on another laptop with Ubuntu 16.10
the printer works correctly and prints the PDF without any problem. I am
totally at loss what to google for or where to search for possible
solutions as there is no error message :(

Thanks for any tip.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cups 2.2.0-2
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 27 16:08:05 2016
Lpstat: device for iP7200-series: usb://Canon/iP7200%20series?serial=0100CA
MachineType: Hewlett-Packard HP EliteBook 8460p
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/iP7200-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/iP7200-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=20d1b3dc-793d-4f98-b4b4-b9d6e062c35a ro nosplash
SourcePackage: cups
UpgradeStatus: Upgraded to yakkety on 2016-12-27 (0 days ago)
dmi.bios.date: 08/04/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.50
dmi.board.name: 161C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.4D
dmi.chassis.asset.tag: CZC23317TB
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8460p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Invalid


** Tags: amd64 apparmor apport-bug yakkety
-- 
Evince PDF doesn't print, yet Writer prints just fine
https://bugs.launchpad.net/bugs/1652791
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

[Sebastien Bacher]

There is a similar report upstream on
https://bugzilla.gnome.org/show_bug.cgi?id=772827 could be a good place
to comment for those having the issue

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

** Bug watch added: GNOME Bug Tracker #772827
   https://bugzilla.gnome.org/show_bug.cgi?id=772827

** Bug watch added: GNOME Bug Tracker #597839
   https://bugzilla.gnome.org/show_bug.cgi?id=597839

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

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in Network Manager Applet:
  Unknown
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1653529] Re: qtwebkit 5.7.1 fails to build on armhf

[Timo Jyrinki]

(retried once, it persisted)

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

Title:
  qtwebkit 5.7.1 fails to build on armhf

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  Build log: https://launchpadlibrarian.net/300952415/buildlog_ubuntu-
  zesty-armhf.qtwebkit-opensource-src_5.7.1+dfsg-
  1build1~1_BUILDING.txt.gz

  ---
  g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-Wl,--no-undefined -fdebug-types-section -Wl,-O1 -Wl,--enable-new-dtags 
-Wl,--no-keep-memory -shared -Wl,-soname,libQt5WebKit.so.5 -o 
libQt5WebKit.so.5.7.1   -lQt5Gui -lQt5Core -lpthread -lQt5Network -lQt5Core 
-lpthread -lQt5Core -lpthread -lpthread -Wl,-whole-archive -lWebKit1 
-Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit/ 
-Wl,-whole-archive -lWebKit2 -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit2/ -lrt 
-Wl,-whole-archive -lWebCore -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebCore/ -lz 
-lXrender -ljpeg -lpng -lwebp -Wl,-whole-archive -lANGLE -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/ANGLE/ 
-Wl,-whole-archive -lleveldb -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/leveldb/ 
-Wl,-whole-archive -lJa
 vaScriptCore -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/JavaScriptCore/ 
-Wl,-whole-archive -lWTF -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WTF/ -lpthread -lEGL 
-lXext -lX11 -lm -lX11 -lxslt -lxml2 -lxml2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 
-lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstapp-1.0 -lgstbase-1.0 
-lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstbase-1.0 -lgstreamer-1.0 
-lgobject-2.0 -lglib-2.0 -lgstpbutils-1.0 -lgstreamer-1.0 -lgobject-2.0 
-lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstvideo-1.0 
-lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstaudio-1.0 
-lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lsqlite3 -licui18n 
-licuuc -licudata -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lpthread 
-lQt5Qml -lQt5Network -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread 
-lQt5Gui -lQt5Core -lpthread -lQt5Sql -lQt5Core -lpthread -lQt5Core -lpthread 
-lGLESv2 
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `__bss_start'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `_edata'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `_end'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `_edata'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `__bss_start'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `_end'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `__bss_start'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `__bss_start'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_edata'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_edata'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_end'
  
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_end'
  collect2: error: ld returned 1 exit status
  ---

  This has built fine on Debian.

  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1653529/+subscriptions

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

[Touch-packages] [Bug 1653529] [NEW] qtwebkit 5.7.1 fails to build on armhf

[Timo Jyrinki]

Public bug reported:

Build log: https://launchpadlibrarian.net/300952415/buildlog_ubuntu-
zesty-armhf.qtwebkit-opensource-src_5.7.1+dfsg-1build1~1_BUILDING.txt.gz

---
g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-Wl,--no-undefined -fdebug-types-section -Wl,-O1 -Wl,--enable-new-dtags 
-Wl,--no-keep-memory -shared -Wl,-soname,libQt5WebKit.so.5 -o 
libQt5WebKit.so.5.7.1   -lQt5Gui -lQt5Core -lpthread -lQt5Network -lQt5Core 
-lpthread -lQt5Core -lpthread -lpthread -Wl,-whole-archive -lWebKit1 
-Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit/ 
-Wl,-whole-archive -lWebKit2 -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit2/ -lrt 
-Wl,-whole-archive -lWebCore -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebCore/ -lz 
-lXrender -ljpeg -lpng -lwebp -Wl,-whole-archive -lANGLE -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/ANGLE/ 
-Wl,-whole-archive -lleveldb -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/leveldb/ 
-Wl,-whole-archive -lJava
 ScriptCore -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/JavaScriptCore/ 
-Wl,-whole-archive -lWTF -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WTF/ -lpthread -lEGL 
-lXext -lX11 -lm -lX11 -lxslt -lxml2 -lxml2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 
-lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstapp-1.0 -lgstbase-1.0 
-lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstbase-1.0 -lgstreamer-1.0 
-lgobject-2.0 -lglib-2.0 -lgstpbutils-1.0 -lgstreamer-1.0 -lgobject-2.0 
-lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstvideo-1.0 
-lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstaudio-1.0 
-lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lsqlite3 -licui18n 
-licuuc -licudata -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lpthread 
-lQt5Qml -lQt5Network -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread 
-lQt5Gui -lQt5Core -lpthread -lQt5Sql -lQt5Core -lpthread -lQt5Core -lpthread 
-lGLESv2 
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `__bss_start'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `_edata'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0):
 multiple definition of `_end'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `_edata'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `__bss_start'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0):
 multiple definition of `_end'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `__bss_start'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `__bss_start'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_edata'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_edata'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_end'
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0):
 multiple definition of `_end'
collect2: error: ld returned 1 exit status
---

This has built fine on Debian.

https://wiki.ubuntu.com/Touch/QtTesting

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qt5.7

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

Title:
  qtwebkit 5.7.1 fails to build on armhf

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  Build log: https://launchpadlibrarian.net/300952415/buildlog_ubuntu-
  zesty-armhf.qtwebkit-opensource-src_5.7.1+dfsg-
  1build1~1_BUILDING.txt.gz

  ---
  g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-Wl,--no-undefined -fdebug-types-section -Wl,-O1 -Wl,--enable-new-dtags 
-Wl,--no-keep-memory -shared -Wl,-soname,libQt5WebKit.so.5 -o 
libQt5WebKit.so.5.7.1   -lQt5Gui -lQt5Core -lpthread -lQt5Network -lQt5Core 
-lpthread -lQt5Core -lpthread -lpthread -Wl,-whole-archive -lWebKit1 
-Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit/ 
-Wl,-whole-archive -lWebKit2 -Wl,-no-whole-archive 
-L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit2/ -lrt 
-Wl,-whole-archive -lWebCore -Wl,-no-whole-archive 

[Touch-packages] [Bug 1548300] Re: XDG_RUNTIME_DIR not set when using sudo -i

[Benpro]

As a temporary patch, you could set this to /etc/profile:
export XDG_RUNTIME_DIR="/run/user/$UID"

** Also affects: sudo (Debian)
   Importance: Undecided
   Status: New

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

Title:
  XDG_RUNTIME_DIR not set when using sudo -i

Status in sudo:
  New
Status in sudo package in Ubuntu:
  Confirmed
Status in sudo package in Debian:
  New

Bug description:
  According to the man page `sudo -i` will run the command with an
  environment "similar" to the one a user would receive at log in.

  When trying to use tools that use D-Bus, specifically: systemctl
  --user, it will be impossible to control them via sudo.

  While there is a workaround; setting the XDG_RUNTIME_DIR manually,
  this means any configuration change that causes the XDG_RUNTIME_DIR to
  change will have to be applied in several locations.

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

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

[Touch-packages] [Bug 1548300] Re: XDG_RUNTIME_DIR not set when using sudo -i

[Launchpad Bug Tracker]

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

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

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

Title:
  XDG_RUNTIME_DIR not set when using sudo -i

Status in sudo:
  New
Status in sudo package in Ubuntu:
  Confirmed
Status in sudo package in Debian:
  New

Bug description:
  According to the man page `sudo -i` will run the command with an
  environment "similar" to the one a user would receive at log in.

  When trying to use tools that use D-Bus, specifically: systemctl
  --user, it will be impossible to control them via sudo.

  While there is a workaround; setting the XDG_RUNTIME_DIR manually,
  this means any configuration change that causes the XDG_RUNTIME_DIR to
  change will have to be applied in several locations.

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

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

[Touch-packages] [Bug 1548300] Re: XDG_RUNTIME_DIR not set when using sudo -i

[Benpro]

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

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

Title:
  XDG_RUNTIME_DIR not set when using sudo -i

Status in sudo:
  New
Status in sudo package in Ubuntu:
  Confirmed
Status in sudo package in Debian:
  New

Bug description:
  According to the man page `sudo -i` will run the command with an
  environment "similar" to the one a user would receive at log in.

  When trying to use tools that use D-Bus, specifically: systemctl
  --user, it will be impossible to control them via sudo.

  While there is a workaround; setting the XDG_RUNTIME_DIR manually,
  this means any configuration change that causes the XDG_RUNTIME_DIR to
  change will have to be applied in several locations.

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

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

[Touch-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth signal is unusably poor

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Brand new Macbook Pro 12,1.  Brand new Ubuntu 16.04 install (from
  scratch).

  In MacOS the machine can connect to my bluetooth speaker from across
  the room and play A2DP no trouble at all.  In Ubuntu 16.04 I have to
  literally hold up the macbook 1 inch away from the speaker to get it
  to connect and play, and even then it's a bit choppy.  Turning off
  Wifi seems to help a bit, which leads me to think this is some kind of
  transmit power issue.

  Syslog is chock full of warnings about skipping audio:

  Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 206099 us (= 36352 bytes) in audio stream
  Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 382089 us (= 67400 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 394108 us (= 69520 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 328125 us (= 57880 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 59087 us (= 10420 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 14036 us (= 2472 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 247134 us (= 43592 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 342190 us (= 60360 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 172035 us (= 30344 bytes) in audio stream
  Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 803140 us (= 141672 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 651085 us (= 114848 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 202043 us (= 35640 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 265112 us (= 46764 bytes) in audio stream

  
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

  $ uname -a
  Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsusb
  Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
  Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
  Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
  Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ hciconfig 
  hci0: Type: BR/EDR  Bus: USB
BD Address: 98:01:A7:A8:D4:6A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:5198 acl:2 sco:0 events:269 errors:0
TX bytes:7021 acl:2 sco:0 commands:218 errors:0

  [bluetooth]# show
  Controller 98:01:A7:A8:D4:6A
Name: badassm
Alias: badassm
Class: 0x1c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Vendor specific   (5005--1000-8000-0002ee01)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: Message Access 

[Touch-packages] [Bug 1322854] Re: [4389W1B, Conexant CX20585, Speaker, Internal] Sound works for a while, then breaks

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

Title:
  [4389W1B, Conexant CX20585, Speaker, Internal] Sound works for a
  while, then breaks

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Today sound from speakers suddenly stopped while I was playing music.
  The problem persists reboot. Headphones work fine. When I dual-boot
  Windows on the same machine, there is no problem with the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ke 2142 F pulseaudio
   /dev/snd/controlC0:  ke 2142 F pulseaudio
ke 2726 F alsamixer
   /dev/snd/pcmC0D0p:   ke 2142 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Sat May 24 16:22:22 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-16 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ke 2142 F pulseaudio
   /dev/snd/controlC0:  ke 2142 F pulseaudio
ke 2726 F alsamixer
   /dev/snd/pcmC0D0p:   ke 2142 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [4389W1B, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4389W1B
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4389W1B
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

[Robie Basak]

Please reconsider the Importance of this bug, as it makes the phone
unusable for it's basic function (reliably receiving calls).

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions

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

[Touch-packages] [Bug 1653506] [NEW] Not possible to connect to Ubuntu from remote device

[Konrad Zapałowicz]

Public bug reported:

The Ubuntu is not letting the remote device in in case when the remote
device is the initiator of the connection request. It drops connection
request on the L2CAP level with 'security block' error code.

The step-by-step example:

1. Ubuntu pairs & connects to remote device
2. Ubuntu disconnects
3. Remote device tries to reconnect

It is seen from the HCI trace that the root cause is the problem in
finding the agent that could carry the auth process on. In this case
however the agent has been registered previously.

The HCI trace:

> ACL Data RX: Handle 12 flags 0x02 dlen 12 
> 
> [hci0] 941.214394
  L2CAP: Connection Request (0x02) ident 38 len 4
PSM: 25 (0x0019)
Source CID: 65
< ACL Data TX: Handle 12 flags 0x00 dlen 16 
[hci0] 
941.214473
  L2CAP: Connection Response (0x03) ident 38 len 8
Destination CID: 64
Source CID: 65
Result: Connection pending (0x0001)
Status: Authorization pending (0x0002)
= bluetoothd: Authentication attempt without agent  
[hci0] 
941.214871
= bluetoothd: Access denied: org.bluez.Error.Rejected   
   
941.214921
< ACL Data TX: Handle 12 flags 0x00 dlen 16 
[hci0] 
941.214916
  L2CAP: Connection Response (0x03) ident 38 len 8
Destination CID: 64
Source CID: 65
Result: Connection refused - security block (0x0003)
Status: No further information available (0x)

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Assignee: Konrad Zapałowicz (kzapalowicz)
 Status: New


** Tags: bluez

** Description changed:

  The Ubuntu is not letting the remote device in in case when the remote
- device is the initiator if the connection request. It drops connection
+ device is the initiator of the connection request. It drops connection
  request on the L2CAP level with 'security block' error code.
  
  The step-by-step example:
  
  1. Ubuntu pairs & connects to remote device
  2. Ubuntu disconnects
  3. Remote device tries to reconnect
  
  It is seen from the HCI trace that the root cause is the problem in
  finding the agent that could carry the auth process on. In this case
  however the agent has been registered previously.
  
  The HCI trace:
  
  > ACL Data RX: Handle 12 flags 0x02 dlen 12   
  
[hci0] 941.214394
-   L2CAP: Connection Request (0x02) ident 38 len 4
- PSM: 25 (0x0019)
- Source CID: 65
+   L2CAP: Connection Request (0x02) ident 38 len 4
+ PSM: 25 (0x0019)
+ Source CID: 65
  < ACL Data TX: Handle 12 flags 0x00 dlen 16   
  
[hci0] 941.214473
-   L2CAP: Connection Response (0x03) ident 38 len 8
- Destination CID: 64
- Source CID: 65
- Result: Connection pending (0x0001)
- Status: Authorization pending (0x0002)
+   L2CAP: Connection Response (0x03) ident 38 len 8
+ Destination CID: 64
+ Source CID: 65
+ Result: Connection pending (0x0001)
+ Status: Authorization pending (0x0002)
  = bluetoothd: Authentication attempt without agent
  
[hci0] 941.214871
  = bluetoothd: Access denied: org.bluez.Error.Rejected 

 941.214921
  < ACL Data TX: Handle 12 flags 0x00 dlen 16   
  
[hci0] 941.214916
-   L2CAP: Connection Response (0x03) ident 38 len 8
- Destination CID: 64
- Source CID: 65
- Result: Connection refused - security block (0x0003)
- Status: No further information available (0x)
+   L2CAP: Connection Response (0x03) ident 38 len 8
+ Destination CID: 64
+ Source CID: 65
+ Result: Connection refused - security block (0x0003)
+ Status: No further information available (0x)

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

Title:
  Not possible to connect to Ubuntu from remote device

Status in bluez package in 

[Touch-packages] [Bug 1652505] Re: Cannot connect to pulseaudio

[GDR!]

Here's a log of pulseaudio -

** Attachment added: "dead-pulseaudio.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1652505/+attachment/4799032/+files/dead-pulseaudio.txt

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

Title:
  Cannot connect to pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  What I expect to happen: audio working like in Ubuntu 14.04

  What is happening: programs cannot connect to pulseaudio server, the
  server itself isn't crashing. For example, pavuctl hangs on
  "connecting to pulseaudio", and all media applications are doing the
  same. It sometimes happens that one application (which opened
  connection to PA earlier) is still playing but new ones can't connect.

  pulseaudio -k && pulseaudio

  fixes this issue temporarly, until the next time it happens. The
  problem occurs multiple times per session.

  This is happening on 2 systems, one is not my own - a clean xubuntu
  16.04 install - and the other is my own, where I tried various tweaks
  to default.pa to fix the problem. None worked. This happens with a
  clean default.pa too. I also tried installing oem-audio-hda-daily-lts-
  xenial-dkms and that did not help either.

  The errors reported in pulseaudio stderr are as following:
  E: [alsa-sink-ALC892 Analog] alsa-sink.c: ALSA woke us up to write new data 
to the device, but there was actually nothing to write.
  E: [alsa-sink-ALC892 Analog] alsa-sink.c: Most likely this is a bug in the 
ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
  E: [alsa-sink-ALC892 Analog] alsa-sink.c: We were woken up with POLLOUT set 
-- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

   AUDIO STOPS WORKING BELOW THIS LINE, LONG TIME AFTER THE PREVIOUS
  LINE IS PRINTED 

  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  E: [pulseaudio] shm.c: shm_open() failed: No such file or directory
  ^CE: [pulseaudio] shm.c:  shm_unlink(/pulse-shm-3403108683) failed: No such 
file or directory
  E: [pulseaudio] shm.c:  shm_unlink(/pulse-shm-1445609972) failed: No such 
file or directory

  
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:8.0-0ubuntu3.1
Candidate: 1:8.0-0ubuntu3.1
Version table:
   *** 1:8.0-0ubuntu3.1 500
  500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.0-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ➜  ~ lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  ➜  ~ lsmod | grep snd
  snd_usb_audio 176128  0
  snd_usbmidi_lib36864  1 snd_usb_audio
  snd_hda_codec_hdmi 53248  1
  snd_hda_codec_realtek86016  1
  snd_hda_codec_generic77824  1 snd_hda_codec_realtek
  snd_hda_intel  40960  6
  snd_hda_codec 135168  4 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
  snd_hda_core   73728  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
  snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
  snd_pcm   106496  6 
snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
  snd_seq_midi   16384  0
  snd_seq_midi_event 16384  1 snd_seq_midi
  snd_rawmidi32768  2 snd_usbmidi_lib,snd_seq_midi
  snd_seq69632  2 snd_seq_midi_event,snd_seq_midi
  snd_seq_device 16384  3 snd_seq,snd_rawmidi,snd_seq_midi
  snd_timer  32768  3 snd_pcm,snd_seq
  snd81920  23 
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
  soundcore  16384  1 snd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  

[Touch-packages] [Bug 1466479] Re: "Searching for available drivers..." gives no indication of progress

[Stuart Gillies]

There is another aspect to this minor but irritating bug. Whilst
additional drivers are being searched for, the panel displays the
message "No additional drivers are in use". This should not be displayed
as at this point the software does not know if this is true or not.

Not mission critical, but it undermines the professionalism of Ubuntu.

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

Title:
  "Searching for available drivers..." gives no indication of progress

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  software-properties 0.92.37.3, Ubuntu 14.04

  1. Open System Settings > "Software & Updates".
  2. Choose "Additional Drivers".
  3. Wait 30 seconds.

  What you see:
  2. The text "Searching for available drivers..." centered in the box, but no 
other hint of progress.
  3. A list of drivers.

  What you should see:
  2. A progress bar, if the driver search has determinate progress; otherwise a 
spinner.

  : “The
  ‘Additional Drivers’ tab should begin with a listbox containing a
  progress bar and the text ‘Searching for available drivers…’ until the
  search is complete.”

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

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

[Touch-packages] [Bug 1642929] Re: no screen output prior to login while in docking station

[kringalf]

Can be closed. I had to reinstall and the problem doesn't exist any more

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

Title:
  no screen output prior to login while in docking station

Status in xorg package in Ubuntu:
  New

Bug description:
  while the laptop is in the docking station there is no output on any monitor 
as long as i'm not logged into kde.
  The output stops right after the password for the encrypted root disk and the 
screens stay blank until i login to kde
  if i start outside the docking station i get output on the screen through the 
whole boot process including the login process for kde

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Nov 18 12:16:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535]
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0JC5MT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Nov 14 11:57:52 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 812 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

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

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

[Touch-packages] [Bug 1653495] Re: systemd-resolved breaks Steam

[Bas Zoetekouw]

** Attachment added: "packet capture when using resolved"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+attachment/4799004/+files/dns-resolved.pcap

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

Title:
  systemd-resolved breaks Steam

Status in systemd package in Ubuntu:
  New

Bug description:
  When systemd-resolved is active and /etc/resolv.conf points to
  127.0.0.53, steam fails to resolve domain names, and refuses to update
  or install games.  Often, it doesn't even start, because it wants to
  update itself, but cannot reach its content servers.

  Manually (dig/host/nslookup/etc), resolving works fine, and also
  Chrome etc do'nt show any problems.  It seems Steam uses some uncommon
  type of DNS records or so?

  If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
  local resolver, everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  2 11:04:03 2017
  InstallationDate: Installed on 2016-12-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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

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

[Touch-packages] [Bug 1653495] Re: systemd-resolved breaks Steam

[Bas Zoetekouw]

I'm attaching DNS logs of a steam session using systemd-resolved, and of
one using Google directly.

** Attachment added: "dns packet capture without resoled"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653495/+attachment/4799003/+files/dns-google.pcap

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

Title:
  systemd-resolved breaks Steam

Status in systemd package in Ubuntu:
  New

Bug description:
  When systemd-resolved is active and /etc/resolv.conf points to
  127.0.0.53, steam fails to resolve domain names, and refuses to update
  or install games.  Often, it doesn't even start, because it wants to
  update itself, but cannot reach its content servers.

  Manually (dig/host/nslookup/etc), resolving works fine, and also
  Chrome etc do'nt show any problems.  It seems Steam uses some uncommon
  type of DNS records or so?

  If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
  local resolver, everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  2 11:04:03 2017
  InstallationDate: Installed on 2016-12-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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

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

[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely

[Timo Jyrinki]

Can you test the ticket? It would be ready for xenial (overlay) and
zesty.

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

Title:
  Mir-backed InputDeviceModel’s count property is not updated timely

Status in qtsystems-opensource-src package in Ubuntu:
  In Progress

Bug description:
  I’m trying to use InputDeviceModel from QML with the following
  example:

  import QtQuick 2.4
  import QtSystemInfo 5.5
  Item {
InputDeviceModel {
  id: idm
  filter: InputInfo.Mouse
  onCountChanged: console.log("mice model count:", devices, count)
  onAdded: console.log("added mouse:", inputDevice, count)
  onRemoved: console.log("removed mouse:", deviceId, count)
}
readonly property bool hasMouse: idm.count > 0
onHasMouseChanged: console.log("has mouse:", hasMouse)
  }

  When I launch the example with qmlscene on my arale with no mouse
  connected, I’m not seeing any output (expected).

  Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following:
mice model count: 1 0
added mouse: QInputDevice(0x17f6298) 1
(note how 'hasMouse', which supposedly was initially false, hasn’t been 
updated)

  Then I disconnect the combo, and I’m seeing the following:
mice model count: 0 1
has mouse: true
removed mouse: 15 0

  Then I connect it again, and I’m seeing the following:
mice model count: 1 0
has mouse: false
added mouse: QInputDevice(0x18ee508) 1

  It appears the countChanged property is emitted before a device is
  added to/removed from the model, and thus the row count hasn’t
  actually been updated yet. So any property binding that relies on
  'count' will have an incorrect value.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+subscriptions

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

[Touch-packages] [Bug 1653495] [NEW] systemd-resolved breaks Steam

[Bas Zoetekouw]

Public bug reported:

When systemd-resolved is active and /etc/resolv.conf points to
127.0.0.53, steam fails to resolve domain names, and refuses to update
or install games.  Often, it doesn't even start, because it wants to
update itself, but cannot reach its content servers.

Manually (dig/host/nslookup/etc), resolving works fine, and also Chrome
etc do'nt show any problems.  It seems Steam uses some uncommon type of
DNS records or so?

If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
local resolver, everything works fine again.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-8
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jan  2 11:04:03 2017
InstallationDate: Installed on 2016-12-22 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. Latitude E7470
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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


** Tags: amd64 apport-bug package-from-proposed 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/1653495

Title:
  systemd-resolved breaks Steam

Status in systemd package in Ubuntu:
  New

Bug description:
  When systemd-resolved is active and /etc/resolv.conf points to
  127.0.0.53, steam fails to resolve domain names, and refuses to update
  or install games.  Often, it doesn't even start, because it wants to
  update itself, but cannot reach its content servers.

  Manually (dig/host/nslookup/etc), resolving works fine, and also
  Chrome etc do'nt show any problems.  It seems Steam uses some uncommon
  type of DNS records or so?

  If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
  local resolver, everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  2 11:04:03 2017
  InstallationDate: Installed on 2016-12-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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

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

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

[bugproxy]

--- Comment From sthou...@in.ibm.com 2017-01-02 03:57 EDT---
Screening the issue.

the wiki instructions are missing one package:

linux-image-extra-4.8.0-32-generic

Without it, you won't have the ipr module, so the boot will fail if your
root device is ipr based.

Can you try installing linux-image-extra to the package list for
installing the 4.8 kernel?

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

Title:
  [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu
  16.04.1 is dropping to (initramfs)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)
   
  Contact Information = pavsu...@in.ibm.com 
   
  ---uname output---
  Linux (none) 4.8.0-27-generic #29~16.04.1-Ubuntu SMP Fri Nov 4 17:24:37 UTC 
2016 ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@powerkvm3-lp1:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 RAID bus controller: IBM Obsidian-E PCI-E SCSI controller (rev 
01)
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
  0001:03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0001:03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0001:03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0001:03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0001:05:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0004:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
  0004:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:02:10.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:02:11.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0005:09:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0005:09:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0005:09:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0005:0f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0005:0f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
  0040:00:00.0 PCI bridge: IBM Device 03dc
  0044:00:00.0 PCI bridge: IBM Device 03dc
  0044:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
  0044:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
  0044:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
  0044:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
  0044:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
  0044:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
  0045:00:00.0 PCI bridge: IBM Device 03dc
  0045:01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0045:01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0045:01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
  0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01) 

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
 

[Touch-packages] [Bug 1653489] [NEW] [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)

[bugproxy]

Public bug reported:

---Problem Description---
Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)
 
Contact Information = pavsu...@in.ibm.com 
 
---uname output---
Linux (none) 4.8.0-27-generic #29~16.04.1-Ubuntu SMP Fri Nov 4 17:24:37 UTC 
2016 ppc64le GNU/Linux
 
---Additional Hardware Info---
root@powerkvm3-lp1:~# lspci
:00:00.0 PCI bridge: IBM Device 03dc
:01:00.0 RAID bus controller: IBM Obsidian-E PCI-E SCSI controller (rev 01)
0001:00:00.0 PCI bridge: IBM Device 03dc
0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
0001:05:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
0004:00:00.0 PCI bridge: IBM Device 03dc
0004:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
0004:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
0005:00:00.0 PCI bridge: IBM Device 03dc
0005:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:10.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:11.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)
0005:09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:0f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
0005:0f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
0040:00:00.0 PCI bridge: IBM Device 03dc
0044:00:00.0 PCI bridge: IBM Device 03dc
0044:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
0044:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
0045:00:00.0 PCI bridge: IBM Device 03dc
0045:01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01) 

 
Machine Type = P8 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Install Ubuntu 16.04.1 OS using netboot images. 
Then upgrade the kernel by Installing the kernel 4.8 on the same.
After upgrading the kernel, we are booting to the new 4.8 kernel installed and 
the booting drops to (initramfs) prompt.


 Petitboot (v1.2.6-a96e9ae)8284-22A 100E5CA
 ??
Ubuntu 16.04.1 LTS (16.04) (on /dev/sdd2)
Ubuntu, with Linux 4.4.0-57-generic (recovery mode)
Ubuntu, with Linux 4.4.0-57-generic
Ubuntu, with Linux 4.8.0-27-generic (recovery mode)
Ubuntu, with Linux 4.8.0-27-generic
 *  Ubuntu
  [Disk: sdg2 / cbe9647e-7e2c-4fa9-a6ea-482961f5a5a9]
Red Hat Enterprise Linux Server (0-rescue-1b320bf4f31b40dd8241cdc5f9bfa51c)
Red Hat Enterprise Linux Server 

[Touch-packages] [Bug 1653489] [NEW] [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)
 
Contact Information = pavsu...@in.ibm.com 
 
---uname output---
Linux (none) 4.8.0-27-generic #29~16.04.1-Ubuntu SMP Fri Nov 4 17:24:37 UTC 
2016 ppc64le GNU/Linux
 
---Additional Hardware Info---
root@powerkvm3-lp1:~# lspci
:00:00.0 PCI bridge: IBM Device 03dc
:01:00.0 RAID bus controller: IBM Obsidian-E PCI-E SCSI controller (rev 01)
0001:00:00.0 PCI bridge: IBM Device 03dc
0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ca)
0001:03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
0001:05:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01)
0004:00:00.0 PCI bridge: IBM Device 03dc
0004:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
0004:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre 
Channel Host Adapter (rev 10)
0005:00:00.0 PCI bridge: IBM Device 03dc
0005:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:10.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:02:11.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca)
0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)
0005:09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:09:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0005:0f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
0005:0f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter (rev 03)
0040:00:00.0 PCI bridge: IBM Device 03dc
0044:00:00.0 PCI bridge: IBM Device 03dc
0044:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) 
(rev 10)
0044:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
0044:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator 
(Lancer) (rev 10)
0045:00:00.0 PCI bridge: IBM Device 03dc
0045:01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01)
0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 
Gigabit Ethernet PCIe (rev 01) 

 
Machine Type = P8 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Install Ubuntu 16.04.1 OS using netboot images. 
Then upgrade the kernel by Installing the kernel 4.8 on the same.
After upgrading the kernel, we are booting to the new 4.8 kernel installed and 
the booting drops to (initramfs) prompt.


 Petitboot (v1.2.6-a96e9ae)8284-22A 100E5CA
 ??
Ubuntu 16.04.1 LTS (16.04) (on /dev/sdd2)
Ubuntu, with Linux 4.4.0-57-generic (recovery mode)
Ubuntu, with Linux 4.4.0-57-generic
Ubuntu, with Linux 4.8.0-27-generic (recovery mode)
Ubuntu, with Linux 4.8.0-27-generic
 *  Ubuntu
  [Disk: sdg2 / cbe9647e-7e2c-4fa9-a6ea-482961f5a5a9]
Red Hat Enterprise Linux Server (0-rescue-1b320bf4f31b40dd8241cdc5f9bfa51c)
Red Hat Enterprise Linux Server 

[Touch-packages] [Bug 1522675] Re: Needless scary warning: Can't drop privileges for downloading : _apt user not allowed

[dino99]

** Summary changed:

- Can't drop privileges for downloading : _apt user not allowed
+ Needless scary warning: Can't drop privileges for downloading : _apt user not 
allowed

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

Title:
  Needless scary warning: Can't drop privileges for downloading : _apt
  user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Fix Committed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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