[Touch-packages] [Bug 1663727] Re: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) => linux (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/1663727

Title:
  16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

Status in linux package in Ubuntu:
  New

Bug description:
  I've just performed an "apt-get update" on a Dell 2950 Server - which
  was already running 16.04.1 and now it's spewing EDID errors - I'm not
  sure what changed from 16.04.1 to 16.04.2..

  I've attached dmesg to this, but basically it's dumping the following
  in logs and to the screen.

  [drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but
  no|invalid EDID

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

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

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

[Ryan Tandy]

On Tue, Jan 17, 2017 at 12:49:36AM -, Haw Loeung wrote:
>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

http://www.openldap.org/its/?findid=7506 says:

fixed in RE25
fixed in RE24 (2.4.45)

OpenLDAP 2.4.45 has not been released just yet.

-- 
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:
  New

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:

[Touch-packages] [Bug 1663797] [NEW] cannt launch ubuntu

[stefano kasangian]

Public bug reported:

ubuntu software

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Feb 11 05:31:36 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d]
InstallationDate: Installed on 2017-01-24 (17 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. E402SA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=f8e8e1c2-cff3-4441-b2bf-fb2d47ffc105 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/20/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E402SA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E402SA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: E402SA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sat Feb 11 04:21:28 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


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

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

Title:
  cannt launch ubuntu

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu software

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-36.38-generic 4.8.16
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb 11 05:31:36 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d]
  InstallationDate: Installed on 2017-01-24 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E402SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic.efi.signed 
root=UUID=f8e8e1c2-cff3-4441-b2bf-fb2d47ffc105 ro quiet splash 

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

[Haw Loeung]

Also:

https://anonscm.debian.org/git/pkg-
openldap/openldap.git/tree/libraries/libldap/tls_g.c#n317

-- 
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:
  New

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://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Haw Loeung]

Hmm, not too sure why that is. The version in Debian (and also Ubuntu)
definitely doesn't include that patch:

| $ chdist apt-get xenial source slapd
| Reading package lists... Done
| Picking 'openldap' as source package instead of 'slapd'
| NOTICE: 'openldap' packaging is maintained in the 'Git' version control 
system at:
| git://anonscm.debian.org/pkg-openldap/openldap.git
| Please use:
| git clone git://anonscm.debian.org/pkg-openldap/openldap.git
| Need to get 4993 kB of source archives.
| Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main openldap 
2.4.42+dfsg-2ubuntu3.1 (dsc) [3040 B]
| Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main openldap 
2.4.42+dfsg-2ubuntu3.1 (tar) [4813 kB]
| Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main openldap 
2.4.42+dfsg-2ubuntu3.1 (diff) [177 kB]
| Fetched 4993 kB in 14s (343 kB/s)

| $ grep DH_BITS ./libraries/libldap/tls_g.c
| #define DH_BITS (1024)
| gnutls_dh_params_generate2(ctx->dh_params, DH_BITS);

Via online source viewer also confirms this:

https://anonscm.debian.org/git/pkg-openldap/openldap.git/tree/libraries/libldap/tls_g.c#n47
https://anonscm.debian.org/git/pkg-openldap/openldap.git/tree/libraries/libldap/tls_g.c#n294

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

Title:
  No support for DHE ciphers (TLS)

Status in openldap package in Ubuntu:
  New

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  

[Touch-packages] [Bug 1642638] Re: backspace is not working on upright bq e5

[Launchpad Bug Tracker]

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

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

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

Title:
  backspace is not working on upright bq e5

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Hi,
  I bought last week bq e5 ubuntu, just updated the system.
  have problem with backspace deleting
  on upright (default position,power button upper right) it does not work
  on horrizontally it works in both directions
  on upright buttom up(power button down left) it also works

  "only" the default position does not work

  see questions:
  https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069

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

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

[Touch-packages] [Bug 1663794] Re: Poweroff/Reboot Hangs :: Ubuntu 16.04

[Renê Barbosa]

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663794/+attachment/4816889/+files/dmesg.log

** Package changed: linux (Ubuntu) => systemd (Ubuntu)

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

Title:
  Poweroff/Reboot Hangs :: Ubuntu 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading my laptop (Dell Inspiron 5447) to Ubuntu 16.04 I saw
  that I can not shut down or restart after a few hours using the
  system. It hangs in Plymouth and stays that way until I force the
  shutdown by pressing the On / Off button.

  As this is a common bug (there are tons of questions on the Internet)
  I tried to fix it, but none of my attempts were effective. Already
  tried:

  1. Boot with acpi=force
  2. Disable Swap
  3. Run 'sync' before reboot or shutdown
  4. Use another kernel version (4.7, 4.8, 4.9 and 4.10 from mainline)
  5. Disabling USB 3.0
  6. Disabling TLP

  The most interesting thing is: I can shutdown/reboot normally using
  14.04 and the kernel from Xenial HWE and it's because of that I
  believe this is a systemd bug.

  The problem can also be reached just running "halt" of "systemctl
  halt" after booting 16.04 in this machine. Running these commands with
  "force" option is working fine.

  My Machine Specs:

  Dell Inspiron 5447 - BIOS A10
  Intel Core i5-4210 Processor
  8 GB RAM
  480 SSD Sandisk
  Hybrid Graphics (i915/amdgpu - Radeon R7 M265)

  --- BUG Information 

  Reproducible:
  Always

  Steps to Reproduce:
  1.Power on the machine
  2.Do something, anything or nothing for a few hours
  3.Try to shutdown/reboot using halt, shutdown, reboot, etc

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off/rebooting the machine.

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

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

[Touch-packages] [Bug 1663794] [NEW] Poweroff/Reboot Hangs :: Ubuntu 16.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading my laptop (Dell Inspiron 5447) to Ubuntu 16.04 I saw
that I can not shut down or restart after a few hours using the system.
It hangs in Plymouth and stays that way until I force the shutdown by
pressing the On / Off button.

As this is a common bug (there are tons of questions on the Internet) I
tried to fix it, but none of my attempts were effective. Already tried:

1. Boot with acpi=force
2. Disable Swap
3. Run 'sync' before reboot or shutdown
4. Use another kernel version (4.7, 4.8, 4.9 and 4.10 from mainline)
5. Disabling USB 3.0
6. Disabling TLP

The most interesting thing is: I can shutdown/reboot normally using
14.04 and the kernel from Xenial HWE and it's because of that I believe
this is a systemd bug.

The problem can also be reached just running "halt" of "systemctl halt"
after booting 16.04 in this machine. Running these commands with "force"
option is working fine.

My Machine Specs:

Dell Inspiron 5447 - BIOS A10
Intel Core i5-4210 Processor
8 GB RAM
480 SSD Sandisk
Hybrid Graphics (i915/amdgpu - Radeon R7 M265)

--- BUG Information 

Reproducible:
Always

Steps to Reproduce:
1.Power on the machine
2.Do something, anything or nothing for a few hours
3.Try to shutdown/reboot using halt, shutdown, reboot, etc

Actual Results:
The computer is not shutting down: "Reached target shutdown" and hangs there.

Expected Results:
Powering off/rebooting the machine.

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

-- 
Poweroff/Reboot Hangs :: Ubuntu 16.04
https://bugs.launchpad.net/bugs/1663794
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1638395] Re: Unable to locate remote printer when printing

[KeithG]

Same here. Adding the line to /etc/hosts with the .local works. The printers 
are automatically detected (as expected) and auto populate the printers. I did 
not have to go to the cups web interface to add them. Without the .local, it 
does not work.
Has worked with every release since 11.04. This is the first release that it 
does not work correctly. Had to do this to both 16.10 computers on my network.

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

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

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

[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Iiro Laiho]

launchpad-groovix: I meant it's too late to do anything about that this
bug slipped into xenial in first place. Fixing the problem afterwards
however should be possible, if little more complicated, sorry for being
unclear. The #1642966 probably is fixable and there has been effort to
do that to the point there is a PPA that's supposed to contain the fix.
However, efforts to make it an official SRU seem to have been stalled
for since a month.

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

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Michael Pardee]

(iiro) "Did you look the cups log to make sure that it really is the
same problem?"

Without any fixes I get these messages about 2 minutes after restarting
cups and cupsd is no longer running:

I [09/Feb/2017:04:08:47 -0600] Printer sharing is off and there are no jobs 
pending, will restart on demand.
I [09/Feb/2017:04:08:47 -0600] Scheduler shutting down normally.

After installing the proposed updates or switching to
BrowseLocalProtocols dnssd those messages go away and cupsd stays
running and client print jobs don't fail with "Connection error:
Transport endpoint is not connected."


(iiro) "but it's now too late to do anything"
Assuming there is absolutely no way to fix bug 1642966, why not switch "-l" to 
"-f" in /lib/systemd/system/cups.service as an official fix?  Is that the only 
way to completely disable this buggy feature?

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

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Touch-packages] [Bug 1663379] Re: Problems in 17.04 alfa 2

[APolihron]

Great job Timo.

** Changed in: ubuntu-mate
   Status: New => Fix Released

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

Title:
  Problems in 17.04 alfa 2

Status in ubuntu-mate:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Destro: Ubuntu Mate
  Windows manager:  Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  OpenGL renderer string: Gallium 0.4 on AMD POLARIS11 (DRM 3.8.0 / 
4.9.0-15-generic, LLVM 3.9.1)
  OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.4
  OpenGL core profile shading language version string: 4.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 13.0.4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
  OpenGL ES profile extensions:

  The problem is that all the pictures that i open on this os i will see them 
blue-is (look at the pics)
  This problem is only for AMD cards, this bug is not present on a laptop with 
intel hd 4000 video card.

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

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

[Touch-packages] [Bug 1663379] Re: Problems in 17.04 alfa 2

[Timo Aaltonen]

cool

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Problems in 17.04 alfa 2

Status in ubuntu-mate:
  New
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Destro: Ubuntu Mate
  Windows manager:  Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  OpenGL renderer string: Gallium 0.4 on AMD POLARIS11 (DRM 3.8.0 / 
4.9.0-15-generic, LLVM 3.9.1)
  OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.4
  OpenGL core profile shading language version string: 4.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 13.0.4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
  OpenGL ES profile extensions:

  The problem is that all the pictures that i open on this os i will see them 
blue-is (look at the pics)
  This problem is only for AMD cards, this bug is not present on a laptop with 
intel hd 4000 video card.

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

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

[Mathieu Trudel-Lapierre]

** Changed in: ubiquity (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

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

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-installer/ubiquity/xenial-proposed

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Committed
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

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

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

[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Iiro Laiho]

launchpad-groovix: Weird. This "feature" shouldn't be active at all when
printer sharing is enabled. Did you look the cups log to make sure that
it really is the same problem?

And yes, this is a serious issue, but if you read the earlier messages,
you see that the fix will cause the bug 1642966 that will result the
breakage of some systems. This really should have been fixed before the
release of 16.04 xenial (or the patch that caused this maybe shouldn't
have been written in first place since it AFAIK solved a thing that was
not really a problem), but it's now too late to do anything to the fact
that it was not and it's now difficult to fix it since breakage of
systems that have a LTS release installed should be avoided.

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

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Touch-packages] [Bug 1622686] Re: double header in 16.10

[Mathieu Trudel-Lapierre]

Since it's reportedly fixed just by modifying the icon theme in SRUs,
let's not introduce changes to ubiquity now.

For yakkety; this is Won't Fix: we're not doing point-releases, so even
if it was available, it would not benefit many installs (given that
ubiquity would need to be on the ISO for the changes to apply to direct
installs (rather than live)).

For xenial, I'm applying the changes to the bzr branch for the next
ubiquity upload.

** Changed in: ubiquity (Ubuntu Yakkety)
   Status: New => Won't Fix

** Changed in: ubiquity (Ubuntu Xenial)
   Status: New => In Progress

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

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

Title:
  double header in 16.10

Status in humanity-icon-theme package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in humanity-icon-theme source package in Xenial:
  Fix Released
Status in ubiquity source package in Xenial:
  In Progress
Status in humanity-icon-theme source package in Yakkety:
  Fix Released
Status in ubiquity source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

  During install and oem-firstboot, the header bar at the top of the
  screen in Ubiquity is twice as tall as it should be on hidpi screens
  (looking like two normal sized header bars stacked on top of each
  other), and the blue a11y icon is double sized.

  This looks obviously incorrect and ugly and makes a bad first
  impression on users installing Ubuntu on a hidpi laptop or customers
  of Ubuntu OEMs booting new machines for the first time.  Arstechnica
  commented negatively on this in their review of Dell's XPS 13:
  http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still-
  delivers-linux-now-embraces-svelte-hardware/

  Users of the Dell XPS 13 are affected as well as users of other brands
  of laptops with hidpi screens.  System76 is temporarily carrying a
  patched version of Humanity to work around this bug.

  The a11y icon is double-sized because the version of Humanity shipping
  in Ubuntu doesn't support @2 hidpi scaling, which results in the
  header bar doubling its height.  Because the header bar is drawn with
  CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars
  stacked one on top of the other.  The fix to the Humanity icon theme
  adds @2 hidpi support, which shrinks the icon and restores the header
  bar to its normal height.

  
  [Test Case]
  ISO install:
  1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer 
with a hidpi screen.
  2. Note the double-sized header and icon during install.
  - Using an iso with a fixed version of Humanity, the header and icon 
should look normal.

  OEM-Firstboot:
  1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi 
screen.
  2. After installing, click the launcher icon to "Prepare for shipping to the 
end user" and reboot.
  3. During oem-firstboot, note the double-sized header and icon during install.
  - To test the fix, install a fixed version of humanity before preparing 
the system for the end user.
  

  [Regression Potential]

  This patch affects the look of anything using the Humanity icon set.
  The look of Nautilus, and many other GTK apps will be affected.  This
  is not a regression but fixes another bug and resolves a discrepancy
  between rendering of icons on hidpi screens vs lowdpi screens.

  The biggest risk for regression comes from the off chance that there
  is an error or omission in the index.theme files.  Comparing icons on
  a broad range of applications and systems should catch this class of
  issues.  If any issues with icons are found, check there.

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

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

[Touch-packages] [Bug 1663747] Re: unity_inspector_get_unity_running improperly returns true on KDE 5.6

[Launchpad Bug Tracker]

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

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

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

Title:
  unity_inspector_get_unity_running improperly returns true on KDE 5.6

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  Chromium uses unity_inspector_get_unity_running to determine if 
close/minimize/maximize buttons are hidden when in a maximized state.
  
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/unity_service.cc?rcl=0ddb4374a9221dba28e9ea8a1edaacb32dcc0861=124

  libunity checks if the com.canonical.Unity Dbus service is created and
  uses that as the return value for unity_inspector_get_unity_running.
  (see src/unity-inspector.vala)

  KDE Plasma 5.6 supports the unity launcher API and creates a
  com.canonical.Unity service.  Even though unity is certainly not
  running, UnityInspector thinks it is.

  Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=594490

  KDE bug report:
  https://bugs.kde.org/show_bug.cgi?id=360403

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

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

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

[Amos Hayes]

I just encountered this bug today when upgrading from a fully updated
14.04 server to 16.04 using do-release-upgrade. My static IP configured
in /etc/network/interfaces was configured to come up on eth0. Logging in
on the console and replacing eth0 with ens32 in that interfaces file and
rebooting fixed things.

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

Title:
  VMWare network interface name change with wily → xenial upgrade

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I just (2016-02-26) upgraded from wily to xenial in my VMWare VM. The
  network interface name changed but the upgrade process didn't change
  /etc/network/interfaces. As such I was left without networking. This
  may be related to bug #1473542, but obviously isn't the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Feb 26 16:54:47 2016
  InstallationDate: Installed on 2015-10-29 (120 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic 
root=UUID=9b4f66d9-95e1-45ff-b167-8ce887475c7e ro elevator=noop
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Touch-packages] [Bug 1370572] Re: Unknown libmtp error when copying content from internal storage to SD card using MTP

[Bib]

Neither mtpfs nor jmtpfs are useful, nor help (uninstalled).

[228663.430977] usb 3-2: new high-speed USB device number 47 using xhci_hcd
[228663.450770] usb 3-2: New USB device found, idVendor=22b8, idProduct=710e
[228663.450781] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[228663.450786] usb 3-2: Product: XT890
[228663.450791] usb 3-2: Manufacturer: Motorola
[228663.450795] usb 3-2: SerialNumber: Medfield2BE00F30
[231590.515653] usb 3-2: USB disconnect, device number 47
[240467.466285] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[241716.808139] usb 3-2: new high-speed USB device number 48 using xhci_hcd
[241716.828029] usb 3-2: New USB device found, idVendor=22b8, idProduct=710e
[241716.828075] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[241716.828095] usb 3-2: Product: XT890
[241716.828101] usb 3-2: Manufacturer: Motorola
[241716.828107] usb 3-2: SerialNumber: Medfield2BE00F30
[244687.571791] usb 3-2: usbfs: process 27218 (events) did not claim interface 
0 before use
[244690.796493] usb 3-2: USB disconnect, device number 48
[249139.690112] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[250458.573693] [drm:intel_dp_start_link_train] *ERROR* too many full retries, 
give up
[250842.719857] usb 3-2: new high-speed USB device number 49 using xhci_hcd
[250842.739777] usb 3-2: New USB device found, idVendor=22b8, idProduct=710e
[250842.739788] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[250842.739794] usb 3-2: Product: XT890
[250842.739798] usb 3-2: Manufacturer: Motorola
[250842.739803] usb 3-2: SerialNumber: Medfield2BE00F30


It seems I can copy/move files, but not folders :

Erreur lors de la copie du fichier dans « 
mtp://[usb:003,049]/M%C3%A9moire%20de%20stockage%20interne/Music ».
This error was when I copied and empty folder. Although speaking of file 
instead of a dir.
There may be or not an error : the french string is /Mémoire de stockage 
interne/Music.
Although copy succeeds when catching files without a parent directory.

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

Title:
  Unknown libmtp error when copying content from internal storage to SD
  card using MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 1
  Desktop: Ubuntu 14.04/14.10

  SUMMARY:
  Unknown libmtp error when copying content from internal storage to SD card 
using MTP.

  This might be the case for someone who has a new memory card and they
  want to copy/move content to it from device's internal storage.

  STEPS:
  1) Connect Ubuntu device to Ubuntu host PC over USB
  2) Attempt to copy/move some music content directly from device's internal 
storage to device's SD card using MTP

  EXPECTED RESULT:
  The content should be copied/moved successfully.

  ACTUAL RESULT:
  The following error is displayed on desktop:
  "libmtp error: Unknown error".

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

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

[Touch-packages] [Bug 1663747] [NEW] unity_inspector_get_unity_running improperly returns true on KDE 5.6

[Thomas Anderson]

Public bug reported:

Chromium uses unity_inspector_get_unity_running to determine if 
close/minimize/maximize buttons are hidden when in a maximized state.
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/unity_service.cc?rcl=0ddb4374a9221dba28e9ea8a1edaacb32dcc0861=124

libunity checks if the com.canonical.Unity Dbus service is created and
uses that as the return value for unity_inspector_get_unity_running.
(see src/unity-inspector.vala)

KDE Plasma 5.6 supports the unity launcher API and creates a
com.canonical.Unity service.  Even though unity is certainly not
running, UnityInspector thinks it is.

Chromium bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=594490

KDE bug report:
https://bugs.kde.org/show_bug.cgi?id=360403

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

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

Title:
  unity_inspector_get_unity_running improperly returns true on KDE 5.6

Status in libunity package in Ubuntu:
  New

Bug description:
  Chromium uses unity_inspector_get_unity_running to determine if 
close/minimize/maximize buttons are hidden when in a maximized state.
  
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/unity_service.cc?rcl=0ddb4374a9221dba28e9ea8a1edaacb32dcc0861=124

  libunity checks if the com.canonical.Unity Dbus service is created and
  uses that as the return value for unity_inspector_get_unity_running.
  (see src/unity-inspector.vala)

  KDE Plasma 5.6 supports the unity launcher API and creates a
  com.canonical.Unity service.  Even though unity is certainly not
  running, UnityInspector thinks it is.

  Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=594490

  KDE bug report:
  https://bugs.kde.org/show_bug.cgi?id=360403

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

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

[Touch-packages] [Bug 1470091] Re: update for V3 kernel bits and improved multiple fan slice support

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~jgrimm/ubuntu/+source/iproute2/+git/iproute2/+merge/317014

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

Title:
  update for V3 kernel bits and improved multiple fan slice support

Status in iproute2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  New
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in ubuntu-fan source package in Trusty:
  Fix Released
Status in iproute2 source package in Vivid:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in ubuntu-fan source package in Vivid:
  Fix Released
Status in iproute2 source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in ubuntu-fan source package in Wily:
  Fix Released

Bug description:
  Fan V2 to V3 transition plan
  

  Currently we have V2 Fan kernel patches paired with an
  /etc/defaults/ubuntu-fan based single fan mapping setup.  We want to
  transition to both V3 Fan kernel patches with fanctl based configuration
  allowing multiple fans to be configured together.

  The new V3 kernel bits fix a significant limitation wherein we could not
  have multiple slices of different overlay address ranges on the same local
  address.  This update introduces an incompatible kernel interface against
  a different device.  The new functionality is a full superset of the old.

  The new V3 kernel bits require updated iproute2 patches to handle the
  new netlink form carrying the expanded map forms.

  In order to manage multiple Fan devices we are updating ubuntu-fan to use
  the new fanctl command line tool and a new fan specific configuration file.

  This plan assumes we are not wedded to the kernel interface, that the
  supported API is the /etc/defaults/ubuntu-fan fan configuration.

  Considerations
  ==
  We are unable to depend on kernel features, as we have no meaninful
  dependencies to kernel versions.

  We need to change the primary configuration file and format for ubuntu-fan
  package to allow multiple slices of multiple fans to be configured
  together.

  We have V2 kernel bits in the wild.  We have V2 iproute in the wild.

  Steps
  =
  1) update fanctl to support both the V2 and V3 kernel interfaces as we cannot
     depend on a kernel version meaningfully.
  2) update iproute2 to support configuring both V2 and V3 kernel interfaces.
  3) update ubuntu-fan with the updated fanctl, supporting migration
     of the /etc/default/fan contents to /etc/network/fan (or directly
     handling that form), and depending on the updated iproute2 bits.
  4) release updated iproute2 bits.
  5) release updated ubuntu-fan bits.
  6) release updated kernel bits (V3 kernel module).

  Testing
  ===
  Need to test old and new kernels with old and new ubuntu-fan levels.
  We obviously do not expect the old userspace to work with the new kernels,
  but it should fail obviously.

  ===

  Discussions on this with the Ubuntu Tech Board are in the thread
  below:

https://lists.ubuntu.com/archives/technical-
  board/2015-July/002122.html

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

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

[Touch-packages] [Bug 1663727] Re: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

[Brian Murray]

** Package changed: ubuntu => xorg (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/1663727

Title:
  16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

Status in xorg package in Ubuntu:
  New

Bug description:
  I've just performed an "apt-get update" on a Dell 2950 Server - which
  was already running 16.04.1 and now it's spewing EDID errors - I'm not
  sure what changed from 16.04.1 to 16.04.2..

  I've attached dmesg to this, but basically it's dumping the following
  in logs and to the screen.

  [drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but
  no|invalid EDID

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

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

[Touch-packages] [Bug 1663727] [NEW] 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I've just performed an "apt-get update" on a Dell 2950 Server - which
was already running 16.04.1 and now it's spewing EDID errors - I'm not
sure what changed from 16.04.1 to 16.04.2..

I've attached dmesg to this, but basically it's dumping the following in
logs and to the screen.

[drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but
no|invalid EDID

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


** Tags: 16.04.2 bot-comment dell edid radeon
-- 
16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors
https://bugs.launchpad.net/bugs/1663727
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1663679] Re: tracker-miner-fs assert failure: *** Error in `/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 0x000055c09c7eab30 ***

[Seth Arnold]

Hello Benjamin, do you have a reliable way to reproduce this crash?

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  tracker-miner-fs assert failure: *** Error in `/usr/lib/tracker
  /tracker-miner-fs': double free or corruption (out):
  0x55c09c7eab30 ***

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  When I boot the computer

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-miner-fs 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/tracker/tracker-miner-fs': double 
free or corruption (out): 0x55c09c7eab30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 10 18:36:26 2017
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2014-12-30 (772 days ago)
  InstallationMedia: Edubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f561dd8c3a8 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f561dd8c4b8 "double free or corruption (out)", action=3) at malloc.c:5046
   _int_free (av=, p=, have_lock=) 
at malloc.c:3902
   __GI___libc_free (mem=) at malloc.c:2982
   g_pattern_match () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-miner-fs assert failure: *** Error in 
`/usr/lib/tracker/tracker-miner-fs': double free or corruption (out): 
0x55c09c7eab30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip epoptes fuse lpadmin mysql mythtv 
plugdev sambashare sudo vboxsf vboxusers video

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

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

[Touch-packages] [Bug 1661799] Re: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players

[David]

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

Parole will no longer play .wmv files in Ubuntu 16.04.2 LTS since the
recent point update.

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

Title:
  [16.04] latest gstreamer1.0 update broke WMA support for some audio &
  video players

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Noise won't play any .wma files after Elementary OS update. It
  displays a message saying it needs the .wma plugin to work (even
  though it has always worked on .wma files). Asks if I want to download
  the plugin but then can't find the plugin.

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

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

[Touch-packages] [Bug 1424114] Re: lvm snapshot is not being autoextended

[Donk]

@Josip Rodin:
On Ubuntu 14, have you installed the package "dmeventd"?

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

Title:
  lvm snapshot is not being autoextended

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After setting auto extend threshold and rebooting, lvm snapshots are
  not being auto extended.

  Steps to recreate:
  1. Using Ubuntu 14.04 LTS
  2. Set snapshot_autoextend_threshold to less than 100
  # grep autoext /etc/lvm/lvm.conf 
  snapshot_autoextend_threshold = 50
  snapshot_autoextend_percent = 20
  3. Reboot server to have lvm reread lvm.conf
  4. Create a snapshot of a mounted logical volume
  # lvcreate -s /dev/testVG/testLV -L 1G -n testLVsnap
  5. Make modifications to mounted logical volume
  6. List logical volumes and snapshots
  # lvs
LV VG Attr  LSize  Pool Origin Data%  Move Log Copy%  
Convert
testLV testVG owi-aos-- 10.00g  
 
testLVsnap testVG swi-a-s--  1.00g  testLV  95.04

  What I expected to have happened:
  Once Data% of snapshot reached the snapshot_autoextend_threshold, the 
snapshot logical volume should have been auto extended.

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

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

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

[Treviño]

** Description changed:

  Snaps that use the app indicator area via Qt can't display their icon
  there.
  
  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77
  
  Some research:
  
  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name
  
  didrocks mentions also:
  
  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp
+ 
+ 

+ 
+ SRU bug for libappindicator:
+ 
+ [Impact]
+ 
+ Indicator icons pointing to a position inside the snap aren't properly
+ found by unity, that shows a "missing icon" emblem
+ 
+ [Test case]
+ 
+ * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
+   in any folder you want
+ * Run:
+   - snapcraft prime
+   - sudo snap try prime
+   - snap run gtk3-appindicator
+ 
+ An indicator should open (with proper icon), then if you select "Custom
+ Themed Icon" from its menu, you should see a proper icon.
+ 
+ When snaps are generated in non updated systems, the icon will be still
+ missing.
+ 
+ [Regression potential]
+ 
+ If $SNAP is defined for an app not running in snap confinement the icons
+ couldn't be properly visible

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

  


  SRU bug for libappindicator:

  [Impact]

  Indicator icons pointing to a position inside the snap aren't properly
  found by unity, that shows a "missing icon" emblem

  [Test case]

  * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as 
snapcraft.yaml
in any folder you want
  * Run:
- snapcraft prime
- sudo snap try prime
- snap run gtk3-appindicator

  An indicator should open (with proper icon), then if you select
  "Custom Themed Icon" from its menu, you should see a proper icon.

  When snaps are generated in non updated systems, the icon will be
  still missing.

  [Regression potential]

  If $SNAP is defined for an app not running in snap confinement the
  icons couldn't be properly visible

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

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

[Touch-packages] [Bug 1663702] Re: Please merge with Debian unstable 2.4.44+dfsg-3

[Nish Aravamudan]

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

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

Title:
  Please merge with Debian unstable 2.4.44+dfsg-3

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  to be completed

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

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

[Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Nish Aravamudan]

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

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

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

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

[Touch-packages] [Bug 1663725] [NEW] root on raid device doesn't get /dev/disk/by-id/md-{name, uuid} symlinks after boot

[Ryan Harper]

Public bug reported:

ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

ubuntu@ubuntu:~$ apt-cache policy systemd
systemd:
  Installed: 232-8
  Candidate: 232-8
  Version table:
 *** 232-8 500
500 http://ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages
100 /var/lib/dpkg/status


3) root@ubuntu:~# ls -al /dev/disk/by-id/md-*
lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-name-ubuntu:foobar -> 
../../md0
lrwxrwxrwx 1 root root 9 Feb 10 19:42 
/dev/disk/by-id/md-uuid-bd97a135:166d5e7e:29e6b0eb:a3cad7c3 -> ../../md0


4)root@ubuntu:~# ls -al /dev/disk/by-id/md-* returns nothing


Note, I can re-trigger events on md0 and the links will appear.

udevadm test $(udevadm info -q path -n /dev/md0)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-8
ProcVersionSignature: User Name 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic ppc64le
.var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
ApportVersion: 2.20.4-0ubuntu1
Architecture: ppc64el
CustomUdevRuleFiles: main_disk-part1.rules.rules third_disk.rules.rules 
md0.rules.rules second_disk-part1.rules.rules second_disk.rules.rules 
third_disk-part1.rules.rules main_disk-part2.rules.rules 
fourth_disk.rules.rules fourth_disk-part1.rules.rules main_disk.rules.rules
Date: Fri Feb 10 19:38:42 2017
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.9.0-15-generic 
root=UUID=a8f0a084-efb9-11e6-9e80-525400123456 ro console=hvc0
ProcLoadAvg: 0.32 0.17 0.06 1/146 6210
ProcLocks:
 1: POSIX  ADVISORY  WRITE 5006 00:12:22238 0 EOF
 2: POSIX  ADVISORY  WRITE 5015 00:12:22033 0 EOF
 3: FLOCK  ADVISORY  WRITE 5007 00:12:22011 0 EOF
 4: POSIX  ADVISORY  WRITE 4979 00:12:21491 0 EOF
 5: POSIX  ADVISORY  WRITE 2643 00:12:13926 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swap.img   file   1157056 0   -1
ProcVersion: Linux version 4.9.0-15-generic (buildd@bos01-ppc64el-020) (gcc 
version 6.3.0 20161229 (User Name 6.3.0-2ubuntu1) ) #16-User Name SMP Fri Jan 
20 15:28:49 UTC 2017
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 1
cpu_coreson: Number of cores online = 1
cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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


** Tags: apport-bug curtin ppc64el uec-images zesty

** Tags added: curtin

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

Title:
  root on raid device doesn't get /dev/disk/by-id/md-{name,uuid}
  symlinks after boot

Status in systemd package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04
  ubuntu@ubuntu:~$ uname -a
  Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  ubuntu@ubuntu:~$ apt-cache policy systemd
  systemd:
Installed: 232-8
Candidate: 232-8
Version table:
   *** 232-8 500
  500 http://ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages
  100 /var/lib/dpkg/status

  
  3) root@ubuntu:~# ls -al /dev/disk/by-id/md-*
  lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-name-ubuntu:foobar 
-> ../../md0
  lrwxrwxrwx 1 root root 9 Feb 10 19:42 
/dev/disk/by-id/md-uuid-bd97a135:166d5e7e:29e6b0eb:a3cad7c3 -> ../../md0

  
  4)root@ubuntu:~# ls -al /dev/disk/by-id/md-* returns nothing

  
  Note, I can re-trigger events on md0 and the links will appear.

  udevadm test $(udevadm info -q path -n /dev/md0)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-8
  ProcVersionSignature: User Name 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: ppc64el
  CustomUdevRuleFiles: main_disk-part1.rules.rules third_disk.rules.rules 
md0.rules.rules second_disk-part1.rules.rules second_disk.rules.rules 
third_disk-part1.rules.rules main_disk-part2.rules.rules 
fourth_disk.rules.rules fourth_disk-part1.rules.rules main_disk.rules.rules
  Date: Fri Feb 10 19:38:42 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

Re: [Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Ryan Tandy]

On Fri, Feb 10, 2017 at 07:03:14PM -, Nish Aravamudan wrote:
>Ah ok, do you want me to send the patches via git to you there? The
>Server Team has adopted
>(https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow) for
>Ubuntu merges so we have our own tree (that's tracking the archive(s)
>for Ubuntu & Debian). But I am happy to send a patch or pull request
>anywhere as you would like.

Not sure. I'll have a look when you're done. I'll probably pull it in as 
a patch, to avoid dragging in the entire second copy of the history.

>Note that in the process of doing the merge, I think I found a bit of
>delta that is actually missing. The last several merges have mentioned
>d/rules installing the apport hook (added in 2.4.23-0ubuntu1), but I
>believe that it got accidentally dropped on the next merge to Debian
>(2.4.23-6ubuntu1) and no one has noticed since -- note that this is a
>good reason to use the above workflow, as the d/changelog mentioned
>delta that I couldn't find! Can you confirm that you see the same. I'll
>fix this in the new merge (but does mean, I think apport for openldap
>has been broken for a long time).

My branch only has ubuntu history starting from when I got involved 
(around 2.4.40) - made one attempt at importing the bzr history into git 
but it didn't go well.

>From the bzr history, it looks to me like it got lost in 
2.4.25-4ubuntu1, when the conversion to dh was merged:

http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/openldap/wily/revision/46#debian/rules

But yes, a long time.

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

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

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

Re: [Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Nish Aravamudan]

On 10.02.2017 [18:27:24 -], Ryan Tandy wrote:
> On Fri, Feb 10, 2017 at 06:12:22PM -, Nish Aravamudan wrote:
> >I'm merging openldap 2.4.44+dfsg-3 today, I hope. Any concerns you have,
> >Ryan?
> 
> Thanks for working on it. I thought zesty would have frozen by now, 
> actually.

I think FF is next week :)

> FWIW, there is an ubuntu branch in the packaging repository on alioth. 
> My usual workflow is to merge release tags into that branch.

Ah ok, do you want me to send the patches via git to you there? The
Server Team has adopted
(https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow) for
Ubuntu merges so we have our own tree (that's tracking the archive(s)
for Ubuntu & Debian). But I am happy to send a patch or pull request
anywhere as you would like.

> I'm expecting to do a -4 with translation updates and bug fixes in the 
> next while. Should be minor update compared to the merge.

Good to know!

Note that in the process of doing the merge, I think I found a bit of
delta that is actually missing. The last several merges have mentioned
d/rules installing the apport hook (added in 2.4.23-0ubuntu1), but I
believe that it got accidentally dropped on the next merge to Debian
(2.4.23-6ubuntu1) and no one has noticed since -- note that this is a
good reason to use the above workflow, as the d/changelog mentioned
delta that I couldn't find! Can you confirm that you see the same. I'll
fix this in the new merge (but does mean, I think apport for openldap
has been broken for a long time).

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

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

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

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[George Hawkins]

I have experienced this problem trying to start lxde using the TightVNC
vncserver from systemd.

The process with the displayed PID is always lxsession.

I resolved it by adding PAMName=login to my unit file.

This suggestion came from https://bugs.archlinux.org/task/42425

Note: I did not have to specify "-fg" to vncserver, as also suggested in
this bug (this option is anyway not supported by TightVNC).

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.18 series:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1663699] Re: Unintended-upgrade in progress during shutdown

[s. c.]

** Description changed:

- i ceased to get shutdowns and restarts on mint cinnamon serena 18.1, so i 
changed from the preferred nvidia driver to the nouveau open source driver. 
since i did that my os is often hanging indefinitely. this seems to be 
prevalent mostly with restarts, but i also get it intermittently with shutdowns.
+ i ceased to get shutdowns and restarts on mint cinnamon serena 18.1, so i 
changed from the preferred nvidia driver to the nouveau open source driver. 
since i made the driver change my os is often hanging indefinitely during 
restarts. this seems to be prevalent mostly with restarts, but i also get it 
intermittently with shutdowns.
  i run an old intel board (dell xps 410-64 bit from 2007).
  i went through all the 4.4 series kernels listed in the terminal. i finally 
tried the newest kernel:4.9.0-040900-generic  , but the bug is still there.
  
  can anyone give me instructions as to how to be rid of "Unintended-upgrade in 
progress during shutdown, sleeping for 5s" so my restarts and shutdowns will 
not hang?
  if you need something else, please give a terminal command that will work.
  
  cinnamon version: 3.2.7
  
  file:///home/sncalaska/Pictures/sys%20info.jpg - i made this an
  attachment

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

Title:
  Unintended-upgrade in progress during shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  i ceased to get shutdowns and restarts on mint cinnamon serena 18.1, so i 
changed from the preferred nvidia driver to the nouveau open source driver. 
since i made the driver change my os is often hanging indefinitely during 
restarts. this seems to be prevalent mostly with restarts, but i also get it 
intermittently with shutdowns.
  i run an old intel board (dell xps 410-64 bit from 2007).
  i went through all the 4.4 series kernels listed in the terminal. i finally 
tried the newest kernel:4.9.0-040900-generic  , but the bug is still there.

  can anyone give me instructions as to how to be rid of "Unintended-upgrade in 
progress during shutdown, sleeping for 5s" so my restarts and shutdowns will 
not hang?
  if you need something else, please give a terminal command that will work.

  cinnamon version: 3.2.7

  file:///home/sncalaska/Pictures/sys%20info.jpg - i made this an
  attachment

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

Henry, do you use Ubuntu Trusty, and install kernels manually? See
comment #79.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

Re: [Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Ryan Tandy]

On Fri, Feb 10, 2017 at 06:12:22PM -, Nish Aravamudan wrote:
>I'm merging openldap 2.4.44+dfsg-3 today, I hope. Any concerns you have,
>Ryan?

Thanks for working on it. I thought zesty would have frozen by now, 
actually.

FWIW, there is an ubuntu branch in the packaging repository on alioth. 
My usual workflow is to merge release tags into that branch.

I'm expecting to do a -4 with translation updates and bug fixes in the 
next while. Should be minor update compared to the merge.

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

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

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

[Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

[Nish Aravamudan]

I'm merging openldap 2.4.44+dfsg-3 today, I hope. Any concerns you have,
Ryan?

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

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Nish Aravamudan]

Hello, I'm a bit confused. As you noted, Xenial (and on) have 2.4.42 as
the base, but the fix you mention is in 2.4.39. So is it not fixed
upstream? Or is this a result of the GnuTLS build?

** 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] [Bug 1663699] [NEW] Unintended-upgrade in progress during shutdown

[s. c.]

Public bug reported:

i ceased to get shutdowns and restarts on mint cinnamon serena 18.1, so i 
changed from the preferred nvidia driver to the nouveau open source driver. 
since i did that my os is often hanging indefinitely. this seems to be 
prevalent mostly with restarts, but i also get it intermittently with shutdowns.
i run an old intel board (dell xps 410-64 bit from 2007).
i went through all the 4.4 series kernels listed in the terminal. i finally 
tried the newest kernel:4.9.0-040900-generic  , but the bug is still there.

can anyone give me instructions as to how to be rid of "Unintended-upgrade in 
progress during shutdown, sleeping for 5s" so my restarts and shutdowns will 
not hang?
if you need something else, please give a terminal command that will work.

cinnamon version: 3.2.7

file:///home/sncalaska/Pictures/sys%20info.jpg - i made this an
attachment

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "my system"
   
https://bugs.launchpad.net/bugs/1663699/+attachment/4816674/+files/sys%20info.jpg

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

Title:
  Unintended-upgrade in progress during shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  i ceased to get shutdowns and restarts on mint cinnamon serena 18.1, so i 
changed from the preferred nvidia driver to the nouveau open source driver. 
since i did that my os is often hanging indefinitely. this seems to be 
prevalent mostly with restarts, but i also get it intermittently with shutdowns.
  i run an old intel board (dell xps 410-64 bit from 2007).
  i went through all the 4.4 series kernels listed in the terminal. i finally 
tried the newest kernel:4.9.0-040900-generic  , but the bug is still there.

  can anyone give me instructions as to how to be rid of "Unintended-upgrade in 
progress during shutdown, sleeping for 5s" so my restarts and shutdowns will 
not hang?
  if you need something else, please give a terminal command that will work.

  cinnamon version: 3.2.7

  file:///home/sncalaska/Pictures/sys%20info.jpg - i made this an
  attachment

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

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

[Touch-packages] [Bug 1663702] [NEW] Please merge with Debian unstable 2.4.44+dfsg-3

[Nish Aravamudan]

Public bug reported:

to be completed

** Affects: openldap (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

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

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  Please merge with Debian unstable 2.4.44+dfsg-3

Status in openldap package in Ubuntu:
  In Progress

Bug description:
  to be completed

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

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

[Touch-packages] [Bug 1663689] [NEW] gettext() does not work on aarch64

[Christoph Müllner]

Public bug reported:

Code to reproduce the bug

I was not able to get the proper translation from gettext() on an aarch64
Ubuntu Xenial machine. The same code however works fine on x86_64.

To reproduce the issue one can use the following instructions:

1) Create the following directory structure:
   mkdir -p fi/LC_MESSAGES

2) Create the file fi/LC_MESSAGES/messages.po with the following content:
msgid ""
msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
msgid "Basic test"
msgstr "Perustesti"

3) Compile a mo:
   msgfmt -o fi/LC_MESSAGES/messages.mo fi/LC_MESSAGES/messages.po

4) Compile the attached file and run it (no special compiler flags used).
   The code essentially does:
   a. setlocale(LC_ALL, "fi_FI");
   b. bindtextdomain("messages", "./locale");
   c. textdomain("messages");
   d. gettext("Basic test")

On aarch64 this results in "Basic test".
On x86_64 this results in "Perustesti".

FWIW, I was able to reproduce this bug on the following aarch64 Linux
distributions as well:

 * Fedora 25 (see [1])
 * CentOS 7
 * OpenSUSE Leap 42.2

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1418635

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

** Attachment added: "Testcase to trigger the bug"
   
https://bugs.launchpad.net/bugs/1663689/+attachment/4816662/+files/gettext_bug.c

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

Title:
  gettext() does not work on aarch64

Status in gettext package in Ubuntu:
  New

Bug description:
  Code to reproduce the bug

  I was not able to get the proper translation from gettext() on an aarch64
  Ubuntu Xenial machine. The same code however works fine on x86_64.

  To reproduce the issue one can use the following instructions:

  1) Create the following directory structure:
 mkdir -p fi/LC_MESSAGES

  2) Create the file fi/LC_MESSAGES/messages.po with the following content:
  msgid ""
  msgstr ""
  "MIME-Version: 1.0\n"
  "Content-Type: text/plain; charset=ISO-8859-1\n"
  "Content-Transfer-Encoding: 8bit\n"
  msgid "Basic test"
  msgstr "Perustesti"

  3) Compile a mo:
 msgfmt -o fi/LC_MESSAGES/messages.mo fi/LC_MESSAGES/messages.po

  4) Compile the attached file and run it (no special compiler flags used).
 The code essentially does:
 a. setlocale(LC_ALL, "fi_FI");
 b. bindtextdomain("messages", "./locale");
 c. textdomain("messages");
 d. gettext("Basic test")

  On aarch64 this results in "Basic test".
  On x86_64 this results in "Perustesti".

  FWIW, I was able to reproduce this bug on the following aarch64 Linux
  distributions as well:

   * Fedora 25 (see [1])
   * CentOS 7
   * OpenSUSE Leap 42.2

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1418635

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

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

[Touch-packages] [Bug 1663690] [NEW] [Satellite C655D, Conexant CX20585, Speaker, Internal] Pulseaudio fails to detect card

[rattei]

Public bug reported:

no sound from speakers or headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   rattei 2121 F...m pulseaudio
 /dev/snd/controlC0:  rattei 2121 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb 10 11:53:01 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-28 (805 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA ATI SB
Symptom_Jack: Speaker, Internal
Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] Pulseaudio fails 
to detect card
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (116 days ago)
dmi.bios.date: 12/20/2011
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-03G02C:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite C655D
dmi.product.version: PSC0YU-03G02C
dmi.sys.vendor: TOSHIBA

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


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

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

Title:
  [Satellite C655D, Conexant CX20585, Speaker, Internal] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  no sound from speakers or headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rattei 2121 F...m pulseaudio
   /dev/snd/controlC0:  rattei 2121 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 10 11:53:01 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-28 (805 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA ATI SB
  Symptom_Jack: Speaker, Internal
  Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] Pulseaudio 
fails to detect card
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (116 days ago)
  dmi.bios.date: 12/20/2011
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-03G02C:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite C655D
  dmi.product.version: PSC0YU-03G02C
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1166789] Re: [Satellite C650, Conexant CX20585, Speaker, Internal] Pulseaudio fails to detect card

[Launchpad Bug Tracker]

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

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

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

Title:
  [Satellite C650, Conexant CX20585, Speaker, Internal] Pulseaudio fails
  to detect card

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  [Satellite C650, Conexant CX20585, Speaker, Internal] Pulseaudio fails
  to detect card

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Apr  9 16:23:40 2013
  InstallationDate: Installed on 2012-07-28 (255 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Speaker, Internal
  Title: [Satellite C650, Conexant CX20585, Speaker, Internal] Pulseaudio fails 
to detect card
  UpgradeStatus: Upgraded to quantal on 2012-10-30 (161 days ago)
  dmi.bios.date: 03/16/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.90
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.90:bd03/16/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC14E-002001AR:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C650
  dmi.product.version: PSC14E-002001AR
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1650934] Re: dimmed labels no effect

[Iain Lane]

sweet, I didn't see this - lucky!

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

Title:
  dimmed labels no effect

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  "dim-label" class to match dimmed labels in Ubuntu 17.04 (Zesty Zapus) no 
effect.
  See screenshot

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

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

[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty

[Adam Conrad]

Removing packages from zesty:
jasper 1.900.1-debian1-2.4+deb8u1 in zesty
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty s390x
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper-runtime 1.900.1-debian1-2.4+deb8u1 in zesty s390x
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty amd64
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty arm64
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty armhf
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty i386
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty powerpc
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty ppc64el
libjasper1 1.900.1-debian1-2.4+deb8u1 in zesty s390x
Comment: Removed from Debian; https://bugs.debian.org/812630
Remove [y|N]? y
1 package successfully removed.


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

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

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

Title:
  Please remove jasper from Zesty

Status in digikam package in Ubuntu:
  Fix Released
Status in jasper package in Ubuntu:
  Fix Released
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  Fix Released

Bug description:
  Jasper has been removed from Debian. It would be great if jasper's
  source and all binary packages could be removed in Ubuntu before 17.04
  is released. Jasper has a long security history and shouldn't remain,
  unmaintained, in universe.

  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html

  As of 2017-02-10, all reverse depends in Zesty have been updated to
  drop dependencies on jasper:

  $ reverse-depends -b src:jasper
  No reverse dependencies found

  
  == Original Report ==

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:

  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b

  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

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

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

[Touch-packages] [Bug 1652348] Re: initrd dhcp fails / ignores valid response

[Paul Graydon]

Note: I've also discovered (unsurprisingly, I guess?) that I see the
exact same behaviour on Ubuntu 14.04.  Can this fix be backported?

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Xenial:
  Fix Released
Status in klibc source package in Yakkety:
  Fix Committed

Bug description:
  [SRU justification]
  Changes to ordering of kernel enumeration of network interfaces, which may 
happen in any release, can regress network configuration from an initramfs.  
Support for netbooting should not depend on interface order, it should work 
reliably on all systems.

  [Test case]
  Detailed reproducer described in 
  .

  [Regression potential]
  Moderate regression potential, because of a relatively large patch touching a 
not-widely-used but still critical piece of code.  Regression testing should 
include verifying that MAAS-booted cloud images still work as expected in a 
variety of environments.

  
  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been (re?)introduced 
that is breaking dhcp booting in the initrd environment.  This is stopping 
instances that use iscsi storage from being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect offending commit:
  # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per 
mount namespace limit on the number of mounts

  Ubuntu kernel bisect offending commit submission:
  https://lkml.org/lkml/2016/10/5/308

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

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

[Touch-packages] [Bug 1663666] Re: max-format is not a positive integer assertion installing unity8-session snap

[Michał Sawicz]

This looks like a network error on your side:

 host assertions.ubuntu.com
assertions.ubuntu.com has address 162.213.33.203
assertions.ubuntu.com has address 162.213.33.202

** Package changed: unity8 (Ubuntu) => unity8-session-snap

** Changed in: unity8-session-snap
   Status: New => Incomplete

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

Title:
  max-format is not a positive integer assertion installing
  unity8-session snap

Status in Unity8 Session Snap:
  Incomplete

Bug description:
  I get this assertion when I run the command unity8-snap-install in my zesty 
vm. 
  This happens with the today's zesty daily image.

  sudo snap install unity8-session --edge --devmode
  error: cannot perform the following tasks:
  - Fetch and check assertions for snap "unity8-session" (439) (Get 
https://assertions.ubuntu.com/v1/assertions/snap-revision/rjPkjvvl9AezpBRMi_cxP6yLUf7hychxwsOg7CT68Ygr9JnccHmvCfymWqUEZGTt?max-format=0:
 dial tcp: lookup assertions.ubuntu.com: no such host)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-session-snap/+bug/1663666/+subscriptions

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

[Touch-packages] [Bug 1612835] Re: Please don't depend on jasper

[Tyler Hicks]

** Description changed:

  Jasper is being removed from Debian. It would be great if this could be
- done in Ubuntu too before 16.10 is released.
+ done in Ubuntu too before 17.04 is released.
  
  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.
  
  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

** Description changed:

- Jasper is being removed from Debian. It would be great if this could be
- done in Ubuntu too before 17.04 is released.
+ Jasper is being removed from Debian. It would be great if jasper's
+ source and all binary packages could be removed in Ubuntu before 17.04
+ is released.
  
  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.
  
  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

** Description changed:

  Jasper is being removed from Debian. It would be great if jasper's
  source and all binary packages could be removed in Ubuntu before 17.04
- is released.
+ is released. Jasper has a long security history and shouldn't remain,
+ unmaintained, in universe.
  
  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.
  
  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b
  
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

** Description changed:

- Jasper is being removed from Debian. It would be great if jasper's
+ Jasper has been removed from Debian. It would be great if jasper's
  source and all binary packages could be removed in Ubuntu before 17.04
  is released. Jasper has a long security history and shouldn't remain,
  unmaintained, in universe.
  
  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html
+ 
+ As of 2017-02-10, all reverse depends in Zesty have been updated to drop
+ dependencies on jasper:
+ 
+ $ reverse-depends -b src:jasper
+ No reverse dependencies found
+ 
+ 
+ == Original Report ==
  
  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)
  
  The last 4 are KDE stuff. Since these 

[Touch-packages] [Bug 1650934] Re: dimmed labels no effect

[Pojar Gheorghe–Ioan]

This is fixed with https://launchpad.net/ubuntu/+source/ubuntu-
themes/16.10+17.04.20170126-0ubuntu1

** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  dimmed labels no effect

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  "dim-label" class to match dimmed labels in Ubuntu 17.04 (Zesty Zapus) no 
effect.
  See screenshot

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

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

[Touch-packages] [Bug 1663666] [NEW] max-format is not a positive integer assertion installing unity8-session snap

[Sergio Cazzolato]

Public bug reported:

I get this assertion when I run the command unity8-snap-install in my zesty vm. 
This happens with the today's zesty daily image.

sudo snap install unity8-session --edge --devmode
error: cannot perform the following tasks:
- Fetch and check assertions for snap "unity8-session" (439) (Get 
https://assertions.ubuntu.com/v1/assertions/snap-revision/rjPkjvvl9AezpBRMi_cxP6yLUf7hychxwsOg7CT68Ygr9JnccHmvCfymWqUEZGTt?max-format=0:
 dial tcp: lookup assertions.ubuntu.com: no such host)

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

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

Title:
  max-format is not a positive integer assertion installing
  unity8-session snap

Status in unity8 package in Ubuntu:
  New

Bug description:
  I get this assertion when I run the command unity8-snap-install in my zesty 
vm. 
  This happens with the today's zesty daily image.

  sudo snap install unity8-session --edge --devmode
  error: cannot perform the following tasks:
  - Fetch and check assertions for snap "unity8-session" (439) (Get 
https://assertions.ubuntu.com/v1/assertions/snap-revision/rjPkjvvl9AezpBRMi_cxP6yLUf7hychxwsOg7CT68Ygr9JnccHmvCfymWqUEZGTt?max-format=0:
 dial tcp: lookup assertions.ubuntu.com: no such host)

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

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

[Touch-packages] [Bug 1663664] [NEW] Long time to reconnect keyboard

[Jason Hunter]

Public bug reported:

When I've been away from the computer for a while, the keyboard takes
long time to reconnect, like 30-60 seconds.

Why is that?

Can this be configured? Is there a time interval when the system checks
if something is trying to connect?

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

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

Title:
  Long time to reconnect keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  When I've been away from the computer for a while, the keyboard takes
  long time to reconnect, like 30-60 seconds.

  Why is that?

  Can this be configured? Is there a time interval when the system
  checks if something is trying to connect?

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

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

[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Jason Hunter]

what does it mean that "This bug report was converted into a question:
question #260266"

does it mean it's no longer a bug?

why does it say unassigned? isn't it supposed to be assigned to the
bluetooth group?

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

[Alberto Salvia Novella]

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => Medium

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Medium => High

** Changed in: webbrowser-app (Ubuntu)
   Importance: Medium => High

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

Title:
  webbrowser-app crashed with SIGABRT in
  oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Crash upon maximizimg window.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160318-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 14:37:35 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
   __GI_exit (status=) at exit.c:104
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

[Scott Moser]

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed
Status in resolvconf source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
    lxc launch ubuntu-daily:xenial x1
    lxc exec x1 /bin/bash

    # make sure you're on systemd-229-4ubuntu13
    apt update && apt install -y systemd

    # enable networkd and netplan
    apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
  EOF
    sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

    netplan generate

    # make sure cloud-init.service uses networkd
    sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service

    reboot

    # check that the order of execution with:
    journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

    # the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 1241752] Re: Crash when opening image files larger than 5M (>5M)

[Alberto Salvia Novella]

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

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

Title:
  Crash when opening image files larger than 5M (>5M)

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  This is similar to the bug reported here: http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=710701

  However, the crash that is now getting generated is from an entirely
  different call and file.  Specifically, the error is:

  eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: 
_cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed.
  Aborted (core dumped)

  In the message above, I was using eog, but this affects other apps,
  like gThumb as well.

  In terms of the environment, I'm using Ubuntu 13.10 on an 64-bit
  machine, and am using libcairo2-1.12.16.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libcairo2 1.12.16-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Fri Oct 18 11:08:27 2013
  InstallationDate: Installed on 2013-04-25 (176 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cairo
  UpgradeStatus: Upgraded to saucy on 2013-10-15 (2 days ago)

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

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

[Touch-packages] [Bug 1663647] [NEW] cannot add printer

[Neil Mercer]

Public bug reported:

Terminal log follows

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

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/libappindicator/incons-paths-on-snap-xenial

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

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

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

[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown

[Jogarem]

Well ok that was my first thought,too (boolean) so my first tests were
misleading then. I tested a little bit more and find something maybe
more useful.

When using Ubuntu 16.04.2 fresh installed and I set in
/etc/apt/apt.conf.d/50unattended-upgrades:

Unattended-Upgrade::InstallOnShutdown "true";

it seems to have no effect. Upgrades are there but they do not get installed. I 
get no plymouth message on shutdown.
Same when set to "True".

When I change /usr/share/unattended-upgrades/unattended-upgrade-
shutdown:

(line 120 again)

# check if we need to run unattended-upgrades on shutdown and if so,
# run it
p = None
apt_pkg.init_config()
before <>if apt_pkg.config.find_b("Unattended-Upgrade::InstallOnShutdown", 
False) == True:
env = copy.copy(os.environ)
env["UNATTENDED_UPGRADES_FORCE_INSTALL_ON_SHUTDOWN"] = "1"


Then it seems to work like expected.

Now when i set:

"Unattended-Upgrade::InstallOnShutdown "true";

in /etc/apt/apt.conf.d/50unattended-upgrades it starts upgrading on
shutdown (I see the plymouth message "Unattended Upgrades..."). When I
set it to "false" or just outcomment the whole line it do nothing on
shutdown. So exact the behavior I expect.

Well I'm not a python expert but it seems to me that the  thing
works not as it should or maybe has changed in python3 some how? It may
affect all other statements as well then (like MailOnlyOnError etc) but
I haven't tested them yet...

With the above patch it works for me as it should. At least for the
shutdown setting.

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

Title:
  apt/unattended-upgrades stalls shutdown

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots
  hang while "starting unattended upgrades shutdown". This hang stalls
  the shutdown process for 5-10 mins.

  If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto-
  upgrades and/or 50unattended-upgrades, the problems occurs.

  If I terminate the service before shutdown/reboot (sudo service
  unattended-upgrades stop) the problem still occurs.

  If I remove the package (sudo apt remove unattended-upgrades) the
  problem no longer occurs.

  This occurs on a freshly installed version of Ubuntu Server 16.04.1
  (both unattended-upgrades installed via install GUI or manual install
  of unattended-upgrades)

  Both Kern.log & syslog do not show the shutdown process (I believe
  because the filesystems have already unmounted)

  Original report: http://askubuntu.com/questions/878630/apt-unattended-
  upgrades-stalls-shutdown

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

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

[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

[Kfme]

Hello!
Same problem here. Ubuntu 16.04 LTS. Updated from 14.04 a few months ago. No 
problem back then but, since a few weeks, I had the same message. I haven't 
tried all these options but I just wanted to mention the fact that this bug 
still exists.

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

Title:
  fsck runs on every boot (clean install, single ext4 filesystem)

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  fsck runs early on *every* boot (and always says "/dev/sda1: clean ...")
  The system was always shut down using the regular Unity mechanism (Gear->Shut 
Down...)

  Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1"
  shows the date of installation and never changes.

  This system is a brand new, clean install from the 15.10 beta2 iso, with 
subsequent updates.
  I took all the installer defaults, which created a single ext4 file system.

  Please see attached:
bootscreen.png - screen shot of fsck output at start of bootup (from VM 
window)
dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upstart 1.13.2-0ubuntu16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:10:05 2015
  InstallationDate: Installed on 2015-10-07 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

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

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

[Touch-packages] [Bug 1370572] Re: Unknown libmtp error when copying content from internal storage to SD card using MTP

[Bib]

ubuntu 14.04.5 - Dell XPS13-L322X
Nemo
I had to install mtpfs
Copying from mtp device to same partition or another inside fails with libmtp 
error : unknown error
Moving inside the same partition works, but only from the left USB port.
Moving from one partition to the other works (still left USB port) this way : 
move original folders/files to the PC disk, then from the PC disk to the 2nd 
partition.

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

Title:
  Unknown libmtp error when copying content from internal storage to SD
  card using MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 1
  Desktop: Ubuntu 14.04/14.10

  SUMMARY:
  Unknown libmtp error when copying content from internal storage to SD card 
using MTP.

  This might be the case for someone who has a new memory card and they
  want to copy/move content to it from device's internal storage.

  STEPS:
  1) Connect Ubuntu device to Ubuntu host PC over USB
  2) Attempt to copy/move some music content directly from device's internal 
storage to device's SD card using MTP

  EXPECTED RESULT:
  The content should be copied/moved successfully.

  ACTUAL RESULT:
  The following error is displayed on desktop:
  "libmtp error: Unknown error".

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

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

[Touch-packages] [Bug 1370572] Re: Unknown libmtp error when copying content from internal storage to SD card using MTP

[Bib]

ubuntu 14.04.5 - Dell XPS13-L322X
Nemo
I had to install mtpfs on the PC (and enable USB debuging in the phone).
Copying from mtp device to same partition or another inside fails with libmtp 
error : unknown error
Moving inside the same partition works, but only from the left USB port.
Moving from one partition to the other works (still left USB port) this way : 
move original folders/files to the PC disk, then from the PC disk to the 2nd 
partition.

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

Title:
  Unknown libmtp error when copying content from internal storage to SD
  card using MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 1
  Desktop: Ubuntu 14.04/14.10

  SUMMARY:
  Unknown libmtp error when copying content from internal storage to SD card 
using MTP.

  This might be the case for someone who has a new memory card and they
  want to copy/move content to it from device's internal storage.

  STEPS:
  1) Connect Ubuntu device to Ubuntu host PC over USB
  2) Attempt to copy/move some music content directly from device's internal 
storage to device's SD card using MTP

  EXPECTED RESULT:
  The content should be copied/moved successfully.

  ACTUAL RESULT:
  The following error is displayed on desktop:
  "libmtp error: Unknown error".

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

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

[Touch-packages] [Bug 1663622] Re: package linux-firmware 1.161.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-firmware 1.161.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The error occured during installation of Ubuntu 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.161.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Feb 10 13:21:35 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-11-29 (72 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.161.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to yakkety on 2017-02-10 (0 days ago)

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

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

[Touch-packages] [Bug 1663622] [NEW] package linux-firmware 1.161.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Amit Singh]

Public bug reported:

The error occured during installation of Ubuntu 16.10.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-firmware 1.161.1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Fri Feb 10 13:21:35 2017
Dependencies:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2016-11-29 (72 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: initramfs-tools
Title: package linux-firmware 1.161.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: Upgraded to yakkety on 2017-02-10 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package linux-firmware 1.161.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The error occured during installation of Ubuntu 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.161.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Feb 10 13:21:35 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-11-29 (72 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.161.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to yakkety on 2017-02-10 (0 days ago)

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

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

[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

[Chris Coulson]

Hrmmm, does X crash here too?

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

Title:
  webbrowser-app crashed with SIGABRT in
  oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Crash upon maximizimg window.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160318-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 14:37:35 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
   __GI_exit (status=) at exit.c:104
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1663613] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade:
  trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is
  also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  nothing wrong. The crash popup at ubuntu startup is bothering me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Feb  9 15:54:22 2017
  DuplicateSignature:
   package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4
   Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack):
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', 
which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2017-01-24 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: 
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1663379] Re: Problems in 17.04 alfa 2

[APolihron]

but llvm-toolchain-3.9 (1:3.9.1-4ubuntu3) fix the problem!!!

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

Title:
  Problems in 17.04 alfa 2

Status in ubuntu-mate:
  New
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Destro: Ubuntu Mate
  Windows manager:  Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  OpenGL renderer string: Gallium 0.4 on AMD POLARIS11 (DRM 3.8.0 / 
4.9.0-15-generic, LLVM 3.9.1)
  OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.4
  OpenGL core profile shading language version string: 4.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 13.0.4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
  OpenGL ES profile extensions:

  The problem is that all the pictures that i open on this os i will see them 
blue-is (look at the pics)
  This problem is only for AMD cards, this bug is not present on a laptop with 
intel hd 4000 video card.

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

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

[Touch-packages] [Bug 1663379] Re: Problems in 17.04 alfa 2

[APolihron]

Nope it doesn't

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

Title:
  Problems in 17.04 alfa 2

Status in ubuntu-mate:
  New
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Destro: Ubuntu Mate
  Windows manager:  Marco(compton GPU compositor)
  Video card: Radeon RX 460 4GB 128bit
  OpenGL vendor string: X.Org

  OpenGL renderer string: Gallium 0.4 on AMD POLARIS11 (DRM 3.8.0 / 
4.9.0-15-generic, LLVM 3.9.1)
  OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.4
  OpenGL core profile shading language version string: 4.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 13.0.4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
  OpenGL ES profile extensions:

  The problem is that all the pictures that i open on this os i will see them 
blue-is (look at the pics)
  This problem is only for AMD cards, this bug is not present on a laptop with 
intel hd 4000 video card.

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

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

[Touch-packages] [Bug 1663613] [NEW] package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev

[ruben dos santos barros]

Public bug reported:

nothing wrong. The crash popup at ubuntu startup is bothering me.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Feb  9 15:54:22 2017
DuplicateSignature:
 package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4
 Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack):
  trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which 
is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
InstallationDate: Installed on 2017-01-24 (16 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: zlib
Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: 
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade:
  trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is
  also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  nothing wrong. The crash popup at ubuntu startup is bothering me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Feb  9 15:54:22 2017
  DuplicateSignature:
   package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4
   Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack):
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', 
which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2017-01-24 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: 
trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in 
package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

[Chris Coulson]

This is not a bug in Oxide - the CHECK failure in this case is a red
herring and is a side effect of a bug elsewhere that triggers an unclean
exit() (see bug 1663609)

** Project changed: oxide => qtdeclarative-opensource-src (Ubuntu)

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

Title:
  webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

Status in Canonical System Image:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  17.04 unity7

  ~$ webbrowser-app 
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information
  could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
  APP_ID isn't set, the handler can not be registered
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
  Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
  Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
  Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
  Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

  (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  APP_ID isn't set, the handler ignored
  qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  ^CSegmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)

[Lukáš Tinkl]

** Branch linked: lp:~lukas-kde/ubuntu-ui-toolkit/asyncDbusClipboard

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

Title:
  [regression] Logging in to Unity8 takes 25 seconds (the default DBus
  timeout)

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  [regression] Logging in to Unity8 takes 25 seconds (at least on the
  first login after a fresh boot) ...

  [2017-02-09:11:35:05.263] Empty ualAppId result for "qterminal_drop"
  [2017-02-09:11:35:05.263] Failed to get app info for app "qterminal_drop"
  [2017-02-09:11:35:05.308] Failed to get all properties for 
"com.ubuntu.location.providers.here.AccountsService" : "No such interface"
  [2017-02-09:11:35:05.310] CursorImageProvider: "" not found (nor its 
fallbacks, if any). Going for "left_ptr" as a last resort.
  [2017-02-09:11:35:05.328] qtmir.applications: applicationManagerSingleton - 
engine= 0x56395e4119b0 scriptEngine= 0x56395e4119b0
  [2017-02-09:11:35:05.330] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:05.333] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:35:05.334] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.687] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Keymap applied

  

  [2017-02-09:11:38:19.249] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:19.252] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:38:19.253] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Keymap applied

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

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

[Touch-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later

[Kevin DuBois]

Its even a bit more narrow than that, software clients of android work
(its just ShmBuffer-backed software clients that would be affected).
Furthermore, the nested compositor had to select GL rendering instead of
pasthrough (which is probably common in the wild), and the surface had
to be larger than 480x480.

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

Title:
  [regression] Software clients of nested servers are all black in Mir
  0.25.0 and later

Status in Mir:
  In Progress
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Committed
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

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

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

[Touch-packages] [Bug 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

[Ted Gould]

The log file makes this look like an app that is exporting the unity7
interface as well as the unity8 one. But the snapd in zesty doesn't have
a unity8 interface. So we're starting it as a unity7 app. It is not
realizing this and trying to connect to Mir, even after we've setup XMir
for it.

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

Title:
  [regression] Some apps fail to start with [QPA]
  UbuntuClientIntegration: connection to Mir server failed.

Status in Canonical System Image:
  Confirmed
Status in platform-api:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in Unity8 Session Snap:
  Invalid
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  Invalid

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

  Test Case
  1. Open the app drawer
  2. Launch an app (eg calculator)

  Expected result
  It starts successfully and the app works as expected

  Actual Result
  It launches, the loading screen then a black screen is shown for a sort 
moment, then the window closes.

  They all report:

  >>>
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [QPA] UbuntuClientIntegration: connection to Mir server failed.

  Mir returned: "Failed to connect to server socket: Permission denied"
  <<<

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

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

[Touch-packages] [Bug 1649262] [NEW] webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

17.04 unity7

~$ webbrowser-app 
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.

(webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
UCUriHandler: Empty "APP_ID" environment variable, ignoring.
unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
APP_ID isn't set, the handler can not be registered
Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

(webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
APP_ID isn't set, the handler ignored
qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
^CSegmentation fault (core dumped)

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: Confirmed

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Critical
 Status: Confirmed


** Tags: crash startup
-- 
webbrowser app Segmentation fault (core dumped) on 17.04 Unity7
https://bugs.launchpad.net/bugs/1649262
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtdeclarative-opensource-src 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 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)

[Christian Dywan]

** Tags added: unity8

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

Title:
  [regression] Logging in to Unity8 takes 25 seconds (the default DBus
  timeout)

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  [regression] Logging in to Unity8 takes 25 seconds (at least on the
  first login after a fresh boot) ...

  [2017-02-09:11:35:05.263] Empty ualAppId result for "qterminal_drop"
  [2017-02-09:11:35:05.263] Failed to get app info for app "qterminal_drop"
  [2017-02-09:11:35:05.308] Failed to get all properties for 
"com.ubuntu.location.providers.here.AccountsService" : "No such interface"
  [2017-02-09:11:35:05.310] CursorImageProvider: "" not found (nor its 
fallbacks, if any). Going for "left_ptr" as a last resort.
  [2017-02-09:11:35:05.328] qtmir.applications: applicationManagerSingleton - 
engine= 0x56395e4119b0 scriptEngine= 0x56395e4119b0
  [2017-02-09:11:35:05.330] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:05.333] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:35:05.334] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.687] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Keymap applied

  

  [2017-02-09:11:38:19.249] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:19.252] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:38:19.253] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Keymap applied

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

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

[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[dino99]

After experimenting, the faulty package seems that newer nvidia-375
driver from the zesty-proposed archive ( lp:1662860 ). Made the
reverting to avoid the too many crashes.

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)

[Lukáš Tinkl]

** Branch linked: lp:~lukas-kde/ubuntu-ui-toolkit/asyncDbusClipboard

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

Title:
  [regression] Logging in to Unity8 takes 25 seconds (the default DBus
  timeout)

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  [regression] Logging in to Unity8 takes 25 seconds (at least on the
  first login after a fresh boot) ...

  [2017-02-09:11:35:05.263] Empty ualAppId result for "qterminal_drop"
  [2017-02-09:11:35:05.263] Failed to get app info for app "qterminal_drop"
  [2017-02-09:11:35:05.308] Failed to get all properties for 
"com.ubuntu.location.providers.here.AccountsService" : "No such interface"
  [2017-02-09:11:35:05.310] CursorImageProvider: "" not found (nor its 
fallbacks, if any). Going for "left_ptr" as a last resort.
  [2017-02-09:11:35:05.328] qtmir.applications: applicationManagerSingleton - 
engine= 0x56395e4119b0 scriptEngine= 0x56395e4119b0
  [2017-02-09:11:35:05.330] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:05.333] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:35:05.334] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.687] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Keymap applied

  

  [2017-02-09:11:38:19.249] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:19.252] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:38:19.253] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Keymap applied

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

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

[Touch-packages] [Bug 1663602] [NEW] xorg bug happens after rebooting

[Ross Steiner]

Public bug reported:

Was not doing anything specifically, happened after reboot.

Mouse cursor seemed to be very jerky when moving around and after the
crash notification appeared.  Has returned to normal.  Probably not
directly related, but who knows.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Fri Feb 10 07:22:59 2017
DistUpgraded: 2017-02-08 17:19:08,280 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 530 [1028:06e5]
   Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5]
InstallationDate: Installed on 2017-02-08 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Precision 5510
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=6f33b7d9-0f66-4edc-8921-b7a9b44a8f6c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2017-02-08 (1 days ago)
dmi.bios.date: 12/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.19
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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


** Tags: amd64 apport-bug ubuntu yakkety

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

Title:
  xorg bug happens after rebooting

Status in xorg package in Ubuntu:
  New

Bug description:
  Was not doing anything specifically, happened after reboot.

  Mouse cursor seemed to be very jerky when moving around and after the
  crash notification appeared.  Has returned to normal.  Probably not
  directly related, but who knows.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Fri Feb 10 07:22:59 2017
  DistUpgraded: 2017-02-08 17:19:08,280 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e5]
 Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5]
  InstallationDate: Installed on 2017-02-08 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=6f33b7d9-0f66-4edc-8921-b7a9b44a8f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-02-08 (1 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

[Ryan Beisner]

FWIW - I'm using MAAS 2.1.3+bzr5573-0ubuntu1 (16.04.1) in a LXD
container successfully in production, albeit privileged, per
https://docs.ubuntu.com/maas/2.1/en/installconfig-lxd-install.

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

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

[Touch-packages] [Bug 1663555] Re: Repeated suspend and splash screen freeze after upgrading to 16.04

[Eero Aaltonen]

** Summary changed:

- Problems with nvidia-367 and Quadro K2100M GPU after upgrading to 16.04
+ Repeated suspend and splash screen freeze after upgrading to 16.04

** Description changed:

  Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with
  
  nvidia-367.57-0ubuntu0.16.04.1
  
  After upgrade two graphics problems have occurred.
  
- 1) When booting with two monitors & extended desktop the computer will
- go to suspend mode. Sometimes it will go into suspend repeatedly.
+ 1) When booting with two monitors & extended desktop the computer will go to 
suspend mode. Sometimes it will go into suspend repeatedly.
+ EDIT: although I updated to nvidia-375.26, this seems to occur when the 
laptops own screen is closed. Previously this would cause only a single suspend.
  
  2) Splash screen at startup that prompts for LUKS passphrase has really low 
resolution and does not accept input to decrypt the filesystem. Booting is 
currently only possible with the 'nomodeset' option.
  Kernel version does not affect this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 10 12:48:59 2017
  DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
  InstallationDate: Installed on 2014-09-24 (870 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 nomodeset
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago)
  dmi.bios.date: 05/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0FVDR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb 10 12:44:57 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.18.4-0ubuntu0.2

** Description changed:

  Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with
- 
  nvidia-367.57-0ubuntu0.16.04.1
  
- After upgrade two graphics problems have occurred.
+ After upgrade two problems have occurred.
  
  1) When booting with two monitors & extended desktop the computer will go to 
suspend mode. Sometimes it will go into suspend repeatedly.
- EDIT: although I updated to nvidia-375.26, this seems to occur when the 
laptops 

[Touch-packages] [Bug 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved

[DimkaS]

Still present for me

[176007.813051] audit: type=1400 audit(1486720189.738:122):
apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=14715 comm="EvJobScheduler"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0

[179389.232131] audit: type=1400 audit(1486723571.310:133):
apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=17305 comm="evince"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.10
DISTRIB_CODENAME=yakkety
DISTRIB_DESCRIPTION="Ubuntu 16.10"

Not sure if it affects something.

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

Title:
  AppArmor nameservice abstraction doesn't allow communication with
  systemd-resolved

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Invalid
Status in apparmor source package in Yakkety:
  Fix Released
Status in ntp source package in Yakkety:
  Invalid

Bug description:
  [ Impact ]

  Processes confined by AppArmor profiles making use of the nameservice
  AppArmor abstraction are unable to access the systemd-resolved network
  name resolution service. The nsswitch.conf file shipped in Yakkety
  puts the nss-resolve plugin to use which talks to systemd-resolved
  over D-Bus. The D-Bus communication is blocked for the confined
  processes described above and those processes will fallback to the
  traditional means of name resolution.

  [ Test Case ]

  * Use ntpd to test:
$ sudo apt-get install -y ntp
...
$ sudo systemctl stop ntp

# in another terminal, watch for AppArmor denials
$ dmesg -w

# in the original terminal, start ntp
$ sudo systemctl start ntp

# You'll see a number of denials on the system_bus_socket file:
audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0

   * Use tcpdump to test:

 # Capture traffic on whichever network interface you're currently using
 $ sudo tcpdump -i eth0

 # Look in /var/log/syslog for denials on the system_bus_socket file:
 audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/tcpdump" 
name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  In both situations, ntpd and tcpdump will seemingly work as expected
  due to the name resolution fallback configured in nsswitch.conf.
  However, neither confined process will be using systemd-resolved for
  name resolution.

  [ Regression Potential ]

  This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined-
  by-default programs to start using systemd-resolved. There is some
  potential for regression since those applications have not been
  previously using systemd-resolved.

  [ Original bug description ]

  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Henry]

Ok, I had to manually remove the files as they were added.. after that,
it worked as intended.

Funny thing is, all solutions provide here say that you need to enable
the removal of unused dependencies by setting this:

`Unattended-Upgrade::Remove-Unused-Dependencies "true"`

Problem is.. I already had this set in my `/etc/apt/apt.conf.d
/50unattended-upgrades`..

This is broken, design or not.. it IS a bug.. how can we fix this
permanently? I have servers running unattended upgrades that have
overflowing /boot partitions which is annoying AF.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Henry]

I can't even run `apt-get autoremove` because it starts filling up my
/boot with old kernels until it runs out of space.. who the hell
designed this madness?

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1630872] Re: Clear text (x) does not clear the first suggested but not committed word

[Adnane Belmadiaf]

Maybe this is related bug 1661890

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

Title:
  Clear text (x) does not clear the first suggested but not committed
  word

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  When the "Word suggestions" option in the "Language & Text" settings then the 
(x) clear button does not clear the first not committed word from the text 
input.
  It seems that the suggested word is not yet in the text innut but only in the 
input method and the clear button does not clear the input method.
  After the first word is committed, the second suggestion is cleared if you 
clear the content.

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

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

[Touch-packages] [Bug 1661890] Re: TextField in a Dialog returns nothing if prediction is enabled

[Adnane Belmadiaf]

** Summary changed:

- TextField in a a Dialog returns nothing if prediction is enabled
+ TextField in a Dialog returns nothing if prediction is enabled

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

Title:
  TextField in a Dialog returns nothing if prediction is enabled

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  TextField in a Dialog returns nothing if prediction is enabled,
  TextField return its content correctly when used alone, demo attached.

  using : OTA14

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

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

[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[dino99]

** Description changed:

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.
+ 
+ Got an other crash, and that time 'sound' is fully lost (pulseaudio not
+ reloaded). Wonder if lp:1662860 can be concerned.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  oem4084 F pulseaudio
-  /dev/snd/controlC0:  oem4084 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  oem4084 F pulseaudio
+  /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
-  __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
-  __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
-  snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
-  ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
-  ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
+  __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
+  __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
+  snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
+  ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
+  ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  

[Touch-packages] [Bug 1663555] Re: Problems with nvidia-367 and Quadro K2100M GPU after upgrading to 16.04

[Eero Aaltonen]

** Information type changed from Public Security to Public

** Description changed:

  Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with
  
  nvidia-367.57-0ubuntu0.16.04.1
  
  After upgrade two graphics problems have occurred.
  
- 1) When booting with two monitors & extended desktop the monitors will
- go blank (this is accompanied by a popping sound, probably the
- speakers). This has also occurred repeatedly (tests ongoing).
+ 1) When booting with two monitors & extended desktop the computer will
+ go to suspend mode. Sometimes it will go into suspend repeatedly.
  
- 2) Splash screen at startup that prompts for LUKS passphrase has really
- low resolution and does not accept input to decrypt the filesystem.
- Booting is currently only possible with the 'nomodeset' option.
+ 2) Splash screen at startup that prompts for LUKS passphrase has really low 
resolution and does not accept input to decrypt the filesystem. Booting is 
currently only possible with the 'nomodeset' option.
+ Kernel version does not affect this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 10 12:48:59 2017
  DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
-  bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
-  nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
+  bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
+  nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
+  NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
  InstallationDate: Installed on 2014-09-24 (870 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 nomodeset
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago)
  dmi.bios.date: 05/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0FVDR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb 10 12:44:57 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  

[Touch-packages] [Bug 1663559] [NEW] network-manager 1.2.2 blocked reboot/shutdown process

[Alex Tu]

Public bug reported:

the reboot process is blocked by network-manager time out on current
xenial network-manager 1.2.2, but passed on 1.2.4 which is on proposed
ppa.

Please see attached photo which took for the timeout message shown on
screen.

some more information of proposed network-manager
u@u-7920-Tower:~$ apt-cache policy network-manager
network-manager:
  Installed: 1.2.2-0ubuntu0.16.04.3
  Candidate: 1.2.4-0ubuntu0.16.04.1
  Version table:
 1.2.4-0ubuntu0.16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
 *** 1.2.2-0ubuntu0.16.04.3 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

fix need landing LP: #1645698
fix required by: LP: #1655901

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

** Attachment added: "photo6118623076196394939.jpg"
   
https://bugs.launchpad.net/bugs/1663559/+attachment/4816475/+files/photo6118623076196394939.jpg

** Description changed:

  the reboot process is blocked by network-manager time out on current
  xenial network-manager 1.2.2, but passed on 1.2.4 which is on proposed
  ppa.
  
+ Please see attached photo which took for the timeout message shown on
+ screen.
+ 
  some more information of proposed network-manager
  u@u-7920-Tower:~$ apt-cache policy network-manager
  network-manager:
-   Installed: 1.2.2-0ubuntu0.16.04.3
-   Candidate: 1.2.4-0ubuntu0.16.04.1
-   Version table:
-  1.2.4-0ubuntu0.16.04.1 500
- 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
-  *** 1.2.2-0ubuntu0.16.04.3 500
- 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1.1.93-0ubuntu4 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installed: 1.2.2-0ubuntu0.16.04.3
+   Candidate: 1.2.4-0ubuntu0.16.04.1
+   Version table:
+  1.2.4-0ubuntu0.16.04.1 500
+ 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
+  *** 1.2.2-0ubuntu0.16.04.3 500
+ 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1.1.93-0ubuntu4 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

** Description changed:

  the reboot process is blocked by network-manager time out on current
  xenial network-manager 1.2.2, but passed on 1.2.4 which is on proposed
  ppa.
  
  Please see attached photo which took for the timeout message shown on
  screen.
  
  some more information of proposed network-manager
  u@u-7920-Tower:~$ apt-cache policy network-manager
  network-manager:
    Installed: 1.2.2-0ubuntu0.16.04.3
    Candidate: 1.2.4-0ubuntu0.16.04.1
    Version table:
   1.2.4-0ubuntu0.16.04.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 
+ fix need landing LP: #1645698
+ fix required by: LP: #1655901

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

Title:
  network-manager 1.2.2 blocked reboot/shutdown process

Status in network-manager package in Ubuntu:
  New

Bug description:
  the reboot process is blocked by network-manager time out on current
  xenial network-manager 1.2.2, but passed on 1.2.4 which is on proposed
  ppa.

  Please see attached photo which took for the timeout message shown on
  screen.

  some more information of proposed network-manager
  u@u-7920-Tower:~$ apt-cache policy network-manager
  network-manager:
    Installed: 1.2.2-0ubuntu0.16.04.3
    Candidate: 1.2.4-0ubuntu0.16.04.1
    Version table:
   1.2.4-0ubuntu0.16.04.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  fix need landing LP: #1645698
  fix required by: LP: #1655901

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

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

[Touch-packages] [Bug 1663555] [NEW] Problems with nvidia-367 and Quadro K2100M GPU after upgrading to 16.04

[Eero Aaltonen]

*** This bug is a security vulnerability ***

Public security bug reported:

Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with

nvidia-367.57-0ubuntu0.16.04.1

After upgrade two graphics problems have occurred.

1) When booting with two monitors & extended desktop the monitors will
go blank (this is accompanied by a popping sound, probably the
speakers). This has also occurred repeatedly (tests ongoing).

2) Splash screen at startup that prompts for LUKS passphrase has really
low resolution and does not accept input to decrypt the filesystem.
Booting is currently only possible with the 'nomodeset' option.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Feb 10 12:48:59 2017
DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg for 
file: '/etc/gnome/defaults.list'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed
 nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc]
InstallationDate: Installed on 2014-09-24 (870 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Precision M4800
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 nomodeset
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago)
dmi.bios.date: 05/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0FVDR2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Feb 10 12:44:57 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

** Information type changed from Public to Public Security

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

Title:
  Problems with nvidia-367 and Quadro K2100M GPU after upgrading to
  16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with

  nvidia-367.57-0ubuntu0.16.04.1

  After upgrade two graphics problems have occurred.

  1) When booting with two monitors & extended desktop the monitors will
  go blank (this is accompanied by a popping sound, probably the
  speakers). This has also occurred repeatedly (tests ongoing).

  2) Splash screen at startup that prompts for LUKS passphrase has
  really low resolution and does not accept input to decrypt the
  

[Touch-packages] [Bug 278095]

[Troels]

"[Bug 278095] Re: MASTER crash in getenv() ... spi_atk_bridge_exit_func()"
Launchpad Bug Tracker doc

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

Title:
  MASTER crash in getenv() ... spi_atk_bridge_exit_func()

Status in at-spi:
  Expired
Status in apport package in Ubuntu:
  Invalid
Status in at-spi package in Ubuntu:
  Fix Released
Status in firefox-3.0 package in Ubuntu:
  Invalid
Status in apport source package in Intrepid:
  Invalid
Status in at-spi source package in Intrepid:
  Fix Released
Status in firefox-3.0 source package in Intrepid:
  Invalid
Status in apport source package in Jaunty:
  Invalid
Status in at-spi source package in Jaunty:
  Fix Released
Status in firefox-3.0 source package in Jaunty:
  Invalid

Bug description:
  This crash seems to occur most frequently when opening a new URL in an
  existing Firefox process.  The URL is successfully opened, but the
  client process then crashes while exiting.  The result is that the
  operation appears to work, but there has been a crash in the
  background (which is then displayed by update-notifier and apport).

  Steps to reproduce:

  1. check "Enable assisitive technologies"  in Preferences -> Assistive 
Technologies
  2. restart X session
  3. start firefox
  4. start from terminal: firefox http://www.ubuntu.com 

  Result: see crash.

  Verify: with updated package it shouldnt crash.

  ===

  I am using Ubuntu 8.10 beta

  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/lib/firefox-3.0.3/firefox
  Package: firefox-3.0 3.0.3+build1+nobinonly-0ubuntu1
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/lib/firefox-3.0.3/firefox 
https://bugs.launchpad.net/ubuntu/+source/seahorse-plugins/+filebug/7cEBHSr9Xvdab5iSpVMC09PXb6N?field.title=seahorse-agent+crashed+with+SIGSEGV+in+_XIOError%28%29
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: firefox-3.0
  StacktraceTop:
   getenv () from /lib/tls/i686/cmov/libc.so.6
   g_getenv () from /usr/lib/libglib-2.0.so.0
   ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
   exit () from /lib/tls/i686/cmov/libc.so.6
   __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
  Title: firefox crashed with SIGSEGV in getenv()
  Uname: Linux 2.6.27-4-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev 
video

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/278095/+subscriptions

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

[Touch-packages] [Bug 1663553] [NEW] crossdomain access denied

[dino99]

Public bug reported:

I'm trying to use http://mywebtv.info with different choices (like
http://mywebtv.info/nrj-12 )  but always get that error: " Cannot load
M3U8 Crossdomain access denied " using chromium-browser or midori.

Find nothing related being logged.
Sidenote: reported against 'init' but apport change it to 'init-system-helpers' 
which seems unrelated; and possibly concern some other package(s).

oem@u64:~$ dpkg --list | grep "^ii" | grep "flash"
ii  adobe-flash-properties-gtk  1:20170110.1-0ubuntu1   
 amd64GTK+ control panel for Adobe Flash Player plugin
ii  adobe-flashplugin   1:20170110.1-0ubuntu1   
 amd64Adobe Flash Player plugin
ii  browser-plugin-freshplayer-pepperflash  0.3.5-1ubuntu4  
 amd64PPAPI-host NPAPI-plugin adapter for pepperflash

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: init 1.47
ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
Uname: Linux 4.9.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb 10 11:42:17 2017
SourcePackage: init-system-helpers
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed third-party-packages zesty

** Summary changed:

- crossdmain access denied
+ crossdomain access denied

** Description changed:

  I'm trying to use http://mywebtv.info with different choices (like
  http://mywebtv.info/nrj-12 )  but always get that error: " Cannot load
- M3U8 Crossdomain access denied "
+ M3U8 Crossdomain access denied " using chromium-browser or midori.
  
  Find nothing related being logged.
  Sidenote: reported against 'init' but apport change it to 
'init-system-helpers' which seems unrelated; and possibly concern some other 
package(s).
  
  oem@u64:~$ dpkg --list | grep "^ii" | grep "flash"
  ii  adobe-flash-properties-gtk  1:20170110.1-0ubuntu1 
   amd64GTK+ control panel for Adobe Flash Player plugin
  ii  adobe-flashplugin   1:20170110.1-0ubuntu1 
   amd64Adobe Flash Player plugin
  ii  browser-plugin-freshplayer-pepperflash  0.3.5-1ubuntu4
   amd64PPAPI-host NPAPI-plugin adapter for pepperflash
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: init 1.47
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 11:42:17 2017
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  crossdomain access denied

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  I'm trying to use http://mywebtv.info with different choices (like
  http://mywebtv.info/nrj-12 )  but always get that error: " Cannot load
  M3U8 Crossdomain access denied " using chromium-browser or midori.

  Find nothing related being logged.
  Sidenote: reported against 'init' but apport change it to 
'init-system-helpers' which seems unrelated; and possibly concern some other 
package(s).

  oem@u64:~$ dpkg --list | grep "^ii" | grep "flash"
  ii  adobe-flash-properties-gtk  1:20170110.1-0ubuntu1 
   amd64GTK+ control panel for Adobe Flash Player plugin
  ii  adobe-flashplugin   1:20170110.1-0ubuntu1 
   amd64Adobe Flash Player plugin
  ii  browser-plugin-freshplayer-pepperflash  0.3.5-1ubuntu4
   amd64PPAPI-host NPAPI-plugin adapter for pepperflash

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: init 1.47
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 11:42:17 2017
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Bug Watch Updater]

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

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

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

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Touch-packages] [Bug 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)

[Lukáš Tinkl]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: content-hub (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [regression] Logging in to Unity8 takes 25 seconds (the default DBus
  timeout)

Status in Canonical System Image:
  Confirmed
Status in content-hub package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  [regression] Logging in to Unity8 takes 25 seconds (at least on the
  first login after a fresh boot) ...

  [2017-02-09:11:35:05.263] Empty ualAppId result for "qterminal_drop"
  [2017-02-09:11:35:05.263] Failed to get app info for app "qterminal_drop"
  [2017-02-09:11:35:05.308] Failed to get all properties for 
"com.ubuntu.location.providers.here.AccountsService" : "No such interface"
  [2017-02-09:11:35:05.310] CursorImageProvider: "" not found (nor its 
fallbacks, if any). Going for "left_ptr" as a last resort.
  [2017-02-09:11:35:05.328] qtmir.applications: applicationManagerSingleton - 
engine= 0x56395e4119b0 scriptEngine= 0x56395e4119b0
  [2017-02-09:11:35:05.330] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:05.333] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:35:05.334] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:35:30.687] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:35:30.688] qtmir.mir.keymap: Keymap applied

  

  [2017-02-09:11:38:19.249] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:19.252] ubuntu-app-launch threw an exception getting app 
info for appId: "address-book-app" : Invalid app ID: address-book-app
  [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.camera_camera"
  [2017-02-09:11:38:19.253] Empty ualAppId result for 
"com.ubuntu.gallery_gallery"
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface 
surface=QObject(0x0)
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: SET KEYMAP "us"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Applying keymap "us" "" on 4 
"Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint"
  [2017-02-09:11:38:44.680] qtmir.mir.keymap: Keymap applied

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

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

[Touch-packages] [Bug 1424114] Re: lvm snapshot is not being autoextended

[Josip Rodin]

It looks like it works on Ubuntu 16, syslog contains things like:

Feb 10 11:28:55 hostname lvm[1704]: WARNING: Snapshot vgname-lvname is now 
80.03% full.
Feb 10 11:28:55 hostname lvm[1704]: Size of logical volume vgname/lvname 
changed from 1.00 GiB (256 extents) to 1.20 GiB (308 extents).
Feb 10 11:28:55 hostname lvm[1704]: Logical volume lvname successfully resized.

Feb 10 11:29:12 hostname lvm[1704]: WARNING: Snapshot vgname-lvname is now 
85.65% full.
Feb 10 11:29:12 hostname lvm[1704]: Size of logical volume vgname/lvname 
changed from 1.80 GiB (462 extents) to 2.17 GiB (555 extents).
Feb 10 11:29:12 hostname lvm[1704]: Logical volume lvname successfully resized.

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

Title:
  lvm snapshot is not being autoextended

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After setting auto extend threshold and rebooting, lvm snapshots are
  not being auto extended.

  Steps to recreate:
  1. Using Ubuntu 14.04 LTS
  2. Set snapshot_autoextend_threshold to less than 100
  # grep autoext /etc/lvm/lvm.conf 
  snapshot_autoextend_threshold = 50
  snapshot_autoextend_percent = 20
  3. Reboot server to have lvm reread lvm.conf
  4. Create a snapshot of a mounted logical volume
  # lvcreate -s /dev/testVG/testLV -L 1G -n testLVsnap
  5. Make modifications to mounted logical volume
  6. List logical volumes and snapshots
  # lvs
LV VG Attr  LSize  Pool Origin Data%  Move Log Copy%  
Convert
testLV testVG owi-aos-- 10.00g  
 
testLVsnap testVG swi-a-s--  1.00g  testLV  95.04

  What I expected to have happened:
  Once Data% of snapshot reached the snapshot_autoextend_threshold, the 
snapshot logical volume should have been auto extended.

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

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

[Touch-packages] [Bug 1424114] Re: lvm snapshot is not being autoextended

[Josip Rodin]

On Ubuntu 14, it doesn't seem to work with monitoring = 1 set, either. I
had also tried doing vgchange --monitor y --poll y volumegroup, and
lvcreate --snapshot --monitor y ... and there was no effect.

Testing on Ubuntu 16 now

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

Title:
  lvm snapshot is not being autoextended

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After setting auto extend threshold and rebooting, lvm snapshots are
  not being auto extended.

  Steps to recreate:
  1. Using Ubuntu 14.04 LTS
  2. Set snapshot_autoextend_threshold to less than 100
  # grep autoext /etc/lvm/lvm.conf 
  snapshot_autoextend_threshold = 50
  snapshot_autoextend_percent = 20
  3. Reboot server to have lvm reread lvm.conf
  4. Create a snapshot of a mounted logical volume
  # lvcreate -s /dev/testVG/testLV -L 1G -n testLVsnap
  5. Make modifications to mounted logical volume
  6. List logical volumes and snapshots
  # lvs
LV VG Attr  LSize  Pool Origin Data%  Move Log Copy%  
Convert
testLV testVG owi-aos-- 10.00g  
 
testLVsnap testVG swi-a-s--  1.00g  testLV  95.04

  What I expected to have happened:
  Once Data% of snapshot reached the snapshot_autoextend_threshold, the 
snapshot logical volume should have been auto extended.

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

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

[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

[Louis Bouchard]

** Changed in: gtk+3.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Yakkety)
   Status: New => In Progress

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

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

Status in One Hundred Papercuts:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  In Progress
Status in gtk+3.0 source package in Yakkety:
  In Progress
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  [Impact]
  There are some unlinked calls to libGL.so.1 undetected in the build process 
because of using libepoxy. Running an application that does not depend on 
libgl1 (directly or indirectly) may lead to aborting the process with an 
undefined reference to libGL.so.1.

  [Test Case]
  1. Deploy a server / cloud image of Xenial or Yakkety.
  2. Use a Windows or a Mac client with Cygwin/X and ssh -XY to Ubuntu machine.
  3. sudo apt install firefox; firefox

  Expected result:
  firefox is launched on the client machine.

  Actual result:
  "Couldn't open libGL.so.1" message is printed.

  [Regression Potential]
  Minimal, it is an upstream change already released to zesty. It performs a 
runtime check for GL support and disables GLX function calls in case they're 
not available.

  [Other Info]
  Original bug description:

  virt-manager fails to start:

  $ virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) 
virt-manager version: 1.3.2
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) 
virtManager import: 
  Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such 
file or directory
  $

  Installing the 'libgl1-mesa-glx' package resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:19:27 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted

[Laurent Bonnaud]

According to this:

  https://raspberrypi.stackexchange.com/questions/40839/sap-error-on-
bluetooth-service-status

the error messages about SAP can be avoided by starting bluetoothd with
the "--noplugin=sap" option.

Since SAP is probably of little use in Ubuntu and since it does not work
anyway, how about disabling it by default?


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

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

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

Title:
  Sap driver initialization failed, sap-server: Operation not permitted

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

Bug description:
  Hi,

  here are are messages from the bluetooth daemon:

  $ journalctl -b | grep bluetoothd
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41
  Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 
initialized
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for 
"Service Changed" characteristic
  Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed.
  Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted 
(1)

  There are at least 2 errors concerning:
   - handles
   - Sap driver/server

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct  2 09:59:43 2016
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency 
root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:85:DE:57:27:6F  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:1974 acl:0 sco:0 events:132 errors:0
TX bytes:6033 acl:0 sco:0 commands:132 errors:0

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

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

[Louis Bouchard]

Here are the results of the comparative tests I ran :

https://docs.google.com/spreadsheets/d/1MyNBPVZlBeic1OLqVKe_bcPk2deO_pQs9trIfOFefM0/edit#gid=2034603487

It confirms the assumptions but unfortunately, rebuilding 2.7.12 without
the -fstack-protector-strong leads to worse performances than the stock
2.7.12 build. I'm continuing my investigations.

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

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

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

[Touch-packages] [Bug 1630156] Re: No password needed to Log in after cancel the password and then reset again

[Iain Lane]

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: unity-control-center (Ubuntu Xenial)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: unity-control-center (Ubuntu Yakkety)
   Status: Confirmed => In Progress

** Changed in: unity-control-center (Ubuntu Yakkety)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in unity-control-center source package in Xenial:
  In Progress
Status in lightdm source package in Yakkety:
  Confirmed
Status in unity-control-center source package in Yakkety:
  In Progress

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")
  3. Check that the user is in the nopasswdlogin group
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Check that the user is *not* in the nopasswdlogin group.

  The key problem is: it won't remove user from nopasswdlogin in step 4.
  At step 5, you are left in the group.

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

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

[Touch-packages] [Bug 1579557] Re: lightdm will not start

[Rexhumus Dei]

Im sorry, but is there any update to this error?

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

Title:
  lightdm will not start

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  systemctl status lightdm.service posts this:

  lightdm.service - Light Display Manager
 Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor 
preset: enabled)
Drop-In: /lib/systemd/system/display-manager.service.d
 └─xdiagnose.conf
 Active: inactive (dead) (Result: exit-code) since sø. 2016-05-08 19:22:51 
CEST; 43min ago
   Docs: man:lightdm(1)
Process: 7709 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
Process: 7702 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (co
   Main PID: 7709 (code=exited, status=1/FAILURE)

  mai 08 19:22:51 rowena2 systemd[1]: lightdm.service: Service hold-off time 
over, scheduling restart.
  mai 08 19:22:51 rowena2 systemd[1]: Stopped Light Display Manager.
  mai 08 19:22:51 rowena2 systemd[1]: lightdm.service: Start request repeated 
too quickly.
  mai 08 19:22:51 rowena2 systemd[1]: Failed to start Light Display Manager.

  journalctl -xe posts this:

  mai 08 19:22:51 rowena2 systemd[1]: gpu-manager.service: Start request 
repeated too quickly.
  mai 08 19:22:51 rowena2 systemd[1]: Failed to start Detect the available GPUs 
and deal with any system changes.
  -- Subject: Unit gpu-manager.service has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit gpu-manager.service has failed.
  --
  -- The result is failed.
  mai 08 19:22:51 rowena2 systemd[1]: lightdm.service: Start request repeated 
too quickly.
  mai 08 19:22:51 rowena2 systemd[1]: Failed to start Light Display Manager.
  -- Subject: Unit lightdm.service has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit lightdm.service has failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: i386
  Date: Sun May  8 19:24:25 2016
  InstallationDate: Installed on 2012-04-22 (1476 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120421)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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