date:20161212

** Tags removed: need-duplicate-check

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  Fault revealed with package upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   640:0:116:454622:2016-12-13 16:39:31.618048537 +1100:2016-12-13 
16:39:31.730053750 +1100:/var/crash/_lib_systemd_systemd.0.crash
   600:0:116:292900:2016-12-13 16:41:48.064335584 +1100:2016-12-13 
16:41:49.064335584 +1100:/var/crash/apport.0.crash
  Date: Tue Dec 13 16:41:48 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-05 (222 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649486] [NEW] package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-12 Thread Tioz

Public bug reported:

Fault revealed with package upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashReports:
 640:0:116:454622:2016-12-13 16:39:31.618048537 +1100:2016-12-13 
16:39:31.730053750 +1100:/var/crash/_lib_systemd_systemd.0.crash
 600:0:116:292900:2016-12-13 16:41:48.064335584 +1100:2016-12-13 
16:41:49.064335584 +1100:/var/crash/apport.0.crash
Date: Tue Dec 13 16:41:48 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-05-05 (222 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

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

Status in apport package in Ubuntu:
  New

Bug description:
  Fault revealed with package upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   640:0:116:454622:2016-12-13 16:39:31.618048537 +1100:2016-12-13 
16:39:31.730053750 +1100:/var/crash/_lib_systemd_systemd.0.crash
   600:0:116:292900:2016-12-13 16:41:48.064335584 +1100:2016-12-13 
16:41:49.064335584 +1100:/var/crash/apport.0.crash
  Date: Tue Dec 13 16:41:48 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-05 (222 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1483111] Re: Cellular doesn´t work after reboot the phone

2016-12-12 Thread TarotChen

** Changed in: telepathy-ofono (Ubuntu)
   Status: New => Invalid

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

Title:
  Cellular doesn´t work after reboot the phone

Status in telepathy-ofono package in Ubuntu:
  Invalid

Bug description:
  Test Environment:
  $ system-image-cli -i
  current build number: 276
  device name: mako
  channel: ubuntu-touch/devel-proposed/ubuntu
  last update: 2015-08-10 03:43:38
  version version: 276
  version ubuntu: 20150802
  version device: 20150708
  version custom: 20150802

  Steps:
  1.Boot the phone
  2.Swipe down on the network indicator to make sure the SIM shows the operator 
and signal
  3.Select a contact and call

  actual=>Call failed from the caller side and blank screen shows in
  dial-app, but the phone rings at the receiver side and no voice if
  answer the call.

  4.From another device, make a phone call to the testing phone

  actual=>No incoming call at receiver side, the dialed number is busy
  at caller side

  Error can reproduce on both CMCC and CHN-UNICOM
  Error can reproduce on Arale-Devel-r80
  Error can reproduce on Mako-stable-r204

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

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

[Touch-packages] [Bug 1515093] Re: Cannot swipe to preview photos in another groups

2016-12-12 Thread TarotChen

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot swipe to preview photos in another groups

Status in unity-scopes-shell package in Ubuntu:
  Invalid

Bug description:
  Test Env:
  ~$ system-image-cli -i
  current build number: 171
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 08:12:47
  version version: 171
  version ubuntu: 20151110.1
  version device: 20150821-736d127
  version custom: 2015111

  
  Pre-requisites: 
  Copy some photo taken a month ago to DUT

  Steps:
  1. take photos by camera
  2. go to photo scope
  3. tap on my photos
  =>There are two groups "today" and "Previous 30 days"in my photos page
  4. tap on a photo from "today" group to preview
  5. Continue swiping left to preview the next photo

  Actual: 
  Cannot swipe to preview photos in "previous 30 days" group

  Expected:
  Should be able to swipe to preview all photos displayed in my photos scope 
since they are stored under the same folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1515093/+subscriptions

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

[Touch-packages] [Bug 1649097] Re: 'linux' source package signature is not valid

2016-12-12 Thread Vyacheslav

Reality check:
that means that all source packages received via 'apt-get source' are not 
trusted by Ubuntu clean installation ?

Is there a safe way to get full public key (not short unsafe keyid) for
a source package then?

Thanks

** Summary changed:

- 'linux' source package signature is not valid
+ any source package signature is not valid

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

Title:
  any source package signature is not valid

Status in apt package in Ubuntu:
  New

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Touch-packages] [Bug 1648637] Re: handle interruped read and write calls

This bug was fixed in the package lightdm - 1.21.3-0ubuntu1

---
lightdm (1.21.3-0ubuntu1) zesty; urgency=medium

  * New upstream release:
- Fix crashes introduced in 1.21.2 due to environment variable changes
- Fix incorrect unref in XDMCP server code
- Fix logging warning

 -- Robert Ancell   Fri, 09 Dec 2016
14:04:49 +1300

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

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

Title:
  handle interruped read and write calls

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Yakkety:
  New
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  Use SA_RESTART flag to make sure that interrupted calls to read and/or
  write are restarted.

  In my case read is interrupted when reading login1_session_id. Result
  of not handling EINTR error is that login1_session_id is set to NULL
  and console_kit_cookie gets login1 session id.

  Related warnings in lightdm.log:
  [+0.44s] WARNING: Session pid=617: Error reading from session: Interrupted 
system call
  [+0.70s] DEBUG: Activating VT 7
  [+0.70s] DEBUG: Activating ConsoleKit session c1
  [+0.70s] WARNING: Error getting ConsoleKit session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files

  And because login1_session_id is null fix for 1637758 bug does not
  work.

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

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

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

2016-12-12 Thread Mathew Hodson

** No longer affects: nautilus (Ubuntu Yakkety)

** No longer affects: nautilus (Ubuntu)

** Project changed: nautilus => ubuntu-translations

** Changed in: ubuntu-translations
   Importance: Medium => Undecided

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

** Changed in: ubuntu-translations
 Remote watch: GNOME Bug Tracker #773819 => None

** No longer affects: ubuntu-translations

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

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

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

** Tags removed: nautilus trash

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1638846] Re: Update GLib to fix a bug with Trash in Nautilus

2016-12-12 Thread Mathew Hodson

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

** Project changed: glib => ubuntu

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

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

** Changed in: ubuntu
 Remote watch: GNOME Bug Tracker #662946 => None

** No longer affects: ubuntu

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

** This bug has been marked a duplicate of bug 1633824
   nautilus ignores trash on external drives

** Tags removed: nautilus trash

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

Title:
  Update GLib to fix a bug with Trash in Nautilus

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  As described here there is a bug in Ubuntu 16.10 with trash and
  external drives in Nautilus:
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633824

  Seems that this has been fixed already with GLib 2.50.1 according to
  https://bugzilla.gnome.org/show_bug.cgi?id=773819#c3

  So updating the package for Ubuntu 16.10 would fix this bug.

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

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

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

2016-12-12 Thread Greg Black

Public bug reported:

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

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

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

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

$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10

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

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

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

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

Title:
  systemd starts postfix before resolver

Status in systemd package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1603027] Re: Location detection should be off when it's disabled in the app

2016-12-12 Thread Po-Hsu Lin

Hello,
Thanks for the reply. The problem is that when the location detection is 
disable in the app, when you kill the app and re-open it, the switch still 
remember that you have the detection disabled, but the indicator shows location 
detection service is activated.

** Attachment added: "screenshot20161213_111948839.png"
   
https://bugs.launchpad.net/ubuntu-weather-app/+bug/1603027/+attachment/4790994/+files/screenshot20161213_111948839.png

** Changed in: ubuntu-weather-app
   Status: Incomplete => New

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

Title:
  Location detection should be off when it's disabled in the app

Status in Ubuntu Weather App:
  New
Status in indicator-location package in Ubuntu:
  New

Bug description:
  The location detection setting in weather app is not consistent with
  the stat of the location indicator after restarting the app.

  com.ubuntu.weather  3.3.244

  Steps:
  1. Make sure you have location detection activated, open the weather app
  2. Disable the location detection in the cog-wheel setting page
  3. Close the app
  4. Open the app again, and observe the location indicator

  Expected result:
  * The location indicator should be in "activated" mode in step 1
  * The location indicator should be in "de-activated" mode in step 2
  * The location indicator should be in "de-activated" mode in step 4

  Actual result:
  * The location indicator is still in "activated" mode in step 4

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

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

[Touch-packages] [Bug 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder

2016-12-12 Thread erwan KRUG

Hi everybody,

has any answer been found or is this just a matter of root permissions
on androids ?

I have the same issue: "libmtp error:  Could not send object info"

keep me up-dated ! :)
erwan.

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

Title:
  "libmtp error: Could not send object info" when copying content to
  root MTP folder

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Ubuntu device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Ubuntu 14.10

  SUMMARY:
  "libmtp error: Could not send object info" when copying content to root MTP 
folder

  STEPS:
  1) Connect Ubuntu MTP device over USB
  2) Attempt to copy some content to the root of the MTP folder

  EXPECTED RESULT:
  The copy operation should succeed. (This is the Android behaviour).

  ACTUAL RESULT:
  An error message is presented on desktop: "libmtp error: Could not send 
object info"

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

2016-12-12 Thread Daniel van Vugt

** Tags added: unity8-desktop

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-12-12 Thread Daniel van Vugt

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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

[Touch-packages] [Bug 1649436] [NEW] package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: package libdbus-1-3:amd64 is already installed and configured

2016-12-12 Thread Michel

Public bug reported:

I just read the mensage of error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Mon Dec 12 23:12:04 2016
DuplicateSignature:
 package:libdbus-1-3:amd64:1.10.6-1ubuntu3.1
 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
 dpkg: error processing package libbrlapi0.6:amd64 (--configure):
  package libbrlapi0.6:amd64 is already installed and configured
ErrorMessage: package libdbus-1-3:amd64 is already installed and configured
InstallationDate: Installed on 2016-12-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: dbus
Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: 
package libdbus-1-3:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade:
  package libdbus-1-3:amd64 is already installed and configured

Status in dbus package in Ubuntu:
  New

Bug description:
  I just read the mensage of error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Dec 12 23:12:04 2016
  DuplicateSignature:
   package:libdbus-1-3:amd64:1.10.6-1ubuntu3.1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package libbrlapi0.6:amd64 (--configure):
package libbrlapi0.6:amd64 is already installed and configured
  ErrorMessage: package libdbus-1-3:amd64 is already installed and configured
  InstallationDate: Installed on 2016-12-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: dbus
  Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: 
package libdbus-1-3:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649436] Re: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: package libdbus-1-3:amd64 is already installed and configured

** Tags removed: need-duplicate-check

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

Title:
  package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade:
  package libdbus-1-3:amd64 is already installed and configured

Status in dbus package in Ubuntu:
  New

Bug description:
  I just read the mensage of error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdbus-1-3:amd64 1.10.6-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Dec 12 23:12:04 2016
  DuplicateSignature:
   package:libdbus-1-3:amd64:1.10.6-1ubuntu3.1
   Processing triggers for desktop-file-utils (0.22-1ubuntu5) ...
   dpkg: error processing package libbrlapi0.6:amd64 (--configure):
package libbrlapi0.6:amd64 is already installed and configured
  ErrorMessage: package libdbus-1-3:amd64 is already installed and configured
  InstallationDate: Installed on 2016-12-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: dbus
  Title: package libdbus-1-3:amd64 1.10.6-1ubuntu3.1 failed to install/upgrade: 
package libdbus-1-3:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649431] Re: several missing include local/foo

2016-12-12 Thread Tyler Hicks

** Description changed:

  It is surprising that /etc/apparmor.d/local/usr.bin.webbrowser.app
  exists, but is impotent because no other file includes it.
  
  There are several such files on my 16.04 system:
  
  $ cd /etc/apparmor.d && for i in local/*; do find . -type f | xargs sudo grep 
"include.*$i" >/dev/null || echo "$i is not included anywhere"; done | grep -v 
README
  local/usr.bin.ubuntu-core-launcher is not included anywhere
  local/usr.bin.webbrowser-app is not included anywhere
  local/usr.lib.snapd.snap-confine is not included anywhere
  local/usr.sbin.ippusbxd is not included anywhere
+ 
+ The impact of this bug is that it is not possible to add site-specific
+ rules to some AppArmor profiles in an Ubuntu system. Note that this
+ should not be a problem with profiles shipped in the apparmor-profiles
+ packages (since the upstream apparmor build system checks for the
+ existence of such include rules) and likely only affects other packages
+ which ship their own AppArmor profiles.

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

Title:
  several missing include local/foo

Status in AppArmor:
  Invalid
Status in ippusbxd package in Ubuntu:
  Confirmed
Status in snap-confine package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  It is surprising that /etc/apparmor.d/local/usr.bin.webbrowser.app
  exists, but is impotent because no other file includes it.

  There are several such files on my 16.04 system:

  $ cd /etc/apparmor.d && for i in local/*; do find . -type f | xargs sudo grep 
"include.*$i" >/dev/null || echo "$i is not included anywhere"; done | grep -v 
README
  local/usr.bin.ubuntu-core-launcher is not included anywhere
  local/usr.bin.webbrowser-app is not included anywhere
  local/usr.lib.snapd.snap-confine is not included anywhere
  local/usr.sbin.ippusbxd is not included anywhere

  The impact of this bug is that it is not possible to add site-specific
  rules to some AppArmor profiles in an Ubuntu system. Note that this
  should not be a problem with profiles shipped in the apparmor-profiles
  packages (since the upstream apparmor build system checks for the
  existence of such include rules) and likely only affects other
  packages which ship their own AppArmor profiles.

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

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

[Touch-packages] [Bug 1649431] Re: several missing include local/foo

2016-12-12 Thread Tyler Hicks

I'm not going to add a task for ubuntu-core-launcher because that
package was replaced by snap-confine.

I'm marking the apparmor task as Invalid because this bug only applies
to profiles that are not shipped by the apparmor or apparmor-profiles
packages. The upstream apparmor project has an install-time check that
verifies that all of the profiles have an "#include
" rule.

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

** Changed in: ippusbxd (Ubuntu)
   Importance: Undecided => Low

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

** Also affects: snap-confine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: snap-confine (Ubuntu)
   Status: New => Confirmed

** Changed in: snap-confine (Ubuntu)
   Importance: Undecided => Low

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  several missing include local/foo

Status in AppArmor:
  Invalid
Status in ippusbxd package in Ubuntu:
  Confirmed
Status in snap-confine package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  It is surprising that /etc/apparmor.d/local/usr.bin.webbrowser.app
  exists, but is impotent because no other file includes it.

  There are several such files on my 16.04 system:

  $ cd /etc/apparmor.d && for i in local/*; do find . -type f | xargs sudo grep 
"include.*$i" >/dev/null || echo "$i is not included anywhere"; done | grep -v 
README
  local/usr.bin.ubuntu-core-launcher is not included anywhere
  local/usr.bin.webbrowser-app is not included anywhere
  local/usr.lib.snapd.snap-confine is not included anywhere
  local/usr.sbin.ippusbxd is not included anywhere

  The impact of this bug is that it is not possible to add site-specific
  rules to some AppArmor profiles in an Ubuntu system. Note that this
  should not be a problem with profiles shipped in the apparmor-profiles
  packages (since the upstream apparmor build system checks for the
  existence of such include rules) and likely only affects other
  packages which ship their own AppArmor profiles.

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

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

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

The Stable Release Update process requires a waiting period of 7 days so
that we can watch for regressions.  That means it'll first be eligible
for publication on the 14th.

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1648634] Re: opencryptoki breaks p11-kit

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

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

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

Title:
  opencryptoki breaks p11-kit

Status in opencryptoki package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed

Bug description:
  When opencryptoki is installed, it creates a symlink from /etc/pkcs11
  to /var/lib/opencryptoki, which is readable only by root.

  This means that anything using p11-kit to find the PKCS#11 modules
  which are configured to be available in the system (which is basically
  any well-behaved application) now breaks:

  $ openconnect -c 'pkcs11:token=eToken;id=%01' server.example.com
  POST https://server.example.com/
  Attempting to connect to server [fec0::1]:443
  p11-kit: couldn't open config file: /etc/pkcs11/pkcs11.conf: Permission denied
  Error loading certificate from PKCS#11: PKCS #11 initialization error.
  Loading certificate failed. Aborting.

  $ p11tool --list-tokens
  p11-kit: couldn't open config file: /etc/pkcs11/pkcs11.conf: Permission denied
  pkcs11_init: PKCS #11 initialization error.

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

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

[Touch-packages] [Bug 1648634] Re: opencryptoki breaks p11-kit

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

** Changed in: p11-kit (Ubuntu)
   Status: New => Confirmed

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

Title:
  opencryptoki breaks p11-kit

Status in opencryptoki package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed

Bug description:
  When opencryptoki is installed, it creates a symlink from /etc/pkcs11
  to /var/lib/opencryptoki, which is readable only by root.

  This means that anything using p11-kit to find the PKCS#11 modules
  which are configured to be available in the system (which is basically
  any well-behaved application) now breaks:

  $ openconnect -c 'pkcs11:token=eToken;id=%01' server.example.com
  POST https://server.example.com/
  Attempting to connect to server [fec0::1]:443
  p11-kit: couldn't open config file: /etc/pkcs11/pkcs11.conf: Permission denied
  Error loading certificate from PKCS#11: PKCS #11 initialization error.
  Loading certificate failed. Aborting.

  $ p11tool --list-tokens
  p11-kit: couldn't open config file: /etc/pkcs11/pkcs11.conf: Permission denied
  pkcs11_init: PKCS #11 initialization error.

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

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

[Touch-packages] [Bug 1649097] Re: 'linux' source package signature is not valid

Julian, do you have any ideas how this could be handled better? I'm
short on ideas here. The gpgv output seems useful but it's also
potentially misleading.

Thanks

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

Title:
  'linux' source package signature is not valid

Status in apt package in Ubuntu:
  New

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Touch-packages] [Bug 1649097] Re: 'linux' source package signature is not valid

Thanks for the bug report.

This isn't as dire as it looks:

APT's security model is based on signed InRelease files that have
sha256sums of all archive contents. In this case, the InRelease file
will have a sha256sum for one of the Sources files, and that file will
have a sha256sum for the linux source package files:

Checksums-Sha256:
 5c1141401c8f3468b2d5f71906aea181a8f7c9e195c4cc3252a085962bbf4f4d 9611 
linux_4.4.0-53.74.dsc
 730e75919b5d30a9bc934ccb300eaedfdf44994ca9ee1d07a46901c46c221357 132860730 
linux_4.4.0.orig.tar.gz
 5ad7a47f2bcb66858f26fb539e39e07724c676a8eca84239c850fa87c2900b0e 12162206 
linux_4.4.0-53.74.diff.gz


If these sha256sums don't match what was downloaded, apt itself would throw an 
error.

All these files are in /var/lib/apt/lists/ .

The .dsc file is signed by whoever uploads the package for building to
our buildfarm. Developers' keys change all the time. It's still useful
to have the .dsc file to see what the builders saw, regardless if the
signature on the file is from an expired key or not.

Now, where things get really interesting: You've used a 32 bit keyid to
download the key from the keyservers. 32 bit keyids are not safe to use
in this manner because it's relatively simple to generate keys with
colliding 32 bit keyids. This was done for all keys in the 'strongly
connected set' a few years ago, including Brad's key. When someone
uploaded all these keys to the SKS keyservers, it was insanely
confusing. So, the group that generated all the colliding keys generated
revocation certificates for all the keys and uploaded them all, to kill
them.

So, your command to download the key by 32 bit keyid downloaded _two_
keys -- Brad's real key, "11D6 ADA3 D9E8 3D93 ACBD  837F 0C7B 589B 105B
E7F7", is not revoked:

$ gpg --check-sigs "11D6 ADA3 D9E8 3D93 ACBD  837F 0C7B 589B 105B E7F7"
pub   4096R/0C7B589B105BE7F7 2011-09-06
uid  Brad Figg 
sig! 052F367018D5C3D8 2012-01-09  John Johansen 
sig! 5759F35001AA4A64 2011-12-10  Steve Langasek 

sig! 3D76C845FA1447CA 2011-09-06  Tim Gardner (4K key) 

sig! 8972F4DFDC6DC026 2011-12-09  Kees Cook 
sig! 2F099E8D005E81F4 2011-12-09  Steve Beattie 
sig-30C7B589B105BE7F7 2011-09-06  Brad Figg 
sig!30C7B589B105BE7F7 2011-09-06  Brad Figg 
sub   4096R/E79D7BDFF336E4D5 2011-09-06
sig! 0C7B589B105BE7F7 2011-09-06  Brad Figg 

1 bad signature
14 signatures not checked due to missing keys


My output may look different from yours because I added this to my 
~/.gnupg/gpg.conf file:

keyid-format long

For more information, see https://evil32.com/

Thanks

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

Title:
  'linux' source package signature is not valid

Status in apt package in Ubuntu:
  New

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

2016-12-12 Thread Justin King-Lacroix

Any idea when this will be released to Trusty?

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1649097] Re: 'linux' source package signature is not valid

** Information type changed from Private Security to Public Security

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

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

Title:
  'linux' source package signature is not valid

Status in apt package in Ubuntu:
  New

Bug description:
  In short:

  The GPG key 105BE7F7, with that 'linux' source package is signed,
  revoked on 08/16/16 (4 months ago!)


  How to reproduce:

  $ apt-get source linux-image-$(uname -r)
  ...
  Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
  ...
  Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 
4.4.0-53.74 (tar) [133 MB]
  ...
  gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
  gpgv: Can't check signature: public key not found
  dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
  ...

  ### if you add this key:

  $ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
  $ apt-key list
  ...
  pub   4096R/105BE7F7 2011-09-06
  uid  Brad Figg 
  sub   4096R/F336E4D5 2011-09-06

  pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
  uid  Brad Figg 

  ### THE KEY IS REVOKED 4 MONTHS AGO!

  ### Additional info:
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  ### My unmodified /etc/apt/sources.list in attachment.
  ### Note, /etc/apt/sources.list.d/ directory is empty.

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

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

[Touch-packages] [Bug 1649097] [NEW] 'linux' source package signature is not valid

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

In short:

The GPG key 105BE7F7, with that 'linux' source package is signed,
revoked on 08/16/16 (4 months ago!)


How to reproduce:

$ apt-get source linux-image-$(uname -r)
...
Picking 'linux' as source package instead of 'linux-image-4.4.0-53-generic'
...
Get:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main linux 4.4.0-53.74 
(tar) [133 MB]
...
gpgv: Signature made Пт 02 дек 2016 18:32:18 MSK using RSA key ID 105BE7F7
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./linux_4.4.0-53.74.dsc
...

### if you add this key:

$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 105BE7F7
$ apt-key list
...
pub   4096R/105BE7F7 2011-09-06
uid  Brad Figg 
sub   4096R/F336E4D5 2011-09-06

pub   4096R/105BE7F7 2014-06-16 [revoked: 2016-08-16]
uid  Brad Figg 

### THE KEY IS REVOKED 4 MONTHS AGO!

### Additional info:
$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

### My unmodified /etc/apt/sources.list in attachment.
### Note, /etc/apt/sources.list.d/ directory is empty.

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


** Tags: gpg invalid linux signature source
-- 
'linux' source package signature is not valid
https://bugs.launchpad.net/bugs/1649097
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt 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 1629611] Re: dns server priority broken

2016-12-12 Thread Thomas M Steenholdt

Unfortunately not much traction here, and this appears to annoy people
across distros.

In the meantime, an ugly hack is to manually add all internal domains to
the NetworkManager VPN config file's dns-search= parameter:

dns-search=domain1.lan;domain2.lan;domain3.lan;example.com;

This causes NetworkManager to split DNS all lookups for these domains to
the VPN DNS server, but with the added overhead of searching through all
domains for non-existing hostname queries (make sure the primary
internal domains are mentioned first). Also, for a multi-city setup like
ours, I need to add A LOT of domains to get a functional DNS while on
VPN - Including in-addr.arpa specifications for all IP subnets.

So there's a way to sweeten the deal - but this is by no means anything
other than a hack.

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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

[Touch-packages] [Bug 1646947] Re: Model slowness causes significant UI hang when reordering the scopes list

** Branch linked: lp:~josharenson/unity-scopes-shell/fix-overview-
results-sorting

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

Title:
  Model slowness causes significant UI hang when reordering the scopes
  list

Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  == Background ==
  I recently implemented an autoscrolling mechanism 
(lp:~josharenson/unity8/autoscroller-alternative) for the ScopesList to resolve 
lp:1575319 This branch, I believe, is exposing an issue that has likely always 
been present.

  == Steps to Reproduce ==
  1. Install the autosceoller branch mentioned above on a mobile device. For 
the sake of this bug, you can probably just copy the changed qml files.
  2. Install enough scopes so that the list is longer than the display; about 
20 should work.
  3. Open the scopes list, press and hold to enter 'edit' mode, and drag the 
bottom most scope to the top of the list (which should automatically scroll 
upwards).
  4. Release the scope

  Expected behavior: scope drops to new position in list
  Actual behavior: UI hangs for several seconds

  == Evidence ==
  There are several possible culprits for this issue, however I've ruled out 
two big ones.
  Qt - Since the issue isn't present in the mock, its unlikely a Qt bug
  Unity8 - I have a qt profiler trace from the unity8-dash that shows no 
activity at all during the hang. Thus, I believe the issue is somewhere in the 
scopes or categories model. I've attached the trace for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1646947/+subscriptions

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

[Touch-packages] [Bug 1645827] Re: [SRU] Add support for ocata cloud-archive

This bug was fixed in the package software-properties - 0.96.20.5

---
software-properties (0.96.20.5) xenial; urgency=medium

  * cloudarchive: Enable support for the Ocata Ubuntu Cloud Archive on
16.04 (LP: #1645827).

 -- Corey Bryant   Tue, 29 Nov 2016 13:49:16
-0500

** Changed in: software-properties (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Add support for ocata cloud-archive

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  Fix Released
Status in software-properties source package in Zesty:
  New

Bug description:
  Please add support for:

 cloud-archive:ocata
 cloud-archive:ocata-proposed

  This will also need to be SRU'ed back to xenial.

  [Impact]
  End users have to manually enable the ocata cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:ocata
  sudo add-apt-repository cloud-archive:ocata-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

2016-12-12 Thread Stunts

Ok, so it turns out I'm still having some issues with this after OTA-14.
I can still pair the phone with the Hands Free System (HFS), but...
I can only do this if I make the phone search for the HFS. If I try the pairing 
by having the HFS search for the phone, I get an error - the PIN (hardcoded to 
) is requested by the HFS, but the phone never displays any requests, and 
the connection fails with an error.
Would a new log file, this time with this very behaviour, be interesting for 
further debugging?

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

[Touch-packages] [Bug 1645827] Update Released

The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Add support for ocata cloud-archive

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Zesty:
  New

Bug description:
  Please add support for:

 cloud-archive:ocata
 cloud-archive:ocata-proposed

  This will also need to be SRU'ed back to xenial.

  [Impact]
  End users have to manually enable the ocata cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:ocata
  sudo add-apt-repository cloud-archive:ocata-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1646758] Re: Can't update or install apps

2016-12-12 Thread Pat McGowan

This landed in 587 on Dec 7

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

Title:
  Can't update or install apps

Status in Canonical System Image:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  bq M10 rc-proposed r243

  When trying to update an app this morning, I got an error about destination 
path not being writable. The app is YouTube by Mateo Salta. 
  Screenshot with the error attached.

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

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

[Touch-packages] [Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2016-12-12 Thread Dan Streetman

> Note that there is a current SRU in trusty which blocks this.

is that current SRU for bug 1562344?

> But this being "wishlist" it's not
> that urgent anyway, 

This isn't really wishlist, this is needed to persistently identify NVMe
drives on systems with multiple drives.

> and my gut feeling is that it's okay to wait a bit until we get some more
> fixes queued up?

I'd like to see this patch get started in trusty-proposed sooner than
later, is it possible to go ahead with this for trusty?  (and can we
also add the workaround patch for bug 1647485?)

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

Title:
  introduce disk/by-id (model_serial) symlinks for NVMe drives

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  In Progress
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
  SERIAL symlinks.

  [Test Case]

  On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
  with the patch, it will contain link(s) named by the drive serial
  number. This should be the *only* change in `ls -l /dev/disk/*/*`.

  On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
  identical (aside from dates, of course) before and after the upgrade
  to the -proposed version.

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or  clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This patch is already included upstream and in zesty systemd.

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

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

[Touch-packages] [Bug 1590892] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-12 Thread Neil Rotherham

What is runmbbservice and should I get rid of it?

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

Title:
  package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Could not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 18:23:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-21 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-12 Thread Dan Streetman

** Patch removed: "lp1647485-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788261/+files/lp1647485-trusty.debdiff

** Patch removed: "lp1647485-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788262/+files/lp1647485-xenial.debdiff

** Patch removed: "lp1647485-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788263/+files/lp1647485-yakkety.debdiff

** Patch removed: "lp1647485-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788264/+files/lp1647485-zesty.debdiff

** Attachment removed: "lp1647485-workaround.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4788259/+files/lp1647485-workaround.tgz

** Patch added: "workaround-use-string_escape-release-for-nvme-symlin.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4790906/+files/workaround-use-string_escape-release-for-nvme-symlin.patch

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2016-12-12 Thread Dan Streetman

> Note that there is not much point with debdiffs, it's easier to cherry-pick 
> the fix directly into
> the packaging branches with gbp pq and debian/git-cherry-pick.

ok, I removed the debdiffs as they're not needed.

I did attach a single patch, that works around the bug in a simple way,
by updating only the NVMe udev rules to force whitespace replacement
with underscores.  This allows the NVMe symlinks to work even for
devices with whitespace in their model/serial strings, while leaving the
rest of udev unchanged.  This patch would allow the ubuntu udev pkgs to
work correctly, while the bug is discussed upstream.  Note that this
workaround will not break anything even if upstream uses an alternate
way of fixing this.

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

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

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

2016-12-12 Thread Mossroy

For those still having this issue on Ubuntu 16.04 : please check that you did 
not disable the automatic installation of updates.
It might be the reason why the old kernels were not removed for me (not 100% 
yet). See discussion in https://ubuntuforums.org/showthread.php?t=2344232
With a GUI, it's in System settings->Software and updates->Updates tab : "When 
there are security updates" should be set to "Download and install 
automatically" (its default value).
(please comment on the forum thread)

-- 
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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

2016-12-12 Thread Stefan

In the example above, I dimmed backlight to complete black (nothing
visible) 2x, just before posting the log...

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

Title:
  Possible to manually set display brightness to 0 on Ubuntu Touch on
  Aquaris E5

Status in indicator-power package in Ubuntu:
  Invalid
Status in repowerd package in Ubuntu:
  New

Bug description:
  Possible to manually set display brightness to 0 on Ubuntu Touch

  It is possible to move the brightness slider to the very left
  position, which will set the display brightness of affected device to
  zero, or, to total darkness.

  This is a bug, since this leads to user's inability to set the brightness 
back or, generally, to operate the device.
  There is a slight chance, though, to return the brightness back to non-zero 
value (blindly, trying by user's memory).

  Also, this gets even more problematic, if we think about a scenario, where 
such Ubuntu device is locked by a PIN.
  User has to try to unlock the device on the dark screen, open the top panel 
with settings, scroll to the far right (to access the brightness settings), and 
then trying to hit the correct slider - all on a dark screen.

  This happened on Aquaris E5.

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

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

[Touch-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

2016-12-12 Thread Stefan

And here is the second one...

** Attachment added: "repowerd.log"
   
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790905/+files/repowerd.log

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

Title:
  Possible to manually set display brightness to 0 on Ubuntu Touch on
  Aquaris E5

Status in indicator-power package in Ubuntu:
  Invalid
Status in repowerd package in Ubuntu:
  New

Bug description:
  Possible to manually set display brightness to 0 on Ubuntu Touch

  It is possible to move the brightness slider to the very left
  position, which will set the display brightness of affected device to
  zero, or, to total darkness.

  This is a bug, since this leads to user's inability to set the brightness 
back or, generally, to operate the device.
  There is a slight chance, though, to return the brightness back to non-zero 
value (blindly, trying by user's memory).

  Also, this gets even more problematic, if we think about a scenario, where 
such Ubuntu device is locked by a PIN.
  User has to try to unlock the device on the dark screen, open the top panel 
with settings, scroll to the far right (to access the brightness settings), and 
then trying to hit the correct slider - all on a dark screen.

  This happened on Aquaris E5.

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

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

[Touch-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

2016-12-12 Thread Stefan

My config attached.

** Attachment added: "config-default.xml"
   
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1483427/+attachment/4790904/+files/config-default.xml

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

Title:
  Possible to manually set display brightness to 0 on Ubuntu Touch on
  Aquaris E5

Status in indicator-power package in Ubuntu:
  Invalid
Status in repowerd package in Ubuntu:
  New

Bug description:
  Possible to manually set display brightness to 0 on Ubuntu Touch

  It is possible to move the brightness slider to the very left
  position, which will set the display brightness of affected device to
  zero, or, to total darkness.

  This is a bug, since this leads to user's inability to set the brightness 
back or, generally, to operate the device.
  There is a slight chance, though, to return the brightness back to non-zero 
value (blindly, trying by user's memory).

  Also, this gets even more problematic, if we think about a scenario, where 
such Ubuntu device is locked by a PIN.
  User has to try to unlock the device on the dark screen, open the top panel 
with settings, scroll to the far right (to access the brightness settings), and 
then trying to hit the correct slider - all on a dark screen.

  This happened on Aquaris E5.

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

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

[Touch-packages] [Bug 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI

2016-12-12 Thread Ray-Ven

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

** This bug has been marked a duplicate of bug 1467190
   No audio over DisplayPort MST

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

Title:
  Lenovo Onelink Pro Dock - No audio via Dock-HDMI

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound over Laptop HDMI works, but won't work over Dock with Kernels
  newer than 2.16 in all ubuntu releases since trusty. Persists with
  latest bios (state 16.08.16) Freshinstall makes no difference.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 21 14:23:10 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET34WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S0AX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S0AX00
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1649385] Re: id command: German translation typo

2016-12-12 Thread Torsten Franz

I have review this translation.

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

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

Title:
  id command:  German translation typo

Status in Ubuntu Translations:
  Fix Released

Bug description:
  when calling "id -z root", Ubuntu id tells me:

id: die Option --zero ist im Sandardformat nicht zulässig

  There is no word like "Sandardformat" - it should mean
  "Standardformat"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 20:20:08 2016
  InstallationDate: Installed on 2016-11-27 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649385] Re: id command: German translation typo

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

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

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

Title:
  id command:  German translation typo

Status in Ubuntu Translations:
  Fix Released

Bug description:
  when calling "id -z root", Ubuntu id tells me:

id: die Option --zero ist im Sandardformat nicht zulässig

  There is no word like "Sandardformat" - it should mean
  "Standardformat"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 20:20:08 2016
  InstallationDate: Installed on 2016-11-27 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

btw.. there are some side effects X-) now in unity7 the wired connection
is missing and the indicator panel looks weird, see attached screenshot.
this is a daily build.. like today daily build without unity8 installed.
i don't care enough to report unity7 bugs.. but just saying

** Attachment added: "dkk.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640214/+attachment/4790862/+files/dkk.png

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Touch-packages] [Bug 1649385] Re: id command: German translation typo

2016-12-12 Thread Torsten Franz

** Package changed: coreutils (Ubuntu) => ubuntu-translations

** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

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

Title:
  id command:  German translation typo

Status in Ubuntu Translations:
  Fix Released

Bug description:
  when calling "id -z root", Ubuntu id tells me:

id: die Option --zero ist im Sandardformat nicht zulässig

  There is no word like "Sandardformat" - it should mean
  "Standardformat"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 20:20:08 2016
  InstallationDate: Installed on 2016-11-27 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI

2016-12-12 Thread Ray-Ven

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

what a shame - still not working - tried it in xenial and yakkety again

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

Title:
  Lenovo Onelink Pro Dock - No audio via Dock-HDMI

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound over Laptop HDMI works, but won't work over Dock with Kernels
  newer than 2.16 in all ubuntu releases since trusty. Persists with
  latest bios (state 16.08.16) Freshinstall makes no difference.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 21 14:23:10 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET34WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S0AX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S0AX00
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1648982] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

** Tags removed: need-duplicate-check

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in cups package in Ubuntu:
  New

Bug description:
  not update successfully and package is bad

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 10 20:41:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-10  20:41:13
   Requested-By: ajinkya-im-possible (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), 
python3-apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), apport-gtk:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), python3-problem-report:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.1), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.1), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  DuplicateSignature:
   package:cups-daemon:2.1.3-4
   Removing cups-core-drivers (2.1.3-4ubuntu0.1) ...
   dpkg: error processing package cups-daemon (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2016-12-03 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Sony Corporation VPCCB45FN
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2110V2
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2110V2:bd09/27/2011:svnSonyCorporation:pnVPCCB45FN:pvrC60A1P3G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCB45FN
  dmi.product.version: C60A1P3G
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1645798] Re: No snaps appear in scope on Core 16

2016-12-12 Thread Rodney Dawes

Michi, the exception itself seems to be from
https://bazaar.launchpad.net/~unity-team/unity-scopes-
api/trunk/view/head:/src/scopes/internal/zmq_middleware/ZmqMiddleware.cpp
and getting bubbled up through the bits.

Judging from the logs, what appears to happen is that the scope is
started, and initialized, and we are then sent a Query(), and we have a
Reply object to push results back through. At that point, the socket
seems to get closed and the middleware is stopped. The scope then has
results and tries to push(), but since the middleware is stopped, we get
the exception from deep inside the scopes API.

It's true that the scope itself could probably handle this very
unexpected situation more gracefully on its own, but doing so won't
really resolve the problem here of there not being any results, since
the socket is closed and thus it's impossible for the scope to give any
results back to the shell.

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

Title:
  No snaps appear in scope on Core 16

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  Confirmed
Status in unity-api package in Ubuntu:
  Invalid
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  No snaps appear in scope on Core 16 whereas they do appear in unity8
  snap on classic

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

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

[Touch-packages] [Bug 1648982] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

2016-12-12 Thread Emily Ratliff

** Information type changed from Private Security to Public

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in cups package in Ubuntu:
  New

Bug description:
  not update successfully and package is bad

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 10 20:41:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-12-10  20:41:13
   Requested-By: ajinkya-im-possible (1000)
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), 
python3-apport:amd64 (2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), apport-gtk:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2), python3-problem-report:amd64 
(2.20.1-0ubuntu2.1, 2.20.1-0ubuntu2.2)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.1), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.1), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  DuplicateSignature:
   package:cups-daemon:2.1.3-4
   Removing cups-core-drivers (2.1.3-4ubuntu0.1) ...
   dpkg: error processing package cups-daemon (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2016-12-03 (7 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Sony Corporation VPCCB45FN
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=e703e877-2af5-49c0-90d6-27a018ee1929 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2110V2
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2110V2:bd09/27/2011:svnSonyCorporation:pnVPCCB45FN:pvrC60A1P3G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCB45FN
  dmi.product.version: C60A1P3G
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1649385] Re: id command: German translation typo

2016-12-12 Thread Christian González

Just found it in translations:
https://translations.launchpad.net/ubuntu/yakkety/+source/coreutils/+pots/coreutils/de/705/+translate

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

Title:
  id command:  German translation typo

Status in coreutils package in Ubuntu:
  New

Bug description:
  when calling "id -z root", Ubuntu id tells me:

id: die Option --zero ist im Sandardformat nicht zulässig

  There is no word like "Sandardformat" - it should mean
  "Standardformat"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 20:20:08 2016
  InstallationDate: Installed on 2016-11-27 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649385] [NEW] id command: German translation typo

2016-12-12 Thread Christian González

Public bug reported:

when calling "id -z root", Ubuntu id tells me:

  id: die Option --zero ist im Sandardformat nicht zulässig

There is no word like "Sandardformat" - it should mean "Standardformat"

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec 12 20:20:08 2016
InstallationDate: Installed on 2016-11-27 (15 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  id command:  German translation typo

Status in coreutils package in Ubuntu:
  New

Bug description:
  when calling "id -z root", Ubuntu id tells me:

id: die Option --zero ist im Sandardformat nicht zulässig

  There is no word like "Sandardformat" - it should mean
  "Standardformat"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 12 20:20:08 2016
  InstallationDate: Installed on 2016-11-27 (15 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649153] Re: upgrade from 15.10 to 16.04 broken, bricks computer

Could you please run ubuntu-bug 1649153 so log files regarding the
upgrade process will be added to the bug?

** Package changed: apt (Ubuntu) => ubuntu-release-upgrader (Ubuntu)

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Incomplete

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

Title:
  upgrade from 15.10 to 16.04 broken, bricks computer

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  I upgraded (or tried to) from 15.10 to 16.04.

  After a few errors as per bug 1561467 and a few crash-report popups
  which I don't know whether were related or not, I finally got the
  error message:

  "Could not install the upgrades
  The upgrade has aborted. YOUR SYSTEM COULD BE IN AN UNUSABLE STATE. A 
recovery will run now (dpkg --configure -a)"
  (emphasys added).

  By clicking "Close", I expedted the "recovery" to run and hopefully recover 
something, but nothing happened.
  Almost immediately, the upgrade window with the checklist ("download stuff", 
"install stuff", ... "cleanup", "restart computer") disappeared (without 
prompting me to restart the computer) and I got a message like "Upgrade 
complete. The system was updated but there were errors" or something like that. 
(obviously this is all unacceptable: you tell me my system could be unusable 
and don't give me a clue about what the fuck happened and what I am supposed to 
do?!?)

  So, I tried running "dpkg --configure -a" in a terminal, but I only
  got a very long series of almost identical errors regarding dependency
  problems for many many packages, which ended more or less like
  "Aborting, too many errors".

  After a bit of googling, I tried this which I seemed to understand could 
maybe fix the issue:
sudo apt-get -f install
  (or "sudo apt-get install -f", can't remember now)

  
  This seems to have worked. I could reboot (got a couple of crash reports, I 
hope they won't pop up at every reboot), my system is now 16.04 and tried some 
random stuff which seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 11 23:17:12 2016
  InstallationDate: Installed on 2013-10-11 (1157 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (0 days ago)

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

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

[Touch-packages] [Bug 1517257] Re: apport-retrace should install and use gdb for target release

** Changed in: apport (Ubuntu)
Milestone: None => ubuntu-17.01

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

Title:
  apport-retrace should install and use gdb for target release

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  apport-retrace will use the version of gdb installed on the system
  performing the retrace. This can cause issues retracing crash reports
  from releases that have a newer toolchain revision than the system
  performing the retrace. Subsequently, it would be better if apport-
  retrace were to install gdb into the sandbox being used for retracing
  and used that version of gdb for analyzing the core dump.

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

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

[Touch-packages] [Bug 1649370] [NEW] libnss-{resolve,myhostname} don’t install correctly if previously removed without being purged

2016-12-12 Thread Anders Kaseorg

Public bug reported:

# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns

libnss-resolve.postinst and libnss-myhostname.postinst only update
/etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ].  If the
package was previously removed but not purged (it is in the Config-Files
state), dpkg passes the previous version as $2, so this fails.

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


** Tags: zesty

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

Title:
  libnss-{resolve,myhostname} don’t install correctly if previously
  removed without being purged

Status in systemd package in Ubuntu:
  New

Bug description:
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname resolve [!UNAVAIL=return] dns
  # apt remove libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns

  libnss-resolve.postinst and libnss-myhostname.postinst only update
  /etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ].  If the
  package was previously removed but not purged (it is in the Config-
  Files state), dpkg passes the previous version as $2, so this fails.

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

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

[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser

2016-12-12 Thread Cerin

This is still broken in 16.04.

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

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Precise:
  Triaged
Status in apparmor source package in Quantal:
  Fix Released

Bug description:
  SRU Justification:

  Impact: when chromium-browser or Google Chrome are set as the default
  browser, the user is unable to open links via PDF files

  Development fix: the fix will be applied to Quantal via pocket copy of
  this SRU.

  Stable fix: this was fixed in r2039 by adding the following to 
/etc/apparmor.d/abstractions/ubuntu-helpers:
# While the chromium and chrome sandboxes are setuid root, they only link
# in limited libraries so glibc's secure execution should be enough to not
# require the santized_helper (ie, LD_PRELOAD will only use standard system
# paths (man ld.so)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,

  TEST CASE:
  1. Install chromium-browser and/or Google Chrome

  2. Launch chromium-browser (or Chrome) and set it as the default web
  browser

  3. Open a PDF with a link in it (attached) in evince and click on the
  link.

  At this point, chromium-browser (or Chrome) should open to the link
  specified. Without the patch, it does not open and there are AppArmor
  denials in /var/log/kern.log.

  Regression potential: the regression potential is considered low.
  Launching chromium-browser and Chrome via evince is currently broken,
  so there is no regression potential there, however ubuntu-helpers is
  included by the (disable by default) firefox profile so a mistake in
  the added policy could prevent firefox policy from loading.

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

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

[Touch-packages] [Bug 1282314] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser

2016-12-12 Thread Cerin

This is still broken in 16.04.

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

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  This is similar to bug #964510 but found on Ubuntu 13.10 Saucy which
  already has the patch for that bug, and with a different message:

  Feb 19 23:50:14 sammy kernel: [413602.643399] type=1400
  audit(1392853814.794:89): apparmor="DENIED" operation="file_mmap"
  parent=28174 profile="/usr/bin/evince//sanitized_helper"
  name="/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18" pid=28181 comm
  ="chrome-sandbox" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

  Symptoms are the same, evince fails to launch chromium when it's
  selected as the default.

  Evince run from the command line outputs the following when you click
  a link:

  /usr/lib/chromium-browser/chrome-sandbox: error while loading
  shared libraries: libstdc++.so.6: failed to map segment from shared
  object: Permission denied

  Another user reported the same issue
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/comments/15
  but received no response to date.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2016-12-12 Thread Anders Kaseorg

Whether or not it’s enabled, it is started automatically via D-BUS
activation (/lib/systemd/system/dbus-org.freedesktop.resolve1.service ->
systemd-resolved.service).

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

While I've accepted this into -proposed and the Test Case is rather
obvious it'd still be helpful if someone were to update the description
such that it follows the SRU template.

https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in glib2.0 source package in Yakkety:
  Fix Committed
Status in nautilus source package in Yakkety:
  Invalid

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

Hello Sadi, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  New
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

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

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

[Touch-packages] [Bug 1633824] Re: nautilus ignores trash on external drives

Hello Dylan, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  nautilus ignores trash on external drives

Status in GLib:
  Fix Released
Status in Nautilus:
  Invalid
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in glib2.0 source package in Yakkety:
  Fix Committed
Status in nautilus source package in Yakkety:
  Invalid

Bug description:
  Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to
  trash in general. However only the items removed from permanently
  installed drives shows up in the trash virtual folder. In the case of
  usb removable drives, the .Trash-1000 folder is correctly created, and
  the files are in there but the nautilus GUI does not show those files
  in its virtual trash folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 11:48:03 2016
  InstallationDate: Installed on 2016-02-19 (239 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1644320] Re: [SRU] New upstream release 2.50.1

Hello Iain, or anyone else affected,

Accepted glib2.0 into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/glib2.0/2.50.2-2ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] New upstream release 2.50.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Upstream have released a new bugfix release.

  [ Changes ]

  From NEWS:

  Overview of changes in GLib 2.50.2
  ==

  * Bugs fixed:
   767882 Bit shift overflow (-Wshift-overflow) warning in gparam.h
   769135 External control for g_test_add/g_test_run
   769630 gfile: G_FILE_MONITOR_WATCH_MOVES was actually introduced in 2.46
   772054 Patch for glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   773303 GApplication leaks option_strings
   773344 glib-compile-resources: Fix creating depfile with other targets
  
  * Translation updates:
   French
   Galician
   German
   Lithuanian
   Norwegian bokmål
   Occitan
   Serbian
   Slovak

  
  Overview of changes in GLib 2.50.1
  ==

  * Update Unicode support to Unicode 9.0.0

  * Bugs fixed:
   662946 gunixmounts monitoring doesn't work correctly with libmount
   771591 Update to Unicode 9.0.0
   772054 glib/gspawn-win32-helper.c: unexpected behavior re 
CommandLineToArgvW()
   772255 gresolver: Mark GResolver as an abstract class
   772269 Add --version options to glib-compile-resources and 
glib-compile-schemas
   772297 completion: Complete gsettings describe
   772511 g_log_default_handler crashes windows apps with "Unspecified fatal 
err...

  * Translation updates: 
   Brazilian Portuguese
   Catalan
   Croatian
   Czech
   Danish
   Hungarian
   Italian
   Latvian 
   Polish
   Swedish

  
  [ QA, testing, regression potential ]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

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

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

[Touch-packages] [Bug 1646758] Re: Can't update or install apps

2016-12-12 Thread Jesse

I'm still encountering this problem on the Nexus 4, rc-proposed channel.
Using the LGE Nexus 4, r582 build.

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

Title:
  Can't update or install apps

Status in Canonical System Image:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  bq M10 rc-proposed r243

  When trying to update an app this morning, I got an error about destination 
path not being writable. The app is YouTube by Mateo Salta. 
  Screenshot with the error attached.

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2016-12-12 Thread Stan Hu

Lukasz, could we get an updated release for Ubuntu 16.04 (xenial)? We're
finding that the latest kernel updates are overwriting our custom dbus
packages, and we would prefer to have an official release soon. Thank
you!

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

[Touch-packages] [Bug 1637800] Re: add a motd script for news

2016-12-12 Thread Dimitri John Ledkov

Please use .timer systemd unit to asynchronously fetch these news on
boot, and periodically thereafter (there is support for both stanzas),
do so safely from https, have templated news, and cache them, at the end
include the cached news into motd.

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

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

[Touch-packages] [Bug 1649355] Re: package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instance

** Tags removed: need-duplicate-check

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

Title:
  package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is
  different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  E: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb:
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which
  is different from other instances of package libpng12-0:amd64

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.51-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Mon Dec 12 18:41:22 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu5
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ...
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  DuplicateSignature:
   package:libpng12-0:1.2.51-0ubuntu3
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instances 
of package libpng12-0:amd64
  InstallationDate: Installed on 2016-12-03 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: libpng
  Title: package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different 
from other instances of package libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649355] [NEW] package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instan

2016-12-12 Thread Giorgio

Public bug reported:

E: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb: trying
to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is
different from other instances of package libpng12-0:amd64

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpng12-0 1.2.51-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
Date: Mon Dec 12 18:41:22 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu5
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu5
 zlib1g 1:1.2.8.dfsg-2ubuntu4
DpkgTerminalLog:
 Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ...
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
DuplicateSignature:
 package:libpng12-0:1.2.51-0ubuntu3
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
ErrorMessage: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', 
which is different from other instances of package libpng12-0:amd64
InstallationDate: Installed on 2016-12-03 (8 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: libpng
Title: package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from 
other instances of package libpng12-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is
  different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  E: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb:
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which
  is different from other instances of package libpng12-0:amd64

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.51-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Mon Dec 12 18:41:22 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu5
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu5
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ...
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  DuplicateSignature:
   package:libpng12-0:1.2.51-0ubuntu3
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instances 
of package libpng12-0:amd64
  InstallationDate: Installed on 2016-12-03 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: libpng
  Title: package libpng12-0 1.2.51-0ubuntu3 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different 
from other instances of package libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2016-12-12 Thread Sean O'Donnell

This is affecting me.

Decided to give Ubuntu 16.04 a try and I cannot for the life of me get
Optical or the green, black and orange/brown cables working either (The
3.5mm jacks).

Audio works in windows fine, I did the echo "options snd-hda-intel
position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf fix and it
worked for a day, when I restarted from windows to Linux it broke again.

Everything shows up. It should be working but sound does not play at
all.

HDMI Audio works fine via my monitor.

Motherboard: Gigabyte Gaming 7 Z170
Card: HDA Intel PCH 
Chip: Creative CA0132  

If I can do anything to help please let me know. I can't switch over
from windows if I don't have audio.

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Skylinux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx: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.

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

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

[Touch-packages] [Bug 1649352] [NEW] http direct to terminals?

*** This bug is a security vulnerability ***

Public security bug reported:

Hi Dustin,

Some recent changes introduced what looks to be a serious problem:

http://launchpadlibrarian.net/296647523/base-
files_9.6ubuntu7_9.6ubuntu8.diff.gz

-SERVER="https://motd.ubuntu.com";
+# White space separated list of 0 to many news services
+SERVER="http://motd.ubuntu.com";
[...]
+   if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" 
-o- "$s" >"$NEWS" 2>"$ERR"; then
+   echo
+   # At most, 2 lines of at most 80 characters
+   cat "$NEWS" | tail -n 2 | cut -c -80

This allows any network man-in-the-middle attacker, DNS response forger,
or BGP forger, to write 160 raw bytes directly to terminals.

The previous version wasn't good (open for abuse by anyone who could
trick one of the myriad x.509 Certificate Authorities to mis-issue a
certificate) but this version is open for abuse by significantly more
attackers.

While most terminals are reasonably safe against outright maliciousness
this has been a recurring exploitation theme for twenty years, and even
what is "safe" for them to display could be wildly confusing to users
unfamiliar with maliciously controlled terminals. (And users have wide
tastes in terminals, some are fairly brittle.)

cat(1) does not do any filtering for 'safe' display of arbitrary inputs.
less(1) does, assuming -r is not in LESS environment variable or the
less(1) command line. If you wish to keep the pipeline, perhaps tr(1)'s
-d flag could be useful.

On a related note, is there a reason why the motd.ubuntu.com server
can't do HTTPS?

Thanks

** Affects: base-files (Ubuntu)
 Importance: Critical
 Status: Confirmed

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

Title:
  http direct to terminals?

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Hi Dustin,

  Some recent changes introduced what looks to be a serious problem:

  http://launchpadlibrarian.net/296647523/base-
  files_9.6ubuntu7_9.6ubuntu8.diff.gz

  -SERVER="https://motd.ubuntu.com";
  +# White space separated list of 0 to many news services
  +SERVER="http://motd.ubuntu.com";
  [...]
  + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" 
-o- "$s" >"$NEWS" 2>"$ERR"; then
  + echo
  + # At most, 2 lines of at most 80 characters
  + cat "$NEWS" | tail -n 2 | cut -c -80

  This allows any network man-in-the-middle attacker, DNS response
  forger, or BGP forger, to write 160 raw bytes directly to terminals.

  The previous version wasn't good (open for abuse by anyone who could
  trick one of the myriad x.509 Certificate Authorities to mis-issue a
  certificate) but this version is open for abuse by significantly more
  attackers.

  While most terminals are reasonably safe against outright
  maliciousness this has been a recurring exploitation theme for twenty
  years, and even what is "safe" for them to display could be wildly
  confusing to users unfamiliar with maliciously controlled terminals.
  (And users have wide tastes in terminals, some are fairly brittle.)

  cat(1) does not do any filtering for 'safe' display of arbitrary
  inputs. less(1) does, assuming -r is not in LESS environment variable
  or the less(1) command line. If you wish to keep the pipeline, perhaps
  tr(1)'s -d flag could be useful.

  On a related note, is there a reason why the motd.ubuntu.com server
  can't do HTTPS?

  Thanks

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

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

[Touch-packages] [Bug 1649352] Re: http direct to terminals?

2016-12-12 Thread Dimitri John Ledkov

This looks a lot like a call-home backdoor.

** Changed in: base-files (Ubuntu)
   Importance: Undecided => Critical

** Changed in: base-files (Ubuntu)
   Status: New => Confirmed

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

Title:
  http direct to terminals?

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Hi Dustin,

  Some recent changes introduced what looks to be a serious problem:

  http://launchpadlibrarian.net/296647523/base-
  files_9.6ubuntu7_9.6ubuntu8.diff.gz

  -SERVER="https://motd.ubuntu.com";
  +# White space separated list of 0 to many news services
  +SERVER="http://motd.ubuntu.com";
  [...]
  + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" 
-o- "$s" >"$NEWS" 2>"$ERR"; then
  + echo
  + # At most, 2 lines of at most 80 characters
  + cat "$NEWS" | tail -n 2 | cut -c -80

  This allows any network man-in-the-middle attacker, DNS response
  forger, or BGP forger, to write 160 raw bytes directly to terminals.

  The previous version wasn't good (open for abuse by anyone who could
  trick one of the myriad x.509 Certificate Authorities to mis-issue a
  certificate) but this version is open for abuse by significantly more
  attackers.

  While most terminals are reasonably safe against outright
  maliciousness this has been a recurring exploitation theme for twenty
  years, and even what is "safe" for them to display could be wildly
  confusing to users unfamiliar with maliciously controlled terminals.
  (And users have wide tastes in terminals, some are fairly brittle.)

  cat(1) does not do any filtering for 'safe' display of arbitrary
  inputs. less(1) does, assuming -r is not in LESS environment variable
  or the less(1) command line. If you wish to keep the pipeline, perhaps
  tr(1)'s -d flag could be useful.

  On a related note, is there a reason why the motd.ubuntu.com server
  can't do HTTPS?

  Thanks

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

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

[Touch-packages] [Bug 1648905] Re: VPN username and settings not saved

2016-12-12 Thread Sebastien Bacher

the issue has been fixed in 1.2.6

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=bb45adeda0bf427ada23b09daf970b0757e82d60

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  VPN username and settings not saved

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The OpenConnect VPN auth-dialog doesn't remember usernames and other
  settings.

  See discussion (and fix) in
  https://bugzilla.redhat.com/show_bug.cgi?id=1332491

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

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

[Touch-packages] [Bug 1562111] Re: network-manager no longer restarts dnsmasq

2016-12-12 Thread Sebastien Bacher

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  network-manager no longer restarts dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  restarting Network Manager does not have any effect on it's child
  dnsmasq (nor does stopping and starting)

  ubuntu@ubuntu:~$ pidof dnsmasq
  2355
  ubuntu@ubuntu:~$ sudo systemctl restart NetworkManager
  ubuntu@ubuntu:~$ pidof dnsmasq
  2355

  This problem started in 15.10 and still exists in 16.04 beta2 - it
  works as expected in 14.04.

  The upshot is you cannot load any extra dnsmasq configuration set in
  the conf dir /etc/NetworkManager/dnsmasq.d/ because dnsmasq doesn't
  get restarted.

  
  (As a related issue dnsmasq is also running as 'nobody' and I don't think it 
should, Bug #1105493)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  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: Fri Mar 25 18:13:33 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.107  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  53d8bcbd-4047-4705-904a-60eef9d821c1  802-3-ethernet   
1458929440  Fri 25 Mar 2016 06:10:40 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 -- 
   Mosquitoa88863fb-196e-4000-8103-880e0698d514  802-11-wireless  
1458929448  Fri 25 Mar 2016 06:10:48 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes wlp4s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Mosquitoa88863fb-196e-4000-8103-880e0698d514  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails

2016-12-12 Thread mir-ci-bot

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.26.0

** Changed in: mir
   Status: Fix Released => Fix Committed

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

Title:
  mir_demo_server --test-client
  [mir_demo_client_scroll|mir_demo_client_flicker] fails

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_flicker || echo FAILED
  ...
  Connected
  Surface created
  [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:19:54.463779] mirserver: Stopping
  FAILED

  $ bin/mir_demo_server --test-timeout 3 --test-client 
bin/mir_demo_client_scroll || echo FAILED
  ...
  Connected
  Mir chose pixel format 3
  Surface created
  [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client 
terminated by signal 15
  [2016-03-11 17:21:51.922045] mirserver: Stopping
  FAILED

  I suspect these clients ignore SIGTERM

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

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

[Touch-packages] [Bug 1645501] Re: corefiles not created in armhf chroot on arm64 porter

There is some discussion going on upstream regarding how to solve this,
after that's sorted I'll redo the zesty patch and upload SRUs for this.

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

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Precise:
  Invalid
Status in gdb source package in Trusty:
  Triaged
Status in gdb source package in Xenial:
  Triaged
Status in gdb source package in Yakkety:
  Triaged

Bug description:
  Impact
  --
  Its not possible to create a corefile in an armhf chroot on an arm64 system.

  Test Case
  -
  On an arm64 system enter an armhf chroot, then 
  1) execute "gdb --args cat"
  2) in gdb type run
  3) press Ctrl-Z
  4) generate-core-file /tmp/my.core

  With the current version of gdb you'll see "Unable to fetch floating
  point registers.", with the version in -proposed you'll see "Saved
  corefile".

  Regression Potential
  
  I'm not quite sure.

  
  I'm filing this about gdb per Steve's suggestion, although this could be an 
issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

    47 Program received signal SIGSEGV, Segmentation fault.
    48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
    49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
    50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

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

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

[Touch-packages] [Bug 1441147] Re: Infographic text should reset after midnight

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

** This bug is no longer a duplicate of bug 1438645
   The circle on the lock screen shows yesterday's info
** This bug has been marked a duplicate of bug 1378814
   greeter does not properly update infographic after unlock

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

Title:
  Infographic text should reset after midnight

Status in unity8 package in Ubuntu:
  New

Bug description:
  I just woke up and looked at my phone.  "6 text messages sent today."

  Who's been using my phone!?

  But seriously, unity8 should notice when the clock ticks into a new
  day and reset the infographic.

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

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

[Touch-packages] [Bug 1397963] Re: [sim pin] SIM PIN + passcode screens too similar

This is no longer true, the dialogs are different.

** Changed in: ubuntu-ux
   Status: In Progress => Fix Released

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

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

Title:
  [sim pin] SIM PIN + passcode screens too similar

Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  unity8 8.01+15.04.20141125.2-0ubuntu1, Ubuntu 15.04

  The SIM PIN and lock-screen dialogs for passcode are too similar to
  one another, I repeatedly end up putting my passcode as SIM PIN, this
  could lead to locking your SIM card.

  Fixing this might also fix bug 1387207.

  
  UX comment--

  Desired resolution: please see comment #2

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

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

[Touch-packages] [Bug 1438645] Re: The circle on the lock screen shows yesterday's info

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

** This bug has been marked a duplicate of bug 1378814
   greeter does not properly update infographic after unlock

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

Title:
  The circle on the lock screen shows yesterday's info

Status in libusermetrics package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When I wake up in the morning and look at my phone, I see for example:
  "14 text messages sent today" which is not true. It was true
  yesterday.

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

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

[Touch-packages] [Bug 1649334] [NEW] can't copy paste error messages

Public bug reported:

when you get an error like network error or etc you can't copy the error
message because the error message text is not selectable.

go to www.qwer234234aasdv.com or whatever site that doesn't exist to
trigger an error message and try to select and coppy the error message
text

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

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

Title:
  can't copy paste error messages

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  when you get an error like network error or etc you can't copy the
  error message because the error message text is not selectable.

  go to www.qwer234234aasdv.com or whatever site that doesn't exist to
  trigger an error message and try to select and coppy the error message
  text

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

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

[Touch-packages] [Bug 1649168] Re: weekly log rotation is often a day late

2016-12-12 Thread Doug Smythies

There is also issue 93 at GitHub:

https://github.com/logrotate/logrotate/issues/93

I seem to be unable to create a GitHub account so that I can add to the
issue discussion, and point to here.


** Bug watch added: github.com/logrotate/logrotate/issues #93
   https://github.com/logrotate/logrotate/issues/93

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

Title:
  weekly log rotation is often a day late

Status in logrotate package in Ubuntu:
  New

Bug description:
  Over the last few Ubuntu releases, the status file the logrotate
  generates and uses has been adding more and more detailed time stamp
  information.

  In 12.04 it seems to only keep information to the day.
  In 14.04 it seems to only keep information to the hour.
  In 16.04 it seems to keep information to the second.

  However, the weekly section of the logrotate program calculates the
  time since the last rotation to the second with absolutely no jitter
  margin, and therefore as often as every other week, weekly logs that
  should rotate on Sunday do not rotate until Monday. I have 43 weeks of
  weekly rotation data, where on 17 of those weeks the rotation was on
  Monday and not Sunday. Note that the week after Monday rotation it
  will always rotate on Sunday due to "the current weekday is before the
  weekday of the last rotation" condition.

  Code segment:

  case ROT_WEEKLY:
  /* rotate if:
 1) the current weekday is before the weekday of the
 last rotation
 2) more then a week has passed since the last
 rotation */
  state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday)
 ||
 ((mktime(&now) -
   mktime(&state->lastRotated)) >
  (7 * 24 * 3600)));

  There is an upstream bug report at: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776
  which I will attempt to link in. It suggests introducing a 60 jitter 
allowance. I would make it more myself.

  I first noticed this issue during 16.04 development in 2016.02 (Feb).
  See also: https://ubuntuforums.org/showthread.php?t=2320149

  Do not ask me to run apport collect for this bug report, because it is
  not needed, and it never works for me anyhow.

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

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

[Touch-packages] [Bug 1649332] [NEW] webbrowser snap, can only view some sites

Public bug reported:

webbrowser snap on unity8/17.04

only some site works, for ex launchpad.net, ubuntu.com, etc but others
like youtube.com or reddit.com don't work i get "network error please
check your nettwork connection.., etc" but my network connection is fine
(works great on unity7 session), i also get the same message using
firefox with libertine or chrome snap

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

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

Title:
  webbrowser snap, can only view some sites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  webbrowser snap on unity8/17.04

  only some site works, for ex launchpad.net, ubuntu.com, etc but others
  like youtube.com or reddit.com don't work i get "network error please
  check your nettwork connection.., etc" but my network connection is
  fine (works great on unity7 session), i also get the same message
  using firefox with libertine or chrome snap

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

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

[Touch-packages] [Bug 1637779] Re: ext4 filesystem fails randomly with checksum error

2016-12-12 Thread Sam Wisdom

Also got this issue after using ext2fsd (dual-boot), never had any
issues before

I have attached my dumpe2fs output

** Attachment added: "dumpe2fs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4790759/+files/dumpe2fs.txt

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

Title:
  ext4 filesystem fails randomly with checksum error

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  package version:
  linux-image-4.8.0-26-generic:
Installed: 4.8.0-26.28
Candidate: 4.8.0-26.28
Version table:
   *** 4.8.0-26.28 500
  500 http://sk.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  fresh installation of Ubunut 16.10, all updates included

  While I am working with system after few minutes root filesystem /dev/sdb5 
switches into readonly mode
  in dmesg is this:

  [  304.921552] EXT4-fs error (device sdb5): ext4_iget:4476: inode #24577: 
comm updatedb.mlocat: checksum invalid
  [  304.925565] Aborting journal on device sdb5-8.
  [  304.926507] EXT4-fs (sdb5): Remounting filesystem read-only
  [  304.927416] EXT4-fs error (device sdb5): ext4_journal_check_start:56: 
Detected aborted journal
  [  304.943408] EXT4-fs error (device sda1): ext4_iget:4476: inode #12: comm 
updatedb.mlocat: checksum invalid

  when it happens I must do fsck f /dev/sdb1 once, second time it says
  everything is fine. after reboot when I start dto do something it soon
  happens again

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

-- 
Mailing list: https://launchpad.net/~touch-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: Segmentation fault (core dumped) on 17.04

gpu intel sandybridge something

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

Title:
  Segmentation fault (core dumped) on 17.04

Status in webbrowser-app package in Ubuntu:
  New

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/ubuntu/+source/webbrowser-app/+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 1649313] Re: Mediascanner is not working

2016-12-12 Thread Victor gonzalez

** Summary changed:

- mediascanner not working
+ Mediascanner is not working

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

Title:
  Mediascanner is not working

Status in mediascanner package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Mediascanner doesn't work in
  frieza_arm64 so files in sdcards aren't detected.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard r other external devices should
  be detected

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

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

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

2016-12-12 Thread han solo

OTA-14 update now
still NOT working

same problem with sending sms(right side of touch do not response)
but scrolling in browser works(touch response on right side)

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

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 1588349] Re: Checking for updates never finishes on 3G when no updates available

2016-12-12 Thread Anupam

** Description changed:

If I'm using wi-fi and go to settings and then select updates, "Checking for
updates..." screen appears with a spinner for a few seconds; if there is any
update available it shows, otherwise informs about the unavailability of
updates.
But while using mobile data (3G/H) *if there is no update available*, it gets
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I
waited as long as 10-15 minutes.
Note: If there is an update available then the behaviour is normal, i.e.
shows the available update(s) after a few seconds.
I'm seeing this behaviour from the very beginning (OTA-6 days).

Related to bug #1528886
+
+ UPDATE: It's gotten weirder after the introduction of the new update
+ panel in OTA-13. When there is an update available, it keeps on
+ "Checking for updates..." along with the list of available updates:

** Attachment added: "checking and listing available at once"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1588349/+attachment/4790760/+files/screenshot20161212_215042136.png

** Description changed:

Related to bug #1528886

- UPDATE: It's gotten weirder after the introduction of the new update
- panel in OTA-13. When there is an update available, it keeps on
- "Checking for updates..." along with the list of available updates:
+ UPDATE: It's gotten weirder after the introduction of the new update panel in
OTA-13. When there is an update available, it keeps on "Checking for
updates..." along with the list of available updates:
+ https://launchpadlibrarian.net/297883544/screenshot20161212_215042136.png

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

Title:
Checking for updates never finishes on 3G when no updates available

Status in Canonical System Image:
Confirmed
Status in system-image package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
Incomplete

Bug description:
If I'm using wi-fi and go to settings and then select updates, "Checking for
updates..." screen appears with a spinner for a few seconds; if there is any
update available it shows, otherwise informs about the unavailability of
updates.
But while using mobile data (3G/H) *if there is no update available*, it gets
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I
waited as long as 10-15 minutes.
Note: If there is an update available then the behaviour is normal, i.e.
shows the available update(s) after a few seconds.
I'm seeing this behaviour from the very beginning (OTA-6 days).

Related to bug #1528886

UPDATE: It's gotten weirder after the introduction of the new update panel in
OTA-13. When there is an update available, it keeps on "Checking for
updates..." along with the list of available updates:
https://launchpadlibrarian.net/297883544/screenshot20161212_215042136.png

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

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

[Touch-packages] [Bug 1543351] Re: Add on-screen-keyboard support for Xmir/Libertine apps

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

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

Title:
  Add on-screen-keyboard support for Xmir/Libertine apps

Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Libertine:
  Fix Released
Status in Libertine devel series:
  Fix Released
Status in Libertine trunk series:
  Fix Released
Status in Ubuntu UX:
  New
Status in libertine package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

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

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

[Touch-packages] [Bug 1557717] Re: indicator-session should emit Shutdown not Reboot for unity8

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

** Changed in: indicator-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-session should emit Shutdown not Reboot for unity8

Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In indicator-session, the following code exists:

case PROMPT_WITH_UNITY:
  /* NB: TYPE_REBOOT instead of TYPE_SHUTDOWN because
 the latter adds lock & logout options in Unity... */
  show_unity_end_session_dialog (self, END_SESSION_TYPE_REBOOT);

  Can we get that fixed?  unity8 doesn't currently have such issues, but
  is forced to hack a shutdown dialog when asked to show a reboot dialog
  because of this.

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

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

[Touch-packages] [Bug 1589220] Re: Launching a sidestage app in portrait and spreading, app won't focus

2016-12-12 Thread Guillaume F

This doesn't happen any more in OTA-14. Maybe the new switcher fixed
this without knowing.

I'm marking this as "Fix released", but it's the first time I do it,
feel free to correct me if it's not the appropriate way of doing it.

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

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

Title:
  Launching a sidestage app in portrait and spreading, app won't focus

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - tablet in portrait view
  - launch an app that you know to be in sidestage mode
  - spread apps with a right swipe
  - turn the tablet back in landscape view
  - try to focus on the recently opened sidestage app

  Expected result:
  The app goes in the foreground, in sidestage.

  Current result:
  I don't know exactly: if you spread slowly, you can glimpse the "use three 
fingers" screen that you get when no app is in sidestage, and selecting the 
newly opened app won't work and focuses on another one. Switching to yet 
another app, the sidestage app finally shows.

  Not sure my description is very clear but hopefully it will be easy to
  reproduce!

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

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

[Touch-packages] [Bug 1560039] Re: "Unlock SIM" untranslated in indicator network

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

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

Title:
  "Unlock SIM" untranslated in indicator network

Status in Canonical System Image:
  Fix Released
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Insert a SIM card.
  - Switch the phone to Spanish.
  - Reboot the phone.
  - Open indicator network.

  Expected result.
  - "Unlock SIM" button must appear in Spanish.

  Actual result.
  - "Unlock SIM" button displays the message in English.

  current build number: 286
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  The string appears in this file: /usr/lib/arm-linux-
  gnueabihf/qt5/qml/Ubuntu/Settings/Menus/ModemInfoItem.qml part of
  package qtdeclarative5-ubuntu-settings-components

  By the way, the string was also part of an old version of unity8.mo,
  but no longer ships it.

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

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

[Touch-packages] [Bug 1557717] Re: indicator-session should emit Shutdown not Reboot for unity8

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

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

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

Title:
  indicator-session should emit Shutdown not Reboot for unity8

Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In indicator-session, the following code exists:

case PROMPT_WITH_UNITY:
  /* NB: TYPE_REBOOT instead of TYPE_SHUTDOWN because
 the latter adds lock & logout options in Unity... */
  show_unity_end_session_dialog (self, END_SESSION_TYPE_REBOOT);

  Can we get that fixed?  unity8 doesn't currently have such issues, but
  is forced to hack a shutdown dialog when asked to show a reboot dialog
  because of this.

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

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

[Touch-packages] [Bug 1637779] Re: ext4 filesystem fails randomly with checksum error

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

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

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

Title:
  ext4 filesystem fails randomly with checksum error

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  package version:
  linux-image-4.8.0-26-generic:
Installed: 4.8.0-26.28
Candidate: 4.8.0-26.28
Version table:
   *** 4.8.0-26.28 500
  500 http://sk.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  fresh installation of Ubunut 16.10, all updates included

  While I am working with system after few minutes root filesystem /dev/sdb5 
switches into readonly mode
  in dmesg is this:

  [  304.921552] EXT4-fs error (device sdb5): ext4_iget:4476: inode #24577: 
comm updatedb.mlocat: checksum invalid
  [  304.925565] Aborting journal on device sdb5-8.
  [  304.926507] EXT4-fs (sdb5): Remounting filesystem read-only
  [  304.927416] EXT4-fs error (device sdb5): ext4_journal_check_start:56: 
Detected aborted journal
  [  304.943408] EXT4-fs error (device sda1): ext4_iget:4476: inode #12: comm 
updatedb.mlocat: checksum invalid

  when it happens I must do fsck f /dev/sdb1 once, second time it says
  everything is fine. after reboot when I start dto do something it soon
  happens again

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseeded by systemd

2016-12-12 Thread Dimitri John Ledkov

upstart-watchdog should be removed, as this functionality is not needed
going forward. There are extensive "watchdog" facilities provided built-
in into systemd. System units can specify OnFailure mode in systemd to
trigger a reboot. Session units should not cause device reboots.

** Also affects: upstart-watchdog (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: upstart-watchdog (Ubuntu)
   Status: New => Triaged

** Changed in: upstart-watchdog (Ubuntu)
   Importance: Undecided => High

** Changed in: upstart-watchdog (Ubuntu)
Milestone: None => ubuntu-17.03

** Changed in: upstart-watchdog (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  RM Upstart, obsolete, superseeded by systemd

Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

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

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

[Touch-packages] [Bug 1581066] Re: [desktop] Display doesn't dim or turn off on inactivity

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

** No longer affects: powerd (Ubuntu)

** This bug has been marked a duplicate of bug 1595947
   brightness not changing from either  u-s-s or hardkey on unity8-desktop

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

Title:
  [desktop] Display doesn't dim or turn off on inactivity

Status in repowerd package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When leaving my laptop idle, the screen stays at a constant brightness
  forever. I have System Settings configured to "Lock when idle" after 2
  minutes, but that doesn't happen. Adjusting the screen brightness
  manually doesn't do anything.

  Expectation:
  Screen dims after a short period of time, and turns off (and locks) after the 
configured 2 minutes of inactivity.

  Actual:
  Screen stays on and at the same brightness indefinitely.

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel

I still do see it from time to time, mostly when there is a connection
being established.

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

Title:
  [unity8][desktop] wrong network indicator icon  - cogwheel

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  clean 17.04 install on a desktop PC (NOT laptop, only wired connection
  does not have a wireless network card)

  the network indicator, top bar/panel is wrong. it is showing the
  cogwheel. it is like this since i can remember (15.04 + on desktop)

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

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

[Touch-packages] [Bug 1583802] Re: Keyboard layout is not respected in some places

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

** This bug has been marked a duplicate of bug 1626435
   Keyboard layout not applied on the shell

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

Title:
  Keyboard layout is not respected in some places

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  I'm trying Unity8 on my desktop (and reporting bugs from there,
  cool!), I've followed Michael Hall's how to, so I have the same PPAs
  on my system.

  The keyboard layout is not the same everywhere in the OS. I switched
  to French and it works in most places, but in some others, an English
  keyboard persists. These other places include the greeter and the
  Online Accounts (the rest of the System Settings app seems fine). I'm
  not sure where else but I'll keep searching.

  I have to say, it has its advantages, since alt-gr does not work and I
  have to copy/paste things like "@"!

  Thanks for your great work, it's really exciting to see the progress!

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

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

[Touch-packages] [Bug 1422011] Re: CA.pl does not use CA_default dir in openssl.cnf correctly

2016-12-12 Thread Ian Gibbs

Here's the workaround I use for this.

 * Set everything apart from dir in openssl.conf
 * Create the CA
 * Rename the folder
 * Set dir to what you named the folder.

All subsequent operations like generating keys, signing certs etc. work
fine. It's just the initial CA generation that doesn't.

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

Title:
  CA.pl does not use CA_default dir in openssl.cnf correctly

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I changed the CA directory to a different path in openssl.cnf:

  [ CA_default ]

  dir = ./something_different

  CA.pl -newca will not work succeed.

  jan@x61s:~$ /usr/lib/ssl/misc/CA.pl -newca
  CA certificate filename (or enter to create)

  Making CA certificate ...
  Generating a 2048 bit RSA private key
  ...+++
  +++
  writing new private key to './demoCA/private/cakey.pem'

  The key gets written to ./demoCA instead of ./something_different.
  CA.pl ignores setting in openssl.cnf until it changes its mind later
  in the process:

  [...]
  Using configuration from /usr/lib/ssl/openssl.cnf
  Enter pass phrase for ./demoCA/private/cakey.pem:
  I am unable to access the ./something_different/newcerts directory
  ./something_different/newcerts: No such file or directory
  jan@x61s:~$

  jan@x61s:~$ lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04
  jan@x61s:~$ apt-cache policy openssl
  openssl:
Installiert:   1.0.1f-1ubuntu2.8
Installationskandidat: 1.0.1f-1ubuntu2.8
Versionstabelle:
   *** 1.0.1f-1ubuntu2.8 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.1f-1ubuntu2 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1589239] Re: Switching from staged to desktop mode should not be so disruptive for legacy apps

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

** This bug has been marked a duplicate of bug 1600290
   Should not kill Xapps when leaving desktop mode

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

Title:
  Switching from staged to desktop mode should not be so disruptive for
  legacy apps

Status in Libertine:
  Invalid
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Currently on the tablet, when one of the legacy apps (eg Firefox or
  Libreoffice) is launched in desktop mode, switching to staged mode
  shows a message prompt in which you can only close the app (the other
  option doesn't have a button and the string is too long, at least in
  French).

  This message is extremely disruptive, you can only turn off your app
  or toggle the desktop mode back on. Running legacy apps in staged mode
  may be discouraged, but in that case, why not show this message when
  you launch an app in staged mode? At the very least, there should be
  an option to say "OK, I know what I'm doing and I really want to run
  Libreoffice in staged mode".

  Thanks!

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

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

[Touch-packages] [Bug 1640214] Re: [unity8][desktop] wrong network indicator icon - cogwheel