date:20161208

Michael, the command fails because /run/user/0/dbus-session doesn't exist.
I also looks like I have a different version installed. I see 264 and 277 
(besides common) in /root/snap/unity8-session.

I adjusted your command to not set DBUS_SESSION_ADDRESS and explicitly
set LD_LIBRARY_PATH (without using snappyenv):

1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64
HOME=/root/snap/unity8-session/277
LD_LIBRARY_PATH=/snap/unity8-session/current/usr/lib/x86_64-linux-gnu
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-
scopes/scoperunner "" /snap/unity8-session/current/usr/lib/x86_64-linux-
gnu/unity-scopes/clickapps/clickscope.ini

This yields:

# U1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common 
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64 
HOME=/root/snap/unity8-session/277 
LD_LIBRARY_PATH=/snap/unity8-session/current/usr/lib/x86_64-linux-gnu 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner 
"" 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini
 QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlDatabase: an instance of QCoreApplication is required for loading driver 
plugins
Failed to open departments db: Cannot open departments database
[2016-12-09 05:56:44.991] ERROR: clickscope: unity::scopes::ConfigException: 
Cannot instantiate run time for clickscope, config file: :
unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope clickscope:
unity::scopes::ConfigException: No endpoint directories specified, and 
XDG_RUNTIME_DIR environment variable not set
scoperunner: unity::scopes::ConfigException: Cannot instantiate run time for 
clickscope, config file: :
unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope clickscope:
unity::scopes::ConfigException: No endpoint directories specified, and 
XDG_RUNTIME_DIR environment variable not set

Running this with snappyenv, I get:

# U1_DEBUG=1 SNAP_USER_COMMON=/root/snap/unity8-session/common 
SNAP_USER_DATA=/root/snap/unity8-session/277 SNAP_ARCH=amd64 
HOME=/root/snap/unity8-session/277 /snap/unity8-session/current/snappyenv 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner 
"" 
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini
 ERROR: ld.so: object '/lib/libsnap-preload-shim.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
mkdir: cannot create directory ‘/lightdm-data’: Read-only file system
/snap/unity8-session/current/snappyenv: 113: exec: /bin/desktop-launch: not 
found

-- 
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 1648699] Re: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-08 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in procps package in Ubuntu:
  New

Bug description:
  The system works otherwise well.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec  8 22:53:09 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-27 (11 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Also affects: unity-scopes-api (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-api (Ubuntu)
   Status: In Progress => Invalid

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => In Progress

-- 
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 1648699] [NEW] package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-12-08 Thread Pavel Hrubeš

Public bug reported:

The system works otherwise well.

ProblemType: Package
DistroRelease: elementary 0.4
Package: procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
Date: Thu Dec  8 22:53:09 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-27 (11 days ago)
InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package loki third-party-packages

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

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

Status in procps package in Ubuntu:
  New

Bug description:
  The system works otherwise well.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec  8 22:53:09 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-27 (11 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

> "BFB" is "Big Flavorful Button" ;)

Ah, as in "BFG-9000" :-)

> So, from your screenshot it looks like you are hitting case number 2 from my 
> previous post. Is
> there a crash report in /var/crash/ for the scoperunner?

/var/crash doesn't exist on a snappy machine. I have no idea where core
dumps end up. It looks like core dumps are disabled. I can't find any
cores anywhere.

> If not, does running "ubuntu-app-launch-appids" on this system show
any snap results?

ubuntu-app-launch doesn't exist either.

> Can you attach the unity8-dash.log and scope-registry.log files? Normally 
> they are in
> ~/.cache/upstart/ but not sure where exactly that equates to for the unity8 
> snap on core.

I'm seeing an unhandled exception from the click scope.

Registry log: pastebin.ubuntu.com/23602020

I suspect that the exception isn't coming from one of the threads that
we hand to the scope. (We very carefully handle all exceptions that a
scope might throw.) It seems more likely that the exception comes from a
thread that wasn't created by the scopes run time.

The trail of exceptions from shutdown() is unsurprising because the
scopes runtime realises that something isn't right and just logs the
error.

unity8-dash log: pastebin.ubuntu.com/23602037

There is a line with "results invalidated". Not sure whether that is
significant.

Note that no network is present inside the core 16 VM. I don't know how
to get that working, and I don't know whether that relates to the crash.
I set up the VM following the instructions Kevin posted:

https://docs.google.com/document/d/1o-
jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc/edit?pli=1#heading=h.q06bivmaid8f

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-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 405294] Re: a2dp skips terribly

2016-12-08 Thread Filip

One thing which I have notices just now, when I start downloading
something it get's much worse

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 405294] Re: a2dp skips terribly

2016-12-08 Thread Filip

Can confirm for ubuntu 16.04.1, have same issue as Dan, tried everything
from previous posts but nothing works..

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1625805] Re: dragonboard: history daemon dereferences a rogue pointer

2016-12-08 Thread Renato Araujo Oliveira Filho

** Branch linked: lp:~renatofilho/history-service/snap-path

** Changed in: history-service (Ubuntu)
   Status: New => Fix Committed

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

Title:
  dragonboard: history daemon dereferences a rogue pointer

Status in Canonical System Image:
  Confirmed
Status in Snappy:
  New
Status in history-service package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  we are running the unity8 session snap on amd64 without any problems.
  to setup and reproduce the problem follow the "on Dragonboard" section of 
  
https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc

  You can also find the panic signature at line 3276 of the attached
  syslog.

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

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

[Touch-packages] [Bug 1646015] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

2016-12-08 Thread Seth Arnold

Niraj, it looks like work was done to make running auditd in containers
actually make sense: https://bugzilla.redhat.com/show_bug.cgi?id=893751

What parts of the work are we missing, if any?

Thanks

** Bug watch added: Red Hat Bugzilla #893751
   https://bugzilla.redhat.com/show_bug.cgi?id=893751

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

Title:
  update-rc.d: warning: start and stop actions are no longer supported;
  falling back to defaults

Status in audit package in Ubuntu:
  New

Bug description:
  HI

  I have the docker image for ubuntu 16.04 and 16.10 .  In both I  was
  tried to install the auditd but getting the following  error.

  apt-get install auditdReading package lists... Done
  Building dependency tree... Done
  The following additional packages will be installed:
  libauparse0
  Suggested packages:
  audispd-plugins
  The following NEW packages will be installed:
  auditd libauparse0
  0 upgraded, 2 newly installed, 0 to remove and 21 not upgraded.
  Need to get 224 kB of archives.
  After this operation, 753 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu yakkety/main amd64 libauparse0 amd64 
1:2.6.6-1ubuntu1 [38.6 kB]
  Get:2 http://archive.ubuntu.com/ubuntu yakkety/main amd64 auditd amd64 
1:2.6.6-1ubuntu1 [186 kB]
  Fetched 224 kB in 0s (409 kB/s)
  debconf: delaying package configuration, since apt-utils is not installed
  Selecting previously unselected package libauparse0:amd64.
  (Reading database ... 6501 files and directories currently installed.)
  Preparing to unpack .../0-libauparse0_1%3a2.6.6-1ubuntu1_amd64.deb ...
  Unpacking libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
  Selecting previously unselected package auditd.
  Preparing to unpack .../1-auditd_1%3a2.6.6-1ubuntu1_amd64.deb ...
  Unpacking auditd (1:2.6.6-1ubuntu1) ...
  Setting up libauparse0:amd64 (1:2.6.6-1ubuntu1) ...
  Setting up auditd (1:2.6.6-1ubuntu1) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Processing triggers for libc-bin (2.24-0ubuntu1) ...

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

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

[Touch-packages] [Bug 1644859] Re: Update Error Brokencount: I cannot load any further updates for about 4 days now...

2016-12-08 Thread Tom G.

** Description changed:

  This package system is broken:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  
- "when I run apt-get install -f" I get the following error: 
+ "when I run apt-get install -f" I get the following error:
  apt-get install -f
  E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
  E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 50.0+build2-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  tom1796 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tom1796 F pulseaudio
  BuildID: 20161114144739
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Nov 25 09:49:44 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-08-11 (836 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
-  default via 192.168.1.1 dev eth0  proto static  metric 100 
-  default via 192.168.200.1 dev wlan0  proto static  metric 600 
-  169.254.0.0/16 dev wlan0  scope link  metric 1000 
-  192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.218  metric 
100 
-  192.168.200.0/24 dev wlan0  proto kernel  scope link  src 192.168.200.6  
metric 600
+  default via 192.168.1.1 dev eth0  proto static  metric 100
+  default via 192.168.200.1 dev wlan0  proto static  metric 600
+  169.254.0.0/16 dev wlan0  scope link  metric 1000
+  192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.218  metric 
100
+  192.168.200.0/24 dev wlan0  proto kernel  scope link  src 192.168.200.6  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-70901242-37de-43fb-9bed-f897e2161106
  Plugins:
-  iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
-  Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
+  iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
+  Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=50.0/20161114144739 (In use)
  RelatedPackageVersions: rhythmbox-mozilla 3.3-1ubuntu7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
-  bp-70901242-37de-43fb-9bed-f897e2161106
-  bp-921bd37f-d835-43f3-b547-842c12151115
-  bp-638f2494-0693-45e3-a276-d36032150714
+  bp-70901242-37de-43fb-9bed-f897e2161106
+  bp-921bd37f-d835-43f3-b547-842c12151115
+  bp-638f2494-0693-45e3-a276-d36032150714
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (205 days ago)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

Title:
  Update Error Brokencount: I cannot load any further updates for about
  4 days now...

Status in apt package in Ubuntu:
  Invalid

Bug description:
  This package system is broken:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f

  "when I run apt-get install -f" I get the following error:
  apt-get install -f
  E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
  E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package:

[Touch-packages] [Bug 1644859] Re: Update Error Brokencount: I cannot load any further updates for about 4 days now...

2016-12-08 Thread Tom G.

Thank you, I was not typing sudo. You fixed my problem Tyler, thank you!
Tom

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

Title:
  Update Error Brokencount: I cannot load any further updates for about
  4 days now...

Status in apt package in Ubuntu:
  Invalid

Bug description:
  This package system is broken:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f

  "when I run apt-get install -f" I get the following error: 
  apt-get install -f
  E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
  E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 50.0+build2-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1796 F pulseaudio
  BuildID: 20161114144739
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Nov 25 09:49:44 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-08-11 (836 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 100 
   default via 192.168.200.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.218  metric 
100 
   192.168.200.0/24 dev wlan0  proto kernel  scope link  src 192.168.200.6  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-70901242-37de-43fb-9bed-f897e2161106
  Plugins:
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=50.0/20161114144739 (In use)
  RelatedPackageVersions: rhythmbox-mozilla 3.3-1ubuntu7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-70901242-37de-43fb-9bed-f897e2161106
   bp-921bd37f-d835-43f3-b547-842c12151115
   bp-638f2494-0693-45e3-a276-d36032150714
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (205 days ago)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1648477] Re: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 1

2016-12-08 Thread Seth Arnold

Incidentally your kernel is nearly five months old; I strongly recommend
installing updates as they address both security and reliability issues.

Thanks

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

Title:
  package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade:
  podproces instalovaný post-installation skript vrátil chybový status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  failed when trying to install driver for BCM4313 network card
  package bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu8
  Ubuntu version:16.04.1 LTS
  kernel version:4.40-31-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   dkms: Install
   bcmwl-kernel-source: Install
   dkms: Configure
   bcmwl-kernel-source: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Dec  8 13:39:56 2016
  ErrorMessage: podproces instalovaný post-installation skript vrátil chybový 
status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
podproces instalovaný post-installation skript vrátil chybový status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648477] Re: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 1

2016-12-08 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade:
  podproces instalovaný post-installation skript vrátil chybový status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  failed when trying to install driver for BCM4313 network card
  package bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu8
  Ubuntu version:16.04.1 LTS
  kernel version:4.40-31-generic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   dkms: Install
   bcmwl-kernel-source: Install
   dkms: Configure
   bcmwl-kernel-source: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Dec  8 13:39:56 2016
  ErrorMessage: podproces instalovaný post-installation skript vrátil chybový 
status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
podproces instalovaný post-installation skript vrátil chybový status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 655304] Re: zh manpages in passwd package, between all chinese chars, there are spaces

2016-12-08 Thread Oskar Wallgren

Right. The .png in the original report and mine differs. This bug is
fixed and what's left now is the issue in #312454 .

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

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

Title:
  zh manpages in passwd package, between all chinese chars, there are
  spaces

Status in Ubuntu Translations:
  Triaged
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow package in Debian:
  Fix Released

Bug description:
  It is so ugly and hard to read.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: passwd 1:4.1.4.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Oct  6 02:43:46 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100812)
  ProcEnviron:
   LANGUAGE=zh_CN:zh_TW:zh:en
   PATH=(custom, user)
   LANG=zh_CN.utf8
   SHELL=/usr/bin/zsh
  SourcePackage: shadow

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

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

[Touch-packages] [Bug 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

2016-12-08 Thread Daniel van Vugt

Does Mir have the required client API functions for those yet?

** Package changed: ubuntu => gtk+3.0 (Ubuntu)

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

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

Title:
  Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

Status in GTK+:
  New
Status in Mir:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK apps on Mir: Input focus is unreliable and sporadic. Background
  windows ignore input and/or focus switches apparently randomly.

  Example:

  $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

  Show the "Scores" - you can switch focus between this and the main
  window with Alt+` but doesn't respond to input.

  Other dialogs (e.g. "About") work fine. From the Mir side there's no
  obvious difference between these windows.

  In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
  events being correctly received on the client side. That shows most of
  the Mir stack is working correctly.

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

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

[Touch-packages] [Bug 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]

2016-12-08 Thread Daniel van Vugt

Even if we don't have the kernel support in place yet I think Mir could
still do better.

What the user sees is:
Unknown command line options: --vt 1

What that means is:
A non-mesa-kms graphics driver was chosen (or none at all? can't tell). And 
that's not even a bug at all if some working driver has been found. It's 
presently a bug in the snap to pass a driver-specific option (--vt), but I 
would also argue that should not be true and the snap should be allowed to 
(along with LightDM). VT support should be generally available and not buried 
in just one graphics driver. Then the above error will never happen again 
(we've been hitting it for years now).

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

Title:
  Running Mir-Server snap, gives error! [Unknown command line options:
  --vt 1]

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  I don't know, if this is right place!
  Trying to run mir-server gives error:

  Dec  8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Main process exited, code=exited, status=1/FAILURE
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Unit entered failed state.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Failed with result 'exit-code'.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Service hold-off time over, scheduling restart.

  Running on Raspberry pi 2, Ubuntu snappy core!

  runned lsb_release -rd

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

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

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

[Touch-packages] [Bug 655304] Re: zh manpages in passwd package, between all chinese chars, there are spaces

2016-12-08 Thread Oskar Wallgren

With latest upstream version of command most
PAGER=./src/objs/most LANGUAGE=ja_JP LC_ALL=ja_JP.UTF-8 man shadow

** Attachment added: "japanese.png"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/655304/+attachment/4789324/+files/japanese.png

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

Title:
  zh manpages in passwd package, between all chinese chars, there are
  spaces

Status in Ubuntu Translations:
  Triaged
Status in shadow package in Ubuntu:
  New
Status in shadow package in Debian:
  Fix Released

Bug description:
  It is so ugly and hard to read.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: passwd 1:4.1.4.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Oct  6 02:43:46 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100812)
  ProcEnviron:
   LANGUAGE=zh_CN:zh_TW:zh:en
   PATH=(custom, user)
   LANG=zh_CN.utf8
   SHELL=/usr/bin/zsh
  SourcePackage: shadow

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

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

[Touch-packages] [Bug 893024] Re: Support 802.1x auth requirement detection and fallback

2016-12-08 Thread dwmw2

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


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

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

Title:
  Support 802.1x auth requirement detection and fallback

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  NetworkManager asks for 802.1x user name and password when there is no
  802.1x support on switch port.

  Background:

  We use 802.1x wired authentication on our campus network.
  NetworkManager does not fall back nicely when connecting to a non-
  authenticated switch.

  What happens:

  NetworkManager asks for user name and password when "Use 802.1x
  security" is selected in the connection editor and the computer is
  connected to an unauthenticated port.

  What should happen:

  Network manager should notice that the port is not access-controlled
  and do one of the following: (1) ask for connecting unauthenticated or
  (2) connect unauthenticated without asking.

  There should be a setting for selecting #1 or #2.

  Now the user is asked about information which has no effect on
  completing the connection.

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

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

[Touch-packages] [Bug 1445543] [NEW] Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze

You have been subscribed to a public bug:

GTK apps on Mir: Input focus is unreliable and sporadic. Background
windows ignore input and/or focus switches apparently randomly.

Example:

$ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg

Show the "Scores" - you can switch focus between this and the main
window with Alt+` but doesn't respond to input.

Other dialogs (e.g. "About") work fine. From the Mir side there's no
obvious difference between these windows.

In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input
events being correctly received on the client side. That shows most of
the Mir stack is working correctly.

** Affects: gtk
 Importance: Undecided
 Assignee: Andreas Pokorny (andreas-pokorny)
 Status: New

** Affects: mir
 Importance: High
 Status: Invalid

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Assignee: Andreas Pokorny (andreas-pokorny)
 Status: Confirmed


** Tags: gtk-mir mir snappyrdp
-- 
Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
https://bugs.launchpad.net/bugs/1445543
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

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

2016-12-08 Thread Josh Arenson

Seems to be caused by the last for loop in
OverviewResultsModel::setResults, which is being executed 131071
times Working on a patch

-- 
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 1647696] Re: the app switcher and the app drawer are a bit laggy on MX4

2016-12-08 Thread dinamic

** Summary changed:

- the app switcher and the app drawer are very laggy on MX4
+ the app switcher and the app drawer are a bit laggy on MX4

** Description changed:

- the app switcher and the app drawer are very laggy on MX4
- i am not sure how to view the actual FPS but they feel very laggy
+ the app switcher and the app drawer are a bit laggy on MX4
+ i am not sure how to view the actual FPS but they feel a bit laggy
  
  mx4/rc-proposed

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

Title:
  the app switcher and the app drawer are a bit laggy on MX4

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  the app switcher and the app drawer are a bit laggy on MX4
  i am not sure how to view the actual FPS but they feel a bit laggy

  mx4/rc-proposed

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

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

[Touch-packages] [Bug 1556387] Re: Unity8 Login Hangs

2016-12-08 Thread lol24h

On Ubuntu 16.10 and native system (thinkpad x230t) Intel Ivy-bridge
behaviour is the same

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

Title:
  Unity8 Login Hangs

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Attempted to Install and Login using Unity8 on top of Ubuntu 16.04 Desktop 
Build.
  Am amble to Signon to Unity Desktop distributed by build however when I 
attempt to singon to Unity8, the password accepts but the Signon Screen does 
not go away. The only thing I can do is either shutdown the machine or Restart.

  The following data is from my test image:
  gene@U1604DSKDLYX:~$ uname -a
  Linux U1604DSKDLYX 4.4.4-040404-generic #201603031931 SMP Fri Mar 4 00:34:16 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  gene@U1604DSKDLYX:~$ sudo apt-get install unity8-desktop-session-mir
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  unity8-desktop-session-mir is already the newest version 
(1.0.12+15.10.20150609-0ubuntu1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

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

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

[Touch-packages] [Bug 1310186] Re: mediascanner prevents unmounting usb device

There doesn't appear to be a way to be notified of unmount attempts at
the moment. There is an fschange modification about ten years ago
(http://stefan.buettcher.org/cs/fschange/), but that never made it into
the kernel.

It looks like it's impossible for mediascanner to automatically back off
when an unmount attempt is made.

You can kill the mediascanner process and then unmount. (Not of much
help to naive user, I admit.)

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

Title:
  mediascanner prevents unmounting usb device

Status in mediascanner2 package in Ubuntu:
  Triaged

Bug description:
  Trying to unmount a block device I just mounted, I get the following
  error (sorry for not resetting the locale. It says "Device is busy"):

  :~$ sudo umount /media/tkluck/tjk-backup 
  umount2: Apparaat of hulpbron is bezig
  umount: /media/tkluck/tjk-backup: apparaat is bezig
  (Welke processen het apparaat gebruiken kan mogelijk
   gevonden worden met behulp van lsof(8) of fuser(1).)
  umount2: Apparaat of hulpbron is bezig

  I get the same error in a dialog window when trying to unmount from
  the file manager.

  Using lsof shows that the media-scanner daemon is the culprit:

  tkluck@ultrabook-tjk:~$ lsof /media/tkluck/tjk-backup 
  COMMANDPID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  mediascan 2898 tkluck   16r   DIR  252,3   2498562 
/media/tkluck/tjk-backup
  mediascan 2898 tkluck   17r   DIR  252,3 4096 50855937 
  mediascan 2898 tkluck   18r   DIR  252,3 4096 39080372 
  mediascan 2898 tkluck   19r   DIR  252,312288 39080513 
  mediascan 2898 tkluck   20r   DIR  252,320480 39080525 
  mediascan 2898 tkluck   21r   DIR  252,3 4096 46792990 
  mediascan 2898 tkluck   22r   DIR  252,3 4096 46792991 
  mediascan 2898 tkluck   23r   DIR  252,316384 46793749 
  mediascan 2898 tkluck   24r   DIR  252,3 4096 47317994 
  mediascan 2898 tkluck   25r   DIR  252,3 4096 47317997 
  mediascan 2898 tkluck   26r   DIR  252,3 4096 47317999 

  Sending it

  sudo kill -9 2898

  solved this for me.

  This is on Ubuntu GNOME 14.04. I uninstalled the mediascanner2.0 to
  solve this "once and for all" (which has no other impact since I do
  not use Unity).

  My guess is that the scan usually finishes quickly after mounting. But
  because this particular drive contains a big filetree, it doesn't,
  resulting in the issue.

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

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

[Touch-packages] [Bug 1648167] Re: Touch window controls dismiss the touch overlay instead

2016-12-08 Thread Lukáš Tinkl

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

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

Title:
  Touch window controls dismiss the touch overlay instead

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:
  * three-finger-tap a window to get the window controls
  * tap on one of the window control buttons (close/min/max)

  Expected:
  * the action is taken

  Current:
  * touch controls are dismissed instead

  No autotest for this, looks like.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20161129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  7 18:17:15 2016
  InstallationDate: Installed on 2016-05-06 (214 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (15 days ago)

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

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

[Touch-packages] [Bug 1648450] Re: Mediascanner keeps volume busy when removing and gives errors

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

** This bug has been marked a duplicate of bug 1310186
   mediascanner prevents unmounting usb device

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

Title:
  Mediascanner keeps volume busy when removing and gives errors

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  This annoying thing happens when I connect a USB drive with a lot of
  media content and then shortly try to "safely remove" the device.

  Step to reproduce:
  1) Connect a USB drive with a lot of media content (not sure if a lot of 
media is really needed, but I'm not going to delete stuff from my disk to test)
  2) From Nautilus right-click the device icon and choose "safely remove the 
device"
  3) Observe that a dialog opens saying that "Volume is busy"
  4) Click "Eject Anyway"
  5) Observe an error dialog saying something like "Unable to stop "WDC 
WD10JPVX-22JC3T0"

  So did it fail or what? Is this good or bad? Will I corrupt my data if
  I just disconnect it after possibly copying some files? This is not
  good usability, at least.

  What should happen:
  - The device should get disconnected without errors. If not right after 
safely removing, but after having clicked "Eject Anyway".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mediascanner2.0 0.111+16.04.20160317-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  8 14:43:21 2016
  InstallationDate: Installed on 2016-09-13 (86 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Changed in: lightdm/1.2
   Importance: Undecided => High

** Changed in: lightdm/1.2
   Status: New => Fix Committed

** Changed in: lightdm/1.2
Milestone: None => 1.2.12

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

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 1648637] Re: handle interruped read and write calls

** Branch linked: lp:lightdm/1.2

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

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 1648637] Re: handle interruped read and write calls

** Changed in: lightdm/1.10
   Importance: Undecided => High

** Changed in: lightdm/1.10
   Status: New => Fix Committed

** Changed in: lightdm/1.10
Milestone: None => 1.10.7

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

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 1648637] Re: handle interruped read and write calls

** Branch linked: lp:lightdm/1.10

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

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 1648644] [NEW] XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and keyboard not responsive, also no audio

2016-12-08 Thread Robert Sloboda

Public bug reported:

16.04.1 image has no native keyboard or mouse interaction. I'm writing
this bug report on the affected platform, a new Samsung Chromebook 3,
XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
input, I needed to use an external USB keyboard-mouse.

Let me know if this platform has been tested. I'm assuming this newer
Samsung platform is not yet tested with Ubuntu and that there are some
issues to work through. This is a fantastic platform for Ubuntu use -
R, Edu, Software Development, General Linux use. I hope we can find a
fix to the problem.

Let me know what I can do to help. I've seen this issue since previous
Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
someone has already taken the lead on this issue?

Thanks again, let me know what I can do to help test any proposed fixes.
I have plenty of MAC, PC, and Chromebook platforms available for
testing, but to this point haven't before volunteered for Ubuntu
testing-debugging :)

As a side note, the audio also isn't working which seems to be a common
problem with Ubuntu on several Chromebook platforms, including Acer and
Samsung.

** Affects: kernel-package (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: audio chromebook keyboard mouse samsung xe500c13-k02us

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

Title:
  XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and
  keyboard not responsive, also no audio

Status in kernel-package package in Ubuntu:
  New

Bug description:
  16.04.1 image has no native keyboard or mouse interaction. I'm writing
  this bug report on the affected platform, a new Samsung Chromebook 3,
  XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
  input, I needed to use an external USB keyboard-mouse.

  Let me know if this platform has been tested. I'm assuming this newer
  Samsung platform is not yet tested with Ubuntu and that there are some
  issues to work through. This is a fantastic platform for Ubuntu use -
  R, Edu, Software Development, General Linux use. I hope we can find
  a fix to the problem.

  Let me know what I can do to help. I've seen this issue since previous
  Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
  someone has already taken the lead on this issue?

  Thanks again, let me know what I can do to help test any proposed
  fixes. I have plenty of MAC, PC, and Chromebook platforms available
  for testing, but to this point haven't before volunteered for Ubuntu
  testing-debugging :)

  As a side note, the audio also isn't working which seems to be a
  common problem with Ubuntu on several Chromebook platforms, including
  Acer and Samsung.

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

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

[Touch-packages] [Bug 1648644] Re: XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and keyboard not responsive, also no audio

2016-12-08 Thread Robert Sloboda

Not sure which package needs updating, or if this is an interaction
between packages. I'll leave that judgment to the experts. Maybe some
additional debugging is needed (special kernel) to log the functionality
and package interactions and help narrow down the problem?  This problem
has been around at least since Ubuntu 14 LTS and previous model Samsung
Chromebooks, according to my web research.

** Package changed: pulseaudio (Ubuntu) => kernel-package (Ubuntu)

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

Title:
  XE500C13-K02US Samsung Chromebook 3 Ubuntu 16.04.1 touchpad and
  keyboard not responsive, also no audio

Status in kernel-package package in Ubuntu:
  New

Bug description:
  16.04.1 image has no native keyboard or mouse interaction. I'm writing
  this bug report on the affected platform, a new Samsung Chromebook 3,
  XE500C13-K02US. In order to get Ubuntu to recognize keyboard and mouse
  input, I needed to use an external USB keyboard-mouse.

  Let me know if this platform has been tested. I'm assuming this newer
  Samsung platform is not yet tested with Ubuntu and that there are some
  issues to work through. This is a fantastic platform for Ubuntu use -
  R, Edu, Software Development, General Linux use. I hope we can find
  a fix to the problem.

  Let me know what I can do to help. I've seen this issue since previous
  Samsung Chromebook models and since Ubuntu 14 LTS, so I'm assuming
  someone has already taken the lead on this issue?

  Thanks again, let me know what I can do to help test any proposed
  fixes. I have plenty of MAC, PC, and Chromebook platforms available
  for testing, but to this point haven't before volunteered for Ubuntu
  testing-debugging :)

  As a side note, the audio also isn't working which seems to be a
  common problem with Ubuntu on several Chromebook platforms, including
  Acer and Samsung.

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

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

** Changed in: lightdm/1.18
   Importance: Undecided => High

** Changed in: lightdm/1.18
   Status: New => Fix Committed

** Changed in: lightdm/1.18
Milestone: None => 1.18.4

-- 
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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
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:
  New

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 1648301] Re: phone app doesn't support landscape mode rendering itself unusable in windowed mode

2016-12-08 Thread Bill Filler

I agree it should be usable in windowed mode, and reflow to fit in the
available size

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

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided => High

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  phone app doesn't support landscape mode rendering itself unusable in
  windowed mode

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  On a phone running Ubuntu Touch, I would think, phone app is the
  absolute essential. It should even more so be ready for every user
  scenario. But it isn't. It does not support landscape mode.

  When in staged mode, it just simply ignores the landscape mode and
  forcefully displays itself vertically. Well, at least it can be used,
  so fine.

  However, when in windowed mode, you can no longer make use of this. I
  use my Ubuntu Touch phone mostly in landscape windowed mode. I cannot
  make phone calls, because I can't even see the "call" button (attached
  screen from my Meizu MX4 Ubuntu Edition).

  Now, regardless whether or not it is anticipated by Canonical that
  users will like me use Ubuntu Touch on the phone in landscape windowed
  mode, it just should be possible! And it's not a big deal either, make
  the UI a bit more responsive.

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

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

[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen

2016-12-08 Thread Michal Predotka

Possible design with added transparency for 'cool' factor ;)

** Attachment added: "OSK.svg.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+attachment/4789311/+files/OSK.svg.png

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

Title:
  5 useless buttons on the lock-screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  bq e4.5 OTA-14

  In the case I use '4-digit passcode' for 'Lock security', the new
  keyboard visible on the lock screen has 5 buttons out of 18 (counting
  'Cancel' and 'Emergency') which do not have any use. I marked them on
  the attached screenshot.

  The same keyboard appears when I create or change the 4-digit passcode
  in System Settings.

  IMO it'd be better to remove those useless buttons, and possibly
  rearrange the useful ones. That could make it look better and provide
  better/bigger touch target.

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

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

** Branch linked: lp:lightdm/1.18

-- 
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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
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:
  New

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 1648637] Re: handle interruped read and write calls

** Branch linked: lp:lightdm/1.20

-- 
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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
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:
  New

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 1648637] Re: handle interruped read and write calls

** Changed in: lightdm/1.20
   Importance: Undecided => High

-- 
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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
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:
  New

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 1648637] Re: handle interruped read and write calls

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

** Changed in: lightdm
Milestone: None => 1.21.2

** Changed in: lightdm/1.20
   Status: New => Fix Committed

** Changed in: lightdm/1.20
Milestone: None => 1.20.1

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  New
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  New
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:
  New

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 1648253] Re: No drop shadow when sliding away application

2016-12-08 Thread Pat McGowan

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

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

Title:
  No drop shadow when sliding away application

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When sliding an application away from left to right there was a drop
  shadow but there isn't any more.

  Slight regression from OTA13.

  Running Pro5 on OTA14 stable channel.

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

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

[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen

2016-12-08 Thread Pat McGowan

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  5 useless buttons on the lock-screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  bq e4.5 OTA-14

  In the case I use '4-digit passcode' for 'Lock security', the new
  keyboard visible on the lock screen has 5 buttons out of 18 (counting
  'Cancel' and 'Emergency') which do not have any use. I marked them on
  the attached screenshot.

  The same keyboard appears when I create or change the 4-digit passcode
  in System Settings.

  IMO it'd be better to remove those useless buttons, and possibly
  rearrange the useful ones. That could make it look better and provide
  better/bigger touch target.

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

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

[Touch-packages] [Bug 1648251] Re: Black area to left of application sliding in when launched

2016-12-08 Thread Pat McGowan

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

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

Title:
  Black area to left of application sliding in when launched

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When an application is selected in the apps scope and begins to slide
  in from the right to the left of the screen there is a black area that
  can be quickly seen to the left of where the application is sliding
  into.

  A small visual flaw but it is something the user would see every time
  they open an application.

  I cannot get a screenshot of this.

  Running Pro 5 OTA14 on stable

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

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

2016-12-08 Thread Alberts Muktupāvels

** Description changed:

  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.

-- 
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 Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
Status in lightdm package in Ubuntu:
  New
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

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 1648637] Re: handle interruped read and write calls

** Changed in: lightdm
   Status: Triaged => Fix Committed

-- 
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 Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
Status in lightdm package in Ubuntu:
  New
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

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 1648637] Re: handle interruped read and write calls

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.20
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.18
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  handle interruped read and write calls

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.2 series:
  New
Status in Light Display Manager 1.20 series:
  New
Status in lightdm package in Ubuntu:
  New
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

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 1648593] Re: Keyboard usualy not showing up in apps after unlocking the screen

2016-12-08 Thread zub

Happens to me too. But if, after unlocking the screen, I tap the chat
area (where the converation is displayed) in Telegram and then tap the
text entry widget the keyboard does pop up. Maybe the OSK needs to see a
change of the focused widget after return from lock screen?

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

Title:
  Keyboard usualy not showing up in apps after unlocking the screen

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  for the last month or even more I am experiencing this weird bug with OSK not 
popping up after putting my phone to "sleep", that is locking the screen and 
then unlocking it. It mostly happens with Telegram to me, as that is one 
particular app that I keep running all the time, but I've experienced this in 
other apps (including my own) as well and therefore expect it not to be related 
to Telegram at all.

  Steps to reproduce:
  1. Open any app (like Telegram) - OSK should pop up and work upon clicking on 
any input
  2. Lock the device (shut the screen down)
  -- The length of the phone being asleep seems to have little influence on the 
actual OSK keyboard behaviour - it seems to be pretty much random --
  3. Unlock the device
  4. Switch to the previously opened app if you are not there already

  Sometimes it is hard for me to reproduce this while other times I seem
  to be bumping into this every time I unlock the screen - so it is not
  something I've seen once or twice in my life but is pretty much
  common.

  To fix this behaviour switching out of the app and back to it again
  usually works, though sometimes restarting the app is the only way to
  get the OSK working.

  I am on rc-proposed, MX4

  Thank you very much for looking into this

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

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

[Touch-packages] [Bug 1648632] [NEW] OTA 14 new phone screen unlock very poor compared to OTA-13

2016-12-08 Thread Dave H

Public bug reported:

Hi, after updating my Meizu MX4 to OTA-14 the screen unlock has changed
to the poor looking desktop/tablet  version. When compared to the
original phone unlock screen (up to OTA-13) this new version looks very
weak, lacking the sophistication of the original version. You would not
see such a screen unlock on an Android or Apple devices. It would be
good to understand why this has been changed, I can only think that you
have settled for the one version, this is a real shame for the phone and
in my opinion is a retrograde step lowering the chances of normal users
adopting the Ubuntu phone.

Can you please consider changing the phone unlock screen back to the
version used before OTA-14.

Your support is appreciated,

Regards

Dave H

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

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

Title:
  OTA 14 new phone screen unlock very poor compared to OTA-13

Status in libusermetrics package in Ubuntu:
  New

Bug description:
  Hi, after updating my Meizu MX4 to OTA-14 the screen unlock has
  changed to the poor looking desktop/tablet  version. When compared to
  the original phone unlock screen (up to OTA-13) this new version looks
  very weak, lacking the sophistication of the original version. You
  would not see such a screen unlock on an Android or Apple devices. It
  would be good to understand why this has been changed, I can only
  think that you have settled for the one version, this is a real shame
  for the phone and in my opinion is a retrograde step lowering the
  chances of normal users adopting the Ubuntu phone.

  Can you please consider changing the phone unlock screen back to the
  version used before OTA-14.

  Your support is appreciated,

  Regards

  Dave H

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

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] opencryptoki breaks p11-kit

2016-12-08 Thread dwmw2

Public bug reported:

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.

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

** Affects: p11-kit (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: p11-kit (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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:
  New
Status in p11-kit package in Ubuntu:
  New

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 1595249] Re: "You have to press and hold the record icon" is truncated in german

2016-12-08 Thread Matthias Seidel

Still valid for OTA-14.

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

Title:
  "You have to press and hold the record icon" is truncated in german

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  "You have to press and hold the record icon" (Du musst das Aufnahmesymbol 
berühren und gedrückt halten) is truncated in german language (even in 
landscape mode).
  So nobody can read what to do with the microphone symbol.

  This happens to me on a bq 4.5 with OTA 11.

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

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

[Touch-packages] [Bug 1633499] Re: [SRU] Update to 9.20 in Trusty

2016-12-08 Thread Amr Ibrahim

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

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

Title:
  [SRU] Update to 9.20 in Trusty

Status in libav package in Ubuntu:
  Fix Released

Bug description:
  https://git.libav.org/?p=libav.git;a=shortlog;h=refs/heads/release/9

  version 9.20:
   - avcodec: bump micro version

  version 9.19:
   - h264: deMpegEncContextize
   - h264: remove silly macros
   - mpegvideo: split ff_draw_horiz_band().
   - error_resilience: add required headers.
   - error_resilience: decouple ER from MpegEncContext
   - h264: remove a pointless if()
   - h264: simplify calls to ff_er_add_slice().
   - tls: Use the right return value for breaking out due to the interrupt 
callback
   - rtmpcrypt: Do the xtea decryption in little endian mode

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

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

[Touch-packages] [Bug 1648620] [NEW] package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2016-12-08 Thread Alexis

Public bug reported:

it is related with smfpd daemon; but i don't know how. 
in the console appears the message:
"
insserv: There is a loop at service plymouth if started
insserv: Starting smfpd depends on plymouth and therefore on system facility 
`$all' which can not be true!
"

i have installed the xerox phaser 3140 driver for linux two weeks ago.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
Date: Thu Dec  8 17:47:59 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2016-09-11 (88 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in procps package in Ubuntu:
  New

Bug description:
  it is related with smfpd daemon; but i don't know how. 
  in the console appears the message:
  "
  insserv: There is a loop at service plymouth if started
  insserv: Starting smfpd depends on plymouth and therefore on system facility 
`$all' which can not be true!
  "

  i have installed the xerox phaser 3140 driver for linux two weeks ago.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Thu Dec  8 17:47:59 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-09-11 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

2016-12-08 Thread Renato Araujo Oliveira Filho

** Branch linked: lp:~renatofilho/unity8-session-snap/fix-1646611

** Also affects: unity8-session-snap
   Importance: Undecided
   Status: New

** Changed in: unity8-session-snap
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in Unity8 Session Snap:
  New
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

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

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

[Touch-packages] [Bug 1648617] Re: package linux-image-4.4.0-47-generic keeps reporting a system problem

2016-12-08 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-47-generic keeps reporting a system problem

Status in apt package in Ubuntu:
  New

Bug description:
  Many times all that is required is to start the system and log in.
  Immediately the report of a system problem shows up. This is a regular
  occurrence. The release is 16.04. The description is "Ubuntu 16.04.1
  LTS".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1757 F pulseaudio
  Date: Wed Dec  7 08:18:48 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=8d4566d4-7212-4261-963c-93d573dbeb91
  InstallationDate: Installed on 2016-11-20 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO F0BF0016US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=bca2cbc9-8ad9-4a9c-a8ef-fa4e75436d48 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: apt
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O1SKT26AUS
  dmi.board.name: SKYBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN 3258041700079
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO1SKT26AUS:bd11/11/2015:svnLENOVO:pnF0BF0016US:pvrideacentreAIO700-22ISH:rvnLENOVO:rnSKYBAY:rvrSDK0J40700WIN3258041700079:cvnLENOVO:ct13:cvrNone:
  dmi.product.name: F0BF0016US
  dmi.product.version: ideacentre AIO 700-22ISH
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1648617] [NEW] package linux-image-4.4.0-47-generic keeps reporting a system problem

2016-12-08 Thread David A Ploen

Public bug reported:

Many times all that is required is to start the system and log in.
Immediately the report of a system problem shows up. This is a regular
occurrence. The release is 16.04. The description is "Ubuntu 16.04.1
LTS".

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  david  1757 F pulseaudio
Date: Wed Dec  7 08:18:48 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
HibernationDevice: RESUME=UUID=8d4566d4-7212-4261-963c-93d573dbeb91
InstallationDate: Installed on 2016-11-20 (18 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO F0BF0016US
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=bca2cbc9-8ad9-4a9c-a8ef-fa4e75436d48 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: apt
Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: O1SKT26AUS
dmi.board.name: SKYBAY
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN 3258041700079
dmi.chassis.type: 13
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrO1SKT26AUS:bd11/11/2015:svnLENOVO:pnF0BF0016US:pvrideacentreAIO700-22ISH:rvnLENOVO:rnSKYBAY:rvrSDK0J40700WIN3258041700079:cvnLENOVO:ct13:cvrNone:
dmi.product.name: F0BF0016US
dmi.product.version: ideacentre AIO 700-22ISH
dmi.sys.vendor: LENOVO

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

Title:
  package linux-image-4.4.0-47-generic keeps reporting a system problem

Status in apt package in Ubuntu:
  New

Bug description:
  Many times all that is required is to start the system and log in.
  Immediately the report of a system problem shows up. This is a regular
  occurrence. The release is 16.04. The description is "Ubuntu 16.04.1
  LTS".

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1757 F pulseaudio
  Date: Wed Dec  7 08:18:48 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=8d4566d4-7212-4261-963c-93d573dbeb91
  InstallationDate: Installed on 2016-11-20 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO F0BF0016US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=bca2cbc9-8ad9-4a9c-a8ef-fa4e75436d48 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: apt
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O1SKT26AUS
  dmi.board.name: SKYBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN 3258041700079
  dmi.chassis.type: 13
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO1SKT26AUS:bd11/11/2015:svnLENOVO:pnF0BF0016US:pvrideacentreAIO700-22ISH:rvnLENOVO:rnSKYBAY:rvrSDK0J40700WIN3258041700079:cvnLENOVO:ct13:cvrNone:
  dmi.product.name: F0BF0016US
  dmi.product.version: ideacentre AIO 700-22ISH
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

2016-12-08 Thread dwmw2

It does seem that p11-kit-trust.so is working correctly. If I just make
a symlink from libnssckbi.so to it, corporate trust installed by update-
ca-certificates *does* work in Firefox.

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

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

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

[Touch-packages] [Bug 1648608] [NEW] fingerpint reader

2016-12-08 Thread Philip

Public bug reported:

Multiple attempts to register fingerprint. Scan is not responsive.

** Affects: camera-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 camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1648608

Title:
  fingerpint  reader

Status in camera-app package in Ubuntu:
  New

Bug description:
  Multiple attempts to register fingerprint. Scan is not responsive.

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

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

[Touch-packages] [Bug 1388876] Re: Pinch to zoom not supported when taking video

2016-12-08 Thread Philip

Meizu pro 5
OTA 13

Zoom dos not work consistently. Image of slider disappears when touched
and most time does not work

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

Title:
  Pinch to zoom not supported when taking video

Status in Canonical System Image:
  Fix Released
Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. Open the camera application
  2. Press the Video button to switch to video mode
  3. Place two fingers on the screen and move them apart to attempt to zoom

  Expected result:

  The picture zooms in and a slider appears indicating the zoom level

  Actual result:

  The slider appears but the picture does not zoom in and there is no
  marker on the slider to indicate the zoom level

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

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

[Touch-packages] [Bug 1633046] Re: Pressing play/pause hotkey hangs U8 session

2016-12-08 Thread Jim Hodapp

@Will: thanks for confirming that. I removed media-hub from the list of
affected packages.

** No longer affects: media-hub (Ubuntu)

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

Title:
  Pressing play/pause hotkey hangs U8 session

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Log in to a U8 session in 16.10.
  Press the play/pause hotkey.
  Note that the session is now hung.

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

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

[Touch-packages] [Bug 207135] Re: pulseaudio uses too much CPU

2016-12-08 Thread Francis Chin

Still a problem in 16.04 LTS - constantly burning 20% CPU on idle.

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

Title:
  pulseaudio uses too much CPU

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64
  Processor 3500+) when I'm just listening music using Rhythmbox. Seems
  too much IMHO.

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

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

** Changed in: canonical-devices-system-image
Milestone: p1 => p2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-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:
  In Progress
Status in unity-scope-click package in Ubuntu:
  New

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 1648237] Re: update-manager and unattended-upgrades failure

2016-12-08 Thread bedfojo

And now an error message in the unattended-upgrades log file:

2016-12-08 20:47:28,042 INFO Allowed origins are: ['o=Ubuntu,a=yakkety',
'o=Ubuntu,a=yakkety-security']
2016-12-08 20:47:46,867 ERROR An error occurred: 'Could not resolve
'security.ubuntu.com''
2016-12-08 20:47:46,868 ERROR The URI
'http://security.ubuntu.com/ubuntu/pool/main/g/ghostscript/ghostscript-x_9.19~dfsg+1-0ubuntu6.3_amd64.deb'
failed to download, aborting

Looks like it tries to run before the network is up.

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

Title:
update-manager and unattended-upgrades failure

Status in ubuntu-mate:
New
Status in unattended-upgrades package in Ubuntu:
New
Status in update-manager package in Ubuntu:
New

Bug description:
A series of issues about update-manager and unattended-upgrade. I have set
the system to:
- automatically check for update daily
- when there are security updates, download and install them automatically
- when there are other updates, display them immediately.

What occurs:

(1) unattended-upgrade runs on boot but systematically its log states
every day that: "No packages found that can be upgraded unattended and
no pending auto-removals" even where there are security updates to
install.

(2) update-manager appears not to refresh the cache automatically
after boot.

(3) when the cache is manually refreshed so there are updates, update-
manager runs after a subsequent boot and appears in the panel. However
clicking on it leads it to simply disappear.

(4) update-manager will not launch from the menu. When launched from a
terminal it runs correctly, refreshes the cache and will install
updates.

No crash reports, nothing obvious in log files.

Ubuntu-MATE 16.10 clean install, fully updated.

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

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

[Touch-packages] [Bug 1648599] Re: OSK inserts display-text vs text difference to web textfields upon cursor move and key press

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  OSK inserts display-text vs text difference to web textfields upon
  cursor move and key press

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've noticed many times now (ever since there are auto corrections present in 
the web browser) that when editing a text field in a web browser - for me 
usually gmail message composer (I haven't seen this in native apps yet) - the 
word I just wrote gets inserted to the text upon moving the cursor to a 
different place and start typing again.

  That is:
  1. Open something like Gmail and start composing a new email message
  2. When you have a "few words" written, before you type space after the last 
word, click to a different position inside the text to move the cursor elsewhere
  3. Start typing (anything)

  In most cases this results in the insertion of the last written word
  (that was in display-text property but not in the text property - that
  is if this is similar to QML TextInput) inside the text on the current
  cursor position.

  This is definitely an unexpected behaviour and makes editing while
  while composing a message really painful.

  I am on rc-proposed, MX4.
  Thank you very much for looking into this.

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

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

[Touch-packages] [Bug 1648605] [NEW] Inserted text ends up on a wrong position after clicking in front of the underlined word in text edit field (web browser)

2016-12-08 Thread zubozrout

Public bug reported:

Hello,
if you edit text in a web browser's text input field (like Gmail) and click 
right in front of the last inserted word (the underlined one with auto 
corrections available) and then start typing the cursor should stay in front of 
the stuff it was put as well as the text inserted to the current cursor 
position. Instead it gets moved after the underlined word and new text inserted 
after as well.

I am on rc-proposed, MX4 (and I've been experiencing this bug ever since
auto correction was made available in the web browser)

Thank you very much for looking into this.

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Inserted text ends up on a wrong position after clicking in front of
  the underlined word in text edit field (web browser)

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Hello,
  if you edit text in a web browser's text input field (like Gmail) and click 
right in front of the last inserted word (the underlined one with auto 
corrections available) and then start typing the cursor should stay in front of 
the stuff it was put as well as the text inserted to the current cursor 
position. Instead it gets moved after the underlined word and new text inserted 
after as well.

  I am on rc-proposed, MX4 (and I've been experiencing this bug ever
  since auto correction was made available in the web browser)

  Thank you very much for looking into this.

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

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

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

2016-12-08 Thread bugproxy

--- Comment From bren...@br.ibm.com 2016-12-08 14:42 EDT---
THis problem is now fixed with Ubuntu 17.04

llvm-3.8-dev (>= 1:3.8) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 arm64
armhf ppc64el],

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

Title:
  Enable llvmpipe on libgl-mesa-dri

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Gabriel Krisman Bertazi  - 2015-08-12 
09:53:27 ==
  The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) 
package for ppc64le, even though llvmpipe is fully supported on this 
architecture.  We need this feature enabled in order to run Unity with video 
cards lacking 3D Hardware Acceleration.

  Please enable it and, if possible, backport this change to 14.04.3.

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

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

[Touch-packages] [Bug 1648599] [NEW] OSK inserts display-text vs text difference to web textfields upon cursor move and key press

2016-12-08 Thread zubozrout

Public bug reported:

Hello,
I've noticed many times now (ever since there are auto corrections present in 
the web browser) that when editing a text field in a web browser - for me 
usually gmail message composer (I haven't seen this in native apps yet) - the 
word I just wrote gets inserted to the text upon moving the cursor to a 
different place and start typing again.

That is:
1. Open something like Gmail and start composing a new email message
2. When you have a "few words" written, before you type space after the last 
word, click to a different position inside the text to move the cursor elsewhere
3. Start typing (anything)

In most cases this results in the insertion of the last written word
(that was in display-text property but not in the text property - that
is if this is similar to QML TextInput) inside the text on the current
cursor position.

This is definitely an unexpected behaviour and makes editing while while
composing a message really painful.

I am on rc-proposed, MX4.
Thank you very much for looking into this.

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  OSK inserts display-text vs text difference to web textfields upon
  cursor move and key press

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Hello,
  I've noticed many times now (ever since there are auto corrections present in 
the web browser) that when editing a text field in a web browser - for me 
usually gmail message composer (I haven't seen this in native apps yet) - the 
word I just wrote gets inserted to the text upon moving the cursor to a 
different place and start typing again.

  That is:
  1. Open something like Gmail and start composing a new email message
  2. When you have a "few words" written, before you type space after the last 
word, click to a different position inside the text to move the cursor elsewhere
  3. Start typing (anything)

  In most cases this results in the insertion of the last written word
  (that was in display-text property but not in the text property - that
  is if this is similar to QML TextInput) inside the text on the current
  cursor position.

  This is definitely an unexpected behaviour and makes editing while
  while composing a message really painful.

  I am on rc-proposed, MX4.
  Thank you very much for looking into this.

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

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

[Touch-packages] [Bug 1648593] Re: Keyboard usualy not showing up in apps after unlocking the screen

2016-12-08 Thread Michal Predotka

bq M10 rc-proposed
I had this situation with Telegram today. Can't reproduce it now though.

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

Title:
  Keyboard usualy not showing up in apps after unlocking the screen

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  for the last month or even more I am experiencing this weird bug with OSK not 
popping up after putting my phone to "sleep", that is locking the screen and 
then unlocking it. It mostly happens with Telegram to me, as that is one 
particular app that I keep running all the time, but I've experienced this in 
other apps (including my own) as well and therefore expect it not to be related 
to Telegram at all.

  Steps to reproduce:
  1. Open any app (like Telegram) - OSK should pop up and work upon clicking on 
any input
  2. Lock the device (shut the screen down)
  -- The length of the phone being asleep seems to have little influence on the 
actual OSK keyboard behaviour - it seems to be pretty much random --
  3. Unlock the device
  4. Switch to the previously opened app if you are not there already

  Sometimes it is hard for me to reproduce this while other times I seem
  to be bumping into this every time I unlock the screen - so it is not
  something I've seen once or twice in my life but is pretty much
  common.

  To fix this behaviour switching out of the app and back to it again
  usually works, though sometimes restarting the app is the only way to
  get the OSK working.

  I am on rc-proposed, MX4

  Thank you very much for looking into this

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

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

[Touch-packages] [Bug 1648593] Re: Keyboard usualy not showing up in apps after unlocking the screen

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Keyboard usualy not showing up in apps after unlocking the screen

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  for the last month or even more I am experiencing this weird bug with OSK not 
popping up after putting my phone to "sleep", that is locking the screen and 
then unlocking it. It mostly happens with Telegram to me, as that is one 
particular app that I keep running all the time, but I've experienced this in 
other apps (including my own) as well and therefore expect it not to be related 
to Telegram at all.

  Steps to reproduce:
  1. Open any app (like Telegram) - OSK should pop up and work upon clicking on 
any input
  2. Lock the device (shut the screen down)
  -- The length of the phone being asleep seems to have little influence on the 
actual OSK keyboard behaviour - it seems to be pretty much random --
  3. Unlock the device
  4. Switch to the previously opened app if you are not there already

  Sometimes it is hard for me to reproduce this while other times I seem
  to be bumping into this every time I unlock the screen - so it is not
  something I've seen once or twice in my life but is pretty much
  common.

  To fix this behaviour switching out of the app and back to it again
  usually works, though sometimes restarting the app is the only way to
  get the OSK working.

  I am on rc-proposed, MX4

  Thank you very much for looking into this

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

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

[Touch-packages] [Bug 1648593] [NEW] Keyboard usualy not showing up in apps after unlocking the screen

2016-12-08 Thread zubozrout

Public bug reported:

Hello,
for the last month or even more I am experiencing this weird bug with OSK not 
popping up after putting my phone to "sleep", that is locking the screen and 
then unlocking it. It mostly happens with Telegram to me, as that is one 
particular app that I keep running all the time, but I've experienced this in 
other apps (including my own) as well and therefore expect it not to be related 
to Telegram at all.

Steps to reproduce:
1. Open any app (like Telegram) - OSK should pop up and work upon clicking on 
any input
2. Lock the device (shut the screen down)
-- The length of the phone being asleep seems to have little influence on the 
actual OSK keyboard behaviour - it seems to be pretty much random --
3. Unlock the device
4. Switch to the previously opened app if you are not there already

Sometimes it is hard for me to reproduce this while other times I seem
to be bumping into this every time I unlock the screen - so it is not
something I've seen once or twice in my life but is pretty much common.

To fix this behaviour switching out of the app and back to it again
usually works, though sometimes restarting the app is the only way to
get the OSK working.

I am on rc-proposed, MX4

Thank you very much for looking into this

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Keyboard usualy not showing up in apps after unlocking the screen

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  for the last month or even more I am experiencing this weird bug with OSK not 
popping up after putting my phone to "sleep", that is locking the screen and 
then unlocking it. It mostly happens with Telegram to me, as that is one 
particular app that I keep running all the time, but I've experienced this in 
other apps (including my own) as well and therefore expect it not to be related 
to Telegram at all.

  Steps to reproduce:
  1. Open any app (like Telegram) - OSK should pop up and work upon clicking on 
any input
  2. Lock the device (shut the screen down)
  -- The length of the phone being asleep seems to have little influence on the 
actual OSK keyboard behaviour - it seems to be pretty much random --
  3. Unlock the device
  4. Switch to the previously opened app if you are not there already

  Sometimes it is hard for me to reproduce this while other times I seem
  to be bumping into this every time I unlock the screen - so it is not
  something I've seen once or twice in my life but is pretty much
  common.

  To fix this behaviour switching out of the app and back to it again
  usually works, though sometimes restarting the app is the only way to
  get the OSK working.

  I am on rc-proposed, MX4

  Thank you very much for looking into this

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

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

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

2016-12-08 Thread Mikkel Kirkgaard Nielsen

I am also seing this on a 14.04 server using logrotate package version
3.8.7-1ubuntu1:

$ dpkg -l|grep logrotate
ii  logrotate  3.8.7-1ubuntu1   
amd64Log rotation utility

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty


Execution of logrotate from cron.daily aborts because of an existing file. Mail 
from cron below ("Filen eksisterer" is Danish for "File exists"):

/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: Filen eksisterer
run-parts: /etc/cron.daily/logrotate exited with return code 1

Looking at the syslog files there is both a syslog.1 and a syslog.1.gz
where the latter shouldn't exist because of delaycompress option. Also
the .gz is a compressed version of the plain file:

$ gunzip --stdout /var/log/syslog.1.gz | diff --report-identical-files - 
/var/log/syslog.1
Files - and /var/log/syslog.1 are identical


This suggests that logrotate was most likely interrupted after compressing 
syslog.1 to syslog.1.gz but before it was moved/rotated into syslog.2.gz. On 
subsequent executions this stale file causes logrotate to abort rotation 
entirely.


The issue has been addressed in recent upstream releases; 
https://github.com/logrotate/logrotate/pull/23

Also discussed in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=734688

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill

[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit

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

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

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

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

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

Bug description:
  Good afternoon.  
  I have started seeing something very similar to Debian Dug 734688 "Logs are 
not rotated for a month" but in the latest Ubuntu LTS (16.04).  I seem to have 
  $ logrotate --version
  logrotate 3.8.7
  bundled in it.  A few weeks ago I started getting root emails such as this:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/munin/munin-node.log.1: File 
exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  When I inspected the area of concern I was able to see that there was an 
existing .1 file.  
  manager@warden:/var/log/munin$ ll
  total 580
  drwxr-xr-x  2 munin adm  4096 Sep 27 06:31 ./
  drwxr-xr-x 13 root  syslog   4096 Oct  5 06:26 ../
  -rw-r--r--  1 root  root 3440 Sep 26 13:39 munin-node-configure.log
  -rw-r--r--  1 root  root   490251 Oct  5 10:25 munin-node.log
  -rw-r--r--  1 root  root56598 Sep 21 02:01 munin-node.log.1
  -rw-r--r--  1 root  root24576 Aug 31 02:01 munin-node.log.2
  -rw-r--r--  1 root  root 1906 Sep 19 06:25 munin-node.log.8.gz
  The contents of the munin-node.log file seem to run from the 19th September 
until today.  Unlike other parts of this bug the .1 and .2 files do not seem to 
be already compressed.  

  I deleted all but the munin-node.log file to see if it would resolve the 
problem and was going to leave it at that.  Then I noticed that I have had 
another Ubuntu machine which has been sending similar emails for the past week:
  > Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
  >
  > /etc/cron.daily/logrotate:
  > error: error creating output file /var/log/syslog.1.gz: File exists
  > run-parts: /etc/cron.daily/logrotate exited with return code 1
  Different file, different machine but a very similar error message.  

  Checking on the syslog file I can see that it better fits with other reports 
on this bug as my duplicated .1 files has a corresponding .1.gz file.  
  manager@trac:/var/log$ ll syslog*
  -rw-r- 1 syslog adm 918492 Oct  5 10:30 syslog
  -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
  -rw-r- 1 syslog adm  20638 Oct  2 02:01 syslog.1.gz
  -rw-r- 1 syslog adm  41989 Sep 30 02:00 syslog.2.gz
  -rw-r- 1 syslog adm  18654 Sep 28 02:01 syslog.3.gz
  -rw-r- 1 syslog adm  31720 Sep 26 06:40 syslog.4.gz
  -rw-r- 1 syslog adm  33151 Sep 25 02:01 syslog.5.gz
  -rw-r- 1 syslog adm  17290 Sep 23 02:01 syslog.6.gz
  -rw-r- 1 syslog adm  39275 Sep 21 06:35 syslog.7.gz

  There has been some speculation that a full or nearly full /var
  partition would cause this issue.  I can confirm that /var is part of
  / on my systems and that presently both of them have several gigabytes
  of space.  I run Munin an Icinga to monitor system state.  Neither of
  these show / being completely full in the past month.  They have both
  had /boot fill significantly.  Trac had a highest use value of / being
  99.28% full in the past year  but warden has only had a peak of 33% in
  the past year.

  A quick search of the internet suggests a couple of other people reporting 
similar issues: 
  https://github.com/gitlabhq/gitlabhq/issues/6894
  
http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating
 

  I do not believe that I have altered by logrotate configuration files but 
here is a copy of the ones I know about:
  $ cat /etc/logrotate.conf 
  # see "man logrotate" for details
  # rotate log files weekly
  weekly

  # use the syslog group by default, since this is the owning group
  # of /var/log/syslog.
  su root syslog

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # no packages own wtmp, or btmp -- we'll rotate them here
  /var/log/wtmp {
  missingok
  monthly
  create 0664 root utmp
  rotate 1
  }

  /var/log/btmp {
  missingok
  monthly
  create 0660 root utmp
  rotate 1
  }

  # system-specific logs may be configured here

  $ cat /etc/logrotate.d/rsyslog

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

2016-12-08 Thread Michael Terry

Michi, since it sounds like scoperunner is dying on you, try my
scoperunner command up above again, with the right snappyenv.  Here it
is again (with fixed snappyenv):

DBUS_SESSION_BUS_ADDRESS=`cat /run/user/0/dbus-session | cut -f2- -d=`
HOME=/root/snap/unity8-session/264
SNAP_USER_DATA=/root/snap/unity8-session/264
SNAP_USER_COMMON=/root/snap/unity8-session/common SNAP_ARCH=amd64
SNAP=/snap/unity8-session/current U1_DEBUG=1
/snap/unity8-session/current/snappyenv
/snap/unity8-session/current/usr/lib/x86_64-linux-gnu/unity-
scopes/scoperunner "" /snap/unity8-session/current/usr/lib/x86_64-linux-
gnu/unity-scopes/clickapps/clickscope.ini

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-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:
  In Progress
Status in unity-scope-click package in Ubuntu:
  New

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 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-12-08 Thread Peter S

@anders-frisk650

Well done! Now we're getting somewhere.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

2016-12-08 Thread Luis Henriques

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

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in bridge-utils source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in bridge-utils source package in Yakkety:
  Invalid

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 
do_vfs_ioctl+0x29f/0x490
  Aug 23 15:09:46

[Touch-packages] [Bug 1443902] Re: [address book] Contact form should allow multi source account for a contact

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

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

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

Title:
  [address book] Contact form should allow multi source account for a
  contact

Status in Ubuntu UX:
  Triaged
Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  (You have set a Google account fromm system settings)

   * Launch contact
   * Add a new contact
   * At the bottom, you can choose from different contact storage (gmail, 
personnal,more incoming maybe like owncloud)
   * The Select composent should let the user multi select this option 
(Example: I want this contact only on local, but that one on google account + 
owncloud account)

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

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

[Touch-packages] [Bug 1634622] Re: Possible to add Contacts to Accounts configuration for ownCloud?

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

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

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

Title:
  Possible to add Contacts to Accounts configuration for ownCloud?

Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  In Settings>Personal>Accounts, I've added an ownCloud account. It has
  a toggle for Calendar, and that works. It doesn't have a line for
  Contacts. Are there plans to add that? I'd like to sync Contacts with
  my desktop (which I do via ownCloud), but instructions with
  syncevolution are complicated.

  Someone else reported that this option shows up when using NextCloud,
  so maybe this is a bug.

  Description:  Ubuntu 15.04
  Release:  15.04

  phablet@ubuntu-phablet:~$ apt-cache policy ubuntu-system-settings
  ubuntu-system-settings:
Installed: 0.4+15.04.20160831.1-0ubuntu1
Candidate: 0.4+15.04.20160831.1-0ubuntu1
Version table:
   *** 0.4+15.04.20160831.1-0ubuntu1 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-system-settings 0.4+15.04.20160831.1-0ubuntu1
  Uname: Linux 3.4.0-7-mako armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Oct 18 13:50:24 2016
  InstallationDate: Installed on 2016-09-13 (35 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160913-023544)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648292] Re: Running Mir-Server snap, gives error! [Unknown command line options: --vt 1]

2016-12-08 Thread Janne Hannila

Same problem in mir-kiosk from canonical!

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

Title:
  Running Mir-Server snap, gives error! [Unknown command line options:
  --vt 1]

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  I don't know, if this is right place!
  Trying to run mir-server gives error:

  Dec  8 02:59:06 localhost snap[4768]: Unknown command line options: --vt 1
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Main process exited, code=exited, status=1/FAILURE
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Unit entered failed state.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Failed with result 'exit-code'.
  Dec  8 02:59:06 localhost systemd[1]: snap.mir-server.mir-server.service: 
Service hold-off time over, scheduling restart.

  Running on Raspberry pi 2, Ubuntu snappy core!

  runned lsb_release -rd

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

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

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

[Touch-packages] [Bug 1647148] Re: Implement CUPS server snapd interface

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

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

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

Title:
  Implement CUPS server snapd interface

Status in Canonical System Image:
  In Progress
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The CUPS server is an helpful feature, needed if you want to get
  convergence. Thanks for all your work, see you.

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

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

[Touch-packages] [Bug 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

2016-12-08 Thread Jose' Belmar

What's the latest on this issue? When i flashed touch onto my nexus 4 i saw the 
hotspot menu item for the first boot, but afterward it disappeared. So does 
this mean that the hotspot bug will never be fixed for Nexus 4?
I have one slightlty off-topic question:
Is bluetooth file sharing also missing for similar reasons?

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

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  Insecure hotspots should work using this [3] script.

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
  [3] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

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

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

[Touch-packages] [Bug 655304] Re: zh manpages in passwd package, between all chinese chars, there are spaces

2016-12-08 Thread Oskar Wallgren

I think this may be an incarnation of
https://bugs.launchpad.net/ubuntu/+source/most/+bug/312454

PAGER=most LANGUAGE=zh_CN LC_ALL=zh_CN.UTF-8 man shadow


** Attachment added: "shadow.png"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/655304/+attachment/4789143/+files/shadow.png

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

Title:
  zh manpages in passwd package, between all chinese chars, there are
  spaces

Status in Ubuntu Translations:
  Triaged
Status in shadow package in Ubuntu:
  New
Status in shadow package in Debian:
  Fix Released

Bug description:
  It is so ugly and hard to read.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: passwd 1:4.1.4.2-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Oct  6 02:43:46 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100812)
  ProcEnviron:
   LANGUAGE=zh_CN:zh_TW:zh:en
   PATH=(custom, user)
   LANG=zh_CN.utf8
   SHELL=/usr/bin/zsh
  SourcePackage: shadow

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

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

[Touch-packages] [Bug 1638708] Re: Hardcoded paths in desktop files need to be processed need $SNAP prefixing

2016-12-08 Thread Rodney Dawes

** No longer affects: indicator-printers (Ubuntu)

** No longer affects: indicator-network (Ubuntu)

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

Title:
  Hardcoded paths in desktop files need to be processed need $SNAP
  prefixing

Status in indicator-application package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in several indicator patches, e.g.
  :

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

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

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

[Touch-packages] [Bug 1646256] Re: Update sudo for proper support of netgroups

2016-12-08 Thread Florian Apolloner

Seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666

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

Title:
  Update sudo for proper support of netgroups

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  sudo v1.8.16 has a bug that prevents it from working properly with
  netgroups.

  The main affected usage case that I'm aware of is when using FreeIPA
  to define host groups, and then using those host groups within sudo
  rules.

  It would appear that a release >=1.8.17 resolves the issue.

  https://bugzilla.redhat.com/show_bug.cgi?id=1348672
  
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/sudo.html#abt-sudo2

  Package: sudo 1.8.16-0ubuntu1.2
  Distribution: Ubuntu 16.04 and later

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

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

"BFB" is "Big Flavorful Button" ;)

It's the huge orange "Ubuntu Store" result that appears at the bottom of
the scope.

So, from your screenshot it looks like you are hitting case number 2
from my previous post. Is there a crash report in /var/crash/ for the
scoperunner? If not, does running "ubuntu-app-launch-appids" on this
system show any snap results?

If this is the unity8 snap as well, it looks like in the screenshot that
even System Settings isn't being found. With that and the missing store
result, it seems like the scope is crashing or being killed before it
can push any results. Can you attach the unity8-dash.log and scope-
registry.log files? Normally they are in ~/.cache/upstart/ but not sure
where exactly that equates to for the unity8 snap on core.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-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:
  In Progress
Status in unity-scope-click package in Ubuntu:
  New

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 1646256] Re: Update sudo for proper support of netgroups

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

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

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

Title:
  Update sudo for proper support of netgroups

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  sudo v1.8.16 has a bug that prevents it from working properly with
  netgroups.

  The main affected usage case that I'm aware of is when using FreeIPA
  to define host groups, and then using those host groups within sudo
  rules.

  It would appear that a release >=1.8.17 resolves the issue.

  https://bugzilla.redhat.com/show_bug.cgi?id=1348672
  
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/sudo.html#abt-sudo2

  Package: sudo 1.8.16-0ubuntu1.2
  Distribution: Ubuntu 16.04 and later

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

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

[Touch-packages] [Bug 1648556] [NEW] package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2016-12-08 Thread mugnier

Public bug reported:

no details

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2016j-0ubuntu0.16.04
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
Date: Thu Dec  8 17:56:04 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2013-05-30 (1288 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: tzdata
Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2016-08-30 (99 days ago)

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

Title:
  package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  no details

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016j-0ubuntu0.16.04
  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
  Date: Thu Dec  8 17:56:04 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-05-30 (1288 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: tzdata
  Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-30 (99 days ago)

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

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

[Touch-packages] [Bug 1648556] Re: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2016-12-08 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  no details

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016j-0ubuntu0.16.04
  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
  Date: Thu Dec  8 17:56:04 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-05-30 (1288 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: tzdata
  Title: package tzdata 2016j-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-30 (99 days ago)

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

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

[Touch-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

2016-12-08 Thread Harry

First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function 
properly, it should depend on it.

Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the 
package resolvconf.

Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still does not work 
properly. It is not OK.

And here are some test results.

With NM 1.4.2-2ubuntu3: "systemd-resolve --status"
Global
 DNS Servers: 127.0.1.1
  DNS Domain: dhcp.inet.fi
  DNSSEC NTA: 10.in-addr.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes

With NM 1.4.2-2ubuntu4: "systemd-resolve --status"
Global
  DNSSEC NTA: 10.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: 193.210.18.18
  193.210.19.19
  DNS Domain: dhcp.inet.fi

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

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2016-12-08 Thread Jose Manuel Santamaria Lema

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

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

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

[Touch-packages] [Bug 1569227] Re: Mouse & Touchpad second slider is not labelled (it actually controls wheel/scrolling speed)

2016-12-08 Thread Bill Filler

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Mouse & Touchpad second slider is not labelled (it actually controls
  wheel/scrolling speed)

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  Mouse & Touchpad second slider is not labelled

  It seems to control the mouse wheel speed though (or in the case of
  touchpad the two-finger scrolling speed).

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

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

[Touch-packages] [Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

2016-12-08 Thread Brian Murray

** Changed in: unattended-upgrades (Ubuntu)
 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1618900

Title:
  [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we 
encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages 
can not be downloaded (can be mitigated by using 
APT::Periodic::Download-Upgradeable-Packages "1";) :
  => ERROR An error occurred: 'Could not resolve host: .fr'
  => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'
 failed to download, aborting
  - Important mountpoints like /boot are unmounted before unattended-upgrades 
is running, so newer kernels can not be installed properly (ramdisk and grub 
configuration can not be generated)

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

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

[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

2016-12-08 Thread Renato Araujo Oliveira Filho

** Changed in: telepathy-mission-control-5 (Ubuntu)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

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

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

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

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

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

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

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

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from 14.04.3 to 16.04.1

  Noted during install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Aug  4 09:10:47 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2015-08-19 (351 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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

[Touch-packages] [Bug 1646611] Re: mission-control should use different paths when in a snap environment

2016-12-08 Thread Bill Filler

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  mission-control should use different paths when in a snap environment

Status in Canonical System Image:
  Confirmed
Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When running confined into a snap environment, mission-control needs
  to use different paths for its files:

  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.CC7LOY':
 No such file or directory
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Unable to create directory 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control': Read-only file 
system
  Sep 30 05:31:22 localhost org.freedesktop.Telepathy.AccountManager[4688]: 
(process:4767): mcd-WARNING **: Failed to create file 
'/snap/unity8-session/x1/usr/share/telepathy/mission-control/accounts.cfg.7I1LOY':
 No such file or

  Instead of using $SNAP, it probably should use $SNAP_DATA

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

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

[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard

2016-12-08 Thread Timo Jyrinki

I was a happy user of transparent Literki keyboard back in the days
(http://wiki.openmoko.org/images/b/bf/Debian_timo2.png) so I agree this
could be nice.

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

Title:
  Add option for semi-transparent keyboard

Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  OK, this is not a real bug, rather a characteristic. But one that can be 
easily solved, thus I'd like to make a feature request. 
  Especially in the landscape mode, the onscreen keyboard takes up a large 
portion of the screen. Potentially it can overlap the window where the text is 
being typed into, so you cannot see what you're typing.
  This could be VERY easily solved by letting users to set transparency level 
for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 
70% opacity on Ubuntu Touch phone, in landscape windowed mode.

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

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

[Touch-packages] [Bug 1648538] [NEW] Custom keyboard shortcuts not work

2016-12-08 Thread Luca Ciavatta

Public bug reported:

1) Description: Ubuntu 16.04.1 LTS
   Release: 16.04

2) ubuntu-settings:
   Installed: 15.10.8
   Candidate: 15.10.8
   Version table:
   *** 15.10.8 500
   500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages
   500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 Packages
   100 /var/lib/dpkg/status

3) I made some custom keyboard shortcuts under All Settings > Keyboard > 
Shortcuts
   In particular, I made these:
   CTRL+SHIFT+S - Custom screenshot - gnome-screenshot -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
   CTRL+SHIFT+A - Custom screenshot area - gnome-screenshot -a -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
   CTRL+SHIFT+W - Custom screenshot window - gnome-screenshot -w -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"

   I expected the shortcuts working when I press the right keys
combination.

4) Custom keyboard shortcuts not work.

   The shortcuts worked only one time and after never worked. If I use
the commands directly in a terminal window, the commands work fine.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gnome-settings-daemon (Ubuntu) => ubuntu-settings
(Ubuntu)

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

Title:
  Custom keyboard shortcuts not work

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.1 LTS
 Release:   16.04

  2) ubuntu-settings:
 Installed: 15.10.8
 Candidate: 15.10.8
 Version table:
 *** 15.10.8 500
 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages
 500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 
Packages
 100 /var/lib/dpkg/status

  3) I made some custom keyboard shortcuts under All Settings > Keyboard > 
Shortcuts
 In particular, I made these:
 CTRL+SHIFT+S - Custom screenshot - gnome-screenshot -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
 CTRL+SHIFT+A - Custom screenshot area - gnome-screenshot -a -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"
 CTRL+SHIFT+W - Custom screenshot window - gnome-screenshot -w -f 
"$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png"

 I expected the shortcuts working when I press the right keys
  combination.

  4) Custom keyboard shortcuts not work.

 The shortcuts worked only one time and after never worked. If I use
  the commands directly in a terminal window, the commands work fine.

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

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

[Touch-packages] [Bug 1101881] Re: software-properties-gtk crashed with TypeError in new(): object of type 'NoneType' has no len()

2016-12-08 Thread Brian Murray

** Changed in: software-properties (Ubuntu Wily)
 Assignee: Brian Murray (brian-murray) => (unassigned)

** Changed in: software-properties (Ubuntu Wily)
   Status: Triaged => Won't Fix

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

Title:
  software-properties-gtk crashed with TypeError in __new__(): object of
  type 'NoneType' has no len()

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Wily:
  Won't Fix
Status in software-properties source package in Xenial:
  Fix Released

Bug description:
  [ Impact ]
  Users on architectures other than amd64 of i386 trying to use 
software-properties to choose a server from which to download software will 
receive a crash after closing the "Choose a Download Server" dialog.

  [ Test Case ]
  1) Be on a not i386 or amd64 system (or be on amd64 and use a hack found in 
comment #11)
  2) Launch software-properties-gtk
  3) In the Download from: drop-down choose "Other..."
  4) Observe an empty list of download servers
  5) Click "Cancel"
  6) Observe a traceback in the terminal which you launched 
software-properties-gtk

  Wit the version of software-properties-gtk from -proposed you will not
  receive a crash.

  ---

  on nexus 7

  ProblemType: CrashDistroRelease: Ubuntu 13.04
  Package: software-properties-gtk 0.92.13
  Uname: Linux 3.1.10-8-nexus7 armv7l
  ApportVersion: 2.8-0ubuntu2
  Architecture: armhf
  CrashCounter: 1
  Date: Sat Jan 19 14:44:31 2013
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2013-01-16 (3 days ago)
  InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf 
(20130115-15:18)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', 
'2']SourcePackage: software-properties
  Title: software-properties-gtk crashed with TypeError in __new__(): object of 
type 'NoneType' has no len()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1381050] Re: "Import Key File" fails when the path of the file has special characters

2016-12-08 Thread Brian Murray

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

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Triaged

** Changed in: software-properties (Ubuntu Trusty)
   Status: In Progress => Triaged

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Trusty:
  Triaged

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1648538] [NEW] Custom keyboard shortcuts not work