date:20170829

** Changed in: openldap (Debian)
   Status: Unknown => New

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

Title:
  slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but
  /etc/ldap/slapd.d still exists

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

Bug description:
  after i install slapd and remove it's one of folders, couldnt do apt-
  get ugrade. It said problem about header

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.4
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   ldap-utils: Remove
   slapd: Remove
  Architecture: amd64
  Date: Tue Jul  4 15:22:00 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DpkgHistoryLog:
   Start-Date: 2017-07-04  15:21:46
   Commandline: apt-get remove slapd ldap-utils
   Remove: ldap-utils:amd64 (2.4.31-1+nmu2ubuntu8.4), slapd:amd64 
(2.4.31-1+nmu2ubuntu8.4)
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.4:subprocess installed 
pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-06-03 (761 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to trusty on 2016-05-30 (400 days ago)

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

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

[Touch-packages] [Bug 1713271] Re: Xdiagnose

2017-08-29 Thread Jean-Baptiste Lallement

Thanks for your report but it is too vague to be useful. Did you
experience an issue with Ubuntu that you want to report?

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

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

Title:
  Xdiagnose

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  no idea

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug 26 22:46:56 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Caicos [Radeon HD 
6450/7450/8450 / R5 230 OEM] [1787:3000]
  InstallationDate: Installed on 2017-08-22 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170813)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=02976af5-a2d1-4f31-9e30-cd802c721899 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0404
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LE/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0404:bd07/21/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLE/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS

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

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

Title:
  LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and
  STARTTLS

Status in openldap package in Ubuntu:
  New

Bug description:
  Tested with vivid and wily...
  also logged with openldap as 
http://www.openldap.org/its/index.cgi/Incoming?id=8374

  
  The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different
  between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs.

  When accessing server with a self-signed certificate, the results are:

  
  ldaps://

  neverOK
  hard Error: can't contact LDAP server
  demand   Error: can't contact LDAP server
  allowOK
  try  Error: can't contact LDAP server

  
  ldap:// plus explicit ldap_start_tls_s()

  neverOK
  hard OK
  demand   OK
  allowOK
  try  OK

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

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

[Touch-packages] [Bug 1702290] Re: slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but /etc/ldap/slapd.d still exists

** Bug watch added: Debian Bug tracker #873682
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873682

** Also affects: openldap (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873682
   Importance: Unknown
   Status: Unknown

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

Title:
  slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but
  /etc/ldap/slapd.d still exists

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

Bug description:
  after i install slapd and remove it's one of folders, couldnt do apt-
  get ugrade. It said problem about header

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.4
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   ldap-utils: Remove
   slapd: Remove
  Architecture: amd64
  Date: Tue Jul  4 15:22:00 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DpkgHistoryLog:
   Start-Date: 2017-07-04  15:21:46
   Commandline: apt-get remove slapd ldap-utils
   Remove: ldap-utils:amd64 (2.4.31-1+nmu2ubuntu8.4), slapd:amd64 
(2.4.31-1+nmu2ubuntu8.4)
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.4:subprocess installed 
pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-06-03 (761 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to trusty on 2016-05-30 (400 days ago)

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

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

[Touch-packages] [Bug 1701290] Re: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

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

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

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

Title:
  package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  Expired

Bug description:
  No idea what Im supposed to put here, Ubuntu asked me to report the
  error, so I did.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 29 15:48:29 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-17 (103 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: heimdal
  Title: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (76 days ago)

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

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

[Touch-packages] [Bug 1656979] Re: No support for DHE ciphers (TLS)

Hello Haw,

openldap 2.4.45 is in artful now, so this should be fixed. could you
please try your cipherscan again and confirm?

Thanks!

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

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

Title:
  No support for DHE ciphers (TLS)

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  Seems the OpenLDAP shipped with Xenial (and prior) built against
  GnuTLS does not support DHE cipher suites.

  | hloeung@ldap-server:~$ apt-cache policy slapd
  | slapd:
  |   Installed: 2.4.42+dfsg-2ubuntu3.1
  |   Candidate: 2.4.42+dfsg-2ubuntu3.1
  |   Version table:
  |  *** 2.4.42+dfsg-2ubuntu3.1 500
  | 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  2.4.42+dfsg-2ubuntu3 500
  | 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Our LDAP server is configured with the following:

  | TLSCertificateFile /etc/ssl/certs/ldap-server.crt
  | TLSCertificateKeyFile /etc/ssl/private/ldap-server.key
  | TLSCACertificateFile /etc/ssl/certs/ldap-server_chain.crt
  | TLSProtocolMin 1.0
  | TLSCipherSuite 
PFS:-VERS-SSL3.0:-DHE-DSS:-ARCFOUR-128:-3DES-CBC:-CAMELLIA-128-GCM:-CAMELLIA-256-GCM:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC:%SERVER_PRECEDENCE
  | TLSDHParamFile /etc/ssl/private/dhparams.pem

  I know TLSDHParamFile isn't used by OpenLDAP when built with GnuTLS,
  but thought I'd try anyways. cipherscan[1] shows the following list of
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 5 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 6 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1

  Even with TLSCipherSuite config commented out, we see the following
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 AES256-GCM-SHA384TLSv1.2None  
  None
  | 5 AES256-SHA256TLSv1.2None  
  None
  | 6 AES256-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 7 CAMELLIA256-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 8 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 9 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 10ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 11AES128-GCM-SHA256TLSv1.2None  
  None
  | 12AES128-SHA256TLSv1.2None  
  None
  | 13AES128-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 14CAMELLIA128-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 15ECDHE-RSA-DES-CBC3-SHA   TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 16DES-CBC3-SHA TLSv1,TLSv1.1,TLSv1.2  None  
  None

  I think the fix is in the patch below that's released in 2.4.39:

  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=622d13a32ec8d623c26a11b60b63e443dc86df99

  
  Thanks,

  Haw

  
  [1]https://github.com/jvehent/cipherscan

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

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

[Touch-packages] [Bug 1709384] Re: failed to unmount filesystems during shutdown, reboot hangs

2017-08-29 Thread ben thielsen

i've figured out at least part of this issue.

the system now no longer hangs at shutdown, but there are still
filesystems it complains it is unable to unmount, and the system still
hangs if it unable to unmount /home, which happens to be an nfs share
[i'm uncertain if this is of particular relevance, but it is a
characteristic unique among this system's filesystems].

the root cause was pam_systemd inadvertently excluded from the pam
session config, following customization.  this was causing another
problem [ssh sessions hanging during shutdown instead of being cleanly
terminated], and it was during troubleshooting of the ssh issue when it
hit me that there was a relationship between the two.

during shutdown, systemd brings down the network connection before ssh
processes are gracefully disconnected/terminated.  this leaves the
client unaware, thus the hanging symptom.

additionally, this appears to also leave processes active or files open,
etc., in various locations, and thus affected filesystems are still in
use and cannot be unmounted.  to make matters worse, when the filesystem
in use happens to be an nfs share [in this case,
/home/foo.example.com/], the system hangs at shutdown.

with pam_systemd properly configured in the pam session config, ssh
processes/sessions get to gracefully close, /home/foo.example.com/ and
/tmp/ are cleanly/successfully unmounted, and since the nfs share gets
unmounted, the system does not hang.  however, /var/ and /var/log/ still
fail to be unmounted:

Aug 30 03:27:09 template systemd[1]: Failed unmounting /var/log.
Aug 30 03:27:09 template systemd[1]: Failed unmounting /var.

this is still a problem which shouldn't be happening, but fortunately,
since it's only the nfs unmount fail that makes the system hang, reboots
aren't disastrous.

there are still issues here that need to be addressed:

1] under nominal conditions, filesystems should cleanly unmount.  unmounting 
should not fail.
2] if a filesystem fails to unmount [nfs or otherwise], the system should not 
hang during shutdown.

this can be recreated by doing the following:

• configure the system to mount an nfs share at boot [i used fstab].  it may 
also be enough to just mount an nfs share manually after boot
• disable pam_systemd in the pam session config
• ssh to the computer
• change directory into the nfs share, so the filesystem is in use
• reboot

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

Title:
  failed to unmount filesystems during shutdown, reboot hangs

Status in systemd package in Ubuntu:
  New

Bug description:
  i'd done a new install of 17.04, and this had been working ok.  this
  morning, i did an update, and now the system complains about being
  unable to unmount certain filesystems, as well as hanging during the
  shutdown process upon displaying "[ ok ] reached target shutdown"

  Aug  8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /var/log.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /tmp.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /home.
  Aug  8 16:11:49 template systemd[1]: Failed unmounting /var.

  1] >lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  2] >apt-cache policy systemd
  systemd:
Installed: 232-21ubuntu5
Candidate: 232-21ubuntu5
Version table:
   *** 232-21ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  3] i expected the system to not fail when unmounting filesystems during 
shutdown
  4] it did

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

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

[Touch-packages] [Bug 1702290] Re: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

Hello,

Since you deleted all the contents out of the /etc/ldap/slapd.d folder,
please delete that folder as well, then the uninstallation will proceed.

The init script could probably be more resilient about this.

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

** Summary changed:

- package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
+ slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but 
/etc/ldap/slapd.d still exists

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

Title:
  slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but
  /etc/ldap/slapd.d still exists

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  after i install slapd and remove it's one of folders, couldnt do apt-
  get ugrade. It said problem about header

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: slapd 2.4.31-1+nmu2ubuntu8.4
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   ldap-utils: Remove
   slapd: Remove
  Architecture: amd64
  Date: Tue Jul  4 15:22:00 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DpkgHistoryLog:
   Start-Date: 2017-07-04  15:21:46
   Commandline: apt-get remove slapd ldap-utils
   Remove: ldap-utils:amd64 (2.4.31-1+nmu2ubuntu8.4), slapd:amd64 
(2.4.31-1+nmu2ubuntu8.4)
  DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.4:subprocess installed 
pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-06-03 (761 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: openldap
  Title: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to trusty on 2016-05-30 (400 days ago)

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

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

[Touch-packages] [Bug 1474633] Re: Generic Text-Only driver does nothing

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

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

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

Title:
  Generic Text-Only driver does nothing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I believe that the Generic Text-Only printer driver is not functioning
  correctly.

   The Generic Text-Only driver does not seem to send anything to
  the printer.  A driver named "Generic Text-Only" should be sending
  text to the printer.  We can quibble about how many control codes are
  included in "text".

   I think the goal for a "Text-Only" printer should be that
  printing a file from a text editor should send the same data to the
  printer as copying the text file directly to the printer device (cat
  f.txt > /dev/usb/lp2).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:

  CurrentDesktop: Unity
  Date: Tue Jul 14 23:12:33 2015
  InstallationDate: Installed on 2014-09-05 (313 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for Brother-MFC-7820N: usb://Brother/MFC-7820N?serial=000C5J505362
   device for file-P1092i-on-usb: /tmp/file-P1092i-on-usb.prn
   device for P1092i-on-usb: parallel:/dev/usb/lp2
   device for Parallel-Brother: usb://Brother/MFC-7820N?serial=000C5J505362
  MachineType: Dell Inc. Inspiron One 2330
  Papersize: letter
  PpdFiles:
   P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended)
   Brother-MFC-7820N: Brother MFC-7820N Foomatic/Postscript
   Parallel-Brother: Brother MFC-7820N Foomatic/Postscript
   file-P1092i-on-usb: IBM ProPrinterII Foomatic/ibmpro (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=de488065-a683-4d49-89e1-8e33cac31e4b ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0HJH5X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 20485408280_1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/02/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn0HJH5X:rvrA00:cvnDellInc.:ct13:cvr20485408280_1:
  dmi.product.name: Inspiron One 2330
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

At https://bugs.launchpad.net/ubuntu/+source/open-
iscsi/+bug/1713537/comments/1 I described how open-iscsi (iscsi root)
works with resolvconf in xenial -> zesty.  We will need a solution for
that path as well as 'root=squashfs:http://./squashfs' that MAAS now
uses.

It seems like we should have a general path that covers 
 a.) dns working in initramfs (currently dns does not, it is missing 
libnss_dns.so.2)
 b.) network interfaces that are left up from initramfs getting resolvconf 
populated in the "real root".

My idea for this was just to have initramfs's configure_networking write
a file in /run/network/ that was then read by systemd-resolved when it
started.

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  New
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  New

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions

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

[Touch-packages] [Bug 1713880] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1713880/+attachment/4941116/+files/StacktraceSource.txt

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1713880] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1713880/+attachment/4941117/+files/ThreadStacktrace.txt

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

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1713880] Stacktrace.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1713880/+attachment/4941115/+files/Stacktrace.txt

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1713880] glib-compile-schemas crashed with SIGSEGV in GI_libc_free()

StacktraceTop:
 __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
 g_free (mem=) at ../../../../glib/gmem.c:189
 g_strfreev (str_array=0x85ed14a110) at ../../../../glib/gstrfuncs.c:2497
 set_overrides (strict=0, files=0x85ed0d3300, schema_table=0x85ed0c5120) at 
../../../../gio/glib-compile-schemas.c:2115
 main (argc=, argv=) at 
../../../../gio/glib-compile-schemas.c:2269

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1713880] [NEW] glib-compile-schemas crashed with SIGSEGV in GI_libc_free()

2017-08-29 Thread Chris Hermansen

Public bug reported:

Not a lot,really - a massive number of packages upgraded in Artful,
rebooted with systemctl,then this happened after logging in and before
firing anything else up.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libglib2.0-0 2.53.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Tue Aug 29 17:34:27 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
InstallationDate: Installed on 2017-07-27 (33 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:mov
(%rax),%rdi
 PC (0x7f4dda0a1d52) ok
 source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: glib2.0
StacktraceTop:
 __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
 ?? ()
Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Not a lot,really - a massive number of packages upgraded in Artful,
  rebooted with systemctl,then this happened after logging in and before
  firing anything else up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.53.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Aug 29 17:34:27 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  InstallationDate: Installed on 2017-07-27 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 
/usr/share/glib-2.0/schemas
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f4dda0a1d52 <__GI___libc_free+66>:  mov
(%rax),%rdi
   PC (0x7f4dda0a1d52) ok
   source "(%rax)" (0x85ec00) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   __GI___libc_free (mem=0x85ed2155c0) at malloc.c:2984
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x85eca02fe0, argc=2, argv=0x7ffc56b3feb8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc56b3fea8) at ../csu/libc-start.c:291
   ?? ()
  Title: glib-compile-schemas crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 385687] Re: EOG doesn't display .svg w/ multiple lines of text properly

** Changed in: librsvg
   Status: In Progress => Fix Released

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

Title:
  EOG doesn't display .svg w/ multiple lines of text properly

Status in librsvg:
  Fix Released
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: eog

  Both in previews in nautilus (which comes from eog, I think?) and in
  EOG itself, SVGs that have multiple lines of text in one 'box' show up
  as a solid box where you would expect to see text. By the way, the
  SVGs where made with inkscape. In fact, I'll attach them to this bug
  report.

  Ubuntu version:
  Description:  Ubuntu 9.04
  Release:  9.04

  apt-cache policy eog
  eog:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
   *** 2.26.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com jaunty/main Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2017-08-29 Thread Martin Wimpress

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

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in ubuntu-mate:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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

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

[Touch-packages] [Bug 1711255] Re: systemd RestartSec does not seem to work consistently

2017-08-29 Thread Leo Davis

>A minimal working reproducer with e.g. ExecStart=/bin/false would be
useful. To remove the >uncertainties w.r.t. executables involved. As I
do not have access to the masked product.

OK, I'll try and reproduce it with that.

>Is this reproducible in Ubuntu Artful which has much newer systemd?

Never tried running our software on Artful since Xenial is our current
target platform.

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

Title:
  systemd RestartSec does not seem to work consistently

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The unit file for my service -33005.service:

  [Unit]
  Description=product  33005 service
  Wants=some.mount
  After=some.mount
  PartOf=product.target
  PartOf=someother.service
  [Service]
  Type=simple
  ExecStart=/opt/product/bin/ -conf=/etc/product.conf
  Restart=on-failure
  User=product
  Group=product
  LimitCORE=infinity
  LimitNOFILE=1
  Slice=.slice
  WatchdogSec=120
  RestartSec=10
  StartLimitInterval=120
  StartLimitBurst=10
  [Install]
  WantedBy=product.target

  specifies RestartSec=10, which is also what systemd sees:

  $ systemctl show -33005.service
  Type=simple
  Restart=on-failure
  NotifyAccess=main
  RestartUSec=10s
  ...

  However, today I saw in the journalctl log:
  $ journalctl -u -33005.service
  ...
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Watchdog timeout 
(limit 2min)!
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:28:39 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:28:39 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:28:39 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Stopping product  33005 service...
  Aug 15 23:28:45 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:33:51 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:33:51 a-hostname [3629]: Get http://127.0.0.1:8081/: dial tcp 
127.0.0.1:8081: getsockopt: connection refused
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:34:01 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:34:02 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: -33005.service: Start request 
repeated too quickly.
  Aug 15 23:34:02 a-hostname systemd[1]: Failed to start product  33005 
service.

  Everything looks to me that systemd is behaving as expected until Aug
  15 23:34:02 when it attempts to start -33005.service not at the
  rate I specified in RestartSec, but possibly at the default 100ms
  rate.  This excerpt shows both the expected 10s restart rate as well
  as the unexpected restart rate.

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ uname -a
  Linux a-hostname 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu16
    Candidate: 229-4ubuntu19
    Version table:
   229-4ubuntu19 500
  500 http://internal-repo/ubuntu xenial-updates/main amd64 Packages
   *** 229-4ubuntu16 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://internal-repo/ubuntu xenial-security/main amd64 Packages
   229-4ubuntu4 500
  500 http://internal-repo/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.la

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

2017-08-29 Thread Brian Murray

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

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

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Confirmed
Status in apt-file package in Ubuntu:
  Confirmed
Status in aptitude package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  New

Bug description:
  apt-file is now difficult to use with about a dozen warnings like
  this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

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

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

[Touch-packages] [Bug 1712433] Re: man page typo

2017-08-29 Thread Brian Murray

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  man mount contains the following section:

  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
     parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
     wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  The word 'strogly' should be 'strongly'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

2017-08-29 Thread Vinson Lee

artful preseed installs are still failing for me because of hostname
resolutions during in-target.

After base-installer completes, the in-target installation fails to
resolve the artful repositories. The target has /etc/resolv.conf but
/etc/resolv.conf is not working or available through in-target. in-
target is missing the entire /run/systemd directory.

# chroot /target ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Aug 29 22:32 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

# chroot /target ls -l /run/systemd/resolve/
total 4
-rw-r--r-- 1 root root 89 Aug 29 22:32 stub-resolv.conf

# chroot /target cat /etc/resolv.conf
search 
nameserver 

# chroot /target ls -l /run
total 12
drwxrwxrwt 2 root root 4096 Aug 29 22:30 lock
drwxr-xr-x 2 root root 4096 Aug 29 22:30 mount
drwxr-xr-x 3 root root 4096 Aug 29 22:32 systemd
-rw-rw-r-- 1 root utmp0 Aug 29 22:30 utmp


# in-target ls -l /etc/resolv.conf
Aug 29 22:37:04 in-target: lrwxrwxrwx 1 root root 39 Aug 29 22:32 
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

# in-target ls -l /run/systemd/resolve/
Aug 29 22:40:27 in-target: ls: cannot access '/run/systemd/resolve/'
Aug 29 22:40:27 in-target: : No such file or directory

# in-target cat /etc/resolv.conf
Aug 29 22:41:48 in-target: cat: /etc/resolv.conf
Aug 29 22:41:48 in-target: : No such file or directory

# in-target ls -l /run/
Aug 29 22:44:32 in-target: total 0
Aug 29 22:44:32 in-target: drwxr-xr-x 2 root root  40 Aug 29 22:26 lock
Aug 29 22:44:32 in-target: drwxr-xr-x 2 root root  60 Aug 29 22:26 mount
Aug 29 22:44:32 in-target: drwxr-xr-x 4 root root 100 Aug 29 22:30 udev

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

also, we got new network-manager in artful which may have regressed.

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

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

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

@msaxl

for both examples, can you please attach the existing configs for
ifupdown, network-manager, and networkd? As in the contents of
/etc/network/interfaces /etc/NetworkManager and output of udevadm info
on the interface and contents of /etc/systemd/network?

I want to reproduce these bugs and verify what the current behaviour is
both for upgrade and clean-install cases, and figure out all the bugs /
inconsistencies present to fix any upgrade/clean-install issues.

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

Title:
  systemd-networkd messes up networking

Status in ifupdown package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Oh, my mistake. The journal log was attached and had this bit of info:
Aug 28 14:36:40 hostname sshd[21687]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
Aug 28 14:36:40 hostname sshd[21687]: error: Bind to port 22 on :: failed: 
Address already in use.
Aug 28 14:36:40 hostname sshd[21687]: fatal: Cannot bind any address.
Aug 28 14:36:40 hostname systemd[1]: Failed to start OpenBSD Secure Shell 
server.
Aug 28 14:36:40 hostname systemd[1]: ssh.service: Failed with result 
'exit-code'.

Looks like something else was already listening on ssh's port.

In addition to the status command from my previous command, please also attach 
the output of the following ones:
- ps fauxw
- sudo netstat -anp

Thanks!

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713248] Re: pubkey auth hangs on high latency networks

I'm going to set this to incomplete until there is more information.

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

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

Title:
  pubkey auth hangs on high latency networks

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  This is a weird one. I use a small fleet of laptops to do professional
  network testing, and I wrote some tools that use SSH with pubkey auth
  to run simultaneous tests.

  The problem is, if the wifi connection isn't superb, the auth times
  out more often than not. For example, if I've got a long range 5 GHz
  connection which returns 100% of pings but has a median latency of
  100ms or so, auth hangs after send packet: type 50, never receiving
  the packet type 51 to complete the auth.

  debug2: key: /root/.ssh/id_ecdsa ((nil))
  debug2: key: /root/.ssh/id_ed25519 ((nil))
  debug3: send packet: type 5
  debug3: receive packet: type 6
  debug2: service_accept: ssh-userauth
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug3: send packet: type 50

  This is where it hangs; after approximately a 30 second timeout
  (haven't clocked it precisely) it falls through to any remaining
  available authentication methods - other keys, hostbased, password,
  whatever hasn't been explicitly disabled.

  Yes, UseDNS no is on, on both client and sender. I've also disabled
  all non-essential PAM modules, and disabled HostBasedAuth, RSAAuth,
  and GSSAPI on both client and sender.

  The same two laptops in the same location will complete password
  authentication without a problem - if a pubkey is present for the user
  on the client side, it'll have to time that out first before it fails
  through and asks for the password (which will be promptly accepted and
  work normally); but if there is no pubkey for the client user, it'll
  prompt for the password and accept it immediately.

  If I move the server laptop closer to the router, so that the median
  latency falls in something more like the 50ms range, the pubkey auth
  works fine. I want to reiterate here that we're talking about high
  latency, but we're *not* talking about dropped packets - pings between
  the laptops when they're having problems range from 100ms-900ms
  latency, but with 100% returns. (And, again, password auth works fine,
  it's only pubkey that has the issue - and only when latency is high.)

  I can't find anything on the internets referring to a problem with
  high latency pubkey authentication on machines where pubkey auth works
  fine with lower latency, but here I am.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 26 12:04:22 2017
  InstallationDate: Installed on 2016-11-05 (293 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1713248/+subscriptions

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

[Touch-packages] [Bug 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thanks for filing this bug in Ubuntu.

The provided logs unfortunately do not have enough information to
properly diagnose the problem.

Could you please attach the output of the command below to this bug?

sudo systemctl status ssh.service

Thanks


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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713808] Re: please switch the default bug category to something else than "Display"

this would put "Other" in the top

--- a/apport/ui.py  2017-08-29 22:53:02.0 +0300
+++ b/apport/ui.py  2017-08-29 23:47:24.476337087 +0300
@@ -618,10 +619,8 @@
 
 symptom_descriptions, symptom_names = \
 zip(*sorted(zip(symptom_descriptions, symptom_names)))
-symptom_descriptions = list(symptom_descriptions)
-symptom_names = list(symptom_names)
-symptom_names.append(None)
-symptom_descriptions.append('Other problem')
+symptom_descriptions = ['Other problem'] + list(symptom_descriptions)
+symptom_names = [None] + list(symptom_names)
 
 ch = self.ui_question_choice(_('What kind of problem do you want to 
report?'),
  symptom_descriptions, False)

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport package in Ubuntu:
  New

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2017-08-29 Thread peacecop kalmer:

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

I confirm the bug on 17.04. Creating the file
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf didn't solve
the problem.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Touch-packages] [Bug 1713808] Re: please switch the default bug category to something else than "Display"

huh, "Other problem" doesn't seem to do anything but say that a package
is needed..

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport package in Ubuntu:
  New

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-08-29 Thread Bogdan Arabadzhi

Started working for me about yesterday, but then dropped again.
I use .domain vpn and no .domain get resolved by the system.
It was ok about a week ago, then not working, working for a day, then again - 
none.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-08-29 Thread Bogdan Arabadzhi

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2017-08-29 22:12:30 CEST; 36s ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
  Process: 3497 ExecStartPre=/bin/sh -c [ ! -s /etc/resolv.conf ] && ln -snf 
../run/systemd/resolve/stub-resolv.conf (code=exited, status=1/FAILURE)
 Main PID: 3498 (systemd-resolve)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
   └─3498 /lib/systemd/systemd-resolved

Aug 29 22:12:30 laptop systemd[1]: Starting Network Name Resolution...
Aug 29 22:12:30 laptop systemd-resolved[3498]: Positive Trust Anchors:
Aug 29 22:12:30 laptop systemd-resolved[3498]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 29 22:12:30 laptop systemd-resolved[3498]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 29 22:12:30 laptop systemd-resolved[3498]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19
Aug 29 22:12:30 laptop systemd-resolved[3498]: Using system hostname 'laptop'.
Aug 29 22:12:30 laptop systemd[1]: Started Network Name Resolution.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1713813] Re: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I keep gettin an error that I am out of space on /boot
  This is a default Ubuntu install, so I'd figure y'all would have the default 
/boot partition be the proper size.

  I executed:
  sudo apt-get autoremove linux-image-4.4.0.66-generic

  And this error popped up.

  There has got to be a better way to manage new and old linux images.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mamanakisdm   4396 F pulseaudio
   /dev/snd/pcmC1D0c:   mamanakisdm   4396 F...m pulseaudio
   /dev/snd/pcmC1D0p:   mamanakisdm   4396 F...m pulseaudio
   /dev/snd/controlC1:  mamanakisdm   4396 F pulseaudio
  Date: Tue Aug 29 14:10:50 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=a6ba8e97-6214-4c0c-8267-f063b5e54c12
  InstallationDate: Installed on 2016-11-22 (280 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BHS02400
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root 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.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET66WW (2.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET66WW(2.14):bd07/02/2014:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1713808] Re: please switch the default bug category to something else than "Display"

ok the magic happens in apport/ui.py

** Package changed: apport-symptoms (Ubuntu) => apport (Ubuntu)

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport package in Ubuntu:
  New

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713813] [NEW] package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-08-29 Thread David Mamanakis

Public bug reported:

I keep gettin an error that I am out of space on /boot
This is a default Ubuntu install, so I'd figure y'all would have the default 
/boot partition be the proper size.

I executed:
sudo apt-get autoremove linux-image-4.4.0.66-generic

And this error popped up.

There has got to be a better way to manage new and old linux images.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mamanakisdm   4396 F pulseaudio
 /dev/snd/pcmC1D0c:   mamanakisdm   4396 F...m pulseaudio
 /dev/snd/pcmC1D0p:   mamanakisdm   4396 F...m pulseaudio
 /dev/snd/controlC1:  mamanakisdm   4396 F pulseaudio
Date: Tue Aug 29 14:10:50 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=a6ba8e97-6214-4c0c-8267-f063b5e54c12
InstallationDate: Installed on 2016-11-22 (280 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20BHS02400
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root 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.2
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GNET66WW (2.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BHS02400
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGNET66WW(2.14):bd07/02/2014:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20BHS02400
dmi.product.version: ThinkPad W540
dmi.sys.vendor: LENOVO

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

Title:
  package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I keep gettin an error that I am out of space on /boot
  This is a default Ubuntu install, so I'd figure y'all would have the default 
/boot partition be the proper size.

  I executed:
  sudo apt-get autoremove linux-image-4.4.0.66-generic

  And this error popped up.

  There has got to be a better way to manage new and old linux images.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mamanakisdm   4396 F pulseaudio
   /dev/snd/pcmC1D0c:   mamanakisdm   4396 F...m pulseaudio
   /dev/snd/pcmC1D0p:   mamanakisdm   4396 F...m pulseaudio
   /dev/snd/controlC1:  mamanakisdm   4396 F pulseaudio
  Date: Tue Aug 29 14:10:50 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=a6ba8e97-6214-4c0c-8267-f063b5e54c12
  InstallationDate: Installed on 2016-11-22 (280 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BHS02400
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root 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.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET66WW (2.14 )
  dmi.board.ass

Re: [Touch-packages] [Bug 1370953] Re: layout switch is delayed

2017-08-29 Thread Alexey Nezhdanov

Alex, how much did you pay for your copy of Ubuntu?

The problem is frustrating, but:
1) these people don't owe you anything
2) this is FOSS - go and do it yourself
3) solutions do exist.

Drop that tone!

Am 29.08.2017 9:55 nachm. schrieb "Alex" :

> what the f*cking bullshit 21st century and you can't solve this
> annoying bug during several years??? F*ck your bloody UNITY and solve this
> simplest and most important problem!!!
> how to use the system if not possible to switch layout normally???
> shit! shit! shit!
>
> Ubuntu 17.04
>
> uname -a
> Linux 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 i686
> i686 i686 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370953
>
> Title:
>   layout switch is delayed
>
> Status in console-setup package in Ubuntu:
>   Confirmed
> Status in gconf package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have two layouts configured En and Ru with Ctrl-Shift as layout
>   switch combo.
>
>   When I start typing in wrong layout I notice it, hit Ctrl-Shift and type
> again, but more often than not it is wrong layout again.
>   I repeat the action, but there is no luck. On the third attemt it
> usually either works OR the first letter is still in wrong layout, but the
> second is in correct one - i.e. layout switches as I type.
>
>   The explanation for this is that layout switch takes very unreasonable
>   time - much longer than it is needed to move your fingers from  one
>   key to the other. Each time I encounter the error I retry slower so on
>   the third attempt it is slow enough to actually recognize that layout
>   switch is happening, but with a delay.
>
>   This is extremely annoying and unacceptable. If someone knows how to
>   work around it - please post your suggestions here. It would be nice
>   to have a solution for 3+ layouts setup as well.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/console-setup/+
> bug/1370953/+subscriptions
>

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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

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

[Touch-packages] [Bug 1713808] [NEW] please switch the default bug category to something else than "Display"

You have been subscribed to a public bug:

People use ubuntu-bug to file bugs, and they get a dialog which has the
default bug category selected as "Display (X.org)". Looks like many
don't bother to change that, so please switch the default to "Other
problem" so that 'xorg' doesn't get to be the default target for poor
quality bugs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
CurrentDesktop: Unity
Date: Tue Aug 29 22:55:21 2017
InstallationDate: Installed on 2016-01-12 (595 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
please switch the default bug category to something else than "Display"
https://bugs.launchpad.net/bugs/1713808
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

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

[Touch-packages] [Bug 1711870] Re: Praticamente todas as atualizações apresentaram erro.

you need to use english here..

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

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

Title:
  Praticamente todas as atualizações apresentaram erro.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  As atualizações não poderam ser concluidas. Varios erros surgiram
  durante o processo de atualização

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 19 20:46:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-08-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=689bf1e6-7c78-4ddc-bfd6-07b7238d444c ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  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: Sat Aug 19 20:31:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.4

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

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

[Touch-packages] [Bug 1713189] Re: Got stop job running c1 session

has nothing to do with xorg?

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

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

Title:
  Got stop job running c1 session

Status in Ubuntu:
  New

Bug description:
  Got stop job running c1 session, takes long time to shutdown the pc

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 25 20:02:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8079]
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=bfd4a0da-f910-4231-82fd-4627708c9adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1713808] [NEW] please switch the default bug category to something else than "Display"

Public bug reported:

People use ubuntu-bug to file bugs, and they get a dialog which has the
default bug category selected as "Display (X.org)". Looks like many
don't bother to change that, so please switch the default to "Other
problem" so that 'xorg' doesn't get to be the default target for poor
quality bugs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.10
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
CurrentDesktop: Unity
Date: Tue Aug 29 22:55:21 2017
InstallationDate: Installed on 2016-01-12 (595 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Package changed: apport (Ubuntu) => apport-symptoms (Ubuntu)

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

Title:
  please switch the default bug category to something else than
  "Display"

Status in apport-symptoms package in Ubuntu:
  New

Bug description:
  People use ubuntu-bug to file bugs, and they get a dialog which has
  the default bug category selected as "Display (X.org)". Looks like
  many don't bother to change that, so please switch the default to
  "Other problem" so that 'xorg' doesn't get to be the default target
  for poor quality bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog: Error: [Errno 13] Lupa evätty: '/var/log/apport.log'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports: 644:0:115:6370:2017-08-28 14:06:11.247022082 +0300:2017-08-28 
14:06:11.247022082 +0300:/var/crash/i915-4.7-4.4-dkms.0.crash
  CurrentDesktop: Unity
  Date: Tue Aug 29 22:55:21 2017
  InstallationDate: Installed on 2016-01-12 (595 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1370953] Re: layout switch is delayed

2017-08-29 Thread Alex

what the f*cking bullshit 21st century and you can't solve this annoying 
bug during several years??? F*ck your bloody UNITY and solve this simplest and 
most important problem!!!
how to use the system if not possible to switch layout normally???
shit! shit! shit!

Ubuntu 17.04

uname -a
Linux 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 i686 i686 
i686 GNU/Linux

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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

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

[Touch-packages] [Bug 1632681] Re: SonicWall NetExteder broken by new nsswitch.conf configuration

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

Title:
  SonicWall NetExteder broken by new nsswitch.conf configuration

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  
  In Ubuntu Yakkety the following line in /etc/nsswitch.conf breaks DNS 
resolution via the VPN tunnel created by Sonicwall NetExtender application. 

  
  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns 

  
  Changing this line to:

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve
  [UNAVAIL=return] dns

  or

  hosts: files mdns4_minimal [NOTFOUND=return] dns
  [!UNAVAIL=return] resolve

  
  I have not found documentation on what "resolve" means, so im not sure this 
lines makes global sense, but it solve my dns problem. If i have to guess its 
another systemd incarnation.

  As a side note NetExtender modifies /etc/resolv.conf and adds the VPN
  DNS servers as the first entries. So when NetExtender is connected the
  first lines in /etc/resolv.conf contains the VPN DNS IP and only after
  there is the local dnsmasq entry.

  Sadly i could not found which package creates this file as "dpkg-query
  -S /etc/nsswitch.conf" returns no results on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss3 2:3.26-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 12 13:58:41 2016
  InstallationDate: Installed on 2016-07-27 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nss
  UpgradeStatus: Upgraded to yakkety on 2016-10-07 (4 days ago)

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

I've added open-iscsi and cloud-initramfs-tools and initramfs-tools as also 
affects.
These packages are affected by the generic problem where 'configure_networking' 
from initramfs-tools is executed in the initramfs ('ip=dhcp' for example) and 
then the link is left up. In those cases we need to apply the /etc/resolv.conf 
changes from the initramfs to the "real root".  I described how this *did* work 
for the open-iscsi package in the past, but there was no centralized handling 
of it (although there should have been).



** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  New
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  New

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions

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

[Touch-packages] [Bug 1713803] [NEW] replacement of resolvconf with systemd needs integration

Public bug reported:

There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
 * hooks invoked on change (/etc/resolvconf/update.d/)
 * resolvconf tool (invoked with -a and -d or -u)

Packages which install files into /etc/resolvconf/update.d are:
- dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
  caching path).
- resolvconf: This probably isn't necessary in systemd-resolved path.
- unbound: This is another "validating, recursive, caching DNS resolver".

The list of Depends/Suggests/Recommends on resolvconf.

# for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
depends android-androresolvd
recommends avahi
recommends dhcpcd5
recommends dibbler
recommends ndisc6
recommends whereami
suggests bind9
suggests dnscrypt-proxy
suggests dnsmasq
suggests dnssec-trigger
suggests fetchmail
suggests freedombox-setup
suggests isc-dhcp
suggests netscript-2.4
suggests openvpn
suggests postfix
suggests pppconfig
suggests pump
suggests resolvconf
suggests sendmail
suggests squid3
suggests vpnc
suggests vpnc-scripts

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
Date: Tue Aug 29 18:53:50 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation

Related bugs:
 * bug 1698181: Switch to netplan renderer in Artful

** Affects: android-androresolvd (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Affects: dnscrypt-proxy (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: dnssec-trigger (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: netscript-2.4 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: open-iscsi (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

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

** Affects: vpnc-scripts (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug artful uec-images

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

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

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

** Also affects: android-androresolvd (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
-  * hooks invoked on change (/etc/resolvco

[Touch-packages] [Bug 1311525] Re: Can only use half the sound range without overdriving sound

2017-08-29 Thread Mark Rose

I've been encountering this on an Asus Z97 Extreme6 under Kubuntu 16.04.

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

Title:
  Can only use half the sound range without overdriving sound

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On a Nvidia CK804 (Asus A8N SLI Premium), the audio can only be set to
  "base" (63 %) without overdriving the sound. This is because 0db (100
  %) is reported wrong in pulseaudio; when seen in alsamixer it actually
  sets PCM to 12db, causing distortions.

  According to PulseAudio this is a bug in the alsa driver

  
http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-April/013249.html
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes/

  "If you are experiencing distortions/clipping even though the inner
  volumes are set to 0dB, then this means that the dB information your
  ALSA driver exports is simply incorrect. In this case please file a
  bug against your audio driver and ask them to correct (i.e. shift up)
  the volume scale of that volume control."

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alad   2110 F pulseaudio
   /dev/snd/pcmC0D0p:   alad   2110 F...m pulseaudio
   /dev/snd/controlC1:  alad   2110 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 23 10:18:29 2014
  InstallationDate: Installed on 2014-04-20 (2 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-SLI Premium ACPI BIOS Revision 1303
  dmi.board.name: A8N-SLI Premium
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIPremiumACPIBIOSRevision1303:bd08/10/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIPremium:rvr1.02:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-23T01:09:11.857997

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

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

[Touch-packages] [Bug 1311525] Re: Can only use half the sound range without overdriving sound

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

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

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

Title:
  Can only use half the sound range without overdriving sound

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  On a Nvidia CK804 (Asus A8N SLI Premium), the audio can only be set to
  "base" (63 %) without overdriving the sound. This is because 0db (100
  %) is reported wrong in pulseaudio; when seen in alsamixer it actually
  sets PCM to 12db, causing distortions.

  According to PulseAudio this is a bug in the alsa driver

  
http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-April/013249.html
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes/

  "If you are experiencing distortions/clipping even though the inner
  volumes are set to 0dB, then this means that the dB information your
  ALSA driver exports is simply incorrect. In this case please file a
  bug against your audio driver and ask them to correct (i.e. shift up)
  the volume scale of that volume control."

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alad   2110 F pulseaudio
   /dev/snd/pcmC0D0p:   alad   2110 F...m pulseaudio
   /dev/snd/controlC1:  alad   2110 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 23 10:18:29 2014
  InstallationDate: Installed on 2014-04-20 (2 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-SLI Premium ACPI BIOS Revision 1303
  dmi.board.name: A8N-SLI Premium
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIPremiumACPIBIOSRevision1303:bd08/10/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIPremium:rvr1.02:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-23T01:09:11.857997

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

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

[Touch-packages] [Bug 1711020] Re: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I don't know. System alerted me of an issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-91-generic 4.4.0-91.114
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   linux-headers-4.4.0-91-generic: Remove
   linux-headers-4.4.0-91: Remove
   linux-image-extra-4.4.0-91-generic: Remove
   linux-image-4.4.0-91-generic: Remove
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wayne  1743 F pulseaudio
  Date: Tue Aug 15 22:48:09 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac
  InstallationDate: Installed on 2016-12-17 (241 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire 5733Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 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.12
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5733Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.name: Aspire 5733Z
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1713794] [NEW] Ubuntu sleeps when folding display back into tablet mode.

2017-08-29 Thread Patrick Watson

Public bug reported:

(I just wanted to add sorry if this is in the wrong category, Ubuntu-bug does 
not have a section for power/sleep-related issues)
My Panasonic CF-AX2 folds back to become a tablet, in Windows, the default 
action is to rotate the screen/disable the keyboard and trackpad but in Ubuntu 
it thinks I am putting the laptop to sleep when I fold it back into tablet mode.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.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
CurrentDesktop: Unity:Unity7
Date: Tue Aug 29 19:29:04 2017
DistUpgraded: 2017-04-16 06:38:32,451 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Matsushita Electric Industrial Co., Ltd. 3rd Gen Core processor 
Graphics Controller [10f7:8338]
InstallationDate: Installed on 2016-11-08 (293 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Panasonic Corporation CF-AX2LDWHCE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1d7f9400-64cb-4220-a1f6-b0c4f4f01c65 ro console=tty12 quiet 
processor.ignore_ppc=1 intel_pstate=disable
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-04-16 (135 days ago)
dmi.bios.date: 08/22/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.50L12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CFAX2-1
dmi.board.vendor: Panasonic Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Panasonic Corporation
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.50L12:bd08/22/2013:svnPanasonicCorporation:pnCF-AX2LDWHCE:pvr001:rvnPanasonicCorporation:rnCFAX2-1:rvr1:cvnPanasonicCorporation:ct10:cvr001:
dmi.product.name: CF-AX2LDWHCE
dmi.product.version: 001
dmi.sys.vendor: Panasonic Corporation
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.80+git1704160630.f45853~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1704151930.566f2e~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1704151930.566f2e~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue Aug 29 19:23:12 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputDP-1  HDMI-1 
 LVDS-1   VGA-1
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu zesty

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

Title:
  Ubuntu sleeps when folding display back into tablet mode.

Status in xorg package in Ubuntu:
  New

Bug description:
  (I just wanted to add sorry if this is in the wrong category, Ubuntu-bug does 
not have a section for power/sleep-related issues)
  My Panasonic CF-AX2 folds back to become a tablet, in Windows, the default 
action is to rotate the screen/disable the keyboard and trackpad but in Ubuntu 
it thinks I am putting the laptop to sleep when I fold it back into tablet mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.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
  CurrentDesktop: Unity:Unity7
  Date: Tue Aug 29 19:29:04 2017
  DistUpgraded: 2017-04-16 06:38:32,451 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Cor

[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2017-08-29 Thread Ismael Mendoza

It seems that Lenovo Yoga 300 also has the same problem. I reported Bug
#1713784.

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

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

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

[Touch-packages] [Bug 1712701] Re: Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

** Changed in: gtk+3.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  This bug affects gtk3 >= 3.22.18.1.

  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22&id=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.

  Note that this bug has already been reported in Arch and Debian.

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

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

[Touch-packages] [Bug 1713784] [NEW] Yoga 300 laptop Inverted Internal microphone

2017-08-29 Thread Ismael Mendoza

Public bug reported:

It seems that this laptop is affected by the same issue described here:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978

We have tried several workaround but need a definite fix.

Please see attached the alsa file.

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

** Attachment added: "alsa-info-yoga-300.txt"
   
https://bugs.launchpad.net/bugs/1713784/+attachment/4940930/+files/alsa-info-yoga-300.txt

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

Title:
  Yoga 300 laptop Inverted Internal microphone

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It seems that this laptop is affected by the same issue described
  here: https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1002978

  We have tried several workaround but need a definite fix.

  Please see attached the alsa file.

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

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

[Touch-packages] [Bug 1713775] [NEW] [USB-Audio - Logitech BRIO, recording] fails on suspend/resume

2017-08-29 Thread Rhett Aultman

Public bug reported:

My Logitech BRIO webcam's mic doesn't pass audio after suspend/resume
cycles on my desktop.  The ALSA interfaces are present and the mic
devices appear in pulseaudio and the Ubuntu audio settings applet, but
no audio is seen via arecord or the volume meter in the audio settings
applet.

It doesn't happen on every suspend/resume and I'm trying to establish
the pattern.  I think it may be that this happens only on suspend/resume
where a handle to the mic was left open.  For example, it took 3
suspend/resume cycles to generate this error report, and the one that
finally reproed the issue was the one where I left the mic selection
panel of the audio settings panel open.  I think the open handle to the
mic to supply the volume meter may have been what broke it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0c:   rhett   421 F...m pulseaudio
 /dev/snd/controlC2:  rhett   421 F pulseaudio
 /dev/snd/controlC0:  rhett   421 F pulseaudio
 /dev/snd/controlC1:  rhett   421 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 29 12:53:04 2017
InstallationDate: Installed on 2016-11-21 (280 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Logitech BRIO - Logitech BRIO
Symptom_Type: Sound works for a while, then breaks
Title: [USB-Audio - Logitech BRIO, recording] fails after a while
UpgradeStatus: Upgraded to xenial on 2017-07-24 (36 days ago)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2202
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

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

Title:
  [USB-Audio - Logitech BRIO, recording] fails on suspend/resume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My Logitech BRIO webcam's mic doesn't pass audio after suspend/resume
  cycles on my desktop.  The ALSA interfaces are present and the mic
  devices appear in pulseaudio and the Ubuntu audio settings applet, but
  no audio is seen via arecord or the volume meter in the audio settings
  applet.

  It doesn't happen on every suspend/resume and I'm trying to establish
  the pattern.  I think it may be that this happens only on
  suspend/resume where a handle to the mic was left open.  For example,
  it took 3 suspend/resume cycles to generate this error report, and the
  one that finally reproed the issue was the one where I left the mic
  selection panel of the audio settings panel open.  I think the open
  handle to the mic to supply the volume meter may have been what broke
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0c:   rhett   421 F...m pulseaudio
   /dev/snd/controlC2:  rhett   421 F pulseaudio
   /dev/snd/controlC0:  rhett   421 F pulseaudio
   /dev/snd/controlC1:  rhett   421 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 29 12:53:04 2017
  InstallationDate: Installed on 2016-11-21 (280 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Logitech BRIO - Logitech BRIO
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - Logitech BRIO, recording] fails after a while
  UpgradeStatus: Upgraded to xenial on 2017-07-24 (36 days ago)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: Default string
  dmi.board.name

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

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get update
  Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease  
 
  Hit:2 http://dl.google.com/linux/chrome/deb stable Release
 
  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [92.2 kB]   
 
  Hit:4 http://in.archive.ubuntu.com/ubuntu xenial InRelease
 
  Hit:6 http://archive.canonical.com/ubuntu xenial InRelease
 
  Get:7 http://in.archive.ubuntu.com/ubuntu xenial-updates InRelease [93.3 kB]  
 
  Fetched 185 kB in 2s (78.3 kB/s)  
 
  Reading package lists... Done
  W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature 
by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm 
(SHA1)
  W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature 
by key 3B068FB4789ABE4AEFA3BB491397BC53640DB551 uses weak digest algorithm 
(SHA1)

  
  sudo apt-get install initramfs-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
initramfs-tools
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 8,592 B of archives.
  After this operation, 126 kB of additional disk space will be used.
  Get:1 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 initramfs-tools 
all 0.122ubuntu8 [8,592 B]
  Fetched 8,592 B in 1s (7,879 B/s) 
  Selecting previously unselected package initramfs-tools.
  (Reading database ... 430494 files and directories currently installed.)
  Preparing to unpack .../initramfs-tools_0.122ubuntu8_all.deb ...
  Unpacking initramfs-tools (0.122ubuntu8) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up initramfs-tools (0.122ubuntu8) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8) ...
  ls: cannot access '/var/lib/initramfs-tools': No such file or directory
  update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic
  /usr/sbin/update-initramfs: 206: /usr/sbin/update-initramfs: cannot create 
/var/lib/initramfs-tools/4.4.0-21-generic: Directory nonexistent
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   initramfs-tools: Install
   initramfs-tools: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May  5 17:47:32 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2015-07-10 (299 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (1 days ago)

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

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

[Touch-packages] [Bug 1572004] Re: pcscd consumes 100% CPU

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

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

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Confirmed

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

Title:
  pcscd consumes 100% CPU

Status in pcsc-lite package in Ubuntu:
  Confirmed
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  After upgrading to 16.04, pcscd process is stuck at using 100% CPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1572004/+subscriptions

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

2017-08-29 Thread Claude Champagne

> Sorry, I don't understand why installing it from .deb should change
the behavior

Me neither.  :-)  But you said that you had no problem with the one from
deb.


Again, please take a look at the answer I got from the guy who makes the United 
theme and how he fixed it :

"I wrote a very specific rule that hopefully only fixes this issue in
LibreOffice"

https://github.com/godlyranchdressing/United-GNOME/issues/135

Thanks.

** Bug watch added: github.com/godlyranchdressing/United-GNOME/issues #135
   https://github.com/godlyranchdressing/United-GNOME/issues/135

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

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

[Touch-packages] [Bug 1713674] Re: Starting Xenial lxc without cap_sysadmin fails

2017-08-29 Thread Stéphane Graber

This is already in our stable-2.0 branch, so both LXC 2.1 and LXC 2.0.9
will have it.

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

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

Title:
  Starting Xenial lxc without cap_sysadmin fails

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  Dear all,

  When trying to start an LXC container with Xenial on both host and
  container, if sys_admin capability is dropped (lxc.cap.drop =
  sys_admin in the config file), the container fails to start, because
  systemd fails to mount the cgroup filesystem in the container. The
  workaround is to manually mount the cgroup filesystem before starting
  the container (using the lxc.mount.entry in the config file), but, LXC
  performs the mount too early, before being in the container cgroup
  namespace, that means what's mounted matches host cgroup namespace,
  not container namespace.

  The bug was already reported upstream[1][2], but didn't make it to Ubuntu 
yet, AFAIK.
  A fix was merged in master[3], would it be possible to have it in Ubuntu 
Xenial?

  So far, we manually patch Ubuntu LXC packages with that patch and
  observed no régressions.

  Thanks!

  Cheers,
  P. Schweitzer

  [1]: https://github.com/lxc/lxc/pull/1597
  [2]: https://github.com/lxc/lxc/pull/1606
  [3]: 
https://github.com/lxc/lxc/commit/c1cecfdd050818865653d7941d7bae5d755246ae

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

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

[Touch-packages] [Bug 1652269] Re: udev script shortcuts ifup-scripts

artful still has the same /lib/udev/bridge-network-interface script in
its bridge-utils package, fwiw.

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

Title:
  udev script shortcuts ifup-scripts

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just ran into a problem. I've configured a bridge as a virtual lan
  (for lxc, lxd, and these things), but also configured an USB Ethernet
  dongle to be part of the bridge.

  If the dongle is present at boot time or if the dongle is put in while
  the bridge is down, then

  
  /lib/udev/bridge-network-interface  

  
  tries to take the bridge up. Nice. 

  But it does not call ifup, instead it directly calls

  IFACE=$port /etc/network/if-pre-up.d/vlan

  
  This ifup is not aware that the interface is up and still thinks it would be 
down, and all the other settings (up/down-scripts ...) are not executed. Breaks 
functionality (and can be a security problem, since firewall settings my be 
skipped.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bridge-utils 1.5-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:31:43 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2
   libgcc1 1:6.2.0-5ubuntu12
  InstallationDate: Installed on 2016-04-22 (244 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: bridge-utils
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1652269/+subscriptions

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

[Touch-packages] [Bug 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

2017-08-29 Thread Stéphane Graber

Yeah, that's getting fixed upstream, it's part of the chaos caused by
removing a bunch of upstart jobs that weren't hurting anyone...

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

Title:
  lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

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

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

2017-08-29 Thread Carlo Lobrano

> The LibreOffice 5.4 in the daily build came with it. Unlike you, I
didn't install it from deb.

Sorry, I don't understand why installing it from .deb should change the
behavior

> All themes with a dark header bar do this, unless they are fixed. Like
I said, look at what Adapta or United did to correct this.

Adapta seems affected as well to me, it's just less noticeable. If you
look at the picture the headerbar's border stops just below the close
button on top corner.

** Attachment added: "libreoffice's close button on adwaita"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1704745/+attachment/4940881/+files/adwaita-libreoffice-closebutton.png

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

Title:
Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress

Bug description:
In LibreOffice, there's a white square that appears in the top right.
It's a CSS problem. You could check how the guys from Adapta and
United-Gnome managed to solve it.

I posted the same issue at the Github of United-Gnome theme :
https://github.com/godlyranchdressing/United-GNOME/issues/135

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

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

[Touch-packages] [Bug 1056104] Re: Sends mail when MailOnlyOnError=true and all upgradeable packages are blacklisted

2017-08-29 Thread Balint Reczey

Looking at the code this seems to be fixed from 0.89.
https://github.com/mvo5/unattended-upgrades/commit/25ff94915a9fc99058839d16761cf029896cbe05

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => 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/1056104

Title:
  Sends mail when MailOnlyOnError=true and all upgradeable packages are
  blacklisted

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I have specified an email-address and MailOnlyOnError=true in
  /etc/apt/apt.conf.d/50unattended-upgrades. I have also a couple of
  packages blacklisted. However when unattended-upgrades are run (and
  the only packages eligible for upgrades are blacklisted) I still get
  an email (see below). I do not consider this situation as an error
  that warrants an email.  Apticron will be used to notify that there
  are packages available for upgrades and that are not handled by
  unattended-upgrades.

  I haven't yet been in the situation where there are both upgradeable
  packages and blacklisted packages, so I'm not sure if I will receive
  an email in that case.

  Email:

  Unattended upgrade returned: None

  Packages that are upgraded:

  Packages with upgradable origin but kept back: 
  postgresql-client postgresql-client-common 

  Unattended-upgrades log: Initial blacklisted packages: dcache sun-
  java6-jre sun-java6-jdk sun-java6-bin openjdk-6-jdk openjdk-6-jre
  openjdk-6-jre-headless openjdk-6-jre-lib openjdk-7-jdk openjdk-7-jre
  openjdk-7-jre-headless openjdk-7-jre-lib postgresql-common postgresql
  postgresql-8.3 postgresql-8.4 postgresql-9.0 postgresql-9.1
  postgresql-client postgresql-client-8.3 postgresql-client-8.4
  postgresql-client-9.0 postgresql-client-9.1 postgresql-contrib
  postgresql-contrib-8.3 postgresql-contrib-8.4 postgresql-contrib-9.0
  postgresql-contrib-9.1 libpq5

  Starting unattended upgrades script 
  Allowed origins are: ['o=Ubuntu,a=precise-security', 
'o=Ubuntu,a=precise-updates', 'o=HPC2N,a='] 
  Packages that are auto removed: '' 
  Packages that are upgraded:

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unattended-upgrades 0.76
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Tue Sep 25 12:30:15 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to precise on 2012-03-02 (206 days ago)
  modified.conffile..etc.apt.apt.conf.d.50unattended.upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2012-03-12T20:05:57.072716

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

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

2017-08-29 Thread Claude Champagne

The LibreOffice 5.4 in the daily build came with it. Unlike you, I
didn't install it from deb.

The bug has nothing to do with a VM or not.
 
All themes with a dark header bar do this, unless they are fixed. Like I said, 
look at what Adapta or United did to correct this. 

Or you take it to LibreOffice to correct this. But it will be faster to
fix the theme.

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

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

[Touch-packages] [Bug 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

** Merge proposal linked:
   
https://code.launchpad.net/~cyphermox/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/329823

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Triaged

Bug description:
  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+subscriptions

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

[Touch-packages] [Bug 1713749] [NEW] Gtk-WARNING **: Theme parsing error: gtk.css

2017-08-29 Thread anatoly techtonik

Public bug reported:

I don't know where to report this bug. Pretty much every GUI application
throws these warnings.


$ ubuntu-bug apport-gtk

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:597:14:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:597:14:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:600:17:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:784:14:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:784:14:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:787:17:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1096:14:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1096:14:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1099:17:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2286:8:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2286:18:
Using Pango syntax for the font: style property is deprecated; please
use CSS syntax

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2291:8:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2291:18:
Using Pango syntax for the font: style property is deprecated; please
use CSS syntax

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4357:14:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4357:14:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4419:12:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4419:12:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4428:16:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4428:16:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4443:22:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4443:22:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4499:12:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4501:16:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4501:16:
Expected a string.

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4549:12:
not a number

(apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4549:12:
Expected a string.


This happened after one of Ubuntu Studio upgrades. Studio uses Xfce. Is
there a way to fix this? Maybe there is a better package to report?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apport-gtk 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashReports: 640:1000:118:2325445:2017-08-28 12:29:40.645797729 
+0300:2017-08-28 12:29:41.645797729 +0300:/var/crash/_usr_bin_thunar.1000.crash
CurrentDesktop: XFCE
Date: Tue Aug 29 17:59:02 2017
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to zesty on 2017-04-15 (135 days ago)

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


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

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

Title:
  Gtk-WARNING **: Theme parsing error: gtk.css

Status in apport package in Ubuntu:
  New

Bug description:
  I don't know where to report this bug. Pretty much every GUI
  application throws these warnings.

  
  $ ubuntu-bug apport-gtk

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:597:14: not a number

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:597:14: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:600:17: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:784:14: not a number

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:784:14: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:787:17: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:1096:14: not a number

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:1096:14: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:1099:17: Expected a string.

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:2286:8: not a number

  (apport-gtk:3007): Gtk-WARNING **: Theme parsing error:
  gtk.css:2286:18: Using Pango syntax for the font: style prope

[Touch-packages] [Bug 1713747] [NEW] missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

2017-08-29 Thread Mathieu Trudel-Lapierre

Public bug reported:

For networked systems, for instance booting with an iSCSI root, dhclient
writes an output file in the form of /run/net-.conf that contains
data for other programs to consume. This allows, for instance, open-
iscsi to get the right information and properly connect to the server to
mount the root filesystem.

It is common for DHCP servers to only provide a domain name value, and
no search domains. In this case, isc-dhcp doesn't currently write
DOMAINSEARCH, but people may wish to use short names to resolve things
(such as in iSCSI server).

In the not-initramfs dhclient-script, when domain_search isn't provided
but domain_name is, domain_name is written to the search string. If both
are provided, domain_search is written. The initramfs enter hook should
do the same.

** Affects: isc-dhcp (Ubuntu)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: isc-dhcp (Ubuntu Xenial)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: isc-dhcp (Ubuntu Zesty)
 Importance: High
 Status: Triaged

** Also affects: isc-dhcp (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: New => Triaged

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress
Status in isc-dhcp source package in Zesty:
  Triaged

Bug description:
  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+subscriptions

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

[Touch-packages] [Bug 1707884] Re: GTK3 tooltips are corrupted after latest update

2017-08-29 Thread Amr Ibrahim

** Project changed: xserver-xorg-driver-ati => mesa

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

Title:
  GTK3 tooltips are corrupted after latest update

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After updating to 1:7.9.0-0ubuntu1~16.04.1, I noticed that all GTK3
  tooltips are corrupted. See the attached screen cast. Other tooltips
  are not affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-radeon-hwe-16.04 1:7.9.0-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  1 12:50:06 2017
  InstallationDate: Installed on 2017-06-21 (40 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: xserver-xorg-video-ati-hwe-16.04
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-06-21 (41 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: xserver-xorg-video-ati-hwe-16.04 1:7.9.0-0ubuntu1~16.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Tags:  xenial
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

** Merge proposal linked:
   https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/329811

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

Title:
  usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Earlier this week on Zesty on Azure I saw a cloud-init failure in its 
'mount_cb' function.
  That function esentially does:
   a.) make a tmp directory for a mount point
   b.)  mount some filesystem to that mount point
   c.) call a function
   d.) unmount the directory

  What I recall was that access to a file inside the mount point failed during 
'c'.
  This seems possible as systemd-tmpfiles-clean may be running at the same time 
as cloud-init (cloud-init.service in this example).

  
  It seems that this service basically inhibits *any* other service from using 
tmp files.
  It's ordering statements are only:

After=local-fs.target time-sync.target
Before=shutdown.target

  So while in most cases only services that run early in the boot
  process like cloud-init will be affected, any service could have its
  tmp files removed.  this service could take quite a long time to run
  if /tmp/ had been filled with lots of files in the previous boot.

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

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

[Touch-packages] [Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

2017-08-29 Thread Philip Muškovac

For clarification, the environment the containers run with is:

privileged: false,
cap_add: ['SYS_ADMIN'],
security_opts: ['apparmor:unconfined']

(see https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git
/pangea-tooling/tree/kci/imager.rb)

what's not helpful is that running debootstrap in a container started on the 
shell with
run --cap-add SYS_ADMIN --privileged=false --security-opt 'apparmor:unconfined'
seems to work fine... (result: artful/etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf)

so this might be related to some of the environment setup before live-
build starts running - or that fact that it's running headless, but I
did not have time to take a closer look at that.

As for touching resolv.conf, live-build does mess with it later on in
some way during the chroot build, but that happens far later during the
build.

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

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit 
status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

* Always setup /etc/resolv.conf on new installations.
  On new installations, /etc/resolv.conf will always exist. Move it to /run
  and replace it with the desired final symlink. (LP: #1712283)
* Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

This bug was fixed in the package resolvconf - 1.79ubuntu8

---
resolvconf (1.79ubuntu8) artful; urgency=medium

  * Dereference /etc/resolf.conf when creating runtime configuration when
migrating to resolvconf managed /etc/resolv.conf. The contents of
/etc/resolv.conf (rather than the symlink target information) is
needed in /run/resolvconf/resolv.conf and
/run/resolvconf/interface/original.resolvconf during migration until
resolvconf updates the config next. LP: #1713149

 -- Dimitri John Ledkov   Tue, 29 Aug 2017 14:04:33
+0100

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

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1607874] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-29 Thread Rudi Hansen

I get this error when trying to do a release upgrade from 14.04.5 LTS to
16.04.3 LTS

Witch surprises me when i see this bug was reported almost one year ago.
Any chance this will be fixed?

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  Confirmed

Bug description:
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/sysv-
  rc.0.crash'

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Jul 29 23:52:04 2016
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-18 (833 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.1ubuntu2.14
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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

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

[Touch-packages] [Bug 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

2017-08-29 Thread Christian Brauner

Has the `/etc/init/` directory and associated files been removed from
artful I remember @xnox removing old init scripts.

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

Title:
  lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

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

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

[Touch-packages] [Bug 1713205] Re: Slow suspend when wifi active

2017-08-29 Thread Dave Kokandy

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

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

Title:
  Slow suspend when wifi active

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa package in Debian:
  Fix Released

Bug description:
  Running 17.04 (upgraded over several versions) I see a ten second
  additional delay on suspend if wifi is in use. Looking at the journal
  this looks to be debian wpa bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=835648

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: wpasupplicant 2.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 26 08:13:04 2017
  InstallationDate: Installed on 2014-10-21 (1039 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to zesty on 2017-04-26 (121 days ago)

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

Adding resolvconf task as well, since now:
$ sudo debootstrap --include=resolvconf artful artful

is broken.

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1713726] [NEW] lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

2017-08-29 Thread Seth Forshee

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz

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

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

[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Some solutions:
 a.) Use systemd PrivateTmp which mounts a filesystem over /tmp the process.  
The issue here is that would only solve for systemd boot.
 b.) set up our own tmp and use it.

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

Title:
  usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Earlier this week on Zesty on Azure I saw a cloud-init failure in its 
'mount_cb' function.
  That function esentially does:
   a.) make a tmp directory for a mount point
   b.)  mount some filesystem to that mount point
   c.) call a function
   d.) unmount the directory

  What I recall was that access to a file inside the mount point failed during 
'c'.
  This seems possible as systemd-tmpfiles-clean may be running at the same time 
as cloud-init (cloud-init.service in this example).

  
  It seems that this service basically inhibits *any* other service from using 
tmp files.
  It's ordering statements are only:

After=local-fs.target time-sync.target
Before=shutdown.target

  So while in most cases only services that run early in the boot
  process like cloud-init will be affected, any service could have its
  tmp files removed.  this service could take quite a long time to run
  if /tmp/ had been filled with lots of files in the previous boot.

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

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

[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

>From another bug with the same root cause, a failure might look like this:
Apr 12 07:56:33 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command ['mount', 
'-o', 'ro,sync', '-t', 'auto', '/dev/sr0', '/tmp/tmpzq70nqyi'] with allowed 
return codes [0] (shell=False, capture=True)
Apr 12 07:56:33 ubuntu [CLOUDINIT] util.py[DEBUG]: Failed mount of '/dev/sr0' 
as 'auto': Unexpected error while running command.#012Command: ['mount', '-o', 
'ro,sync', '-t', 'auto', '/dev/sr0', '/tmp/tmpzq70nqyi']#012Exit code: 
32#012Reason: -#012Stdout: ''#012Stderr: 'mount: mount point /tmp/tmpzq70nqyi 
does not exist\n'
Apr 12 07:56:33 ubuntu [CLOUDINIT] util.py[DEBUG]: Recursively deleting 
/tmp/tmpzq70nqyi

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

** Changed in: cloud-init
   Importance: Medium => High

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

Title:
  usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Earlier this week on Zesty on Azure I saw a cloud-init failure in its 
'mount_cb' function.
  That function esentially does:
   a.) make a tmp directory for a mount point
   b.)  mount some filesystem to that mount point
   c.) call a function
   d.) unmount the directory

  What I recall was that access to a file inside the mount point failed during 
'c'.
  This seems possible as systemd-tmpfiles-clean may be running at the same time 
as cloud-init (cloud-init.service in this example).

  
  It seems that this service basically inhibits *any* other service from using 
tmp files.
  It's ordering statements are only:

After=local-fs.target time-sync.target
Before=shutdown.target

  So while in most cases only services that run early in the boot
  process like cloud-init will be affected, any service could have its
  tmp files removed.  this service could take quite a long time to run
  if /tmp/ had been filled with lots of files in the previous boot.

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

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

[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Note there is some discussion of this bug in irc and other options at
https://irclogs.ubuntu.com/2017/07/28/%23ubuntu-devel.html#t16:24

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

Title:
  usage of /tmp during boot is not safe due to systemd-tmpfiles-clean

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Earlier this week on Zesty on Azure I saw a cloud-init failure in its 
'mount_cb' function.
  That function esentially does:
   a.) make a tmp directory for a mount point
   b.)  mount some filesystem to that mount point
   c.) call a function
   d.) unmount the directory

  What I recall was that access to a file inside the mount point failed during 
'c'.
  This seems possible as systemd-tmpfiles-clean may be running at the same time 
as cloud-init (cloud-init.service in this example).

  
  It seems that this service basically inhibits *any* other service from using 
tmp files.
  It's ordering statements are only:

After=local-fs.target time-sync.target
Before=shutdown.target

  So while in most cases only services that run early in the boot
  process like cloud-init will be affected, any service could have its
  tmp files removed.  this service could take quite a long time to run
  if /tmp/ had been filled with lots of files in the previous boot.

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

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

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

2017-08-29 Thread Iain Lane

Ok, and FYI, I just pushed the limits

https://git.launchpad.net/autopkgtest-
cloud/commit/?id=2e76a4e09101237543d332b710c11f9a4fcdbba3

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

Steve,

It seems that unconditional enablement and start of networkd in
src:systemd.postinst has side-effects, especially when netwokr-manager
is directly managing desktop systems, without netplan.

I think we should not unconditially enable and start entworkd in
src:systemd.postinst, and instead have networkd enable baked into cloud-
images and/or done by netcfg or the netplan generator on boot.

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  systemd-networkd messes up networking

Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

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

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1713713] [NEW] package base-files 9.6ubuntu13 failed to install/upgrade: pacote base-files não está pronto para configuração não posso configurar (estado atual 'half-installed')

2017-08-29 Thread Israel Ursulino

Public bug reported:

Meu ubuntu

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: base-files 9.6ubuntu13
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Aug 29 08:09:04 2017
DpkgTerminalLog:
 dpkg: erro ao processar o pacote base-files (--configure):
  pacote base-files não está pronto para configuração
  não posso configurar (estado atual 'half-installed')
ErrorMessage: pacote base-files não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
InstallationDate: Installed on 2016-06-13 (442 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: base-files
Title: package base-files 9.6ubuntu13 failed to install/upgrade: pacote 
base-files não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
UpgradeStatus: Upgraded to zesty on 2017-04-20 (130 days ago)

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package base-files 9.6ubuntu13 failed to install/upgrade: pacote base-
  files não está pronto para configuração  não posso configurar (estado
  atual 'half-installed')

Status in base-files package in Ubuntu:
  New

Bug description:
  Meu ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Aug 29 08:09:04 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote base-files (--configure):
pacote base-files não está pronto para configuração
não posso configurar (estado atual 'half-installed')
  ErrorMessage: pacote base-files não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2016-06-13 (442 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: base-files
  Title: package base-files 9.6ubuntu13 failed to install/upgrade: pacote 
base-files não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-04-20 (130 days ago)

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

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

[Touch-packages] [Bug 1713710] [NEW] RM: obsolete product

Public bug reported:

click-apparmor was a component of Ubuntu Phone which is no longer
developed.

Please remove this package from the Ubuntu Archive.

$ reverse-depends src:click-apparmor
No reverse dependencies found

$ reverse-depends -b src:click-apparmor
No reverse dependencies found

** Affects: click-apparmor (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: u8rm

** Changed in: click-apparmor (Ubuntu)
   Status: New => Triaged

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

Title:
  RM: obsolete product

Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  click-apparmor was a component of Ubuntu Phone which is no longer
  developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:click-apparmor
  No reverse dependencies found

  $ reverse-depends -b src:click-apparmor
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

Inside the old kubuntu-ci image I see:

# ls -latr squashfs-root/etc/resolv.conf 
lrwxrwxrwx 1 root root 29 Aug 29 12:54 squashfs-root/etc/resolv.conf -> 
../run/resolvconf/resolv.conf


I am confused how resolvconf managed to replace /etc/resolv.conf, yet systemd 
did not.
Do you somewhere later modify or update /etc/resolv.conf? or is it never 
touched manually?

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

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit 
status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

* Always setup /etc/resolv.conf on new installations.
  On new installations, /etc/resolv.conf will always exist. Move it to /run
  and replace it with the desired final symlink. (LP: #1712283)
* Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

2017-08-29 Thread msaxl

this was a upgrade so the ifupdown problem should not happen with clean 
installs.
How is the migration planned?

If for example one will do a upgrade from 16.04 to the next 18.04 such
problems are a clear show stopper since breaking the network for most
servers will mean needing physical access.

On my system there is nothing that puts the interface to state up, so I blame 
systemd-networkd being it (normal desktop system, so /etc/network/interfaces 
contains only a lo entry).
But after all I consider having two systems that configure the same set of 
network interfaces will never work reliable.
I think the best would be systemd-networkd.service conflicts 
network-manager.service

What is the pro of enabling systemd-networkd on desktop systems? I see
advantages on server systems over ifupdown, but afaik neither gnome nor
plasma has systemd-networkd integration.

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

Title:
  systemd-networkd messes up networking

Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 713922] Re: network-manager left-click menu doesn't always show in multi-head setup

** Changed in: gtk
   Status: New => Confirmed

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

Title:
  network-manager left-click menu doesn't always show in multi-head
  setup

Status in GTK+:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  My netbook is connected to an external display at times.  I run lucid
  Ubuntu netbook edition as my window manager.  A left-click on the
  network-manager applet does not produce a visible menu under the
  following conditions.

  1) dual-head and internal display below external display
  2) long list of entries make the menu overflow

  I get a long list of entries for example when I have wifi, ethernet
  and GSM active at the same time.  When the list in the network-manager
  applet becomes long enough to hit the lower edge of the screen it
  apparently overflows incorrectly in such a way that the whole menu
  becomes invisible (except for a bar of about 1 pixel height just above
  the applet).  The same long list works fine when the internal display
  is on top of the external display, for what it's worth.

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

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

[Touch-packages] [Bug 1711255] Re: systemd RestartSec does not seem to work consistently

A minimal working reproducer with e.g. ExecStart=/bin/false would be
useful. To remove the uncertainties w.r.t. executables involved. As I do
not have access to the masked product.

Is this reproducible in Ubuntu Artful which has much newer systemd?

** Changed in: systemd (Ubuntu)
   Status: New => 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/1711255

Title:
  systemd RestartSec does not seem to work consistently

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The unit file for my service -33005.service:

  [Unit]
  Description=product  33005 service
  Wants=some.mount
  After=some.mount
  PartOf=product.target
  PartOf=someother.service
  [Service]
  Type=simple
  ExecStart=/opt/product/bin/ -conf=/etc/product.conf
  Restart=on-failure
  User=product
  Group=product
  LimitCORE=infinity
  LimitNOFILE=1
  Slice=.slice
  WatchdogSec=120
  RestartSec=10
  StartLimitInterval=120
  StartLimitBurst=10
  [Install]
  WantedBy=product.target

  specifies RestartSec=10, which is also what systemd sees:

  $ systemctl show -33005.service
  Type=simple
  Restart=on-failure
  NotifyAccess=main
  RestartUSec=10s
  ...

  However, today I saw in the journalctl log:
  $ journalctl -u -33005.service
  ...
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Watchdog timeout 
(limit 2min)!
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:28:39 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:28:39 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:28:39 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Stopping product  33005 service...
  Aug 15 23:28:45 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:33:51 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:33:51 a-hostname [3629]: Get http://127.0.0.1:8081/: dial tcp 
127.0.0.1:8081: getsockopt: connection refused
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:34:01 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:34:02 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: -33005.service: Start request 
repeated too quickly.
  Aug 15 23:34:02 a-hostname systemd[1]: Failed to start product  33005 
service.

  Everything looks to me that systemd is behaving as expected until Aug
  15 23:34:02 when it attempts to start -33005.service not at the
  rate I specified in RestartSec, but possibly at the default 100ms
  rate.  This excerpt shows both the expected 10s restart rate as well
  as the unexpected restart rate.

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ uname -a
  Linux a-hostname 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu16
    Candidate: 229-4ubuntu19
    Version table:
   229-4ubuntu19 500
  500 http://internal-repo/ubuntu xenial-updates/main amd64 Packages
   *** 229-4ubuntu16 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://internal-repo/ubuntu xenial-security/main amd64 Packages
   229-4ubuntu4 500
  500 http://internal-repo/ubuntu xenial/main amd64 Packages

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

--

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

2017-08-29 Thread Iain Lane

That's all well and good, but under the the current limits systemd is
still able to pass, so it is not *required* to fix this bug. The problem
was that the host had piled up stale containers.

That is cleaned up, and the tests are succeeding now.

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

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

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

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

[Touch-packages] [Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

2017-08-29 Thread Rik Mills

A bit old, as we were not able to run the builds for artful while we had
the Qt 5.9 landing PPA enabled to test build our packages against.

https://kci.pangea.pub/job/iso_artful_stable_amd64/3/consoleFull

http://kci.pangea.pub/images/iso_artful_stable_amd64/20170722-2012/

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

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit 
status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

* Always setup /etc/resolv.conf on new installations.
  On new installations, /etc/resolv.conf will always exist. Move it to /run
  and replace it with the desired final symlink. (LP: #1712283)
* Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

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

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

[Touch-packages] [Bug 1713578] Re: Migrate /etc/resolv.conf from resolvconf to systemd-resolved

At the moment the following is done:
- on debootstrap resolved symlink is configured
- on upgrades resolvconf is preserved, and resolved is integrated to feed data 
into resolvconf
- if upgraded resolvconf is removed, the postrm in artful configured symlink to 
point at resolved
- static file is preserved i believe (need to check)
- if /etc/resolv.conf is a static file configured by network-manager, resolved 
may take over it (since network-manager has resolved integration), but 
currently doesn't.

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

Title:
  Migrate /etc/resolv.conf from resolvconf to systemd-resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Moving off of resolvconf and to systemd-resolved requires that
  resolv.conf is properly handled both in the case of new installs (done
  as per 234-2ubuntu9 at least), but also in the case of upgrades from
  previous releases or previous versions of systemd.

  There are various use cases to take into account:

  1) upgrades where resolv.conf is more or less default and dynamic,
  uses DHCP via ifupdown (servers), or 127.0.1.1/DHCP settings from
  NetworkManager (desktops), etc.

  2) upgrades from manual resolv.conf settings (the user has written
  their own, it's static)

  3) upgrades from manual resolv.conf managed via resolvconf.

  3) No resolv.conf?

  Lack of resolv.conf is simple, writing one is always sane.

  Upgrades from dynamic files is also straightforward, copying it to
  /run/systemd/resolve/resolv.conf will keep the current state;
  /etc/resolv.conf will be symlinked to that.

  In the case of a manually-configured resolv.conf; whether it comes
  from resolvconf or is manually configured is non-trivial if we want to
  maintain the current DNS configuration and also remove resolvconf. The
  removal of resolvconf can be forced, but what do we do about the
  existing /etc/resolv.conf file, knowing that /run is a tmpfs?

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

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

[Touch-packages] [Bug 1713363] Re: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Your system appears to be quite damaged, as it appears that many
packages are missing the files they have installed.

Could you please paste the output of:

$ ls -latr /etc/machine-id 
$ cat /etc/machine-id

** Changed in: systemd (Ubuntu)
   Status: New => 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/1713363

Title:
  package systemd 232-21ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  -Computer-
  Processor : Intel(R) Celeron(R) M processor  900MHz
  Memory: 2052MB (940MB used)
  Operating System  : Ubuntu 17.04
  User Name : casaserra (casaserra)
  Date/Time : dom 27 ago 2017 22:21:26 CEST
  -Display-
  Resolution: 1280x1024 pixels
  OpenGL Renderer   : Unknown
  X11 Vendor: The X.Org Foundation
  -Multimedia-
  Audio Adapter : HDA-Intel - HDA Intel
  -Input Devices-
   Lid Switch
   Sleep Button
   Power Button
   Power Button
   AT Translated Set 2 keyboard
   Video Bus
   SynPS/2 Synaptics TouchPad
   Asus EeePC extra buttons
   HDA Intel Mic
   HDA Intel Headphone
   UVC Camera (eb1a:2761)
  -Printers-
  No printers found
  -SCSI Disks-
  ATA SILICONMOTION SM
   USB DISK 3.0
  USB2.0 CardReader SD0

  systemd:
Installato: 232-21ubuntu5
Candidato:  232-21ubuntu5
Tabella versione:
   *** 232-21ubuntu5 500
  500 http://it.archive.ubuntu.com/ubuntu zesty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  3) What you expected to happen: software updates should be got installed
  4) What happened instead: I got a masseage saying some pacakages couldn't be 
installed

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sun Aug 27 20:27:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-08-27 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: ASUSTeK Computer INC. 701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=dffd559d-cd18-4fee-a7c2-7a0504a4b587 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 701
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/11/2009:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 701
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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

[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug

** Project changed: ubuntu-power-systems => ubuntu-z-systems

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

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

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: Confirmed

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

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Confirmed

Bug description:
  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

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

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

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

I believe the sysctl.d changes, as recommended by lxd upstream for
optimal hosts, should be rolled out on the hosts that run armhf & s390x
testing.

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

Title:
  systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz

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

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

[Touch-packages] [Bug 1713226] Re: systemd-networkd messes up networking

Is this on upgrades to artful? or clean-install / clean-bring up of
artful?

Note that artful will no longer have ifupdown installed on clean-install, and 
thus /etc/network/interfaces changes for clean-installs will have no effect at 
all. And one should instead use netplan e.g. $ sudo netplan ifupdown-migrate
to move the system over to networkd.

The router advertisement vs networkmanager is interesting case. In
practice networkd should not have configured the interface imho, if it
was not told to manage it via netplan configuration. Or e.g.
NetworkManager should still consider interface for management, even if
it has acquired RA ipv6.

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

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

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

Title:
  systemd-networkd messes up networking

Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd-234-2ubuntu8 systemd-networkd is enabled by default.

  This causes problems existing configurations
  ex1: if the network has ipv6 enables (the host recieves a router 
advertisement), networkmanager does not configure the network anymore so you 
get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring 
only the link up)

  ex2: if you use systemd-nspawn and configured static ip addresses in
  /etc/network/interfaces, systemd-networkd adds a dhcp obtained address
  on the host0 adapter and a 169.254 address

  For the average user both is not expected, so my solution was
  systemctl disable systemd-networkd, but since you seem to insist
  having this enabled, it must be made sure systemd-networkd does not
  touch existing configurations.

  My suggestion is:
  1) if /etc/network/interfaces contains anything other than lo -> do not 
enable systemd-networkd
  2) if network-manager is enabled, systemd-networkd must be disabled and vice 
versa

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

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

[Touch-packages] [Bug 1713161] Re: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Could you open terminal, and execute $ sudo dpkg-configure -a
and paste the output of it?

** Changed in: systemd (Ubuntu)
   Status: New => 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/1713161

Title:
  package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libpam-systemd:amd64 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 25 21:13:13 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-07-18 (38 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc1~ubuntu1
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to artful on 2017-08-21 (4 days ago)

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

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

[Touch-packages] [Bug 1713671] Re: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

2017-08-29 Thread Julian Andres Klode

Reassigning to readline:

symbol lookup error: /usr/local/lib/libreadline.so.6: undefined symbol:
UP

** Package changed: apt (Ubuntu) => readline6 (Ubuntu)

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

Title:
  package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in readline6 package in Ubuntu:
  New

Bug description:
  ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ban2296 F pulseaudio
   /dev/snd/controlC0:  ban2296 F pulseaudio
  Date: Tue Aug 29 16:36:37 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  HibernationDevice: RESUME=UUID=810c9395-dc41-4e20-8f7a-7667608a8915
  InstallationDate: Installed on 2016-12-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=38c7c7ab-6474-4800-8193-31fb34a145d0 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.12
  RfKill:
   
  SourcePackage: apt
  Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: Default string
  dmi.board.name: B150-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd01/28/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

2017-08-29 Thread Carlo Lobrano

It's Gnome Shell, with Activities, new Ubuntu Dock bar and everything.

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

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

[Touch-packages] [Bug 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

2017-08-29 Thread Daniel van Vugt

Yes graphics driver could be a factor. Also your screenshot suggests
maybe you're not using Gnome Shell, maybe Unity?...

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

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

[Touch-packages] [Bug 1713149] Re: resolv.conf symlink is broken after clean debootstrap

Correct that there is a bug with debootstrap above, if both this new
systemd & resolvconf are being bootstrapped together. (as both
src:systemd and src:resolvconf try to setup /etc/resolv.conf symlink)

Dropping resolvconf from important should resolve this.

The ExecStartPre change should then be dropped.


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

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

Title:
  resolv.conf symlink is broken after clean debootstrap

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Reproducer:
   - debootstrap artful artful

  Expected:
   - "chroot artful cat /etc/resolv.conf" doesn't fail.
   - /etc/resolv.conf is a symlink to something valid in /run

  Actual:
   - "chroot artful cat /etc/resolv.conf" gets you "No such file or directory"
   - /etc/resolv.conf is a symlink to "../run/resolvconf/resolv.conf"
   - "../run/resolvconf/resolv.conf" is a symlink to 
"../run/systemd/resolve/stub-resolv.conf" which is an invalid symlink as that 
points to /run/run/systemd/resolve/stub-resolv.conf" rather than 
"/run/systemd/resolve/stub-resolv.conf"

  This causes all LXC image creation to fail, causing autopkgtest to
  fail (as noticed by the kernel team) and has been causing all images
  to fail building on the upstream build system for the past two days.


  root@vm04:~# chroot artful ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 4.0K
  -rw-r--r-- 1 root root0 Aug 25 20:21 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  lrwxrwxrwx 1 root root   39 Aug 25 20:18 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  root@vm04:~# chroot zesty ls -lh /etc/resolv.conf /run/resolvconf/
  lrwxrwxrwx 1 root root   29 Aug 25 20:20 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

  /run/resolvconf/:
  total 8.0K
  -rw-r--r-- 1 root root0 Aug 25 20:20 enable-updates
  drwxr-xr-x 2 root root 4.0K Aug 25 20:20 interface
  -rw-r--r-- 1 root root  357 Aug 25 20:15 resolv.conf

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

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

[Touch-packages] [Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker