[Touch-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-04 Thread Thomas Hood
Right, I think the file should only document the Ubuntu-specific things
such as the facts that by default resolvconf and the systemd resolver
are used, NetworkManager is used by default on Desktop and ifup on
Server, and so on. There have been hundreds of questions about these
basic things on AskUbuntu and the forums over the years. I have often
referred people to Stephane Graber's blog post
(https://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/) for
background info but this is as of 16.11 no longer adequate.

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

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

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


Re: [Touch-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-04 Thread Steve Langasek
On Fri, Nov 04, 2016 at 11:53:11AM -, Thomas Hood wrote:
> What would be far better, though, is to include a text file or manpage
> explaining how name service currently works in Ubuntu.

That doesn't help the problem that /etc/resolv.conf is the file that the
experienced admin expects to contain the nameservers' addresses.

> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> # For more info see /usr/share/doc/resolvconf/name-service-in-Ubuntu.txt
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

The admin is not going to follow documentation links for the thing that
"should" be working the way it always worked and that Ubuntu has broken. 
Documentation is what you look for when you're looking to understand
something new, not to understand why Ubuntu has become buggy and annoying.

This text should go directly in /etc/resolv.conf.

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

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

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


[Touch-packages] [Bug 1639205] [NEW] PyGIWarning error message when using ubuntu-bug

2016-11-04 Thread Bill Turner, wb4alm
Public bug reported:

Ubuntu 16.04.1   GNOME 3.20   Ubuntu-bug ???


when using the "ubuntu-bug gedit" command to report a problem with gedit, the 
following message was displayed in the terminal screen after completing the bug 
report... 

ubuntu-bug gedit
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk

This error message will be displayed after any use of the ubuntu-bug
command.

(and "ubuntu-bug ubuntu-bug" should be a valid command.  Took a while to
determine that ubuntu-bug is part of apport.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashReports:
 664:1000:116:0:2016-11-04 06:26:07.927235574 -0400:2016-11-04 
06:26:07.927235574 -0400:/var/crash/_usr_bin_update-manager.1000.upload
 640:1000:116:302125:2016-11-04 06:26:04.887287139 -0400:2016-11-04 
06:26:07.931235472 -0400:/var/crash/_usr_bin_update-manager.1000.crash
 600:109:116:0:2016-11-04 06:26:46.238292470 -0400:2016-09-14 
06:35:54.449242309 -0400:/var/crash/_usr_bin_update-manager.1000.uploaded
CurrentDesktop: GNOME
Date: Fri Nov  4 06:45:10 2016
InstallationDate: Installed on 2014-05-11 (908 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  PyGIWarning error message when using ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.1   GNOME 3.20   Ubuntu-bug ???

  
  when using the "ubuntu-bug gedit" command to report a problem with gedit, the 
following message was displayed in the terminal screen after completing the bug 
report... 

  ubuntu-bug gedit
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  This error message will be displayed after any use of the ubuntu-bug
  command.

  (and "ubuntu-bug ubuntu-bug" should be a valid command.  Took a while
  to determine that ubuntu-bug is part of apport.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashReports:
   664:1000:116:0:2016-11-04 06:26:07.927235574 -0400:2016-11-04 
06:26:07.927235574 -0400:/var/crash/_usr_bin_update-manager.1000.upload
   640:1000:116:302125:2016-11-04 06:26:04.887287139 -0400:2016-11-04 
06:26:07.931235472 -0400:/var/crash/_usr_bin_update-manager.1000.crash
   600:109:116:0:2016-11-04 06:26:46.238292470 -0400:2016-09-14 
06:35:54.449242309 -0400:/var/crash/_usr_bin_update-manager.1000.uploaded
  CurrentDesktop: GNOME
  Date: Fri Nov  4 06:45:10 2016
  InstallationDate: Installed on 2014-05-11 (908 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1639223] [NEW] Cannot connect to web with bluetooth connection after resuming from suspend

2016-11-04 Thread Peter Rhone
Public bug reported:

If I resume from suspend and reconnect my phone's bluetooth internet
connection, my web browsers claim I'm offline. I can successfully ping
8.8.8.8 but cannot resolve domain names. Restarting network manager with
"sudo service network-manager restart" and reconnecting to my phone
fixes the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Nov  4 11:57:24 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-12-15 (689 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IpRoute:
 default via 192.168.44.1 dev bnep0  proto static  metric 750 
 169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
 192.168.44.0/24 dev bnep0  proto kernel  scope link  src 192.168.44.77  metric 
750 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-16 (18 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Cannot connect to web with bluetooth connection after resuming from
  suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  If I resume from suspend and reconnect my phone's bluetooth internet
  connection, my web browsers claim I'm offline. I can successfully ping
  8.8.8.8 but cannot resolve domain names. Restarting network manager
  with "sudo service network-manager restart" and reconnecting to my
  phone fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov  4 11:57:24 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-15 (689 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.44.1 dev bnep0  proto static  metric 750 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.44.0/24 dev bnep0  proto kernel  scope link  src 192.168.44.77  
metric 750 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (18 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1639208] Re: The app store button is hardcoded to the Click Store scope

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  The app store button is hardcoded to the Click Store scope

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Clicking the app store icon in the Manage Dash view should activate
  whichever store is default on the system. E.g. Click Store scope on V,
  Snappy Store scope on X, and the Snappy Store app on Y+.

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

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


[Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

2016-11-04 Thread Jonas G. Drange
(Got my bugs mixed up, I didn't actually mention silo 2140. :))

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

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

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


[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

2016-11-04 Thread Heinrich Hartl
I am affected too.
Manually starting ntpd using `systemctl start ntp` doesn't work for me.
ps -ef | grep ntpd # shows no started ntpd.
systemctl status ntp # does not change active (excited), only another last line 
is added.

root@ILS-AP2:~# systemctl start ntp
root@ILS-AP2:~# ps -ef | grep ntp
root 10186 10166  0 14:22 pts/600:00:00 grep --color=auto ntp
root@ILS-AP2:~# systemctl status ntp
● ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
   Active: active (exited) since Mi 2016-11-02 23:50:59 CET; 1 day 14h ago
 Docs: man:systemd-sysv-generator(8)
  Process: 1227 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
  Process: 1367 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)

Nov 02 23:50:59 ILS-AP2 systemd[1]: Starting LSB: Start NTP daemon...
Nov 02 23:50:59 ILS-AP2 ntp[1367]:  * Starting NTP server ntpd
Nov 02 23:50:59 ILS-AP2 ntp[1367]:...done.
Nov 02 23:50:59 ILS-AP2 ntpd[1381]: proto: precision = 0.129 usec (-23)
Nov 02 23:50:59 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 02 23:51:05 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 12:36:22 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 12:38:45 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
Nov 04 14:22:21 ILS-AP2 systemd[1]: Started LSB: Start NTP daemon.
root@ILS-AP2:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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


[Touch-packages] [Bug 1629552] Re: files with the same name installed in / and /usr

2016-11-04 Thread Bug Watch Updater
** Changed in: json-c (Debian)
   Status: Unknown => New

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

Title:
  files with the same name installed in / and /usr

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in genwqe package in Ubuntu:
  Invalid
Status in grub package in Ubuntu:
  Invalid
Status in json-c package in Ubuntu:
  Fix Committed
Status in json-c package in Debian:
  New

Bug description:
  A few remaining packages in Ubuntu are incompatible with a merged /usr
  because they ship the same file in /bin and /usr/bin; it looks like
  Debian will soon default to that, and we surely want to follow suit.

  The duplicate file/symlink needs to be removed, or created in
  postinst.

https://bugs.debian.org/cgi-
  bin/pkgreport.cgi?tag=usrmerge;users=m...@linux.it

  cgroup-lite:

  lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-umount -> 
/bin/cgroups-umount
  lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-mount -> 
/bin/cgroups-mount

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

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


[Touch-packages] [Bug 1580290] Re: First tab is always reloaded when the session is restored

2016-11-04 Thread Olivier Tilloy
Tested and verified in an up-to-date xenial amd64 VM, with webbrowser-
app 0.23+16.04.20161028-0ubuntu1.

I verified that the first tab doesn’t get reloaded at startup if another
tab was previously selected.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  First tab is always reloaded when the session is restored

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  bq M10 rc-proposed OS build 100
  If I have few tabs open and in the first tab is a youtube video, it will 
start playing even if that tap is in the background after restarting the 
Browser.

  Steps to reproduce:
  1. Start Browser
  2. Open a tab with a youtube video in it, for example 
http://summit.ubuntu.com/uos-1605/meeting/22651/convergent-ubuntu-apps
  3. Open few more tabs with other websites
  4. If necessary move the tab with the video so it's the first from the left
  5. Select any other tab
  6. Close  Browser
  7. Start Browser again

  Expected result:
  I don't hear the sound from the video in the background tab.

  What happens instead:
  I hear the sound from the video in the background tab.

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

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


[Touch-packages] [Bug 1466427] Re: User agent string claims it's running Ubuntu 14.04

2016-11-04 Thread Olivier Tilloy
Tested and verified in an up-to-date xenial amd64 VM, with webbrowser-
app 0.23+16.04.20161028-0ubuntu1.

I browsed to whatsmyua.com and the user agent string advertises Ubuntu
16.04.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  User agent string claims it's running Ubuntu 14.04

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu 15.04 r35

  1. Go to a page that reports your user agent string, for example
   or .

  What you see: Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4)
  AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36

  What you should see: The UA string should not say "Ubuntu 14.04".

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

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


[Touch-packages] [Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-04 Thread Thomas Hood
If such a comment were to be added then in order not to mislead it would
have to take into account the configurability of various components. So
you'd have to say something like:

«If the line "nameserver 127.0.0.53" is present then it probably refers
to the systemd resolver listening on the loopback address. By default
the systemd resolver is also configured to handle name queries via the
Name Service Switch whose configuration file is nsswitch.conf. The name
servers to which the systemd resolver forwards queries can be discovered
by running "systemd-resolve --status".»

What would be far better, though, is to include a text file or manpage
explaining how name service currently works in Ubuntu. (Actually we
should have done this long ago.) The file could include the previous
paragraph but would also talk about resolvconf and NetworkManager and
its plugins. The name of this file could then be mentioned in the header
that resolvconf writes into resolv.conf.
/etc/resolvconf/resolv.conf.d/head would then be:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# For more info see /usr/share/doc/resolvconf/name-service-in-Ubuntu.txt
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

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

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


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

2016-11-04 Thread Martin Pitt
Comment #6 is the correct solution. On desktop images we want NM to
manage everything, thus the installer creates
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf. But on a
server, container, or similar environment we do NOT want NM to suddenly
take over existing connections from netplan, networkd, or ifupdown --
there it should be restricted to wifi and 3G.

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

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

Bug description:
  Hello,

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1636862] Re: Shutdown hangs with active iscsi sessions

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Shutdown hangs with active iscsi sessions

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a duplicate of the bug listed here:
  https://bugs.launchpad.net/bugs/1569925 for 16.04.

  That bug was automatically closed though the problem still persists.
  I am opening this bug for 16.10 in hopes that it will catch somebody's
  attention.

  I have 4 servers running the latest 16.10 updates.

  Each server is connected to NetApp storage using iscsi software
  initiator. There are a total of 56 volumes spread across two NetApp
  arrays. Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

"Reached target Shutdown"

  followed by

"systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

"connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
"connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
NOTE: the actual values of the *'s differ for each line above.

  Screenshot of the issue:
  https://www.dropbox.com/s/93mv7cj8asspcpa/ShutdownCapture.JPG?dl=0

  ~# lsb_release -rd
  Description:Ubuntu 16.10
  Release:16.10

  ~# apt-cache policy open-iscsi
  open-iscsi:
Installed: 2.0.873+git0.3b4b4500-14ubuntu8
Candidate: 2.0.873+git0.3b4b4500-14ubuntu8
Version table:
   *** 2.0.873+git0.3b4b4500-14ubuntu8 500
  500 http://repomirror-ict.eng.netapp.com/ubuntu yakkety/main amd64 
Packages
  100 /var/lib/dpkg/status

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

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eno1
  iface eno1 inet dhcp
  # This is an autoconfigured IPv6 interface
  iface eno1 inet6 auto

  # This is an autoconfigured interface
  auto enp4s0
  iface enp4s0 inet static
   address 192.12.21.2
   netmask 255.255.255.0
   mtu 9000
  # This is an autoconfigured interface
  auto enp130s0f3
  iface enp130s0f3 inet static
   address 192.12.22.2
   netmask 255.255.255.0
   mtu 9000

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

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


[Touch-packages] [Bug 1622073] Re: zmq::mechanism_t::socket_type_string off-by-one

2016-11-04 Thread Luca Boccassi
Hi,

Good catch!

This is fixed in 4.2.0 already, and I will fix it for the next 4.1
stable release (4.1.7).

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

Title:
  zmq::mechanism_t::socket_type_string off-by-one

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  Hello, the zmq::mechanism_t::socket_type_string function in
  ./src/mechanism.cpp appears to have an off-by-one mistake:

  const char *zmq::mechanism_t::socket_type_string (int socket_type) const 
  {   
  static const char *names [] = {"PAIR", "PUB", "SUB", "REQ", "REP",
 "DEALER", "ROUTER", "PULL", "PUSH",
 "XPUB", "XSUB", "STREAM"};
  zmq_assert (socket_type >= 0 && socket_type <= 10);
  return names [socket_type];
  }   

  names[11] is "STREAM" but that triggers the assert.

  Thanks

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

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


Re: [Touch-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

2016-11-04 Thread Jonas G. Drange
Silo 2140 as mentioned will give you a way to reproduce this. I am
currently unable to since I've lost the option to log into a unity8 desktop
session.

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

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Incomplete
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/

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

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


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

2016-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package dbus - 1.10.10-1ubuntu2

---
dbus (1.10.10-1ubuntu2) zesty; urgency=medium

  * debian/patches/make-uid-0-immune-to-timeout.patch:
- Add a test patch proposed by Simon McVittie upstream to fix bug
  LP: #1591411.

 -- Łukasz 'sil2100' Zemczak   Tue, 11 Oct
2016 20:12:43 +0200

** Changed in: dbus (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1573017] Re: [webapp-container] SAML detection logic broken

2016-11-04 Thread Olivier Tilloy
Tested and verified in an up-to-date xenial amd64 VM, with webbrowser-
app 0.23+16.04.20161028-0ubuntu1.

I installed webapp-container-autopilot in the VM and ran successfully
the webapp_container test suite. All the tests passed.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [webapp-container] SAML detection logic broken

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  When trying to authenticate to my canonical.com account I keep being ejected 
into the browser application.
  Previously, the SAML detection logic was ensuring this extra authentication 
step was allowed, even if URLs were falling outside of the webapps defined set.

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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


[Touch-packages] [Bug 1572673] Re: [webapp-container] Invalid variable access error 'popupWindowController'

2016-11-04 Thread Olivier Tilloy
Tested and verified in an up-to-date xenial amd64 VM, with webbrowser-
app 0.23+16.04.20161028-0ubuntu1.

I installed webapp-container-autopilot in the VM and ran successfully
the webapp_container test suite. All the tests passed.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [webapp-container] Invalid variable access error
  'popupWindowController'

Status in Canonical System Image:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  There an error while opening an overlay:

  file:///home/alex/dev/work/webapps/branches/webbrowser-
  app/error/src/app/webcontainer/WebViewImplOxide.qml:191:
  ReferenceError: popupWindowController is not defined

  
  [Test case for verification]
  The fix comes with an autopilot test. To run the autopilot tests for the 
webapp container, install webapp-container-autopilot, and run `autopilot3 run 
webapp_container`. All the test cases should pass.

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

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


[Touch-packages] [Bug 1565063] Re: Update the chromium version in the user agent

2016-11-04 Thread Olivier Tilloy
Tested and verified in an up-to-date xenial amd64 VM, with webbrowser-
app 0.23+16.04.20161028-0ubuntu1.

I browsed to whatsmyua.com, and the chromium version advertised in the
UA string was 54.0.2840.71.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Update the chromium version in the user agent

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app source package in Xenial:
  Fix Committed

Bug description:
  We have never updated the version, which is 35, and now we are based on 49
  While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

  Ideally we would query oxide for this dynamically.

  
  [Manual test case]
  Open the browser and browse to http://whatsmyua.com.
  Verify that the chromium version number in the UA string is a recent one (> 
50), and not the previously hardcoded value of "35.0.1870.2".

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

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


[Touch-packages] [Bug 1638301] Re: systemctl start auto-completion it's not working

2016-11-04 Thread Martin Pitt
Please clarify -- I do get the warning about network1.busname, but
completion is still working:

$ systemctl start Unit org.freedesktop.network1.busname could
not be found.

Display all 131 possibilities? (y or n)
alsa-state.service  pppd-dns.service


** Changed in: systemd (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  systemctl start  auto-completion it's not working

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When i try to auto-complete the "systemctl start " the
  following error message is shown in bash:

  Unit org.freedesktop.network1.busname could not be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:42:37 2016
  InstallationDate: Installed on 2015-06-20 (499 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell System Vostro 3450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory 
swapaccount=1 quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GG0VM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Vostro 3450
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1639233] [NEW] date setting takes much time to open from indicator-datetime

2016-11-04 Thread Victor gonzalez
Public bug reported:

Environment:

current build number: 75
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-11-04 10:44:56
version version: 75
version ubuntu: 20161104
version device: 20161014.0
version custom: 20161104

Steps to reproduce:

1º Go to quick settings bar and drag down from the time icon
2º Press over the date & time settings

Current result: date & time setting is displayed after 20 seconds or so

Expected result: date & time settings should be opened faster

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  date setting takes much time to open from indicator-datetime

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Environment:

  current build number: 75
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-04 10:44:56
  version version: 75
  version ubuntu: 20161104
  version device: 20161014.0
  version custom: 20161104

  Steps to reproduce:

  1º Go to quick settings bar and drag down from the time icon
  2º Press over the date & time settings

  Current result: date & time setting is displayed after 20 seconds or
  so

  Expected result: date & time settings should be opened faster

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

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


[Touch-packages] [Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread John McAleely
** 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 qtmultimedia-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1630399

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  In Progress
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

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

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


[Touch-packages] [Bug 1639270] Re: Hard coded paths prevent usage in snaps

2016-11-04 Thread Michael Sheldon
** Patch added: "use_presage_prefix_path_in_default_profile.patch"
   
https://bugs.launchpad.net/ubuntu/+source/presage/+bug/1639270/+attachment/4772499/+files/use_presage_prefix_path_in_default_profile.patch

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

Title:
  Hard coded paths prevent usage in snaps

Status in presage package in Ubuntu:
  New

Bug description:
  Presage currently defines a number of paths at compile time,
  preventing it from working correctly in snap packages.

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

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


[Touch-packages] [Bug 1639270] [NEW] Hard coded paths prevent usage in snaps

2016-11-04 Thread Michael Sheldon
Public bug reported:

Presage currently defines a number of paths at compile time, preventing
it from working correctly in snap packages.

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

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

Title:
  Hard coded paths prevent usage in snaps

Status in presage package in Ubuntu:
  New

Bug description:
  Presage currently defines a number of paths at compile time,
  preventing it from working correctly in snap packages.

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

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


[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Kyle Nitzsche
Dave - thanks.

My guess is this has nothing to do with the Today scope.

I guess is that there is something in the plumbing that does not handle
losing a network during a fresh - so I am glad that Michi is aware.

Regarding network, I wrote and attached here a test scope that displays
the scopes current understanding of the network status twice, the second
time is after waiting 10 seconds.

The code is here: lp:~knitzsche/+junk/test-network-dynamic-enum

I find that the unity::scopes::QueryMetadata::ConnectivityStatus is
wrong much of the time. It is often Unknown for example, whereas I have
been sitting here at my desk with connected wifi all along.


** Attachment added: "knitzsche.testscope-network_0.1_armhf.click"
   
https://bugs.launchpad.net/today-scope/+bug/1637841/+attachment/4772462/+files/knitzsche.testscope-network_0.1_armhf.click

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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


[Touch-packages] [Bug 1639278] [NEW] package systemd 229-4ubuntu12 failed to install/upgrade: los disparadores han entrado en bucle, abandonando

2016-11-04 Thread grpc22
Public bug reported:

A simple Update/Upgrade show this error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu12
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Nov  4 10:24:14 2016
ErrorMessage: los disparadores han entrado en bucle, abandonando
InstallationDate: Installed on 2015-04-27 (556 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Precision T7600
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=bd28a4c9-f184-4e24-978d-25870ad3d50b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu12 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
UpgradeStatus: Upgraded to xenial on 2016-05-07 (180 days ago)
dmi.bios.date: 08/09/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 082WXT
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/09/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA03:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T7600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package need-duplicate-check package-from-proposed 
third-party-packages xenial

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

Title:
  package systemd 229-4ubuntu12 failed to install/upgrade: los
  disparadores han entrado en bucle, abandonando

Status in systemd package in Ubuntu:
  New

Bug description:
  A simple Update/Upgrade show this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  4 10:24:14 2016
  ErrorMessage: los disparadores han entrado en bucle, abandonando
  InstallationDate: Installed on 2015-04-27 (556 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision T7600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=bd28a4c9-f184-4e24-978d-25870ad3d50b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu12 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (180 days ago)
  dmi.bios.date: 08/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/09/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA03:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

2016-11-04 Thread Devid Antonio Filoni
@Alfonso: thank you, I'll test it once I'm back at home. Please note: in
my qtmultimedia patch I haven't added gstreamer0.10-opus package as
depencency so it needs to be installed on devices (I don't know how
packages selection works in phone).

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  In Progress
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

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

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


[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap

2016-11-04 Thread Paweł Stołowski
A quickfix in the shell plugin may fix it for the initial approach
(scopes in same snap as the shell), but it gets more complicated when
scopes are in separate snaps.

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

Title:
  Result art not displayed when run in a snap

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

Bug description:
  When a scope calls result.set_art() the path is not adjusted to take
  in consideration $SNAP.

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

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


[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-04 Thread Michael Sheldon
** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network 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:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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


[Touch-packages] [Bug 1639251] Re: Presage crashes if /etc/presage.xml is unavailable

2016-11-04 Thread Ubuntu Foundations Team Bug Bot
The attachment "add-missing-online-learning-configuration-value.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Presage crashes if /etc/presage.xml is unavailable

Status in presage package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

   1. Delete /etc/presage.xml

   2. Run presage

  Expected result:

   Presage should use its default profile and run as normal

  Actual result:

   Presage crashes because the ONLINE_LEARNING configuration value is
  missing from the default profile.

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

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


[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap

2016-11-04 Thread Paweł Stołowski
I haven't tested the attached branch yet; let's coordinate that since I
think you're working with a silo on all this.

** Branch linked: lp:~stolowski/unity-scopes-shell/art-uri-snap-root

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

Title:
  Result art not displayed when run in a snap

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

Bug description:
  When a scope calls result.set_art() the path is not adjusted to take
  in consideration $SNAP.

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

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


[Touch-packages] [Bug 1639297] Re: Hard coded paths prevent usage in snaps

2016-11-04 Thread Michael Sheldon
** Patch added: "0016-set-plugin-path-from-environment.patch"
   
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1639297/+attachment/4772534/+files/0016-set-plugin-path-from-environment.patch

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

Title:
  Hard coded paths prevent usage in snaps

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  A number of paths are defined at compile time which instead need to be
  set dynamically at run time to allow for usage in snaps.

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

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


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

2016-11-04 Thread Matthias Seidel
This is clearly a regression.

The boot process has to be quit if no errors are found. Otherwise it
confuses the user!

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

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

Status in upstart package in Ubuntu:
  Invalid

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

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

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

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

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

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

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


[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial

2016-11-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/snap

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

Title:
  keyboard does not show up on xenial

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:

  Install ubuntu-keyboard, run maliit-server, click on place to enter
  text -> keyboard shows up.

  What happens:

  Running maliit-server after installing ubuntu-keyboard-english in
  terminal shows following error:

  WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const
  QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is
  not enabled

  Clicking on fields for entering text, does not cause the keyboard to
  show up.

  What I tried so far:

  export QT_IM_MODULE=Maliit
  export GTK_IM_MODULE=Maliit

  and

  gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled 
"[llibubuntu-keyboard-plugin.so,en_gb]"
  gconftool-2 -s --type list --list-type string /maliit/onscreen/active 
"[libubuntu-keyboard-plugin.so,en_gb]"

  according to

  https://github.com/maliit/framework

  and

  https://github.com/maliit/plugins

  but it still won't show up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 18:03:03 2016
  InstallationDate: Installed on 2016-04-03 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.maliit.org.server.conf: [modified]
  mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195

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

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


[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-04 Thread Michael Sheldon
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/snap

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Committed
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network 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:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  Fix Released
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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


[Touch-packages] [Bug 1639270] Re: Hard coded paths prevent usage in snaps

2016-11-04 Thread Ubuntu Foundations Team Bug Bot
The attachment "use_presage_prefix_path_in_default_profile.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Hard coded paths prevent usage in snaps

Status in presage package in Ubuntu:
  New

Bug description:
  Presage currently defines a number of paths at compile time,
  preventing it from working correctly in snap packages.

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

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


[Touch-packages] [Bug 1639297] [NEW] Hard coded paths prevent usage in snaps

2016-11-04 Thread Michael Sheldon
Public bug reported:

A number of paths are defined at compile time which instead need to be
set dynamically at run time to allow for usage in snaps.

** Affects: maliit-framework (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Hard coded paths prevent usage in snaps

Status in maliit-framework package in Ubuntu:
  New

Bug description:
  A number of paths are defined at compile time which instead need to be
  set dynamically at run time to allow for usage in snaps.

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

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


[Touch-packages] [Bug 1639249] Re: Result art not displayed when run in a snap

2016-11-04 Thread Paweł Stołowski
** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Paweł Stołowski (stolowski)

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

Title:
  Result art not displayed when run in a snap

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

Bug description:
  When a scope calls result.set_art() the path is not adjusted to take
  in consideration $SNAP.

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

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


[Touch-packages] [Bug 1637841] Re: Today scope refresh not always working on MX4 with OTA 13

2016-11-04 Thread Dave H
Hi Kyle,

Thanks for the Test scope. I installed it and found a similar result to
you. If you keep repeating the refresh every 30s (ten times in my case)
you get a mixed result.

1. 1 unknown / 2 unknown

2. 1 unknown / 2 unknown

3. 1 connected / 2 unknown  (after pull refresh in Today scope and
recheck Test scope)

4. 1 connected / 2 unknown

5. 1 unknown / 2 unknown

6. 1 connected / 2 unknown

7. 1 unknown / 2 unknown

8. 1 unknown / 2 unknown

9. 1 connected / 2 unknown

10. 1 unknown / 2 unknown

See picture attached (for 1 connected / 2 unknown)

If you need me to try anything else let me know.

Regards

Dave H


** Attachment added: "Test scope result.png"
   
https://bugs.launchpad.net/today-scope/+bug/1637841/+attachment/4772502/+files/Test%20scope%20result.png

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

Title:
  Today scope refresh not always working on MX4 with OTA 13

Status in Today Scope:
  Incomplete
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Hi I am using the Meizu MX4 with OTA-13 installed. Sometimes with weak
  or no wifi the today scope is messed up, in the same way as the below
  report I found for the BQE4.5. If you try to refresh it the problem is
  not resolved (such as only half the date shown, or no date or no
  pictures). Even after returning to a good wifi signal and performing
  the pulldown refresh the problem is not resolved. As I have seen this
  problem from the start on older OTA versions (I have reported before),
  my feeling is there is a fundamental problem with the way scopes are
  refreshed when you pull down the screen. I have also screen the "no
  pictures" on other scopes and the refresh not working, could this be a
  common scope problem and nothing to do with the today scope?.

  Note, when the today scope is messed up if you un-tick the "day info"
  then refresh and then tick day info again, this sometimes helps. If no
  pictures displayed (today and other scopes) I normally have to reset
  the phone to correct the problem.

  Your support us appreciated,

  Regards

  Dave H

  Similar bug (BQE4.5 & OTA9)

  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1637841/+subscriptions

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


[Touch-packages] [Bug 1460458] Re: [system settings] Dual Sim; no possibility to switch on or off each sim card completely.

2016-11-04 Thread Peter Bittner
Nobody assigned to this, and back to backlog?  :-(

This is a valuable feature for dual-SIM phones. Really not an optional
nice-to-have. I'd love to see this being assigned to a milestone again.

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

Title:
  [system settings] Dual Sim; no possibility to switch on or off each
  sim card completely.

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If two sim cards is used there is no possibility to switch each sim card on 
or off completely
  (to completely activate or deactivate sim 1 and sim 2 separately).

  Sim 1 and sim 2 inside:
  Often I do not want to use both sim cards at the same time.
  Sometimes it's needed that only sim 1 is active.
  Sometimes it's needed that only sim 2 is active.
  Sometimes it's needed that sim 1 and sim 2 is active.

  So there should be the possibility to completely activate/deactivate sim 1 
and sim 2 separately.
  Would be nice in the context menu of the network indicator,
  an on/off switch for sim1 and sim2.
  Or at least in systemsettings.

  Bq Aquaris E4.5
  Ubuntu 14.10 (r22)

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

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


[Touch-packages] [Bug 1637663] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-11-04 Thread Harold
I get the same issue in 16.04 with ntp version ntp_1%3a4.2.8p4+dfsg-
3ubuntu5.3_amd64.deb

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

Title:
  package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  root@ntp-srv001:~# apt-get install ntp
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  ntp is already the newest version.
  0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@ntp-srv001:~#

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 28 15:24:45 2016
  DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.10:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 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/ntp/+bug/1637663/+subscriptions

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


[Touch-packages] [Bug 1637663] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  root@ntp-srv001:~# apt-get install ntp
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  ntp is already the newest version.
  0 upgraded, 0 newly installed, 0 to remove and 86 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up ntp (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
  dpkg: error processing package ntp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@ntp-srv001:~#

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 28 15:24:45 2016
  DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.10:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-28 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 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/ntp/+bug/1637663/+subscriptions

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


[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

2016-11-04 Thread Heinrich Hartl
systemctl restart-failed ntp # was no help
# However after 
systemctl stop ntp # changes status active (exited) to inactive (dead)
systemctl start ntp # succeeds.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

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


[Touch-packages] [Bug 1637801] Re: Incorrect Russian translation of "apt list --upgradeable" results

2016-11-04 Thread Gunnar Hjalmarsson
On 2016-11-04 10:01, Julian Andres Klode wrote:
> I want the ability to have translations in apt prefer those from the
> langpack,

I suppose it would be possible to special case apt in Ubuntu by patching
bindtextdomain() in apt-pkg/init.cc. Not able to tell if it's a good
idea.

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

Title:
  Incorrect Russian translation of "apt list --upgradeable" results

Status in Ubuntu Translations:
  Invalid
Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  bor@bor-Latitude-E5450:~$ apt list --upgradeable
  Вывод списка… Готово
  build/неизвестно 20161025 all [может быть обновлён до: 20151105]

  In Russian this means "version 20161025 can be upgraded TO version
  20151105)

  While original English says exactly opposite:

  bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable
  Listing... Done
  build/unknown 20161025 all [upgradable from: 20151105]

  Literal translation (that does not require serious phrase change)
  would probably be

  "может быть обновлен с"

  although it sounds also artificial, as in Russian subject is package
  that is being updated (currently installed), not new version.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1
  Uname: Linux 4.8.0-25-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 30 09:39:47 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (485 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago)

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

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


[Touch-packages] [Bug 1629782] Re: Hotspot crashes the device and reboots

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  Hotspot crashes the device and reboots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  The device hangs and reboots after some tasks related to hotspot.

  There are a couple of ways that this bug occurred.

  1. While the hotspot is on, try to change hotspot settings like
  requiring passwords. Upon clicking the Change button, the bug occurs.
  (happens always)

  2. Turning on the hotspot from the settings app while the wifi is off
  the bug occurs. (happened once)

  
  Not sure what log will be helpful. Please let me know and I'll attach them.

  Device:
  bq E5 HD (OTA 13)

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

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


[Touch-packages] [Bug 1639208] Re: The app store button is hardcoded to the Click Store scope

2016-11-04 Thread Rodney Dawes
Can we instead just get rid of this icon in the manage dash view? Or at
least just hide it for now?

The complexity of handling the either/or situation is too great I think,
and there are already so many other ways to get to the store anyway.
Right now, the store scope also appears in the list of scopes in the
manage dash view anyway, so this is just duplicating something already
in the list. Then the apps scope has the big icon to go to the store. My
understanding is that the new app drawer design also has yet another
hard-coded visual element to open the store, which I think shouldn't be
there.

When we switch to having an app for the store, we can look at
implementing a URL handler for store:/// as well, but I don't think we
should be doing that for the snappy scope and click scope.

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

Title:
  The app store button is hardcoded to the Click Store scope

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Clicking the app store icon in the Manage Dash view should activate
  whichever store is default on the system. E.g. Click Store scope on V,
  Snappy Store scope on X, and the Snappy Store app on Y+.

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

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


[Touch-packages] [Bug 1589149] Re: the two Hotspots buttons seem to disagree

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

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

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


[Touch-packages] [Bug 1618007] Re: Invalid property assignment in ActivityIndicatorStyle.qml

2016-11-04 Thread Pat McGowan
can we cherry pick this regression fix?

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

Title:
  Invalid property assignment in ActivityIndicatorStyle.qml

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  I get

  file:///usr/lib/x86_64-linux-
  
gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24
  Invalid property assignment: "implicitHeight" is a read-only property

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

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


[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => x1

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

  -

  Per the comments the .config/connectivity-service/config.ini file
  seems to hold bad or outdated info and needs to be manually deleted
  and then recreated by the service.

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

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


[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => backlog

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

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

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


[Touch-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP

2016-11-04 Thread Pat McGowan
pending feedback from the system enablement team whether we fix or not

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

** Tags added: bq

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

Title:
  Wifi doesn't reconnect to AP if it uses the same SSID than another AP

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  current build number: 68
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-24 08:00:20
  version version: 68
  version ubuntu: 20150724
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  My ISP (Free in France) provides a hotspot service so that customers
  can use the connection of any other customer using a generic open Wifi
  connection (for reference http://www.free.fr/assistance/2303.html - in
  French)

  The SSID is called 'FreeWifi' on all the boxes but obviously APs are
  all different since it's customers' DSL routers.

  When I connect  to one of this access point, suspend the phone and
  resume it in another location where the SSID is available but from a
  different AP, the phone doesn't connect to this AP and the list of
  networks in the network-indicator doesn't refresh and still show the
  list of network from the previous location. I have to forget the
  network called 'FreeWifi' and reconnect in order to refresh the list
  and make it work.

  It's 100% reproducible.

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

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


[Touch-packages] [Bug 1598584] Re: wifi slows to a crawl when bluetooth is enabled

2016-11-04 Thread Pat McGowan
over to qa for testing

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Jean-Baptiste Lallement (jibel)

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

Title:
  wifi slows to a crawl when bluetooth is enabled

Status in arale:
  New
Status in Canonical System Image:
  In Progress
Status in frieza:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

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

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


[Touch-packages] [Bug 1576989] Re: stale lock files freeze apps

2016-11-04 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: 14 => x1

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

Title:
  stale lock files freeze apps

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

Bug description:
  Debugging why the Notes app would freeze for some people, I found
  there were some stale .lock files around. Those .lock files are
  autocreated by QSettings (with QLockFile) when this file is edited.
  Problem is, that it sometimes seems to happen that the app is
  suspended by our lifecycle and then killed (either by closing from
  spread or OOM killed) and those .lock files stick around. I have
  implemented a workaround in the notes app[1] to clear up those stale
  locks when the app starts app, however, today I ran twice in a row
  into the issue that the very same happened to music app. It would just
  freeze on startup and never come back. Digging around a bit I found
  such a stale lock file on its config file which is created with the
  QML Settings element. This implies that every app using QSettings or
  QML Settings {} are potentially affected. I suspect many more app
  freezes can be traced down to this.

  Now, there is some code in Qt to detect stale lock files [2], however,
  not sure why it doesn't detect those lock files as stale ones and
  decides to wait on them forever though. Probably a bug in the code or
  some of the wrong #ifdefs are triggered for our package builds.

  [1] 
https://code.launchpad.net/~mzanetti/reminders-app/remove-stale-lock-files/+merge/293355
  [2] 
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qlockfile_unix.cpp

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

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


[Touch-packages] [Bug 1637996] Re: app switcher not responsive

2016-11-04 Thread Pat McGowan
Confirmed comment #3 that a browser instance triggers the issue

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

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

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => 14

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Description changed:

  MX4 running 451
  
  After some period of use, the switched frequently becomes unresponsive,
  either it does not reveal right away on a right edge gesture, or when
  revealed selecting an app does nothing for some seconds. When in this
  state it is inconsistent, will work a few times, then not work.
  
  This regressed with the new implementation.
+ 
+ It does seem to require that the browser or a webapp is open. I cannot
+ reproduce it otherwise.

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

Title:
  app switcher not responsive

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

Bug description:
  MX4 running 451

  After some period of use, the switched frequently becomes
  unresponsive, either it does not reveal right away on a right edge
  gesture, or when revealed selecting an app does nothing for some
  seconds. When in this state it is inconsistent, will work a few times,
  then not work.

  This regressed with the new implementation.

  It does seem to require that the browser or a webapp is open. I cannot
  reproduce it otherwise.

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

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


[Touch-packages] [Bug 1639314] [NEW] webbrowser app crashes saving an image in Xenial

2016-11-04 Thread Víctor R . Ruiz
Public bug reported:

Test case.
- Open webbrowser app
- Go to http://apod.nasa.gov/
- Long tap on the image.
- Tap to save the image.

Expected result.
- Image can be saved locally.

Actual result.
- Webbrowser app freezes and crashes.

current build number: 75
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu

I see no webbrowser-app crash files in /var/crash. In the logs I see
this (not sure whether it's related):

libpng error: Read Error
propsReply "An AppArmor policy prevents this sender from sending this message 
to this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 
comm=\"webbrowser-app \") interface=\"org.freedesktop.DBus.Properties\" 
member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 
comm=\"/usr/sbin/NetworkManager --no-daemon \")"
nmReply "An AppArmor policy prevents this sender from sending this message to 
this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 
comm=\"webbrowser-app \") interface=\"org.freedesktop.NetworkManager\" 
member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 
comm=\"/usr/sbin/NetworkManager --no-daemon \")"
"Object path cannot be empty"
[1104/161741:ERROR:object_proxy.cc(583)] Failed to call method: 
org.freedesktop.ScreenSaver.Inhibit: object_path= /org/freedesktop/ScreenSaver: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.7787" (uid=32011 pid=6867 comm="webbrowser-app ") 
interface="org.freedesktop.ScreenSaver" member="Inhibit" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.ScreenSaver" (uid=32011 
pid=2691 comm="unity8 --mode=full-greeter ")

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


** Tags: qa-silo

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

Title:
  webbrowser app crashes saving an image in Xenial

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Test case.
  - Open webbrowser app
  - Go to http://apod.nasa.gov/
  - Long tap on the image.
  - Tap to save the image.

  Expected result.
  - Image can be saved locally.

  Actual result.
  - Webbrowser app freezes and crashes.

  current build number: 75
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  I see no webbrowser-app crash files in /var/crash. In the logs I see
  this (not sure whether it's related):

  libpng error: Read Error
  propsReply "An AppArmor policy prevents this sender from sending this message 
to this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 
comm=\"webbrowser-app \") interface=\"org.freedesktop.DBus.Properties\" 
member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 
comm=\"/usr/sbin/NetworkManager --no-daemon \")"
  nmReply "An AppArmor policy prevents this sender from sending this message to 
this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 
comm=\"webbrowser-app \") interface=\"org.freedesktop.NetworkManager\" 
member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" 
destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 
comm=\"/usr/sbin/NetworkManager --no-daemon \")"
  "Object path cannot be empty"
  [1104/161741:ERROR:object_proxy.cc(583)] Failed to call method: 
org.freedesktop.ScreenSaver.Inhibit: object_path= /org/freedesktop/ScreenSaver: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.7787" (uid=32011 pid=6867 comm="webbrowser-app ") 
interface="org.freedesktop.ScreenSaver" member="Inhibit" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.ScreenSaver" (uid=32011 
pid=2691 comm="unity8 --mode=full-greeter ")

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

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


[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

2016-11-04 Thread Sam Gleske
This issue has been resolved after working with upstream maintainers.

See https://gitlab.com/gnutls/gnutls/issues/145

For the resolution see
https://github.com/libimobiledevice/libimobiledevice/issues/413

** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #413
   https://github.com/libimobiledevice/libimobiledevice/issues/413

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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


[Touch-packages] [Bug 1639318] [NEW] package python2.7 2.7.12-1~16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2016-11-04 Thread marcos
Public bug reported:

atualização

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python2.7 2.7.12-1~16.04
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Fri Nov  4 14:50:53 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: python2.7
Title: package python2.7 2.7.12-1~16.04 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package python2.7 2.7.12-1~16.04 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in python2.7 package in Ubuntu:
  New

Bug description:
  atualização

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python2.7 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Nov  4 14:50:53 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: python2.7
  Title: package python2.7 2.7.12-1~16.04 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1639318/+subscriptions

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


[Touch-packages] [Bug 1289047] Re: [Trusty] hostapd package is broken

2016-11-04 Thread kenn
It's unbelievable to see that the buggy package ist still in repo and no
fix has proposed yet!

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

Title:
  [Trusty] hostapd package is broken

Status in One Hundred Papercuts:
  Triaged
Status in wpa package in Ubuntu:
  Triaged

Bug description:
  When trying to create an access point, I am met with a fatal error
  with hostapd:

  nl80211: Could not configure driver mode
  nl80211 driver initialization failed.
  hostapd_free_hapd_data: Interface wlan0 wasn't started

  What worked before no longer works today after a package upgrade.

  After installing hostapd deb from Ubuntu 13.10, it works.

  WORKAROUND: For this to persist through reboots, execute the following in a 
terminal:
  sudo nano /etc/NetworkManager/NetworkManager.conf

  Add the following entry where the x's are replaced with your WiFi MAC 
address, save, and then reboot:
  [keyfile]
  unmanaged-devices=mac:xx:xx:xx:xx:xx:xx

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hostapd 1:2.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc5-lowlatency x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Thu Mar  6 16:57:20 2014
  InstallationDate: Installed on 2014-02-01 (33 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1589149] Re: the two Hotspots buttons seem to disagree

2016-11-04 Thread Pat McGowan
per comment #15 I confirm that the hotspot may stay active even after
disabling it in each toggle, which is a more serious issue imo.

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

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

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

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


[Touch-packages] [Bug 1622987] Re: Auto-completion seems broken with umount command

2016-11-04 Thread Nairwolf
** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Auto-completion seems broken with umount command

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Xubuntu with the devel version. I've seen this bug with
  Ubuntu also, in the daily version.

  The auto-completion of the command 'umount' seems broken.

  I have an usb key called "Xubuntu 16.10 amd64". I verify that with the
  command lsblk.

  Then, I type 'umount /media' then I press 'tab' to have the
  autocompletion. With 16.04, the autocompletion completes correctly
  with backslash : "/media/nairwolf/\ Xubuntu\ amd64"

  But, now, with Yakkety, the autocompletion stops before the first
  space.

  There is a screenshot to explain what I have :
  https://i.imgur.com/UOyUEyn.png

  Don't forget that I'm typing only "umount /media", and then, I press
  tab to have the autocompletion. And this picture is the result of the
  auto-completion.

  I'm unable to reproduce that with other basic command like "ls", "cd"
  or "rm". That means if I'm typing "ls /media", then "TAB" it will be
  completed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: util-linux 2.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 13 13:07:22 2016
  InstallationDate: Installed on 2016-08-18 (25 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


<    1   2