[Touch-packages] [Bug 1667898] [NEW] Failed to start Zeitgeist activity log service on Ubuntu 17.04

2017-02-24 Thread corrado venturini
em-lo[2901]: g_action_print_detailed_name: 
assertion 'g_action_name_is_valid (action_name)' failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: g_action_print_detailed_name: 
assertion 'g_action_name_is_valid (action_name)' failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: g_action_print_detailed_name: 
assertion 'g_action_name_is_valid (action_name)' failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: g_action_print_detailed_name: 
assertion 'g_action_name_is_valid (action_name)' failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: Allocating size to 
GtkScrolledWindow 0x22f8470 without calling 
gtk_widget_get_preferred_width/height(). How does the code know the size to 
allocate?
Feb 23 10:20:47 corrado-z4 unity-panel-ser[2588]: window_menu_model_new: 
assertion 'BAMF_IS_APPLICATION(app)' failed
Feb 23 10:20:47 corrado-z4 unity-panel-ser[2588]: track_menus: assertion 
'IS_WINDOW_MENU(menus)' failed
Feb 23 10:20:55 corrado-z4 dbus-daemon[2048]: Activating service 
name='org.gnome.GConf'
Feb 23 10:20:55 corrado-z4 dbus-daemon[2048]: Successfully activated service 
'org.gnome.GConf'
Feb 23 10:20:57 corrado-z4 unity-panel-ser[2588]: Already have a menu for 
window ID 46137369 with path /com/canonical/menu/2C00019 from :1.90, 
unregistering that one
Feb 23 10:21:00 corrado-z4 systemd-resolved[1304]: Switching to DNS server 
62.101.93.101 for interface enp2s0.
Feb 23 10:21:03 corrado-z4 systemd-resolved[1304]: Switching to DNS server 
83.103.25.250 for interface enp2s0.
Feb 23 10:21:13 corrado-z4 compiz[2569]: ERROR 2017-02-23 10:21:13 unity 
:0 log.vala:103: Unable to connect to Zeitgeist: Error calling 
StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was reached
Feb 23 10:21:35 corrado-z4 dbus-daemon[2048]: Failed to activate service 
'org.gnome.zeitgeist.Engine': timed out
Feb 23 10:29:53 corrado-z4 dbus[1021]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Feb 23 10:29:53 corrado-z4 systemd[1]: Starting Hostname Service...

corrado@corrado-z4:~$ apt-cache policy zeitgeist*
zeitgeist-datahub:
  Installed: 0.9.16-0.2ubuntu1
  Candidate: 0.9.16-0.2ubuntu1
  Version table:
 *** 0.9.16-0.2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status
zeitgeist-core:
  Installed: 0.9.16-0.2ubuntu1
  Candidate: 0.9.16-0.2ubuntu1
  Version table:
 *** 0.9.16-0.2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status
zeitgeist-explorer:
  Installed: (none)
  Candidate: 0.2-1.1
  Version table:
 0.2-1.1 500
500 http://archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu zesty/universe i386 Packages
zeitgeist:
  Installed: (none)
  Candidate: 0.9.16-0.2ubuntu1
  Version table:
 0.9.16-0.2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu zesty/universe i386 Packages
zeitgeist-extension-fts:
  Installed: (none)
  Candidate: (none)
  Version table:
corrado@corrado-z4:~$ 

I still have the problem with my last install from the last daily Ubuntu 17.04 
"Zesty Zapus" - Alpha amd64 (20170224)
so i think it's time to open a bug.

I attach some doc, let my know if You need more
thanks

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

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

Title:
  Failed to start Zeitgeist activity log service on Ubuntu 17.04

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  I just installed Ubuntu 17.04 from last daily Ubuntu 17.04 "Zesty Zapus" - 
Alpha amd64 (20170222) 
  corrado@corrado-z4:~$ uname -a
  Linux corrado-z4 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:47:35 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z4:~$ 
  corrado@corrado-z4:~$ inxi -Fx
  System:Host: corrado-z4 Kernel: 4.10.0-9-generic x86_64 (64 bit gcc: 
6.3.0)
 Desktop: Gnome  (Gtk 3.22.7-1ubuntu4) Distro: Ubuntu Zesty Zapus 
(development branch)
  Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: 
American Megatrends v: F3 date: 04/24/2013
  CPU:   Dual core Intel Core i3-

[Touch-packages] [Bug 1667898] Re: Failed to start Zeitgeist activity log service on Ubuntu 17.04

2017-02-24 Thread corrado venturini
gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: 
gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' 
failed
  Feb 23 10:20:43 corrado-z4 gnome-system-lo[2901]: Allocating size to 
GtkScrolledWindow 0x22f8470 without calling 
gtk_widget_get_preferred_width/height(). How does the code know the size to 
allocate?
  Feb 23 10:20:47 corrado-z4 unity-panel-ser[2588]: window_menu_model_new: 
assertion 'BAMF_IS_APPLICATION(app)' failed
  Feb 23 10:20:47 corrado-z4 unity-panel-ser[2588]: track_menus: assertion 
'IS_WINDOW_MENU(menus)' failed
  Feb 23 10:20:55 corrado-z4 dbus-daemon[2048]: Activating service 
name='org.gnome.GConf'
  Feb 23 10:20:55 corrado-z4 dbus-daemon[2048]: Successfully activated service 
'org.gnome.GConf'
  Feb 23 10:20:57 corrado-z4 unity-panel-ser[2588]: Already have a menu for 
window ID 46137369 with path /com/canonical/menu/2C00019 from :1.90, 
unregistering that one
  Feb 23 10:21:00 corrado-z4 systemd-resolved[1304]: Switching to DNS server 
62.101.93.101 for interface enp2s0.
  Feb 23 10:21:03 corrado-z4 systemd-resolved[1304]: Switching to DNS server 
83.103.25.250 for interface enp2s0.
  Feb 23 10:21:13 corrado-z4 compiz[2569]: ERROR 2017-02-23 10:21:13 unity 
:0 log.vala:103: Unable to connect to Zeitgeist: Error calling 
StartServiceByName for org.gnome.zeitgeist.Engine: Timeout was reached
  Feb 23 10:21:35 corrado-z4 dbus-daemon[2048]: Failed to activate service 
'org.gnome.zeitgeist.Engine': timed out
  Feb 23 10:29:53 corrado-z4 dbus[1021]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Feb 23 10:29:53 corrado-z4 systemd[1]: Starting Hostname Service...

  corrado@corrado-z4:~$ apt-cache policy zeitgeist*
  zeitgeist-datahub:
Installed: 0.9.16-0.2ubuntu1
Candidate: 0.9.16-0.2ubuntu1
Version table:
   *** 0.9.16-0.2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  zeitgeist-core:
Installed: 0.9.16-0.2ubuntu1
Candidate: 0.9.16-0.2ubuntu1
Version table:
   *** 0.9.16-0.2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  zeitgeist-explorer:
Installed: (none)
Candidate: 0.2-1.1
Version table:
   0.2-1.1 500
  500 http://archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  zeitgeist:
Installed: (none)
Candidate: 0.9.16-0.2ubuntu1
Version table:
   0.9.16-0.2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  zeitgeist-extension-fts:
Installed: (none)
Candidate: (none)
Version table:
  corrado@corrado-z4:~$ 

  I still have the problem with my last install from the last daily Ubuntu 
17.04 "Zesty Zapus" - Alpha amd64 (20170224)
  so i think it's time to open a bug.

  I attach some doc, let my know if You need more
  thanks

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

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


[Touch-packages] [Bug 1608604] Re: Epson L210 multifunctional printer, scanner is not working.

2017-02-24 Thread Aravind Gopal
ReInstalled latest XUbuntu (16.04.2) with latest Epson drivers. Result
is the same. Could not scan. see screenshot photo . Where to file a bug
like this. is it a mystery?

** Attachment added: "Failure and double standards in detection and use of 
hardware"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1608604/+attachment/4826400/+files/Screenshot_2017-02-25_12-31-05.png

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

Title:
  Epson L210 multifunctional printer, scanner is not working.

Status in lsb package in Ubuntu:
  Invalid

Bug description:
  Installed lsb package and installed epson's drivers. Not working.
  Printer setting identifies printer correctly(EPSON-L210-Series). but
  in Simple scan, an error"unable to connect to scanner" arise. when
  tried to change scanner there the scanner name is given as
  "Epson(unknown model)". It seems that there is something wrong with
  hardware detection/identification and/or communication gap between
  printer and scanner modules.

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

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


[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

2017-02-24 Thread Aravind Gopal
ReInstalled latest XUbuntu (16.04.2) with latest Epson drivers. Result
is the same. Could not scan.  see screenshot photo .  Where to file a
bug like this. is it a mystery?

** Attachment added: "Failure /double standars in the hardware detection and 
use"
   
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1536353/+attachment/4826399/+files/Screenshot_2017-02-25_12-31-05.png

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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


[Touch-packages] [Bug 1665914] Re: Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus

2017-02-24 Thread Shelby Jueden
Applying those updates fixed it for me as well! Thank you!

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

Title:
  Ubuntu 16.04 freezes on Thinkpad X61 Tablet when touched by the stylus

Status in xorg package in Ubuntu:
  New

Bug description:
  I have (up to date) Ubuntu 16.04 on IBM Thinkpad X61 Tablet. I can use
  the stylus to move the cursor – but when I touch the screen with it
  (i.e. click), the system immediately freezes.

  When I touch it without X, in the text mode (Ctrl+Alt+F1) it does not
  freeze.

  I tried to debug it over network, but the network also freezes at the
  same moment.

  When I try QubesOS (with kernel 4.1.13-9.pvops.qubes.x86_64) on the
  same machine, the stylus works correctly and the system does not
  freeze.

  Any tips how to debug it? Maybe using the serial port (I have the
  docking station with RS232). Or I can try some older releases and find
  the last one that was working if it helps.

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

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


[Touch-packages] [Bug 647835] Re: Add option to wait for /var/lib/dpkg/lock to become free

2017-02-24 Thread Brian G. Shacklett
This type of situation can have a significant impact on scripted
configuration. The situation first and foremost on my mind is adding
packages via either UserData or Cfn-Init inside of the AWS EC2 service.
Additionally, Packer and Vagrant using the Shell provisioner would be
affected, and I'm sure there are many other cases, as well. My point is
that this has the potential to affect far more than just a one-time
single user interaction, but it would actually make it easier to remove
some kludgey workarounds that may be necessary to overcome dpkg locks in
an enterprise environment.

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

Title:
  Add option to wait for /var/lib/dpkg/lock to become free

Status in aptitude:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  New

Bug description:
  Binary package hint: apt

  Today I was waiting for texlive-full to install when I discovered that
  I would also need texmaker. Also, I plan to add apt-get full-upgrade
  to my nightly crontab, but I don't want it to fail if I happen to be
  manually installing a package at the same time.

  For both of the above situations, it would be useful to have a
  command-line flag that wouldd make apt-get wait for /var/lib/dpkg/lock
  to become free, rather than giving up immediately. I suggest -w and
  --wait, since they're not being used for anything.

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

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


[Touch-packages] [Bug 1667407] Re: improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug

2017-02-24 Thread Bug Watch Updater
** Changed in: coreutils (Debian)
   Status: Unknown => Fix Released

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

Title:
   improve 2x-3x sha256sum performance on ppc64le due to current gcc
  optimization bug

Status in coreutils package in Ubuntu:
  New
Status in coreutils package in Debian:
  Fix Released

Bug description:
  Dear Maintainer,

  The sha256sum provided by coreutils (without openssl) is performing
  poorly with gcc versions >= 4.9 until 7.0 (currently under development).
  The reason for that is the -fschedule-insns optimization that is used
  with -O2. By simply deactivating it, there is a performance improvement
  of 2 to 3 times.

  I'm using Ubuntu 16.10 and the coreutils package version
  8.25-2ubuntu2.

  Please check the following closed debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

  Be aware of the following conditions that are required:
  * If ppc64le
  * If gcc being used is >= 4.9 and < 7.0

  Notes:
  1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
  2) clang is not affected by this bug (verified on v3.8 and v3.9).
  3) strangely the sha512 is not affected by this.

  Below a demonstration of how it performs on my POWER8 machine:

  ===
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m18.670s
  user0m16.566s
  sys 0m0.745s

  $ # now with the following patch: ## Check Michael Stone's patch for an 
improved version.
  $ diff Makefile.in ../Makefile.in
  8989c8989
  < @am__fastdepCC_TRUE@  $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ 
$< &&\
  ---
  > @am__fastdepCC_TRUE@  $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo 
"-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\
  $ cp ../Makefile.in Makefile.in
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m5.903s
  user0m5.560s
  sys 0m0.255s

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

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


[Touch-packages] [Bug 1667881] [NEW] hdmi

2017-02-24 Thread clayton emanuel rodrigues
Public bug reported:

o sistema não reconhece a tyv, através da entrada/saída HDMI

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Feb 25 01:16:38 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed
 i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0487]
InstallationDate: Installed on 2017-02-21 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gateway NV55C
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=beab8c72-b619-44a3-a386-7c39ccfb2730 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2011
dmi.bios.vendor: Gateway
dmi.bios.version: V1.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NV55C
dmi.board.vendor: Gateway
dmi.board.version: V1.27
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V1.27
dmi.modalias: 
dmi:bvnGateway:bvrV1.27:bd11/09/2011:svnGateway:pnNV55C:pvrV1.27:rvnGateway:rnNV55C:rvrV1.27:cvnGateway:ct10:cvrV1.27:
dmi.product.name: NV55C
dmi.product.version: V1.27
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75+git1702140630.f6499b~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1702241930.983348~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1702241930.983348~gd~x
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.8.99+git1702221933.244d4b~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1702161933.860c36~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git1701262001.1516d3~gd~x
xserver.bootTime: Sat Feb 25 01:05:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 732 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1667881

Title:
  hdmi

Status in xorg package in Ubuntu:
  New

Bug description:
  o sistema não reconhece a tyv, através da entrada/saída HDMI

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb 25 01:16:38 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-64-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:0487]
  InstallationDate: Installed on 2017-02-21 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NV55C
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=beab8c72-b619-44a3-a386-7c39ccfb2730 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2011
  

[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

2017-02-24 Thread Bug Watch Updater
** Changed in: libnotify (Debian)
   Status: Unknown => New

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

Title:
  notify-send(1) can't replace an existing notification

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

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

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

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


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

2017-02-24 Thread Apport retracing service
*** This bug is a duplicate of bug 1664131 ***
https://bugs.launchpad.net/bugs/1664131

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1664131, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1664131
   package console-setup 1.108ubuntu15.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

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

Status in console-setup package in Ubuntu:
  New

Bug description:
  Upon boot, a message came up saying system problem detected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 07:42:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-02-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: console-setup
  Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667868] [NEW] package console-setup 1.108ubuntu15.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-02-24 Thread Thilina
*** This bug is a duplicate of bug 1664131 ***
https://bugs.launchpad.net/bugs/1664131

Public bug reported:

Upon boot, a message came up saying system problem detected.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: console-setup 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat Feb 25 07:42:58 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-02-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: console-setup
Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

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

Status in console-setup package in Ubuntu:
  New

Bug description:
  Upon boot, a message came up saying system problem detected.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sat Feb 25 07:42:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-02-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: console-setup
  Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

2017-02-24 Thread Carl Suster
** Bug watch added: Debian Bug tracker #559544
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544

** Also affects: libnotify (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559544
   Importance: Unknown
   Status: Unknown

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

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  Confirmed
Status in libnotify package in Debian:
  Unknown

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

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

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


[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

2017-02-24 Thread Anatoli
I second this. Please backport the fix to 16.04.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Confirmed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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


[Touch-packages] [Bug 1665893] Re: DNS resolution of VPN hosts stopped working

2017-02-24 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1667825 ***
https://bugs.launchpad.net/bugs/1667825

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

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

Title:
  DNS resolution of VPN hosts stopped working

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  I have been using 17.04 for a few weeks now, but a recent update seems
  to have broken DNS resolution for VPN hosts. The local network is
  192.168.50.*, with DNS at 192.168.50.2. The remote network is
  192.168.0.*, with DNS at 192.168.0.2. I can ping remote hosts, but I
  can't resolve their names, although syslog says the following:

  systemd-resolved[2865]: Switching to DNS server 192.168.0.2 for
  interface tun0.

  The remote DNS domain is ozone.caligrafix.cl. Here is what does and
  doesn't work, using a valid remote host name (cali00):

  dig cali00: fails
  dig cali00.ozone.caligrafix.cl: fails
  dig cali00 @192.168.0.2: works
  dig cali00.ozone.caligrafix.cl @192.168.0.2: works

  Here is the complete log of VPN connection setup:

  Feb 18 11:56:34 tadzim3 NetworkManager[2242]:   [1487429794.9928] 
audit: op="connection-activate" uuid="ae3693ea-df59-414e-95a8-bf280a65b8db" 
name="cali-fw" pid=4439 uid=1000 result="success"
  Feb 18 11:56:34 tadzim3 NetworkManager[2242]:   [1487429794.9976] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 Started the VPN service, PID 7173
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.0048] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 Saw the service appear; activating connection
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.1165] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN plugin: state changed: starting (3)
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.1170] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN connection: (ConnectInteractive) reply received
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: OpenVPN 2.4.0 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 
10 2017
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: library versions: OpenSSL 1.0.2g  1 
Mar 2016, LZO 2.08
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]186.103.161.74:25402
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link local: (not bound)
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link remote: 
[AF_INET]186.103.161.74:25402
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: chroot will be delayed 
because of --client, --pull, or --up-delay
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
  Feb 18 11:56:36 tadzim3 nm-openvpn[7180]: [cali-fw-vpn] Peer Connection 
Initiated with [AF_INET]186.103.161.74:25402
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: TUN/TAP device tun0 opened
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: 
/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 7173 
--bus-name org.freedesktop.NetworkManager.openvpn.Connection_6 --tun -- tun0 
1500 1558 10.8.1.2 255.255.255.0 init
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1267] 
manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/7)
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1368] 
devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1368] 
device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown 
configuration found.
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1443] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN connection: (IP Config Get) reply received.
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1463] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",8:(tun0)]:
 VPN connection: (IP4 Config Get) reply received
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: chroot to '/var/lib/openvpn/chroot' 
and cd to '/' succeeded
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: GID set to nm-openvpn
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: UID set to nm-openvpn
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: Initialization Sequence Completed
  Feb 18 11:56:37 tadzim3 

[Touch-packages] [Bug 1667825] Re: Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices

2017-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Requesting Cherry Pick: dns/resolved: consider configuration from
  unmanaged devices

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Please forgive me if this is not the proper channel to request a
  cherry-pick. I'm currently experiencing this issue on Ubuntu 17.04
  using the network-manager-l2tp plugin.

  The Network Manager team recently patched an issue that breaks DNS
  resolution for certain VPN connections due to the PPP/TUN interface
  being unmanaged.

  The patch that corrects this is
  913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa.

  For more information, please see the upstream bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=779087

  Please let me know if I need to submit additional information or if
  this is the incorrect channel to request this.

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

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


[Touch-packages] [Bug 1665893] Re: DNS resolution of VPN hosts stopped working

2017-02-24 Thread Daniel Ramos
*** This bug is a duplicate of bug 1667825 ***
https://bugs.launchpad.net/bugs/1667825

** This bug has been marked a duplicate of bug 1667825
   Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged 
devices

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

Title:
  DNS resolution of VPN hosts stopped working

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  I have been using 17.04 for a few weeks now, but a recent update seems
  to have broken DNS resolution for VPN hosts. The local network is
  192.168.50.*, with DNS at 192.168.50.2. The remote network is
  192.168.0.*, with DNS at 192.168.0.2. I can ping remote hosts, but I
  can't resolve their names, although syslog says the following:

  systemd-resolved[2865]: Switching to DNS server 192.168.0.2 for
  interface tun0.

  The remote DNS domain is ozone.caligrafix.cl. Here is what does and
  doesn't work, using a valid remote host name (cali00):

  dig cali00: fails
  dig cali00.ozone.caligrafix.cl: fails
  dig cali00 @192.168.0.2: works
  dig cali00.ozone.caligrafix.cl @192.168.0.2: works

  Here is the complete log of VPN connection setup:

  Feb 18 11:56:34 tadzim3 NetworkManager[2242]:   [1487429794.9928] 
audit: op="connection-activate" uuid="ae3693ea-df59-414e-95a8-bf280a65b8db" 
name="cali-fw" pid=4439 uid=1000 result="success"
  Feb 18 11:56:34 tadzim3 NetworkManager[2242]:   [1487429794.9976] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 Started the VPN service, PID 7173
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.0048] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 Saw the service appear; activating connection
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.1165] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN plugin: state changed: starting (3)
  Feb 18 11:56:35 tadzim3 NetworkManager[2242]:   [1487429795.1170] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN connection: (ConnectInteractive) reply received
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: OpenVPN 2.4.0 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 
10 2017
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: library versions: OpenSSL 1.0.2g  1 
Mar 2016, LZO 2.08
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]186.103.161.74:25402
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link local: (not bound)
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link remote: 
[AF_INET]186.103.161.74:25402
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: chroot will be delayed 
because of --client, --pull, or --up-delay
  Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
  Feb 18 11:56:36 tadzim3 nm-openvpn[7180]: [cali-fw-vpn] Peer Connection 
Initiated with [AF_INET]186.103.161.74:25402
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: TUN/TAP device tun0 opened
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: 
/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 7173 
--bus-name org.freedesktop.NetworkManager.openvpn.Connection_6 --tun -- tun0 
1500 1558 10.8.1.2 255.255.255.0 init
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1267] 
manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/7)
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1368] 
devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1368] 
device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown 
configuration found.
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1443] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]:
 VPN connection: (IP Config Get) reply received.
  Feb 18 11:56:37 tadzim3 NetworkManager[2242]:   [1487429797.1463] 
vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",8:(tun0)]:
 VPN connection: (IP4 Config Get) reply received
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: chroot to '/var/lib/openvpn/chroot' 
and cd to '/' succeeded
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: GID set to nm-openvpn
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: UID set to nm-openvpn
  Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: Initialization Sequence Completed
  Feb 18 11:56:37 tadzim3 

[Touch-packages] [Bug 1667854] Re: sshd sengault with filezilla login

2017-02-24 Thread laulau
here is an extract of syslog :

Feb 25 00:33:08 SRV kernel: [2441764.971951] sshd[17792]: segfault at 0 ip 
7f232037af02 sp 7ffeec69d8f8 error 4 in 
libc-2.19.so[7f23202ef000+1ba000]
Feb 25 00:33:17 SRV kernel: [2441773.789867] sshd[17796]: segfault at 0 ip 
7f3282284f02 sp 7ffd1e729d28 error 4 in 
libc-2.19.so[7f32821f9000+1ba000]
Feb 25 00:33:24 SRV kernel: [2441780.543528] sshd[17803]: segfault at 0 ip 
7fc6eee2ef02 sp 7ffeb8968d38 error 4 in 
libc-2.19.so[7fc6eeda3000+1ba000]
Feb 25 00:33:31 SRV kernel: [2441787.292209] sshd[17896]: segfault at 0 ip 
7f6b498f6f02 sp 7ffd4c34c848 error 4 in 
libc-2.19.so[7f6b4986b000+1ba000]
Feb 25 00:33:37 SRV kernel: [2441794.246183] sshd[17901]: segfault at 0 ip 
7efc0e7aaf02 sp 7fff96b176b8 error 4 in 
libc-2.19.so[7efc0e71f000+1ba000]

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

Title:
  sshd sengault with filezilla login

Status in openssh package in Ubuntu:
  New

Bug description:
  with recent versions of filezilla / openssh, it's impossible to login
  to ssh server.

  informations :
  protocole : sftp
  port : 22
  authentification : login + password

  os : ubuntu server 14.04 amd64
  openssh : 1:6.6p1-2ubuntu2.8
  filezilla : 3.24 (windows) and 3.21 (ubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-server 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Sat Feb 25 00:57:51 2017
  InstallationDate: Installed on 2013-08-16 (1288 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1667856] [NEW] error deamon tool runit

2017-02-24 Thread Monika Wiosna
Public bug reported:

deamon tools - it is something that is always stopping every installation. 
kind of statement - error deamon tool runit

sometimes software center does not work and computer have to be reseted
at leat 1 time per hour

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Feb 25 01:03:01 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3903]
InstallationDate: Installed on 2017-02-07 (17 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO INVALID
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: A3CN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Flex 2-14
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Flex 2-14
dmi.modalias: 
dmi:bvnLENOVO:bvrA3CN29WW:bd06/27/2014:svnLENOVO:pnINVALID:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoFlex2-14:
dmi.product.name: INVALID
dmi.product.version: Lenovo Flex 2-14
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160714-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.3-1ubuntu2.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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Feb 25 00:58:25 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5264 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.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/1667856

Title:
  error deamon tool runit

Status in xorg package in Ubuntu:
  New

Bug description:
  deamon tools - it is something that is always stopping every installation. 
  kind of statement - error deamon tool runit

  sometimes software center does not work and computer have to be
  reseted at leat 1 time per hour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb 25 01:03:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3903]
  InstallationDate: Installed on 2017-02-07 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO INVALID
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Touch-packages] [Bug 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-24 Thread Seth Arnold
That's an excellent question. In general we can't solve all cases but
perhaps we can find a middle-ground.

In the past, the 'r' flag on the executable determined if the process
was dumpable. I expect that to still hold, but there may be other
reasons why 'r' is required these days.

I don't know how widespread it would be for someone to put 'm' on a
binary but not 'r' so that it couldn't be dumpable. That feels unlikely.
Maybe we could automatically give 'mr' permissions to the files listed
in the attachment specification?

Thanks

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

Title:
  Confined binaries running in namespaces unable to read their
  executable

Status in apparmor package in Ubuntu:
  New

Bug description:
  It seems that binaries confined by Apparmor attempt to read their own
  executable when running in a namespace/container. This breaks many
  profiles that are working perfectly well outside of namespaces.


  
  Original description:

  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
     http://www.rsyslog.com/doc/
    Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.

  I don't know why rsyslog wants to read its own binary but it seems to
  really want to.

  Both the host and the guest are up to date Xenials. Please not that
  the host runs the kernel from -proposed.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
    Installed: 4.4.0-65.86
    Candidate: 4.4.0-65.86
    Version table:
   *** 4.4.0-65.86 100
  100 /var/lib/dpkg/status
  apparmor:
    Installed: 2.10.95-0ubuntu2.5
    Candidate: 2.10.95-0ubuntu2.5
    Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667854] [NEW] sshd sengault with filezilla login

2017-02-24 Thread laulau
Public bug reported:

with recent versions of filezilla / openssh, it's impossible to login to
ssh server.

informations :
protocole : sftp
port : 22
authentification : login + password

os : ubuntu server 14.04 amd64
openssh : 1:6.6p1-2ubuntu2.8
filezilla : 3.24 (windows) and 3.21 (ubuntu)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: openssh-server 1:6.6p1-2ubuntu2.8
ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
Uname: Linux 3.13.0-107-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Sat Feb 25 00:57:51 2017
InstallationDate: Installed on 2013-08-16 (1288 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  sshd sengault with filezilla login

Status in openssh package in Ubuntu:
  New

Bug description:
  with recent versions of filezilla / openssh, it's impossible to login
  to ssh server.

  informations :
  protocole : sftp
  port : 22
  authentification : login + password

  os : ubuntu server 14.04 amd64
  openssh : 1:6.6p1-2ubuntu2.8
  filezilla : 3.24 (windows) and 3.21 (ubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-server 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 3.13.0-107.154-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-107-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Sat Feb 25 00:57:51 2017
  InstallationDate: Installed on 2013-08-16 (1288 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1643737] Re: Network Manager doesn't use 802.1x password entered in GUI

2017-02-24 Thread StuS
Also, re-reading this revealed the bug has slightly changed:

Note this time around, the password seems to re-appear in the GUI after
being entered - however, it's not stored in the conf file, and I'm
promoted to enter it upon reboot, so it's now:

  - storing it somewhere (maybe somewhere preferrable to a globally readable 
file!)
  - and then not using it upon reboot.


After entering it in the conf file, it started working again, upon reboot.

Note that this version has been updated to:

root@stuart:/etc/pam.d# apt list network-manager
Listing... Done
network-manager/xenial-updates,now 1.2.2-0ubuntu0.16.04.3 amd64 
[installed,automatic]


So it's getting better, but not there yet.

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

Title:
  Network Manager doesn't use 802.1x password entered in GUI

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This is a bug that seems to constantly re-surface across multiple
  versions in Ubuntu, and I've seen it in other distributions as well.

  Scenario:
I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I 
enter my identity, my computer cert, my ca cert, my private key file, and my 
password for my private key. 

  What doesn't work:
  I confirm the password works by using openssl. NetworkManager does not save 
the password. When I am asked to re-enter it, the connection fails. I look in 
syslog, and it complains about the private key password being blank.

  Workaround:
  Open the file:

  /etc/NetworkManager/system-connections/[Your network connection]
  Example:
  $> vim /etc/NetworkManager/system-connections/Wired\ connection\ 1

  Add the field:
  private-key-password=[your password]

  Example:
  private-key-password=UtterlyPointlessGloballyReadableStoredInPlaintextPassword

  Save the file.

  Attempt to re-connect. (and it worked for me).
  Look in Network Manager UI, the password seems to now be stored.

  Expected behavior:
  Entering the password in the GUI works (i.e, it is saved to the file, or at 
least used temporarily when connecting, either way - the latter would be more 
secure)

  Additionally, this whole thing is pretty lame, because Network Manager
  restricts you to using an encrypted private key, but this is dumb,
  because the password is then stored in a globally readable file in
  plaintext. Or you can decide to not save a password, and enter every
  time in a gui that fails to use the password you type in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 17:52:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 10.0.50.1 dev eno1  proto static  metric 100 
   10.0.50.0/23 dev eno1  proto kernel  scope link  src 10.0.50.207  metric 100 
   10.0.254.32 via 10.0.50.1 dev eno1  proto dhcp  metric 100 
   169.254.0.0/16 dev eno1  scope link  metric 1000
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  802-3-ethernet  
1479779500  Mon 21 Nov 2016 05:51:40 PM PST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  

[Touch-packages] [Bug 1643737] Re: Network Manager doesn't use 802.1x password entered in GUI

2017-02-24 Thread StuS
Finally got around to filing upstream:

https://bugzilla.gnome.org/show_bug.cgi?id=779201

(as part of my periodic TLS cert renewal, I had to look up this bug to
reference my workaround - it might be nice if their was some clear
documentation in man NetworkManager.conf on the "private-key-password"
config key)

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

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

Title:
  Network Manager doesn't use 802.1x password entered in GUI

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This is a bug that seems to constantly re-surface across multiple
  versions in Ubuntu, and I've seen it in other distributions as well.

  Scenario:
I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I 
enter my identity, my computer cert, my ca cert, my private key file, and my 
password for my private key. 

  What doesn't work:
  I confirm the password works by using openssl. NetworkManager does not save 
the password. When I am asked to re-enter it, the connection fails. I look in 
syslog, and it complains about the private key password being blank.

  Workaround:
  Open the file:

  /etc/NetworkManager/system-connections/[Your network connection]
  Example:
  $> vim /etc/NetworkManager/system-connections/Wired\ connection\ 1

  Add the field:
  private-key-password=[your password]

  Example:
  private-key-password=UtterlyPointlessGloballyReadableStoredInPlaintextPassword

  Save the file.

  Attempt to re-connect. (and it worked for me).
  Look in Network Manager UI, the password seems to now be stored.

  Expected behavior:
  Entering the password in the GUI works (i.e, it is saved to the file, or at 
least used temporarily when connecting, either way - the latter would be more 
secure)

  Additionally, this whole thing is pretty lame, because Network Manager
  restricts you to using an encrypted private key, but this is dumb,
  because the password is then stored in a globally readable file in
  plaintext. Or you can decide to not save a password, and enter every
  time in a gui that fails to use the password you type in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 21 17:52:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 10.0.50.1 dev eno1  proto static  metric 100 
   10.0.50.0/23 dev eno1  proto kernel  scope link  src 10.0.50.207  metric 100 
   10.0.254.32 via 10.0.50.1 dev eno1  proto dhcp  metric 100 
   169.254.0.0/16 dev eno1  scope link  metric 1000
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  802-3-ethernet  
1479779500  Mon 21 Nov 2016 05:51:40 PM PST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  fcbffec0-f9e4-4405-acfa-1cd80dec7362  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 111507] Re: VPN passwords not saved

2017-02-24 Thread Gangadhar
** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Gangadhar (gangadhar)

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

Title:
  VPN passwords not saved

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: network-manager

  Ubuntu 7.04 (PPC)
  XFCE
  vpnc

  Network manager does not save the VPNC passwords properly (when the
  button is checked) so the passwords (user and group secret) must be
  re-entered every time network-manager decides to randomly terminate my
  wireless connection, which it does frequently.

  Perhaps this is a problem of network-manager not talking to gnome-
  keyring properly, or XFCE being unable to access the keyring?

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

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


[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-02-24 Thread Till Kamppeter
Note that this bug is only a problem of the package installation
process. So it is fixed (or not reproducible) if you install the
proposed package and the installation does not error. There is no
difference between before and after on the system's behavior.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1666277] Re: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-02-24 Thread Brian Murray
*** This bug is a duplicate of bug 1487208 ***
https://bugs.launchpad.net/bugs/1487208

** This bug has been marked a duplicate of bug 1487208
   package sudo 1.8.9p5-1ubuntu5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1

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

Title:
  package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  pops out after system start

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40
  Uname: Linux 4.4.0-62-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Feb 19 22:45:27 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-01-21 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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


[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-02-24 Thread Arcan Andrei
Just made an account to post here. The fact that this bug is known for
ALMOST a year irritates me the most, I can't enjoy ubuntu or any linux
distribution in my E200HA.

On-topic: Some guy announced on other forum that they work at this bug
but it's not prioritized and it will be fixed in kernel 4.12, not
before, that's sad. I can't find the link to the forum anymore, I think
they deleted it..

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

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

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

2017-02-24 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu1

---
unattended-upgrades (0.93.1ubuntu1) zesty; urgency=medium

  [ Brian Murray ]
  * When performing a sanity check for packages to install or upgrade return
false when either there are no packages in the cache or the package to
upgrade is not in the change set. (LP: #1654070)
  * Do not mark packages for deletion / autoremoval if unattended-upgrades is
being run in dry-run mode. (LP: #1544942)

  [ Louis Bouchard ]
  * Store delay command line option as an int not a string since we do maths
with it.

 -- Brian Murray   Fri, 06 Jan 2017 13:00:24 -0800

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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


[Touch-packages] [Bug 1654070] Re: sanity check can fail for packages missing dependencies

2017-02-24 Thread Launchpad Bug Tracker
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu1

---
unattended-upgrades (0.93.1ubuntu1) zesty; urgency=medium

  [ Brian Murray ]
  * When performing a sanity check for packages to install or upgrade return
false when either there are no packages in the cache or the package to
upgrade is not in the change set. (LP: #1654070)
  * Do not mark packages for deletion / autoremoval if unattended-upgrades is
being run in dry-run mode. (LP: #1544942)

  [ Louis Bouchard ]
  * Store delay command line option as an int not a string since we do maths
with it.

 -- Brian Murray   Fri, 06 Jan 2017 13:00:24 -0800

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  sanity check can fail for packages missing dependencies

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I've been getting mail for days about pulseaudio-module-gconf and
  -module-zeroconf being upgraded, come to find out its not really
  happening.

  bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose
  Initial blacklisted packages: nvidia-304
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 
'o=Ubuntu,a=xenial-updates']
  Checking: pulseaudio-module-gconf ([])
  Checking: pulseaudio-module-zeroconf ([])
  pkgs that look like they should be upgraded: pulseaudio-module-gconf
  pulseaudio-module-zeroconf
  Fetched 0 B in 0s (0 B/s) 


  fetch.run() result: 0
  blacklist: ['nvidia-304']
  whitelist: []
  Checking the black and whitelist: pulseaudio-module-gconf
  Checking the black and whitelist: pulseaudio-module-zeroconf
  Packages that will be upgraded: pulseaudio-module-gconf 
pulseaudio-module-zeroconf
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  All upgrades installed
  InstCount=0 DelCount=0 BrokenCount=0
  Extracting content from 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 
12:27:12'
  Sending mail to 'bdmurray@bizarro.watchtower.local'
  mail returned: 0
  bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf
  pulseaudio-module-gconf:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3.1
Version table:
   1:8.0-0ubuntu3.1 500
  500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
   *** 1:8.0-0ubuntu3 500
  500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-24 Thread Simon Déziel
On 2017-02-24 04:04 PM, Seth Arnold wrote:
> I'm surprised that the denials you're seeing now
> weren't generated earlier, due to this change.

Well, I just got the word that Apparmor was now working in containers
after waiting for years so I happily jumped in.

I guess the question is: is there a way to let Apparmor magically let a
binary reads itself? Or do we need to update every single profile to
account for that change?

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

Title:
  Confined binaries running in namespaces unable to read their
  executable

Status in apparmor package in Ubuntu:
  New

Bug description:
  It seems that binaries confined by Apparmor attempt to read their own
  executable when running in a namespace/container. This breaks many
  profiles that are working perfectly well outside of namespaces.


  
  Original description:

  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
     http://www.rsyslog.com/doc/
    Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.

  I don't know why rsyslog wants to read its own binary but it seems to
  really want to.

  Both the host and the guest are up to date Xenials. Please not that
  the host runs the kernel from -proposed.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
    Installed: 4.4.0-65.86
    Candidate: 4.4.0-65.86
    Version table:
   *** 4.4.0-65.86 100
  100 /var/lib/dpkg/status
  apparmor:
    Installed: 2.10.95-0ubuntu2.5
    Candidate: 2.10.95-0ubuntu2.5
    Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-02-24 Thread ais523
Just to clarify why this bug has so many me-too votes: the bug happened
once to me, during an update, and never happened again (i.e. it fixed
itself, and I can print just fine, etc.). I subscribed to this thread
because I was curious as to what was going on, and I did see the problem
myself once but the bug doesn't have any ongoing effect on me and I
can't reproduce it.

I suspect that the majority of the people who have confirmed the bug are
in the same boat, whereas some people here have the issue recurring for
some reason. (It's unclear why; either there's something relevantly
different about their configuration, or this is actually two different
bugs with the same symptoms.) So although there are a lot of people
here, I suspect rather fewer people are in a position to test the fix; I
can't reproduce the bug, and thus there's no point in me testing the
fix, as a working fix would look the same as a fix that had no effect at
all.

Would it be reasonable for people in my position to retract our
confirmations of the bug, if we can no longer reproduce? Or is it best
to leave the confirmation there, because I definitely did see the bug
happen, once?

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1667825] [NEW] Requesting Cherry Pick: dns/resolved: consider configuration from unmanaged devices

2017-02-24 Thread Daniel Ramos
Public bug reported:

Please forgive me if this is not the proper channel to request a cherry-
pick. I'm currently experiencing this issue on Ubuntu 17.04 using the
network-manager-l2tp plugin.

The Network Manager team recently patched an issue that breaks DNS
resolution for certain VPN connections due to the PPP/TUN interface
being unmanaged.

The patch that corrects this is
913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa.

For more information, please see the upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=779087

Please let me know if I need to submit additional information or if this
is the incorrect channel to request this.

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


** Tags: patch-accepted-upstream

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

Title:
  Requesting Cherry Pick: dns/resolved: consider configuration from
  unmanaged devices

Status in network-manager package in Ubuntu:
  New

Bug description:
  Please forgive me if this is not the proper channel to request a
  cherry-pick. I'm currently experiencing this issue on Ubuntu 17.04
  using the network-manager-l2tp plugin.

  The Network Manager team recently patched an issue that breaks DNS
  resolution for certain VPN connections due to the PPP/TUN interface
  being unmanaged.

  The patch that corrects this is
  913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa.

  For more information, please see the upstream bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=779087

  Please let me know if I need to submit additional information or if
  this is the incorrect channel to request this.

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

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


[Touch-packages] [Bug 1667802] Re: [ANNOUNCE] wayland 1.13.0

2017-02-24 Thread Hans Joachim Desserud
** Tags added: upgrade-software-version

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

Title:
  [ANNOUNCE] wayland 1.13.0

Status in wayland package in Ubuntu:
  New

Bug description:
  https://lists.freedesktop.org/archives/wayland-
  devel/2017-February/033193.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libwayland-server0 1.12.0-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Feb 24 17:43:40 2017
  Dependencies:
   gcc-6-base 6.3.0-2ubuntu1
   libc6 2.24-7ubuntu2
   libffi6 3.2.1-6
   libgcc1 1:6.3.0-2ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0d7]
  InstallationDate: Installed on 2015-07-26 (579 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
  xserver.bootTime: Thu Mar 10 13:48:25 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.3-2ubuntu4

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

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


[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-02-24 Thread Till Kamppeter
And we are on 419 me-too votes now! So who ever has voted now, please
try the proposed fix! Thanks.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-02-24 Thread Till Kamppeter
This bug report got 418 (!) me-too votes and has tons of duplicates and
no one wants to verify the proposed fix? Please, come up, install the
proposed package and see whether it installs smoothly without hick-up
and give us your feedback here. You will help a lot of people if your
feedback makes the fix getting an official update.

Thank you very much.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1667821] [NEW] load target breaks make

2017-02-24 Thread J.J. Green
Public bug reported:

With the following Makefile:

--

load : hello

hello :
echo "all is well"

--

the commands "make", "make hello", "make load" result in error with
message

  Makefile:1: :: cannot open shared object file: No such file or directory
  Makefile:1: *** :: failed to load. Stop.

this minimal example extracted from a Makefile with a load target which has
been used weekly for 10+ years. 

$ make --version
GNU Make 4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2014 Free Software Foundation, Inc.
Licence GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$ lsb_release -rd
Description:Linux Mint 18.1 Serena
Release:18.1

$ apt-cache policy make
make:
  Installed: 4.1-6
  Candidate: 4.1-6
  Version table:
 *** 4.1-6 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: make-dfsg (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  load target breaks make

Status in make-dfsg package in Ubuntu:
  New

Bug description:
  With the following Makefile:

  --

  load : hello

  hello :
echo "all is well"

  --

  the commands "make", "make hello", "make load" result in error with
  message

Makefile:1: :: cannot open shared object file: No such file or directory
Makefile:1: *** :: failed to load. Stop.

  this minimal example extracted from a Makefile with a load target which has
  been used weekly for 10+ years. 

  $ make --version
  GNU Make 4.1
  Built for x86_64-pc-linux-gnu
  Copyright (C) 1988-2014 Free Software Foundation, Inc.
  Licence GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $ lsb_release -rd
  Description:  Linux Mint 18.1 Serena
  Release:  18.1

  $ apt-cache policy make
  make:
Installed: 4.1-6
Candidate: 4.1-6
Version table:
   *** 4.1-6 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1667821/+subscriptions

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


[Touch-packages] [Bug 1667807] Re: The third 1.10 bug-fix release (1.10.4) was released on 23 February 2017

2017-02-24 Thread Hans Joachim Desserud
** Tags added: upgrade-software-version

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

Title:
  The third 1.10 bug-fix release (1.10.4) was released on 23 February
  2017

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  https://gstreamer.freedesktop.org/releases/1.10/#1.10.4

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.3-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 24 17:50:00 2017
  InstallationDate: Installed on 2015-07-26 (579 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1664426] Re: Can no longer play wma files with Ubuntu 16.04

2017-02-24 Thread Charles Mikesell
Thanks for fixing. Ran update today on all units and am very pleased to
be playing wma files again!!!

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

Title:
  Can no longer play wma files with Ubuntu 16.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Multiple (7) computers were working just fine until a recent update
  apparently removed the plug-in.

  Perhaps you could provide us with an update to put the plug-in back in
  place.(?)

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

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


[Touch-packages] [Bug 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-24 Thread Seth Arnold
Thanks Simon,

https://github.com/torvalds/linux/commit/9f834ec18defc369d73ccf9e87a2790bfa05bf46
changed how ELF executables are loaded by the kernel and required many
changes to profiles. I'm surprised that the denials you're seeing now
weren't generated earlier, due to this change.

Thanks

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

Title:
  Confined binaries running in namespaces unable to read their
  executable

Status in apparmor package in Ubuntu:
  New

Bug description:
  It seems that binaries confined by Apparmor attempt to read their own
  executable when running in a namespace/container. This breaks many
  profiles that are working perfectly well outside of namespaces.


  
  Original description:

  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
     Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
     http://www.rsyslog.com/doc/
    Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.

  I don't know why rsyslog wants to read its own binary but it seems to
  really want to.

  Both the host and the guest are up to date Xenials. Please not that
  the host runs the kernel from -proposed.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
    Installed: 4.4.0-65.86
    Candidate: 4.4.0-65.86
    Version table:
   *** 4.4.0-65.86 100
  100 /var/lib/dpkg/status
  apparmor:
    Installed: 2.10.95-0ubuntu2.5
    Candidate: 2.10.95-0ubuntu2.5
    Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

2017-02-24 Thread Dimon2242
I have this problem too on 16.04.2.

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  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
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1667797] Re: Need manual control over apt update schedule

2017-02-24 Thread Julian Andres Klode
Add a systemd drop-in if you want to constraint times. Note that it
schedules a random time, not 6 and 18:00 (it is randomized by 12 hours).

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

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

Title:
  Need manual control over apt update schedule

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 16.04 (Xenial)

  My ISP is ViaSat Exede satellite service.  They have a monthly data
  cap but it doesn't apply during specific time periods.  With my
  specific service it is called "Late Night Free Zone" (LNFZ) and occurs
  between 12:00 and 05:00 in my time zone (it's relative to each
  subscriber's time zone).

  Currently apt-daily.timer schedules updates at 06:00 and 18:00 according to:
  /lib/systemd/system/apt-daily.timer

  This unnecessarily wastes MBs of my data cap retrieving updates that
  won't be installed outside of the LNFZ anyways.  I would also like to
  enable all automatic updates but only within the LNFZ.  But there
  doesn't seem to be a way to change the schedule without editing the
  file directly and using dpkg-divert to protect it from reverting
  during updates.

  There needs to be an easier way to change this, either in /etc/default
  or /etc/apt, and preferably via front-ends like software-properties-
  gtk.

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

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


[Touch-packages] [Bug 1667802] [NEW] [ANNOUNCE] wayland 1.13.0

2017-02-24 Thread Cristian Aravena Romero
Public bug reported:

https://lists.freedesktop.org/archives/wayland-
devel/2017-February/033193.html

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libwayland-server0 1.12.0-1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Feb 24 17:43:40 2017
Dependencies:
 gcc-6-base 6.3.0-2ubuntu1
 libc6 2.24-7ubuntu2
 libffi6 3.2.1-6
 libgcc1 1:6.3.0-2ubuntu1
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0d7]
InstallationDate: Installed on 2015-07-26 (579 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
xserver.bootTime: Thu Mar 10 13:48:25 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.3-2ubuntu4

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


** Tags: amd64 apport-bug single-occurrence ubuntu zesty

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

Title:
  [ANNOUNCE] wayland 1.13.0

Status in wayland package in Ubuntu:
  New

Bug description:
  https://lists.freedesktop.org/archives/wayland-
  devel/2017-February/033193.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libwayland-server0 1.12.0-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Feb 24 17:43:40 2017
  Dependencies:
   gcc-6-base 6.3.0-2ubuntu1
   libc6 2.24-7ubuntu2
   libffi6 3.2.1-6
   libgcc1 1:6.3.0-2ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0d7]
  InstallationDate: Installed on 2015-07-26 (579 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  

[Touch-packages] [Bug 1667807] [NEW] The third 1.10 bug-fix release (1.10.4) was released on 23 February 2017

2017-02-24 Thread Cristian Aravena Romero
Public bug reported:

https://gstreamer.freedesktop.org/releases/1.10/#1.10.4

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgstreamer1.0-0 1.10.3-1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb 24 17:50:00 2017
InstallationDate: Installed on 2015-07-26 (579 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  The third 1.10 bug-fix release (1.10.4) was released on 23 February
  2017

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  https://gstreamer.freedesktop.org/releases/1.10/#1.10.4

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.3-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 24 17:50:00 2017
  InstallationDate: Installed on 2015-07-26 (579 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-24 Thread Brian Murray
** Changed in: wget (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

Title:
  wget crashed with SIGSEGV in __memset_avx2()

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Xenial:
  In Progress

Bug description:
  EDIT(other user): The crash actually happens when the terminal window
  is too small.

  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.

  To reproduce the bug try the following:

  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso

  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.

  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  evan@HPPC:~$ apt-cache policy wget
  wget:
Installato: 1.17.1-1ubuntu1
Candidato:  1.17.1-1ubuntu1
Tabella versione:
   *** 1.17.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
   Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
   PC (0x7f4eac3b7328) ok
   source "%al" ok
   destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  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/ubuntu/+source/wget/+bug/1573307/+subscriptions

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


[Touch-packages] [Bug 1667801] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2017-02-24 Thread Apport retracing service
*** This bug is a duplicate of bug 1629638 ***
https://bugs.launchpad.net/bugs/1629638

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1629638, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826158/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826161/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826167/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826169/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826170/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826171/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1667801/+attachment/4826172/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1629638

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 24 20:34:18 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-02-24 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224)
  MachineType: Dell Inc. Inspiron N5010
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=05975345-0c7c-4a64-b82a-42c5c26c500c ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YXXJJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn0YXXJJ:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV

2017-02-24 Thread Mike Gresens
Same problem since upgrade to Ubuntu 17.04

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

Title:
  apport-gtk crashed with SIGSEGV

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-24 Thread Brian Murray
I'll upload this to the SRU queue, but it would be could if a test case
and other information were added to the bug description per
http://wiki.ubuntu.com/StableReleaseUpdates.

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

Title:
  wget crashed with SIGSEGV in __memset_avx2()

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Xenial:
  In Progress

Bug description:
  EDIT(other user): The crash actually happens when the terminal window
  is too small.

  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.

  To reproduce the bug try the following:

  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso

  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.

  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  evan@HPPC:~$ apt-cache policy wget
  wget:
Installato: 1.17.1-1ubuntu1
Candidato:  1.17.1-1ubuntu1
Tabella versione:
   *** 1.17.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
   Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
   PC (0x7f4eac3b7328) ok
   source "%al" ok
   destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  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/ubuntu/+source/wget/+bug/1573307/+subscriptions

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


[Touch-packages] [Bug 1667797] [NEW] Need manual control over apt update schedule

2017-02-24 Thread jhansonxi
Public bug reported:

Xubuntu 16.04 (Xenial)

My ISP is ViaSat Exede satellite service.  They have a monthly data cap
but it doesn't apply during specific time periods.  With my specific
service it is called "Late Night Free Zone" (LNFZ) and occurs between
12:00 and 05:00 in my time zone (it's relative to each subscriber's time
zone).

Currently apt-daily.timer schedules updates at 06:00 and 18:00 according to:
/lib/systemd/system/apt-daily.timer

This unnecessarily wastes MBs of my data cap retrieving updates that
won't be installed outside of the LNFZ anyways.  I would also like to
enable all automatic updates but only within the LNFZ.  But there
doesn't seem to be a way to change the schedule without editing the file
directly and using dpkg-divert to protect it from reverting during
updates.

There needs to be an easier way to change this, either in /etc/default
or /etc/apt, and preferably via front-ends like software-properties-gtk.

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

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

Title:
  Need manual control over apt update schedule

Status in apt package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04 (Xenial)

  My ISP is ViaSat Exede satellite service.  They have a monthly data
  cap but it doesn't apply during specific time periods.  With my
  specific service it is called "Late Night Free Zone" (LNFZ) and occurs
  between 12:00 and 05:00 in my time zone (it's relative to each
  subscriber's time zone).

  Currently apt-daily.timer schedules updates at 06:00 and 18:00 according to:
  /lib/systemd/system/apt-daily.timer

  This unnecessarily wastes MBs of my data cap retrieving updates that
  won't be installed outside of the LNFZ anyways.  I would also like to
  enable all automatic updates but only within the LNFZ.  But there
  doesn't seem to be a way to change the schedule without editing the
  file directly and using dpkg-divert to protect it from reverting
  during updates.

  There needs to be an easier way to change this, either in /etc/default
  or /etc/apt, and preferably via front-ends like software-properties-
  gtk.

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

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


[Touch-packages] [Bug 462760] Re: sprof fails to work with shared objects

2017-02-24 Thread Ray Satiro
I am also having this problem. I'm trying to profile libcurl in Ubuntu
16.04 LTS and I get this:

export LD_PROFILE_OUTPUT=`pwd`
export LD_PROFILE=libcurl.so.4
src/.libs/lt-curl google.com > /dev/null
sprof lib/.libs/libcurl.so.4 libcurl.so.4.profile -p >log

_dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state ==
RT_CONSISTENT' failed!

I compiled with -fno-omit-frame-pointer -g -pg in CFLAGS and CXXFLAGS

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

Title:
  sprof fails to work with shared objects

Status in eglibc package in Ubuntu:
  Confirmed
Status in eglibc package in Debian:
  New
Status in eglibc package in Fedora:
  Unknown

Bug description:
  Binary package hint: libc-dev-bin

  When I try to profile a compiled shared object, sprof always fails
  with: "Inconsistency detected by ld.so: dl-open.c: 672: _dl_open:
  Assertion `_dl_debug_initialize (0, args.nsid)->r_state ==
  RT_CONSISTENT' failed!"

  I have the environment variables LD_PROFILE and LD_PROFILE_OUTPUT set
  up as you would expect and a file.so.profile file is created along
  with gmon.out.

  Both the main program and .SO are compiled and linked with -pg

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

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


[Touch-packages] [Bug 1537125] Re: ubuntu-14.04.04: fail to run systemtap test suites

2017-02-24 Thread Michael Hohnbaum
** Changed in: systemtap (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => (unassigned)

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

Title:
  ubuntu-14.04.04: fail to run systemtap test suites

Status in elfutils package in Ubuntu:
  Fix Released
Status in systemtap package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  ubuntu-14.04.04: fail to run systemtap test suites
   
  ---uname output---
  Linux u140404 4.2.0-21-generic #25~14.04.1-Ubuntu SMP Thu Dec 3 13:55:42 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = power8 

  As per launchpad feature systemtap now supported and enabled on 14.04.04
  - https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1511347

  Here are the steps followed to test systemtap -
  1.  Get 14.04.04 guest VM

  2.  apt-get update; apt-get install dpkg-dev; apt-get build-dep
  systemtap

  3. setup repo
  codename=$(lsb_release -c | awk  '{print $2}')
  sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
  deb http://ddebs.ubuntu.com/ ${codename}  main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ ${codename}-security main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ ${codename}-updates  main restricted universe 
multiverse
  deb http://ddebs.ubuntu.com/ ${codename}-proposed main restricted universe 
multiverse
  EOF

  4. apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01
  5E0577F2

  5. apt-get update

  6.  devel packages
  apt-get install linux-image-`uname -r`-dbgsym 
  apt-get install linux-headers-4.2.0-24-generic

  7.  Install required dependencies 
- dejagnu, elfutils-*

  8. apt-get source systemtap

  9.  appy systemtap fixes 
  see BZ - https://bugzilla.linux.ibm.com/show_bug.cgi?id=131220

  root@u140404:~/patch# ll
  total 32
  drwxr-xr-x 2 root root 4096 Jan  7 03:36 ./
  drwx-- 8 root root 4096 Jan  7 03:55 ../
  -rw-r--r-- 1 root root 6763 Jan  7 03:36 systemtap-1
  -rw-r--r-- 1 root root 3094 Jan  7 03:35 systemtap-1511347.diff
  -rw-r--r-- 1 root root 3472 Jan  7 03:36 systemtap-2
  -rw-r--r-- 1 root root 5864 Jan  7 03:36 systemtap-3

  cd /root/systemtap-2.3
  apply above patch in below order
  patch -p1 < /root/patch/systemtap-1511347.diff
  patch -p1 < /root/patch/systemtap-1
  patch -p1 < /root/patch/systemtap-2
  patch -p1 < /root/patch/systemtap-3

  10. ./configure; make -j10; make install

  11.  make check  ---> failed
  root@u140404:~/systemtap-2.3# make check
  /bin/bash ./git_version.sh -k -s . -o git_version.h
  make  check-recursive
  make[1]: Entering directory `/root/systemtap-2.3'
  Making check in .
  make[2]: Entering directory `/root/systemtap-2.3'
CXX  stap-session.o
CXXLDstap
  make  check-local
  make[3]: Entering directory `/root/systemtap-2.3'
  SRCDIR=`cd .; pwd`; \
  PWD=`pwd`; \
make -C testsuite check SYSTEMTAP_RUNTIME=$SRCDIR/runtime 
SYSTEMTAP_TAPSET=$SRCDIR/tapset 
LD_LIBRARY_PATH=$LD_LIBRARY_PATH${LD_LIBRARY_PATH:+:}$PWD/lib-elfutils:$PWD/lib-elfutils/systemtap
 SYSTEMTAP_PATH=$PWD SYSTEMTAP_INCLUDES=$PWD/includes RUNTESTFLAGS="" 
PKGLIBDIR="/usr/local/libexec/systemtap";
  make[4]: Entering directory `/root/systemtap-2.3/testsuite'
  Run "make check" or "make installcheck".
  make  check-DEJAGNU check-local
  make[5]: Entering directory `/root/systemtap-2.3/testsuite'
  srcdir='.'; export srcdir; \
EXPECT=expect; export EXPECT; \
if /bin/bash -c ""env XDG_DATA_DIRS= SYSTEMTAP_SYNC=1 LANG=C 
SYSTEMTAP_TESTREMOTES= SYSTEMTAP_TESTAPPS= 
SYSTEMTAP_RUNTIME=/root/systemtap-2.3/runtime 
SYSTEMTAP_TAPSET=/root/systemtap-2.3/tapset 
LD_LIBRARY_PATH=/root/systemtap-2.3/lib-elfutils:/root/systemtap-2.3/lib-elfutils/systemtap
 CRASH_LIBDIR=/usr/local/lib/systemtap PATH=/root/systemtap-2.3:$PATH 
SYSTEMTAP_PATH=/root/systemtap-2.3 
SYSTEMTAP_INCLUDES=/root/systemtap-2.3/includes  
PKGLIBDIR=/usr/local/libexec/systemtap ./execrc runtest" --version" > /dev/null 
2>&1; then \
  exit_status=0; l='systemtap'; for tool in $l; do \
if "env XDG_DATA_DIRS= SYSTEMTAP_SYNC=1 LANG=C 
SYSTEMTAP_TESTREMOTES= SYSTEMTAP_TESTAPPS= 
SYSTEMTAP_RUNTIME=/root/systemtap-2.3/runtime 
SYSTEMTAP_TAPSET=/root/systemtap-2.3/tapset 
LD_LIBRARY_PATH=/root/systemtap-2.3/lib-elfutils:/root/systemtap-2.3/lib-elfutils/systemtap
 CRASH_LIBDIR=/usr/local/lib/systemtap PATH=/root/systemtap-2.3:$PATH 
SYSTEMTAP_PATH=/root/systemtap-2.3 
SYSTEMTAP_INCLUDES=/root/systemtap-2.3/includes  
PKGLIBDIR=/usr/local/libexec/systemtap ./execrc runtest"  --tool $tool 
--tool_opts \'\' --srcdir $srcdir ; \
then :; else exit_status=1; fi; \
  done; \
else echo "WARNING: could not find '"env XDG_DATA_DIRS= 
SYSTEMTAP_SYNC=1 LANG=C SYSTEMTAP_TESTREMOTES= SYSTEMTAP_TESTAPPS= 

[Touch-packages] [Bug 1667769] Re: apt-daily.service running too early in boot process

2017-02-24 Thread Julian Andres Klode
Unfortunately for us, systemd provides no good interface to improve
things. There's the ability to wait on network, but AFAIUI that does not
really help much, as it does not deal with resume. Also waiting on the
network could time out, and the service would then be marked as failed
and also run 12 hours later.

The best solution would be to have a service that runs while the machine
is online and that other units can bind to: Then you could bind the
timer (!) to the online-ness of the system.

That said, Wants=network-online.target and After=network-online.target
or similar are probably better than nothing.

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

** Changed in: apt (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  apt-daily.service running too early in boot process

Status in apt package in Ubuntu:
  Triaged

Bug description:
  System: ubuntu mate 16.04 with apt version 1.2.19


  Problem:

  On a desktop system I noticed that the package lists were being
  updated very infrequently. This is apparently because on most days the
  apt-daily.service is triggered early in the boot process when the
  network is not up. Since the timer is set to run approximately every
  12 hours, and the system is only on for a few days, the timer tends to
  lapse over night and is then triggered as soon as the system is booted
  the following day.

  Also, `apt-get update` returns true regardless of whether there is a
  network connection, so the apt.systemd.daily script reports success
  and updates the timestamp file regardless. This means that if the
  system is only used for a few hours per day the package list may not
  be updated for many days until the timer lapses while the system
  happens to be already switched on.


  System journal showing typical output during boot process:

  Feb 10 14:38:13 desktop systemd[1]: Starting Daily apt activities...
  Feb 10 14:38:13 desktop apt.systemd.daily[3679]: verbose level 3
  ...
  [truncated]
  ...
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: + apt-get -y update
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:1 
http://security.ubuntu.com/ubuntu xenial-security InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'security.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:2 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'ppa.launchpad.net'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:3 
http://gb.archive.ubuntu.com/ubuntu xenial InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:4 
http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:5 
http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: Reading package lists...
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Temporary fa
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temp
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Te
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Tempo
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu/dists/xenial/InR
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Some index files failed 
to download. They have been ignored, or old ones used instead.
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: + debug_echo download 
updated metadata (success).


  Work-around:

  I have worked around this by creating a file /etc/systemd/system/apt-
  daily.service.d/network.conf containing the following options:

  Wants=network-online.target
  After=network-online.target

  Maybe there is a better way to specify unit dependencies or to edit
  the timer so it will delay on startup, but this seems to fix the issue
  for me.


  Related bug:

  This other bug might be related, but it states that it causes apt-get to hang 
indefinitely, which I have not seen on my system.
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1636049

To manage 

[Touch-packages] [Bug 1666556] Re: [MIR] ubuntu-ui-extras

2017-02-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-ui-extras -
0.2+17.04.20170222-0ubuntu1

---
ubuntu-ui-extras (0.2+17.04.20170222-0ubuntu1) zesty; urgency=medium

  [ Andrew Hayzen ]
  * Add qml-module-qtqml-models2 as a depends, as it was missing
  * When the tab is being destroyed unset the source of the TabIcon
Loader
  * Add qtdeclarative5-dev-tools, qml-module-ubuntu-test and xvfb as
build-deps (LP: #1666556)

 -- Olivier Tilloy   Wed, 22 Feb 2017
10:52:03 +

** Changed in: ubuntu-ui-extras (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [MIR] ubuntu-ui-extras

Status in ubuntu-ui-extras package in Ubuntu:
  Fix Released

Bug description:
  Please consider ubuntu-ui-extras for inclusion in main.

  ubuntu-terminal-app and webbrowser-app now depend on ubuntu-ui-extras
  to provide certain UI components which are shared, they are in main so
  it is required for the ubuntu-ui-extras to also be in main.

  
  [Availability]
  http://launchpad.net/ubuntu-ui-extras - qtdeclarative5-ubuntu-ui-extras0.2 is 
already in universe 
(http://packages.ubuntu.com/search?keywords=qtdeclarative5-ubuntu-ui-extras0.2+=names=all=all)

  [Rationale]
  ubuntu-ui-extras is a new dependency of a package that we already support. 
  webbrowser-app and ubuntu-terminal-app want to use a common component which 
is in ubuntu-ui-extras.

  [Security]
  No CVE entries.
  No Secunia history.
  Written in QML and C++
  Does not open any port.

  [Quality assurance]
  Package provides components for other Qt apps to use.
  The components have been used extensively on ubuntu touch platforms.
  Does not deal with exotic hardware which we cannot support.

  [Dependencies]
  qml-module-qtquick2
  qml-module-ubuntu-components
  qml-module-qtquick-window2

  Which are all in main.

  [Standards compliance]
  Meets the FHS, Debian Policy
  Standard packaging

  [Maintenance]
  ubuntu-ui-extras is already in universe and is maintained by the Ubuntu 
Phablet Team

  [Background information] 
  Package has not been renamed recently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1666556/+subscriptions

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


[Touch-packages] [Bug 1667769] Re: apt-daily.service running too early in boot process

2017-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  apt-daily.service running too early in boot process

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  System: ubuntu mate 16.04 with apt version 1.2.19


  Problem:

  On a desktop system I noticed that the package lists were being
  updated very infrequently. This is apparently because on most days the
  apt-daily.service is triggered early in the boot process when the
  network is not up. Since the timer is set to run approximately every
  12 hours, and the system is only on for a few days, the timer tends to
  lapse over night and is then triggered as soon as the system is booted
  the following day.

  Also, `apt-get update` returns true regardless of whether there is a
  network connection, so the apt.systemd.daily script reports success
  and updates the timestamp file regardless. This means that if the
  system is only used for a few hours per day the package list may not
  be updated for many days until the timer lapses while the system
  happens to be already switched on.


  System journal showing typical output during boot process:

  Feb 10 14:38:13 desktop systemd[1]: Starting Daily apt activities...
  Feb 10 14:38:13 desktop apt.systemd.daily[3679]: verbose level 3
  ...
  [truncated]
  ...
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: + apt-get -y update
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:1 
http://security.ubuntu.com/ubuntu xenial-security InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'security.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:2 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'ppa.launchpad.net'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:3 
http://gb.archive.ubuntu.com/ubuntu xenial InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:4 
http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:5 
http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure 
resolving 'gb.archive.ubuntu.com'
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: Reading package lists...
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Temporary fa
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temp
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Te
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Tempo
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu/dists/xenial/InR
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Some index files failed 
to download. They have been ignored, or old ones used instead.
  Feb 10 14:38:17 desktop apt.systemd.daily[3679]: + debug_echo download 
updated metadata (success).


  Work-around:

  I have worked around this by creating a file /etc/systemd/system/apt-
  daily.service.d/network.conf containing the following options:

  Wants=network-online.target
  After=network-online.target

  Maybe there is a better way to specify unit dependencies or to edit
  the timer so it will delay on startup, but this seems to fix the issue
  for me.


  Related bug:

  This other bug might be related, but it states that it causes apt-get to hang 
indefinitely, which I have not seen on my system.
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1636049

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

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


[Touch-packages] [Bug 1636049] Re: apt-daily timer should run after networking is available

2017-02-24 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1667769 ***
https://bugs.launchpad.net/bugs/1667769

Marking as duplicate of bug #1667769, that one has more details.

** This bug has been marked a duplicate of bug 1667769
   apt-daily.service running too early in boot process

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

Title:
  apt-daily timer should run after networking is available

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  The apt-daily service should have a dependency to run after networking
  is available. On some startups, especially after the host has not been
  running for a while, the apt-daily timer triggers before the network-
  online target. This causes apt-get to hang forever, and it cannot be
  run again without killing the existing processes.

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

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


[Touch-packages] [Bug 1649959] Re: unattended upgrade of apt kills running apt-daily job

2017-02-24 Thread Julian Andres Klode
This has been released in zesty too, but seems we forgot to close it.
Doing so now.

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

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

Title:
  unattended upgrade of apt kills running apt-daily job

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Causes automatic upgrades by unattended-upgrades to be interrupted if apt is 
configured, leaving the system in a partially configured state.

  [Test case]
  Install apt - make sure the apt-daily.service is not restarted (this systemd 
service runs unattended-upgrades)

  [Regression Potential] 
  It's only overriding dh_systemd_start to not be called for the service, so I 
don't see any possibility for regressions.

  [Original Bug report]
  This morning, I discovered that my new xenial system had attempted an 
unattended upgrade overnight but the upgrade was incomplete. It attempted to 
upgrade
  apt apt-transport-https apt-utils firefox firefox-locale-en 
flashplugin-installer libapt-inst2.0 libapt-pkg5.0 libgme0

  but the unattended-upgrades-dpkg.log log terminates after apt is
  configured.

  I had to dpkg --configure --pending and apt-get -f install to get apt back 
into working order.
  There were no errors, crashes or cores logged.

  The journal indicates that apt-daily.service stopped and restarted around the 
time of the upgrade, so I am assuming that is the problem (that systemd killed 
the update session as the result of an update to the unit files)
  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-12-06 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: openafs
  Package: apt 1.3.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-24 Thread Simon Déziel
** Description changed:

+ It seems that binaries confined by Apparmor attempt to read their own
+ executable when running in a namespace/container. This breaks many
+ profiles that are working perfectly well outside of namespaces.
+ 
+ 
+ 
+ Original description:
+ 
  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even the
  kernel so please re-assign if needed.
  
  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:
  
  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536
  
  This prevents rsyslog from starting in the said container:
  
  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
-Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
-Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
-  Docs: man:rsyslogd(8)
-http://www.rsyslog.com/doc/
-   Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
-  Main PID: 232 (code=exited, status=127)
+    Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
+    Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
+  Docs: man:rsyslogd(8)
+    http://www.rsyslog.com/doc/
+   Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
+  Main PID: 232 (code=exited, status=127)
  
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  
+ I don't know why rsyslog wants to read its own binary but it seems to
+ really want to.
  
- I don't know why rsyslog wants to read its own binary but it seems to really 
want to.
- 
- 
- Both the host and the guest are up to date Xenials. Please not that the host 
runs the kernel from -proposed.
+ Both the host and the guest are up to date Xenials. Please not that the
+ host runs the kernel from -proposed.
  
  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
-   Installed: 4.4.0-65.86
-   Candidate: 4.4.0-65.86
-   Version table:
-  *** 4.4.0-65.86 100
- 100 /var/lib/dpkg/status
+   Installed: 4.4.0-65.86
+   Candidate: 4.4.0-65.86
+   Version table:
+  *** 4.4.0-65.86 100
+ 100 /var/lib/dpkg/status
  apparmor:
-   Installed: 2.10.95-0ubuntu2.5
-   Candidate: 2.10.95-0ubuntu2.5
-   Version table:
-  *** 2.10.95-0ubuntu2.5 500
- 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  2.10.95-0ubuntu2 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installed: 2.10.95-0ubuntu2.5
+   Candidate: 2.10.95-0ubuntu2.5
+   Version table:
+  *** 2.10.95-0ubuntu2.5 500
+ 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  2.10.95-0ubuntu2 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
-   Installed: 8.16.0-1ubuntu3
-   Candidate: 8.16.0-1ubuntu3
-   Version table:
-  *** 8.16.0-1ubuntu3 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 8.16.0-1ubuntu3
+   Candidate: 8.16.0-1ubuntu3
+   Version table:
+  *** 8.16.0-1ubuntu3 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 

[Touch-packages] [Bug 1667769] [NEW] apt-daily.service running too early in boot process

2017-02-24 Thread mapatma
Public bug reported:

System: ubuntu mate 16.04 with apt version 1.2.19


Problem:

On a desktop system I noticed that the package lists were being updated
very infrequently. This is apparently because on most days the apt-
daily.service is triggered early in the boot process when the network is
not up. Since the timer is set to run approximately every 12 hours, and
the system is only on for a few days, the timer tends to lapse over
night and is then triggered as soon as the system is booted the
following day.

Also, `apt-get update` returns true regardless of whether there is a
network connection, so the apt.systemd.daily script reports success and
updates the timestamp file regardless. This means that if the system is
only used for a few hours per day the package list may not be updated
for many days until the timer lapses while the system happens to be
already switched on.


System journal showing typical output during boot process:

Feb 10 14:38:13 desktop systemd[1]: Starting Daily apt activities...
Feb 10 14:38:13 desktop apt.systemd.daily[3679]: verbose level 3
...
[truncated]
...
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: + apt-get -y update
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:1 
http://security.ubuntu.com/ubuntu xenial-security InRelease
Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure resolving 
'security.ubuntu.com'
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:2 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure resolving 
'ppa.launchpad.net'
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:3 
http://gb.archive.ubuntu.com/ubuntu xenial InRelease
Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure resolving 
'gb.archive.ubuntu.com'
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:4 
http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease
Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure resolving 
'gb.archive.ubuntu.com'
Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:5 
http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease
Feb 10 14:38:14 desktop apt.systemd.daily[3679]:   Temporary failure resolving 
'gb.archive.ubuntu.com'
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: Reading package lists...
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Temporary fa
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temp
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://gb.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Te
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Tempo
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch 
http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu/dists/xenial/InR
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Some index files failed to 
download. They have been ignored, or old ones used instead.
Feb 10 14:38:17 desktop apt.systemd.daily[3679]: + debug_echo download updated 
metadata (success).


Work-around:

I have worked around this by creating a file /etc/systemd/system/apt-
daily.service.d/network.conf containing the following options:

Wants=network-online.target
After=network-online.target

Maybe there is a better way to specify unit dependencies or to edit the
timer so it will delay on startup, but this seems to fix the issue for
me.


Related bug:

This other bug might be related, but it states that it causes apt-get to hang 
indefinitely, which I have not seen on my system.
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1636049

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

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

Title:
  apt-daily.service running too early in boot process

Status in apt package in Ubuntu:
  New

Bug description:
  System: ubuntu mate 16.04 with apt version 1.2.19


  Problem:

  On a desktop system I noticed that the package lists were being
  updated very infrequently. This is apparently because on most days the
  apt-daily.service is triggered early in the boot process when the
  network is not up. Since the timer is set to run approximately every
  12 hours, and the system is only on for a few days, the timer tends to
  lapse over night and is then triggered as soon as the system is booted
  the following day.

  Also, `apt-get update` returns true regardless of whether there is a
  network connection, so the apt.systemd.daily script reports success
  and updates the timestamp file regardless. This means that if the
  system is only used for a few hours per day 

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

2017-02-24 Thread bugproxy
Upgrade to newest version available.

When filing version upgrade requests, could you please elaborate why you
want them? e.g. are there specific features and/or bug fixes you are
after? Rather than just an updated string in --version.

Also I guess you do not mean the on-the-fly auto-uncompressing C
library, but you mean zlib; will update meta data.

Guessing you are after:

- Add crc32_z() and adler32_z() functions with size_t lengths

Which was added in 1.2.9; which had regressions fixed eventually in
1.2.11.

This bug was fixed in the package zlib - 1:1.2.11.dfsg-0ubuntu1

---
zlib (1:1.2.11.dfsg-0ubuntu1) zesty; urgency=medium

* New upstream release. LP: #1664595
* Drop CVE patches, applied upstream.
* Add watch file, with GPG tarball checking, and version mangling.
* Add stanzas to debian/copyright file to automatically repackage
tarball into dfsg tarball.
* Add new symbols.

-- Dimitri John Ledkov   Thu, 16 Feb 2017 15:15:29
+

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

Title:
  [17.04 FEAT] Upgrade to newest version of zlib >=1.2.11

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released

Bug description:
  Upgrade to newest version available.

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

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


[Touch-packages] [Bug 1667751] Re: Confined binaries running in namespaces unable to read their executable

2017-02-24 Thread Simon Déziel
It doesn't seem to only affect rsyslog as I have for example a shell
script contained by an Apparmor profile and inside the container it
doesn't work as it wants to read /bin/dash:

audit: type=1400 audit(1487935787.212:153): apparmor="DENIED"
operation="file_mprotect" namespace="root//lxd-smb_"
profile="/usr/local/bin/backuppc-wrapper" name="/bin/dash" pid=29187
comm="backuppc-wrappe" requested_mask="r" denied_mask="r" fsuid=165570
ouid=165536

** Summary changed:

- rsyslog profile doesn't work in namespace
+ Confined binaries running in namespaces unable to read their executable

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

Title:
  Confined binaries running in namespaces unable to read their
  executable

Status in apparmor package in Ubuntu:
  New

Bug description:
  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed 
state.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
  Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
  Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.

  
  I don't know why rsyslog wants to read its own binary but it seems to really 
want to.

  
  Both the host and the guest are up to date Xenials. Please not that the host 
runs the kernel from -proposed.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
  linux-image-4.4.0-65-generic:
Installed: 4.4.0-65.86
Candidate: 4.4.0-65.86
Version table:
   *** 4.4.0-65.86 100
  100 /var/lib/dpkg/status
  apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  rsyslog:
Installed: 8.16.0-1ubuntu3
Candidate: 8.16.0-1ubuntu3
Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 12:17:34 2017
  InstallationDate: Installed on 2016-12-19 (66 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-02-24 Thread bugproxy
kernel 4.8: Add support for the additional scheduling layer within the
kernel and util-linux.

015cd867e566e3a27b5e8062eb24eeaa4d77297f

CONFIG_SCHED_DRAWER=y

v4.8 is in yakkety-proposed, currently under validation.

New upstream release of util-linux with additional drawer patches is not
available yet.

>From git, it appears that the following patches are required:

$ git log --oneline 
f88eeb25f2eb89fdbd35a9dfbaa26e234a3b0e14..81a307bd4d906815dad7b6b3c355f663907a68c4
81a307b lscpu: make lookup_cache() more robust
bfbe985 lscpu: fix MMHZ column entry within man page
8eb9604 lscpu: update s390-lpar-drawer testcase
28b1658 lscpu: show additional caches (s390)
0c28f0c lscpu: show machine type (s390)
4632b28 lscpu: show static and dynamic MHz (s390)
156740c lscpu: fix typo in summary output
08fb47a lscpu: add s390 drawer testcase
b3adf6e lscpu: add drawer support

To add support for drawer listings. I shall check if these are trivially 
cherrypicable or not.
Change target to 17.04 where util-linux 2.29 is already included. Which 
completes the funtionallity

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

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

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


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

2017-02-24 Thread bugproxy
---Problem Description---
Interface configuration not restored after driver unbind/bind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13  bytes 1046 (1.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ibmveth2
iface ibmveth2 inet static
address 9.47.68.120
netmask 255.255.240.0
network 9.47.64.0
broadcast 9.47.79.255
gateway 9.47.79.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 9.12.18.2
dns-search pok.stglabs.ibm.com

auto enP28p96s0f0
iface enP28p96s0f0 inet static
address 10.10.10.11
netmask 255.255.255.0

root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0
driver: be2net
version: 11.1.0.0
firmware-version: 10.2.252.1913
expansion-rom-version:
bus-info: 001c:60:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: yes

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/unbind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  remove_id  
uevent  unbind

root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 >
/sys/bus/pci/drivers/be2net/bind

root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net
001c:60:00.0  001c:60:00.1  001c:60:00.2  001c:60:00.3  bind  module  new_id  
remove_id  uevent  unbind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4098  mtu 1500
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0
ifup: interface enP28p96s0f0 already configured

root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0
RTNETLINK answers: Cannot assign requested address

root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 16  bytes 1344 (1.3 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

---uname output---
Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

Machine Type = IBM,8286-42A LPAR

---Steps to Reproduce---
# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind

# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind

== Comment - Vaishnavi Bhat
Hi,

To bind a device to a driver, the device must first not be controlled by any 
other driver. Can you check for 'driver' in the below before you bind ?
$ tree /sys//bus/pci/devices/001c:60:00.0

Thank you.

== Comment - Murilo Fossa Vicentini
Just adding some information, this is not a driver specific issue, this was 
also seen with tg3 and i40e adapters . This behavior is a regression when 
compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon 
bind with the information set in /etc/network/interfaces

Leann,

Could you please have someone from the Kernel team look at this reported
regression.

Thanks.

Michael

 Forwarded Message 
Subject:[Bug 1660762] [NEW] [Regression] Interface configuration not
restored after driver unbind/bind (generic)
Date:   Tue, 31 Jan 2017 19:49:16 -
From:   Launchpad Bug Tracker <1660...@bugs.launchpad.net>
Reply-To:   Bug 1660762 <1660...@bugs.launchpad.net>
To: michael.hohnb...@canonical.com

bugproxy (bugproxy) has assigned this bug to you for Ubuntu:

---Problem Description---
Interface configuration not restored after driver unbind/bind

root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0
enP28p96s0f0: flags=4163  mtu 1500
inet 10.10.10.11  netmask 255.255.255.0  broadcast 10.10.10.255
inet6 fe80::290:faff:fe7a:5840  prefixlen 64  scopeid 0x20
ether 00:90:fa:7a:58:40  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13  bytes 1046 (1.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


[Touch-packages] [Bug 1667758] Re: FTBFS : ZZ builds Missing build dependency: sgmlspl

2017-02-24 Thread dino99
** Description changed:

- Latest iputils version in ZZ fail to build for all arches, due to
- sgmlspl not found on the builders
+ Latest iputils version in ZZ fail to build for all arches, due to sgmlspl not 
found on the builders
+ https://launchpad.net/ubuntu/+source/iputils/3:20161105-1ubuntu1

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

Title:
  FTBFS : ZZ builds Missing build dependency: sgmlspl

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  Latest iputils version in ZZ fail to build for all arches, due to sgmlspl not 
found on the builders
  https://launchpad.net/ubuntu/+source/iputils/3:20161105-1ubuntu1

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

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


[Touch-packages] [Bug 1667761] [NEW] ICE in trunc_int_for_mode, at explow.c:55

2017-02-24 Thread Matthias Klose
Public bug reported:

seen on aarch64-linux-gnu with gcc-4.8.x everywhere, fixed in 4.9
(worked around with -O1)

$ cat trunctfdf2.i
long a;
double b;
double fn1() {
  union {
long double f;
__uint128_t i;
  } c = {b};
  __uint128_t d = c.i & 2;
  a = 1;
  long e = 1 | d;
  return e;
}

$ gcc -std=gnu99 -c -g -O2 trunctfdf2.i
trunctfdf2.i: In function 'fn1':
trunctfdf2.i:12:1: internal compiler error: in trunc_int_for_mode, at 
explow.c:55
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.

** Affects: gcc-4.8 (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Changed in: gcc-4.8 (Ubuntu)
   Status: New => Confirmed

** Changed in: gcc-4.8 (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

- seen with gcc-4.8.x everywhere, fixed in 4.9
+ seen on aarch64-linux-gnu with gcc-4.8.x everywhere, fixed in 4.9
+ (worked around with -O1)
  
- $ cat trunctfdf2.i 
+ $ cat trunctfdf2.i
  long a;
  double b;
  double fn1() {
-   union {
- long double f;
- __uint128_t i;
-   } c = {b};
-   __uint128_t d = c.i & 2;
-   a = 1;
-   long e = 1 | d;
-   return e;
+   union {
+ long double f;
+ __uint128_t i;
+   } c = {b};
+   __uint128_t d = c.i & 2;
+   a = 1;
+   long e = 1 | d;
+   return e;
  }
  
- $ gcc -std=gnu99 -c -g -O2 trunctfdf2.i 
+ $ gcc -std=gnu99 -c -g -O2 trunctfdf2.i
  trunctfdf2.i: In function 'fn1':
  trunctfdf2.i:12:1: internal compiler error: in trunc_int_for_mode, at 
explow.c:55
-  }
-  ^
+  }
+  ^
  Please submit a full bug report,
  with preprocessed source if appropriate.

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

Title:
  ICE in trunc_int_for_mode, at explow.c:55

Status in gcc-4.8 package in Ubuntu:
  Confirmed

Bug description:
  seen on aarch64-linux-gnu with gcc-4.8.x everywhere, fixed in 4.9
  (worked around with -O1)

  $ cat trunctfdf2.i
  long a;
  double b;
  double fn1() {
    union {
  long double f;
  __uint128_t i;
    } c = {b};
    __uint128_t d = c.i & 2;
    a = 1;
    long e = 1 | d;
    return e;
  }

  $ gcc -std=gnu99 -c -g -O2 trunctfdf2.i
  trunctfdf2.i: In function 'fn1':
  trunctfdf2.i:12:1: internal compiler error: in trunc_int_for_mode, at 
explow.c:55
   }
   ^
  Please submit a full bug report,
  with preprocessed source if appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1667761/+subscriptions

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


[Touch-packages] [Bug 1667662] Re: SRU: backport rustc to 14.04 and 16.04

2017-02-24 Thread Chris Coulson
In case it's not clear, rustc needs to exist in the security pocket for
each release

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

Title:
  SRU: backport rustc to 14.04 and 16.04

Status in binutils package in Ubuntu:
  New
Status in cmake package in Ubuntu:
  New
Status in llvm-toolchain-3.9 package in Ubuntu:
  New
Status in llvm-toolchain-4.0 package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New

Bug description:
  newer firefox versions will require rust as a build dependency.
  Backport the recent rustc version and cmake, binutils, llvm versions
  from xenial to trusty.  It looks like xenial is recent and only needs
  the llvm backport.

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

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


[Touch-packages] [Bug 1667758] [NEW] FTBFS : ZZ builds Missing build dependency: sgmlspl

2017-02-24 Thread dino99
Public bug reported:

Latest iputils version in ZZ fail to build for all arches, due to
sgmlspl not found on the builders

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: ftbfs upgrade-software-version zesty

** Tags added: ftbfs upgrade-software-version zesty

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

** Summary changed:

- FTBFS : ZZ build Missing build dependencies: sgmlspl
+ FTBFS : ZZ builds Missing build dependency: sgmlspl

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

Title:
  FTBFS : ZZ builds Missing build dependency: sgmlspl

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  Latest iputils version in ZZ fail to build for all arches, due to
  sgmlspl not found on the builders

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

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


[Touch-packages] [Bug 1667751] [NEW] rsyslog profile doesn't work in namespace

2017-02-24 Thread Simon Déziel
Public bug reported:

I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even the
kernel so please re-assign if needed.

Enabling rsyslog's Apparmor profile in a namespace generates this
denial:

[ 3026.956651] audit: type=1400 audit(1487955263.521:39):
apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
ganymede_" profile="/usr/sbin/rsyslogd"
name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
denied_mask="r" fsuid=165536 ouid=165536

This prevents rsyslog from starting in the said container:

root@ganymede:~# systemctl status rsyslog
● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
 Docs: man:rsyslogd(8)
   http://www.rsyslog.com/doc/
  Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
 Main PID: 232 (code=exited, status=127)

Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Unit entered failed state.
Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Service hold-off time 
over, scheduling restart.
Feb 24 11:54:24 ganymede systemd[1]: Stopped System Logging Service.
Feb 24 11:54:24 ganymede systemd[1]: rsyslog.service: Start request repeated 
too quickly.
Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.


I don't know why rsyslog wants to read its own binary but it seems to really 
want to.


Both the host and the guest are up to date Xenials. Please not that the host 
runs the kernel from -proposed.

root@jupiter:~# apt-cache policy linux-image-4.4.0-65-generic apparmor rsyslog
linux-image-4.4.0-65-generic:
  Installed: 4.4.0-65.86
  Candidate: 4.4.0-65.86
  Version table:
 *** 4.4.0-65.86 100
100 /var/lib/dpkg/status
apparmor:
  Installed: 2.10.95-0ubuntu2.5
  Candidate: 2.10.95-0ubuntu2.5
  Version table:
 *** 2.10.95-0ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
rsyslog:
  Installed: 8.16.0-1ubuntu3
  Candidate: 8.16.0-1ubuntu3
  Version table:
 *** 8.16.0-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.5
ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
Uname: Linux 4.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Feb 24 12:17:34 2017
InstallationDate: Installed on 2016-12-19 (66 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
SourcePackage: apparmor
Syslog: Feb 24 11:04:10 jupiter dbus[1812]: [system] AppArmor D-Bus mediation 
is enabled
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  rsyslog profile doesn't work in namespace

Status in apparmor package in Ubuntu:
  New

Bug description:
  I'm not sure if it's a bug that belongs to Apparmor, rsyslog or even
  the kernel so please re-assign if needed.

  Enabling rsyslog's Apparmor profile in a namespace generates this
  denial:

  [ 3026.956651] audit: type=1400 audit(1487955263.521:39):
  apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-
  ganymede_" profile="/usr/sbin/rsyslogd"
  name="/usr/sbin/rsyslogd" pid=4165 comm="rsyslogd" requested_mask="r"
  denied_mask="r" fsuid=165536 ouid=165536

  This prevents rsyslog from starting in the said container:

  root@ganymede:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead) (Result: exit-code) since Fri 2017-02-24 11:54:24 
EST; 30min ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 232 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=127)
   Main PID: 232 (code=exited, status=127)

  Feb 24 11:54:24 ganymede systemd[1]: Failed to start System Logging Service.
  Feb 24 11:54:24 

[Touch-packages] [Bug 1323238] Re: Checkbox text Property is not working

2017-02-24 Thread Adnane Belmadiaf
*** This bug is a duplicate of bug 1333228 ***
https://bugs.launchpad.net/bugs/1333228

Dup of bug 1333228

** This bug has been marked a duplicate of bug 1333228
   [sdk] Clicking on checkbox label should toggle the checkbox

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

Title:
  Checkbox text Property is not working

Status in Ubuntu UI Toolkit:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Trying setting up text property for the textbox , which should show
  text next to the checkbox.

  Code
CheckBox{
  id:testChkBox
  text: "Testing"
  }

  Expected Result :- It should show the checkbox and text next to it

  Actual Result :- It just render checkbox not the text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1323238/+subscriptions

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


[Touch-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces

2017-02-24 Thread Simon Déziel
I can confirm this problem was fixed for Xenial on 4.4.0-65.86, thank
you.

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in apparmor source package in Zesty:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

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

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


[Touch-packages] [Bug 1666748] Re: Apparmor problem inside a lxd container

2017-02-24 Thread Simon Déziel
*** This bug is a duplicate of bug 1660832 ***
https://bugs.launchpad.net/bugs/1660832

The problem with the Unix socket is indeed fixed by 4.4.0-65.86.
Thanks John. I have other issues with AA in namespaces which I will report in 
other LPs.

** This bug has been marked a duplicate of bug 1660832
   unix domain socket cross permission check failing with nested namespaces

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

Title:
  Apparmor problem inside a lxd container

Status in apparmor package in Ubuntu:
  New

Bug description:
  I've been running /usr/sbin/sshd in a custom Apparmor profile [*] for a long 
time and it works well.
  When I loaded the same profile in a lxd container (named ganymede), it didn't 
work at all:

  apparmor="DENIED" operation="file_perm" namespace="root//lxd-ganymede_
  " profile="/usr/sbin/sshd" pid=30870 comm="sshd"
  family="unix" sock_type="stream" protocol=0 requested_mask="send
  receive" denied_mask="send receive" addr=none peer_addr=none
  peer="---"

  Additional information about my environment:

  Both the host and the guest are up to date Xenials.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-63-generic apparmor 
openssh-server
  linux-image-4.4.0-63-generic:
Installed: 4.4.0-63.84
Candidate: 4.4.0-63.84
Version table:
   *** 4.4.0-63.84 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  openssh-server:
Installed: 1:7.2p2-4ubuntu2.1
Candidate: 1:7.2p2-4ubuntu2.1
Version table:
   *** 1:7.2p2-4ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.2p2-4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  *: 
https://github.com/simondeziel/aa-profiles/blob/4d7fbd9fcca4bd62d97e8d0ba2cdc35e8d48d096/16.04/usr.sbin.sshd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 21:25:55 2017
  InstallationDate: Installed on 2016-12-19 (64 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1177318] Re: Unattended Upgrades fail to parse "${distro_id}:${distro_codename}-security"

2017-02-24 Thread Travis Odom
Note this also affects 14.04 trusty

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

Title:
  Unattended Upgrades fail to parse
  "${distro_id}:${distro_codename}-security"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Beginning with Ubuntu 13.04 Raring Ringtail, unattended-upgrades seems
  not to be able to parse /etc/apt/apt.conf.d/50unattended-upgrades
  anymore. The logfile tells:

  cat /var/log/unattended-upgrades/unattended-upgrades.log 
  2013-05-06 14:57:05,724 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-06 14:57:05,724 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-06 14:57:05,725 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-06 14:57:09,114 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.
  2013-05-07 11:33:04,944 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-07 11:33:04,944 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-07 11:33:04,944 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-07 11:33:08,398 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.

  which means two times, that allowed sources are ['o=Ubuntu,a=raring-
  security', 'o=Ubuntu,a=raring-updates'].

  I do suspect it is because of the automatic distribution setting in
  /etc/apt/apt.conf.d/50unattended-upgrades or the setting of the
  corresponding variables:

  "${distro_id}:${distro_codename}-updates"

  When this line is set manually to "Ubuntu:raring-updates", it will
  work.

  System: Ubuntu Gnome 13.04, all up-to-date

  $ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  $ cat /etc/apt/apt.conf.d/10periodic 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ cat /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

  // List of packages to not update
  Unattended-Upgrade::Package-Blacklist {
  //"vim";
  //"libc6";
  //"libc6-dev";
  //"libc6-i686";
  };
  ...

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

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


[Touch-packages] [Bug 1177318] Re: Unattended Upgrades fail to parse "${distro_id}:${distro_codename}-security"

2017-02-24 Thread Travis Odom
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1255, in 
main(options)
  File "/usr/bin/unattended-upgrade", line 931, in main
allowed_origins = get_allowed_origins()
  File "/usr/bin/unattended-upgrade", line 298, in get_allowed_origins
allowed_origins = get_allowed_origins_legacy()
  File "/usr/bin/unattended-upgrade", line 283, in get_allowed_origins_legacy
(distro_id, distro_codename) = s.split()
ValueError: need more than 0 values to unpack

It is failing to substitute `distro-id` and `distro-codename`, and so
the for loop just gets: `['', '', "-security'", "-updates'",
"-backports'"]`

Replacing the variable placeholders with the correct literal values
fixes it as a workaround.

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

Title:
  Unattended Upgrades fail to parse
  "${distro_id}:${distro_codename}-security"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Beginning with Ubuntu 13.04 Raring Ringtail, unattended-upgrades seems
  not to be able to parse /etc/apt/apt.conf.d/50unattended-upgrades
  anymore. The logfile tells:

  cat /var/log/unattended-upgrades/unattended-upgrades.log 
  2013-05-06 14:57:05,724 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-06 14:57:05,724 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-06 14:57:05,725 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-06 14:57:09,114 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.
  2013-05-07 11:33:04,944 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-07 11:33:04,944 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-07 11:33:04,944 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-07 11:33:08,398 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.

  which means two times, that allowed sources are ['o=Ubuntu,a=raring-
  security', 'o=Ubuntu,a=raring-updates'].

  I do suspect it is because of the automatic distribution setting in
  /etc/apt/apt.conf.d/50unattended-upgrades or the setting of the
  corresponding variables:

  "${distro_id}:${distro_codename}-updates"

  When this line is set manually to "Ubuntu:raring-updates", it will
  work.

  System: Ubuntu Gnome 13.04, all up-to-date

  $ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  $ cat /etc/apt/apt.conf.d/10periodic 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ cat /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

  // List of packages to not update
  Unattended-Upgrade::Package-Blacklist {
  //"vim";
  //"libc6";
  //"libc6-dev";
  //"libc6-i686";
  };
  ...

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

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


[Touch-packages] [Bug 1591833] Re: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)

2017-02-24 Thread quanxian
Move it into 17.10 after Canonical/Intel discussion.

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

Title:
  [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)

Status in intel:
  New
Status in openssl package in Ubuntu:
  Confirmed
Status in openssl package in Debian:
  Confirmed

Bug description:
  In order to support Intel QAT, please upgrade Openssl package from
  1.0.2 to 1.1.0

  HW: Purley-4s

  Upstream schedule:
 Openssl: 1.1.0

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

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


[Touch-packages] [Bug 1667745] [NEW] Wrong system date and time Ubuntu 16.04, Windows dual boot

2017-02-24 Thread Ayşe Nur
Public bug reported:

I tried a lot of things to fix the time, but as long as I can
understand, Windows adjusts the BIOS time to local time, while Ubuntu
assumes the BIOS time is UTC. Getting the time right shouldn't be this
hard.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 24 19:39:45 2017
InstallationDate: Installed on 2017-02-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
NtpStatus:
 remote   refid  st t when poll reach   delay   offset  jitter
 ==
  server  .POOL.  16 p-   6400.0000.000   0.000
  ntp.ubuntu.com  .POOL.  16 p-   6400.0000.000   0.000
SourcePackage: ntp
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ntp.conf: [modified]
mtime.conffile..etc.ntp.conf: 2017-02-24T21:49:57.722761

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


** Tags: amd64 apport-bug xenial

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

Title:
  Wrong system date and time Ubuntu 16.04, Windows dual boot

Status in ntp package in Ubuntu:
  New

Bug description:
  I tried a lot of things to fix the time, but as long as I can
  understand, Windows adjusts the BIOS time to local time, while Ubuntu
  assumes the BIOS time is UTC. Getting the time right shouldn't be this
  hard.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 24 19:39:45 2017
  InstallationDate: Installed on 2017-02-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  NtpStatus:
   remote   refid  st t when poll reach   delay   offset  jitter
   
==
server  .POOL.  16 p-   6400.0000.000   
0.000
ntp.ubuntu.com  .POOL.  16 p-   6400.0000.000   
0.000
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2017-02-24T21:49:57.722761

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

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


[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-24 Thread Harm van Bakel
On closer examination the suspend issue that I was seeing was not
related to the 1.2.6-0ubuntu0.16.04.1 networkmanager upgrade but a bios
upgrade I performed a few days earlier. The forced reboot only occurred
when suspending while powered and resuming on battery after unplugging
the laptop, which is why I hadn't noticed earlier. After downgrading the
bios and reinstalling the networkmanager update everything is working
fine now.

Apologies for the false alarm. For anyone interested, the system is an
XPS 9350 and the offending bios upgrade was 1.4.13 (reverting back to
1.4.12 fixed the issue).

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

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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


[Touch-packages] [Bug 1177318] Re: Unattended Upgrades fail to parse "${distro_id}:${distro_codename}-security"

2017-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Unattended Upgrades fail to parse
  "${distro_id}:${distro_codename}-security"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Beginning with Ubuntu 13.04 Raring Ringtail, unattended-upgrades seems
  not to be able to parse /etc/apt/apt.conf.d/50unattended-upgrades
  anymore. The logfile tells:

  cat /var/log/unattended-upgrades/unattended-upgrades.log 
  2013-05-06 14:57:05,724 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-06 14:57:05,724 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-06 14:57:05,725 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-06 14:57:09,114 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.
  2013-05-07 11:33:04,944 INFO Pakete, die anfangs auf die schwarzen Liste 
standen: 
  2013-05-07 11:33:04,944 INFO Skript für unbeaufsichtigte Upgrades wird 
gestartet.
  2013-05-07 11:33:04,944 INFO erlaubte Ursprünge sind: 
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
  2013-05-07 11:33:08,398 INFO Es wurden keine Pakete gefunden, von denen ein 
unbeaufsichtigtes Upgrade durchgeführt werden kann.

  which means two times, that allowed sources are ['o=Ubuntu,a=raring-
  security', 'o=Ubuntu,a=raring-updates'].

  I do suspect it is because of the automatic distribution setting in
  /etc/apt/apt.conf.d/50unattended-upgrades or the setting of the
  corresponding variables:

  "${distro_id}:${distro_codename}-updates"

  When this line is set manually to "Ubuntu:raring-updates", it will
  work.

  System: Ubuntu Gnome 13.04, all up-to-date

  $ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  $ cat /etc/apt/apt.conf.d/10periodic 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ cat /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

  // List of packages to not update
  Unattended-Upgrade::Package-Blacklist {
  //"vim";
  //"libc6";
  //"libc6-dev";
  //"libc6-i686";
  };
  ...

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

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


[Touch-packages] [Bug 1667562] Re: package systemd 229-4ubuntu16 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-remov

2017-02-24 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this bug report isn't very useful in its current state
and a crash report would be much more useful.  Could you try recreating
this issue by enabling apport to catch the crash report 'sudo service
apport start force_start=1' and then trying to install the same package
again?  This process will create a new bug report so I am marking this
one as Invalid.  Thanks again for helping out!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: package-install-segfault

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

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

Title:
  package systemd 229-4ubuntu16 [modified: usr/share/dbus-1/system-
  services/org.freedesktop.systemd1.service] failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I try to install upstart based on this link :
  http://notesofaprogrammer.blogspot.co.id/2016/09/running-upstart-on-
  ubuntu-1604-lts.html

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 11:02:11 2017
  DpkgTerminalLog:
   Removing systemd (229-4ubuntu16) ...
   systemd is the active init system, please switch to another before removing 
systemd.
   dpkg: error processing package systemd (--purge):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   package:systemd:229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
   Removing systemd (229-4ubuntu16) ...
   systemd is the active init system, please switch to another before removing 
systemd.
   dpkg: error processing package systemd (--purge):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-12-01 (84 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=31650dee-85a7-40f8-8106-bba66f9e6e28 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/18/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

2017-02-24 Thread Brian Murray
** Also affects: vim (Ubuntu Zesty)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed
Status in vim source package in Zesty:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

2017-02-24 Thread Brian Murray
** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-z-incoming

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is something new in Ubuntu 17.04. Whenever I boot up or upon
  returning from sleep, I don't have DNS resolution available. What I
  have to do is go and shutdown systemd-resolved (sudo service systemd-
  resolved stop) and edit /etc/resolv.conf to point to 192.168.1.1 (my
  router) instead of 127.0.0.53. Then everything works peachy. Otherwise
  any DNS resolution attempt will result in SERVFAIL.

  Since this is a major issue out of the box and I don't see any other
  bug report on this yet, I wanted to report it. This happens both on my
  laptop and my desktop PC, so it's not something strange on a single
  machine, but since no one else is complaining about it yet, it may be
  related to my network configuration. My router forwards DNS requests
  to an ODROID C2 on the same subnet, which then does the DNS resolution
  via dnsmasq. Dnsqmasq is set up to forward the requests to multiple
  DNS servers and respond with whichever one was fastest.

  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: MATE
  Date: Mon Jan 16 08:51:43 2017
  InstallationDate: Installed on 2017-01-08 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
  MachineType: LENOVO 7675CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=b64995c7-1fd6-405b-b7ee-de3e56fe0617 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 7675CTO
  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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn7675CTO:pvrThinkPadX61:rvnLENOVO:rn7675CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7675CTO
  dmi.product.version: ThinkPad X61
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-02-24 Thread Serious Diman
Diego, thanks a lot! That did the trick! After removing the file
(/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf)
management of wired and bluetooth modem connections is back!

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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


[Touch-packages] [Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-24 Thread Brian Murray
Your debdiff contains (LP: 1573307) while this might work (i.e.
Launchpad-Bugs-Fixed will be properly created for this bug number) the
syntax most commonly used is LP: #1573307.  Notice the missing "#".

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

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

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

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

Title:
  wget crashed with SIGSEGV in __memset_avx2()

Status in wget package in Ubuntu:
  Confirmed
Status in wget source package in Xenial:
  Triaged

Bug description:
  EDIT(other user): The crash actually happens when the terminal window
  is too small.

  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.

  To reproduce the bug try the following:

  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso

  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.

  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  evan@HPPC:~$ apt-cache policy wget
  wget:
Installato: 1.17.1-1ubuntu1
Candidato:  1.17.1-1ubuntu1
Tabella versione:
   *** 1.17.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
   Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
   PC (0x7f4eac3b7328) ok
   source "%al" ok
   destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  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/ubuntu/+source/wget/+bug/1573307/+subscriptions

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


[Touch-packages] [Bug 1667407] Re: improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug

2017-02-24 Thread Gustavo Serra Scalet
One other possibility (as performed by Fedora) is to have libcrypto
(from openssl) configured through the "--with-openssl=yes" parameter.

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

Title:
   improve 2x-3x sha256sum performance on ppc64le due to current gcc
  optimization bug

Status in coreutils package in Ubuntu:
  New
Status in coreutils package in Debian:
  Unknown

Bug description:
  Dear Maintainer,

  The sha256sum provided by coreutils (without openssl) is performing
  poorly with gcc versions >= 4.9 until 7.0 (currently under development).
  The reason for that is the -fschedule-insns optimization that is used
  with -O2. By simply deactivating it, there is a performance improvement
  of 2 to 3 times.

  I'm using Ubuntu 16.10 and the coreutils package version
  8.25-2ubuntu2.

  Please check the following closed debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

  Be aware of the following conditions that are required:
  * If ppc64le
  * If gcc being used is >= 4.9 and < 7.0

  Notes:
  1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
  2) clang is not affected by this bug (verified on v3.8 and v3.9).
  3) strangely the sha512 is not affected by this.

  Below a demonstration of how it performs on my POWER8 machine:

  ===
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m18.670s
  user0m16.566s
  sys 0m0.745s

  $ # now with the following patch: ## Check Michael Stone's patch for an 
improved version.
  $ diff Makefile.in ../Makefile.in
  8989c8989
  < @am__fastdepCC_TRUE@  $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ 
$< &&\
  ---
  > @am__fastdepCC_TRUE@  $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo 
"-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\
  $ cp ../Makefile.in Makefile.in
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m5.903s
  user0m5.560s
  sys 0m0.255s

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

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


[Touch-packages] [Bug 1667407] Re: improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug

2017-02-24 Thread Brian Murray
** Tags added: yakkety

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

** Also affects: coreutils (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053
   Importance: Unknown
   Status: Unknown

** Changed in: coreutils (Ubuntu)
 Assignee: (unassigned) => Matthias Klose (doko)

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

Title:
   improve 2x-3x sha256sum performance on ppc64le due to current gcc
  optimization bug

Status in coreutils package in Ubuntu:
  New
Status in coreutils package in Debian:
  Unknown

Bug description:
  Dear Maintainer,

  The sha256sum provided by coreutils (without openssl) is performing
  poorly with gcc versions >= 4.9 until 7.0 (currently under development).
  The reason for that is the -fschedule-insns optimization that is used
  with -O2. By simply deactivating it, there is a performance improvement
  of 2 to 3 times.

  I'm using Ubuntu 16.10 and the coreutils package version
  8.25-2ubuntu2.

  Please check the following closed debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

  Be aware of the following conditions that are required:
  * If ppc64le
  * If gcc being used is >= 4.9 and < 7.0

  Notes:
  1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
  2) clang is not affected by this bug (verified on v3.8 and v3.9).
  3) strangely the sha512 is not affected by this.

  Below a demonstration of how it performs on my POWER8 machine:

  ===
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m18.670s
  user0m16.566s
  sys 0m0.745s

  $ # now with the following patch: ## Check Michael Stone's patch for an 
improved version.
  $ diff Makefile.in ../Makefile.in
  8989c8989
  < @am__fastdepCC_TRUE@  $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ 
$< &&\
  ---
  > @am__fastdepCC_TRUE@  $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo 
"-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\
  $ cp ../Makefile.in Makefile.in
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m5.903s
  user0m5.560s
  sys 0m0.255s

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

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


[Touch-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

2017-02-24 Thread Sebastien Bacher
** No longer affects: gtk+3.0 (Ubuntu)

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

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

  and tried to solve the problem following the hints:

  - Reboot does not solve the problem.

  - I could not do any tests with gstreamer-properties as it seems to
  have been removed from gstreamer (what is the successor?).

  - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
  Tab that the microphone of the laptop is OK and that the kernel works
  with it. The Level monitor bar is moving according to environment
  noise and touching of the microphone.

  - "sudo alsa force-reload" does not solve the problem.

  - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
  install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards
  does not solve the problem.

  - audacity is recording through the microphone correctly.

  - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d
  /alsa-base.conf and rebooting does not solve the problem.

  I hope that is a known problem. Please tell me if you need further
  information.

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

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


[Touch-packages] [Bug 1667328] Re: Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

2017-02-24 Thread Till Kamppeter
** Changed in: gstreamer (Ubuntu)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

  and tried to solve the problem following the hints:

  - Reboot does not solve the problem.

  - I could not do any tests with gstreamer-properties as it seems to
  have been removed from gstreamer (what is the successor?).

  - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
  Tab that the microphone of the laptop is OK and that the kernel works
  with it. The Level monitor bar is moving according to environment
  noise and touching of the microphone.

  - "sudo alsa force-reload" does not solve the problem.

  - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
  install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards
  does not solve the problem.

  - audacity is recording through the microphone correctly.

  - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d
  /alsa-base.conf and rebooting does not solve the problem.

  I hope that is a known problem. Please tell me if you need further
  information.

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

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


[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist

2017-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

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

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


[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist

2017-02-24 Thread Olivier Louvignes
Thanks for the tip, will try that. What is extremely frustrating is that
to unblacklist a module you have to edit 4 different, some dynamic
files. I don't really get how such poor design could ever be validated.
Maybe we're missing something (systemd config?).

```
# Blacklists that must be edited on 16.04:
root@toto:/lib/modprobe.d# grep -R iTCO_wdt /*/modprobe.d
/etc/modprobe.d/blacklist-watchdog.conf:# blacklist iTCO_wdt
/lib/modprobe.d/blacklist_linux_4.4.0-64-generic.conf:blacklist iTCO_wdt
/lib/modprobe.d/blacklist_linux-hwe-edge_4.8.0-34-generic.conf:blacklist 
iTCO_wdt
/lib/modprobe.d/blacklist_linux_4.4.0-63-generic.conf:blacklist iTCO_wdt
```

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

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is 
blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is 
blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy systemd
  systemd:
Installed: 228-4ubuntu1
Candidate: 228-4ubuntu1
Version table:
   *** 228-4ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

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

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


[Touch-packages] [Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-24 Thread Jeremy Bicha
I did a reinstall of Ubuntu 17.04 which preserved my home directory but
wiped all modified system configurations (there was also a hiccup which
meant that my installed apps weren't automatically reinstalled).

After the reinstall, I can no longer reproduce this bug, so I guess
we'll probably want to close this bug.

I did have lxd set up with bridged networking, but I probably had other
non-default networking tweaks too.

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

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

Title:
  zesty systemd-resolve timeout

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted my zesty install today so it has network-manager
  1.4.4-1ubuntu2 (re-enabled resolved by default for DNS) and systemd
  232-17ubuntu1 (which is supposed to fix the CNAME problems that got
  resolved by default reverted earlier in zesty).

  I had various DNS issues so I rebooted.

  When I rebooted, I opened up Firefox and browsed several sites.
  I opened a terminal and ran sudo apt update. I disabled a PPA and enabled a 
different PPA and ran sudo apt update then sudo apt dist-upgrade (there were 3 
updates).

  When apt was downloading one of those new packages, it paused mid-
  download. I was unable to browse sites in Firefox. I ran this command
  in a different terminal:

  $ systemd-resolve --status
  Failed to get global data: Connection timed out

  I checked journalctl and there was a very large number of these entries:
  systemd-resolved[3260]: Processing query...

  Finally followed by this repeated 3 times:
  dnsmasq[3563]: Maximum number of concurrent DNS queries reached (max: 150)

  Eventually, after I guess a couple minutes, things returned to normal.
  The apt upgrade completed. systemd-resolve --status looked better and
  I'm able to use Firefox again (to report this bug).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-17ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 19 09:54:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (191 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=352e459f-ebca-4dc8-86e3-b078a000910b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2016-12-20 (60 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1661763] Re: screen turns off during standby, doesn't wake up on resume

2017-02-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  screen turns off during standby, doesn't wake up on resume

Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  screen turns off during standby, doesn't wake up on resume

  had to reboot to recover

  Feb  2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here 
]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at 
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock || 
cdclk < crtc_clock)
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm 
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi 
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp 
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core 
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul 
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel 
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper 
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211 
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me 
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal 
processor_thermal_device 
 intel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm btqca btintel bluetooth 
intel_lpss_acpi intel_lpss hp_accel lis3lv02d input_polldev int3402_thermal 
int3406_thermal int340x_thermal_zone tpm_crb mac_hid int3400_thermal 
acpi_thermal_rel acpi_pad dptf_power hp_wireless parport_pc ppdev lp parport 
ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_pci_sdmmc i915 i2c_algo_bit 
drm_kms_helper syscopyarea psmouse sysfillrect nvme sysimgblt fb_sys_fops 
nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid video fjes
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg 
Not tainted 4.8.0-34-generic #36-Ubuntu
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY 
Notebook/81D1, BIOS F.28 10/05/2016
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548911]  0286 
8055b5e8 975531437930 8e430a22
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548924]  975531437980 
 975531437970 8e08319b
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548930]  37f88e1a9a80 
975412ad86c0 97555c5b3c00 9755660a6000
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548948]  [] 
dump_stack+0x63/0x81
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548957]  [] 
__warn+0xcb/0xf0
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548965]  [] 
warn_slowpath_fmt+0x5f/0x80
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548998]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549068]  [] 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549131]  [] 
intel_check_primary_plane+0xc6/0xe0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549151]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549211]  [] 
intel_plane_atomic_check+0x132/0x1f0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549230]  [] 
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549292]  [] 
intel_atomic_check+0x155/0x760 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549339]  [] 
drm_atomic_check_only+0x187/0x610 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549377]  [] 
drm_atomic_commit+0x17/0x60 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549397]  [] 
drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549430]  [] 
__setplane_internal+0x17b/0x270 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549436]  [] ? 
unix_stream_read_generic+0x24f/0x920
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549467]  [] 
drm_mode_cursor_universal+0x139/0x240 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549498]  [] 
drm_mode_cursor_common+0x7e/0x180 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549530]  [] 
drm_mode_cursor_ioctl+0x50/0x70 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549555]  [] 
drm_ioctl+0x200/0x4f0 [drm]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549585]  [] ? 

[Touch-packages] [Bug 1661763] Re: screen turns off during standby, doesn't wake up on resume

2017-02-24 Thread Tomislav
What I see is similar, but not identical to Gábor's description:

Feb 24 14:51:10 tena kernel: [  761.070735] CPU: 0 PID: 1132 Comm: Xorg 
Tainted: GW   4.4.
0-64-generic #85~14.04.1-Ubuntu
Feb 24 14:51:10 tena kernel: [  761.070736] Hardware name: Dell Inc. Latitude 
E5570/0R3VX4, BIOS 1.7.3
 06/15/2016
Feb 24 14:51:10 tena kernel: [  761.070737]   880097f47928 
813dc80c 88
0097f47970
Feb 24 14:51:10 tena kernel: [  761.070738]  c069e700 880097f47960 
8107e9d6 88
0097156000
Feb 24 14:51:10 tena kernel: [  761.070739]  880097308000 0004 
880097cf8b78 88
0097f479ec
Feb 24 14:51:10 tena kernel: [  761.070741] Call Trace:
Feb 24 14:51:10 tena kernel: [  761.070742]  [] 
dump_stack+0x63/0x87


Notice that in my case, it says "Xorg Tainted", where Gábor sees "Xorg Not 
Tainted". Not sure if it's the same bug, but it sounds like it might be. I'm on 
Ubuntu 14.04 ("4.4.0-64-generic #85~14.04.1-Ubuntu SMP Mon Feb 20 12:10:54 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux"), on a Latitude E5570. Fresh install a few 
days ago.

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

Title:
  screen turns off during standby, doesn't wake up on resume

Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  screen turns off during standby, doesn't wake up on resume

  had to reboot to recover

  Feb  2 22:51:59 ubuntu8 kernel: [318555.548546] [ cut here 
]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548650] WARNING: CPU: 3 PID: 14496 at 
/build/linux-RZGRu0/linux-4.8.0/drivers/gpu/drm/i915/intel_display.c:14328 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548654] WARN_ON_ONCE(!crtc_clock || 
cdclk < crtc_clock)
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548657] Modules linked in: msr ccm 
rfcomm bnep hid_multitouch i2c_designware_platform i2c_designware_core hp_wmi 
sparse_keymap nls_iso8859_1 arc4 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc 
snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp 
snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_dsp snd_hda_ext_core 
kvm_intel snd_soc_sst_match kvm iwlmvm snd_soc_core irqbypass crct10dif_pclmul 
snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec 
crc32_pclmul mac80211 snd_hda_core ghash_clmulni_intel snd_hwdep aesni_intel 
snd_pcm aes_x86_64 lrw snd_seq_midi glue_helper snd_seq_midi_event ablk_helper 
snd_rawmidi cryptd iwlwifi snd_seq snd_seq_device snd_timer input_leds cfg80211 
joydev serio_raw rtsx_pci_ms memstick snd soundcore uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 shpchp videobuf2_core videodev media mei_me 
idma64 mei virt_dma btusb btrtl intel_lpss_pci intel_pch_thermal 
processor_thermal_device intel_soc_dts_iosf ucsi int3403_thermal hci_uart btbcm 
btqca btintel bluetooth intel_lpss_acpi intel_lpss hp_accel lis3lv02d 
input_polldev int3402_thermal int3406_thermal int340x_thermal_zone tpm_crb 
mac_hid int3400_thermal acpi_thermal_rel acpi_pad dptf_power hp_wireless 
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq 
rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect 
nvme sysimgblt fb_sys_fops nvme_core drm ahci rtsx_pci libahci i2c_hid wmi hid 
video fjes
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548904] CPU: 3 PID: 14496 Comm: Xorg 
Not tainted 4.8.0-34-generic #36-Ubuntu
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548907] Hardware name: HP HP ENVY 
Notebook/81D1, BIOS F.28 10/05/2016
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548911]  0286 
8055b5e8 975531437930 8e430a22
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548924]  975531437980 
 975531437970 8e08319b
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548930]  37f88e1a9a80 
975412ad86c0 97555c5b3c00 9755660a6000
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548936] Call Trace:
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548948]  [] 
dump_stack+0x63/0x81
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548957]  [] 
__warn+0xcb/0xf0
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548965]  [] 
warn_slowpath_fmt+0x5f/0x80
  Feb  2 22:51:59 ubuntu8 kernel: [318555.548998]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549068]  [] 
skl_max_scale.part.120+0x75/0x80 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549131]  [] 
intel_check_primary_plane+0xc6/0xe0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549151]  [] ? 
drm_atomic_helper_normalize_zpos+0x264/0x300 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549211]  [] 
intel_plane_atomic_check+0x132/0x1f0 [i915]
  Feb  2 22:51:59 ubuntu8 kernel: [318555.549230]  [] 
drm_atomic_helper_check_planes+0x84/0x200 [drm_kms_helper]
  Feb  2 22:51:59 ubuntu8 

[Touch-packages] [Bug 1664093] Re: iv had so many issues since upgrading to the new ubuntu 16.04 lts but this is just a quick start of what just a few are for now..

2017-02-24 Thread Marc Deslauriers
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

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

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

Title:
  iv had so many issues since upgrading to the new ubuntu 16.04 lts but
  this is just a quick start of what just a few are for now..

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  iv had issues with plymouth not loading on boot. my internet keeps
  dropping out. my system isnt able to detect my broardband dongle so as
  i can use the internet through it. my wifi between my phones and this
  system is not making a link up to one another,just the same as imnot
  able to make the same link via usd cable beteen the laptop and any of
  my phones. im not able to expand the screen while using my firefox
  browser to fullscreen mode, when i try by way of the usual  double
  click method to expand it up, it then crashes firefox and only ends up
  having to restart, so i havnt even bothered to see weather it will
  with any other browser either.

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

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


[Touch-packages] [Bug 1663481] Re: webbrowser-app crashed with SIGABRT in __run_exit_handlers()

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

** Information type changed from Private Security to Public

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

Title:
  webbrowser-app crashed with SIGABRT in __run_exit_handlers()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  If i launch ubuntu web browser than this a error:
  webbrowser-app crashed with SIGABRT in __run_exit_handlers()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: webbrowser-app 0.23+17.04.20170125.1-0ubuntu1
  Uname: Linux 4.9.2-040902-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Feb 10 11:49:24 2017
  ExecutablePath: /usr/bin/webbrowser-app
  ProcCmdline: webbrowser-app
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f69908e45d8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:83
   __GI_exit (status=) at exit.c:105
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: Upgraded to zesty on 2017-02-09 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1664489] Re: Rootkit

2017-02-24 Thread Marc Deslauriers
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  Rootkit

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I cant use sudo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Feb 14 01:22:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fa44]
  InstallationDate: Installed on 2016-12-02 (73 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite P55-A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=7327dc4b-a986-43c3-82f3-2c35bca052f6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VG10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd11/20/2014:svnTOSHIBA:pnSatelliteP55-A:pvrPSPMEU-00G002:rvnIntel:rnVG10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P55-A
  dmi.product.version: PSPMEU-00G002
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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 Feb 13 22:38:53 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12781 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Touch-packages] [Bug 1667372] Re: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2017-02-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package python-decorator 4.0.6-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in python-decorator package in Ubuntu:
  New

Bug description:
  error message when boot system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-decorator 4.0.6-1
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Feb 22 22:16:54 2017
  Dependencies:
   
  DuplicateSignature:
   package:python-decorator:4.0.6-1
   Setting up python-decorator (4.0.6-1) ...
   /var/lib/dpkg/info/python-decorator.postinst: 6: 
/var/lib/dpkg/info/python-decorator.postinst: pycompile: not found
   dpkg: error processing package python-decorator (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-12-06 (78 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-decorator
  Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1667372/+subscriptions

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


[Touch-packages] [Bug 1667562] Re: package systemd 229-4ubuntu16 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-remov

2017-02-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package systemd 229-4ubuntu16 [modified: usr/share/dbus-1/system-
  services/org.freedesktop.systemd1.service] failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I try to install upstart based on this link :
  http://notesofaprogrammer.blogspot.co.id/2016/09/running-upstart-on-
  ubuntu-1604-lts.html

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri Feb 24 11:02:11 2017
  DpkgTerminalLog:
   Removing systemd (229-4ubuntu16) ...
   systemd is the active init system, please switch to another before removing 
systemd.
   dpkg: error processing package systemd (--purge):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   package:systemd:229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
   Removing systemd (229-4ubuntu16) ...
   systemd is the active init system, please switch to another before removing 
systemd.
   dpkg: error processing package systemd (--purge):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-12-01 (84 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=31650dee-85a7-40f8-8106-bba66f9e6e28 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu16 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/18/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1667569] Re: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2

2017-02-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

Status in apt package in Ubuntu:
  New

Bug description:
  my update option in not working give error message W: Unable to read
  /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
  and my wifi option not came how to fix it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agnisys03   2084 F pulseaudio
  Date: Thu Feb 23 23:35:05 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=e7184cb7-23c1-4872-afda-17a379043dea
  InstallationDate: Installed on 2016-03-12 (348 days ago)
  InstallationMedia: It
  IwConfig:
   enx64d4da695796  no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUSTeK Computer Inc. U56E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=9e60c12c-47c3-42c7-8d17-f6bc68d7897b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7
  RfKill:
   0: i2400m-usb:1-1.1:1.0: WiMAX
Soft blocked: yes
Hard blocked: no
  SourcePackage: apt
  Title: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U56E.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U56E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U56E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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


[Touch-packages] [Bug 1666049] Re: I cant download the apps i want

2017-02-24 Thread Marc Deslauriers
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

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

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

Title:
  I cant download the apps i want

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  it has been two days since i upgraded my software but since then i was
  not able to download other software from ubntu software sener

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-63.84~14.04.2-generic 4.4.44
  Uname: Linux 4.4.0-63-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Feb 19 21:46:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express 
Integrated Graphics Controller [8086:7270]
 Subsystem: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express 
Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2016-02-23 (362 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Apple Inc. MacBook2,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic 
root=UUID=9ecda836-300e-4f09-b579-cc61bb044a19 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB21.88Z.00A5.B07.0706270922
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4208CAA
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4208CAA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
  dmi.product.name: MacBook2,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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: Sun Feb 19 20:42:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40028 
   vendor APP
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Touch-packages] [Bug 1665286] Re: [unity8][qt] tiled app opens a transparent window "object types editor" when launched

2017-02-24 Thread Lukáš Tinkl
That warning is fixed by
https://code.launchpad.net/~aacid/qtubuntu/fix_unregistered_metatype_warning/+merge/317633

No idea if it also fixes the reported bug though

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

Title:
  [unity8][qt] tiled app opens a transparent window "object types
  editor" when launched

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8

  install tiled, apt install tiled
  launch tiled, you'll see a transparent window opened beneath the main window 
called "Object Types Editor"

  see attached screenshot

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

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


[Touch-packages] [Bug 1667503] Re: El sistema es muy lento

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

** Information type changed from Private Security to Public

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

Title:
  El sistema es muy lento

Status in xorg package in Ubuntu:
  New

Bug description:
  Utilizo ubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-80.88-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-80-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Feb 23 17:22:55 2017
  DistUpgraded: 2017-01-09 00:45:28,018 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9803] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:9082]
  InstallationDate: Installed on 2016-08-20 (187 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: Sony Corporation VPCYB10AL
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic 
root=UUID=0eb47a11-7bd6-4d5a-90c7-29f4fae24f9f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: Upgraded to vivid on 2017-01-09 (45 days ago)
  dmi.bios.date: 09/13/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0162Z7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0162Z7:bd09/13/2011:svnSonyCorporation:pnVPCYB10AL:pvrC9006R37:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCYB10AL
  dmi.product.version: C9006R37
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Feb 23 17:19:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1667372] Re: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

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

** Information type changed from Private Security to Public

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

Title:
  package python-decorator 4.0.6-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in python-decorator package in Ubuntu:
  New

Bug description:
  error message when boot system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-decorator 4.0.6-1
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Feb 22 22:16:54 2017
  Dependencies:
   
  DuplicateSignature:
   package:python-decorator:4.0.6-1
   Setting up python-decorator (4.0.6-1) ...
   /var/lib/dpkg/info/python-decorator.postinst: 6: 
/var/lib/dpkg/info/python-decorator.postinst: pycompile: not found
   dpkg: error processing package python-decorator (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-12-06 (78 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python-decorator
  Title: package python-decorator 4.0.6-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1667372/+subscriptions

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


[Touch-packages] [Bug 1667218] Re: Help bugs/system crashes

2017-02-24 Thread Marc Deslauriers
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  Help bugs/system crashes

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Please help I am exhausted and cannot take much more of life and need
  a F#% computer to work as I have NEVER had issues since ubuntu
  10.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 22 23:56:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2016-12-31 (53 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK Computer Inc. K54C
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54C.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54C
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54C.207:bd04/18/2012:svnASUSTeKComputerInc.:pnK54C:pvr1.0:rvnASUSTeKComputerInc.:rnK54C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54C
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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: Wed Feb 22 23:49:22 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 732 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://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 1666748] Re: Apparmor problem inside a lxd container

2017-02-24 Thread Simon Déziel
On 2017-02-22 02:19 PM, John Johansen wrote:
> You can try the set of kernel in
> 
> http://people.canonical.com/~jj/linux+jj/

I haven't had a chance to try those kernels but 4.4.0-65.86 has just hit
-proposed so I'll give it a try and report back, thanks.

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

Title:
  Apparmor problem inside a lxd container

Status in apparmor package in Ubuntu:
  New

Bug description:
  I've been running /usr/sbin/sshd in a custom Apparmor profile [*] for a long 
time and it works well.
  When I loaded the same profile in a lxd container (named ganymede), it didn't 
work at all:

  apparmor="DENIED" operation="file_perm" namespace="root//lxd-ganymede_
  " profile="/usr/sbin/sshd" pid=30870 comm="sshd"
  family="unix" sock_type="stream" protocol=0 requested_mask="send
  receive" denied_mask="send receive" addr=none peer_addr=none
  peer="---"

  Additional information about my environment:

  Both the host and the guest are up to date Xenials.

  root@jupiter:~# apt-cache policy linux-image-4.4.0-63-generic apparmor 
openssh-server
  linux-image-4.4.0-63-generic:
Installed: 4.4.0-63.84
Candidate: 4.4.0-63.84
Version table:
   *** 4.4.0-63.84 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
   *** 2.10.95-0ubuntu2.5 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.10.95-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  openssh-server:
Installed: 1:7.2p2-4ubuntu2.1
Candidate: 1:7.2p2-4ubuntu2.1
Version table:
   *** 1:7.2p2-4ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.2p2-4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  *: 
https://github.com/simondeziel/aa-profiles/blob/4d7fbd9fcca4bd62d97e8d0ba2cdc35e8d48d096/16.04/usr.sbin.sshd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 21:25:55 2017
  InstallationDate: Installed on 2016-12-19 (64 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161219)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic.efi.signed 
root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 
nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never
  PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree'
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >