date:20170223

There are also allocations for mysql, ceph and others.
Is libvirt just the one installed on a system with a gui more commonly?
At least mysql should have some footprint ...


Hmm I just checked mysql despite being allocated at 64001 becomes a <1000 
number on install.
So that is no good example.

But I found that ceph is using its:
$ id ceph
uid=64045(ceph) gid=64045(ceph) groups=64045(ceph)

Probably for a similar reason as libvirt - to stay consistent across nodes.
I'll check if they show up as well ...

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

Title:
  Libvirt Qemu appears in the list of users in Ligthdm and user
  switecher

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher

I currently only have a KDE/sddm system and there ceph does not show up there.
I'll get access to another system later today and check there for ceph - maybe 
we can learn the trick from it how to hide.

Maybe I can spawn a new 16.04.2 default ISO to test locally sooner.

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

Title:
  Libvirt Qemu appears in the list of users in Ligthdm and user
  switecher

Status in base-passwd package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher

Note: this is only affecting new installs, as he update keeps the old
UID. So if there was a libvirt user it stays as-is.

Ok,
new guest, after installing the software I have several high User IDs:
libvirt-qemu @ 64055
ceph @ 64045

I see, it is "just the same" for ceph.
So it might be a more widespread generic issue that has no solution yet, but 
libvirt just has more exposure on UI based systems to be noticed faster?


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

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

Title:
  Libvirt Qemu appears in the list of users in Ligthdm and user
  switecher

Status in base-passwd package in Ubuntu:
  New
Status in ceph package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes

2017-02-23 Thread Alexandros Frantzis

Could you please attach /var/log/repowerd.log at the time of the issue.

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 5 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in repowerd:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher

** Attachment added: "example of high user ids visible"
   
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1667113/+attachment/4825074/+files/base-passswd-high-sys-users-visible.png

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

Title:
  Libvirt Qemu appears in the list of users in Ligthdm and user
  switecher

Status in base-passwd package in Ubuntu:
  New
Status in ceph package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667247] [NEW] NetworkManager stops working until re-run

2017-02-23 Thread Aleksei

Public bug reported:

after awake from sleep(open my lenovo laptop lid) network manager shows
- it is connected to one of wi-fi's networks (not mine) - switching
on\off wifi, networking service doesn't help.

Here is workaround: 
ps -Af | grep -i networkmanager (write down the pid)
sudo kill pid
sudo /usr/sbin/NetworkManager --no-daemon

It happens time to time when awake after sleep

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
Uname: Linux 4.4.23-040423-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 23 11:57:58 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-12-17 (433 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
beeline-198  242d5038-e875-4c07-b0ec-ba6fc4470e24  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
----
 
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  NetworkManager stops working until re-run

Status in network-manager package in Ubuntu:
  New

Bug description:
  after awake from sleep(open my lenovo laptop lid) network manager
  shows - it is connected to one of wi-fi's networks (not mine) -
  switching on\off wifi, networking service doesn't help.

  Here is workaround: 
  ps -Af | grep -i networkmanager (write down the pid)
  sudo kill pid
  sudo /usr/sbin/NetworkManager --no-daemon

  It happens time to time when awake after sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  Uname: Linux 4.4.23-040423-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:57:58 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
beeline-198  242d5038-e875-4c07-b0ec-ba6fc4470e24  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

[Touch-packages] [Bug 1667247] Re: NetworkManager stops working until re-run

2017-02-23 Thread Aleksei

+sometimes display's brightness is too dark when awake after sleep - needs to 
be altered manually
I know it is different bug - but, however)

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

Title:
  NetworkManager stops working until re-run

Status in network-manager package in Ubuntu:
  New

Bug description:
  after awake from sleep(open my lenovo laptop lid) network manager
  shows - it is connected to one of wi-fi's networks (not mine) -
  switching on\off wifi, networking service doesn't help.

  Here is workaround: 
  ps -Af | grep -i networkmanager (write down the pid)
  sudo kill pid
  sudo /usr/sbin/NetworkManager --no-daemon

  It happens time to time when awake after sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  Uname: Linux 4.4.23-040423-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:57:58 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
beeline-198  242d5038-e875-4c07-b0ec-ba6fc4470e24  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher

The user Objects have an attribute for system accounts:
property Boolean SystemAccount
Whether or not the account is a system account, such as adm. System accounts 
aren't returned by ListCachedUsers and should generally be ignored.

It also has a shell property, but that (by default) seems to have no impact on 
listCachedUsers
property String Shell, method SetShell(String path)
The user's login shell.

ListCachedUsers then is what is used by lightdm to fetch the list:
method ListCachedUsers()
returns: users: an array of paths for the user objects
Returns a subset of the users who exist, typically those who have logged in 
recently, for populating chooser lists such as those used by GDM's greeter.
Currently the accountsservice process scans /etc/passwd for users, filters out 
those with UID values which are below a threshold point to screen out system 
users, and sorts the rest by the number of times the users in question appear 
in /var/log/wtmp. Above a certain length, it's expected that the caller will 
disregard the list and present only an entry field. The entry field always 
needs to be available because we know that some results may be missing from 
this list.


Best API def I found so far is from sssd:
https://fedorahosted.org/sssd/wiki/DesignDocs/AccountsService

Call is from lightdm at load_users in common/user-list.c

This can be reproduced more easily by a direct dbus call:
$ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers


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

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

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

** Changed in: base-passwd (Ubuntu)
   Status: New => Invalid

** Summary changed:

- Libvirt Qemu appears in the list of users in Ligthdm and user switecher
+ System users appears in Ligthdm and user switcher (Accountsservice has no 
filter for shell types)

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  New
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few

2017-02-23 Thread Daniel van Vugt

** Summary changed:

- [gallium] EGL clients that saturate the GPU cause the Mir server to slow, 
freeze and stutter, showing very few frames
+ [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) 
that saturate the GPU cause the Mir server to slow, freeze and stutter, 
displaying very few frames

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

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

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

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

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

[Touch-packages] [Bug 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most
  restarts

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On the vast majority of restarts of Ubuntu 16.04 I get no internal
  sound at all.

  There are no reported issues in system settings on the only sound card
  I have. The volume is not muted.

  On an estimated 1 in 10 restart, the sound works, and both the test
  sounds get played and other applications work fine.

  There is no reported errors or messages on the restarts when the sound
  has failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 27 15:56:02 2016
  InstallationDate: Installed on 2015-10-29 (334 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  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.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

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

2017-02-23 Thread Simplehuman

#31, same problem also. As workaround for me - I just downgraded 
network-manager package to 1.4.4-1ubuntu1 . Downloaded it from here - 
https://launchpad.net/ubuntu/+source/network-manager/1.4.4-1ubuntu1/ and then 
sudo dpkg -i network-manager_1.4.4-1ubuntu1_amd64.deb . And blocked this 
version in Synaptic. Probably not the best solution, but the best that I could 
find for now and it works.
Bug is really critical for dayly use.

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

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

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

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

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

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

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

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

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

[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

So while I understand to unify code paths by relying on accoutnsservice
lightdm needs to get back the feature of "hidden-shells=" IMHO.

So in some sense this is a regression in lightdm due to the change to
use accountsservice.

The solution clearly extceeds my Dbus-foo, but shouldn't lightdm be able
to get back "hidden-shells" by implementing a filter on the "Shell"
property of each user that accountsservice provides?

Maybe this was discussed in the lightdm/accountsservice communities -
I'm not part of them and search engines didn't find it for me - but
given how often the question how to hid users came up I'd think some
discussion on the shell filtering might already exist.

Waiting for the expertise of the triagers of lightdm/accountsservice on
that bug now.

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  New
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-02-23 Thread Martin Pitt

Yes, there, see "man resolved.conf". But I'd recommend a separate file
to avoid changing the package-provided conffile:

sudo mkdir -p /etc/systemd/resolved.conf.d
printf "[Resolve]\nDNSSEC=no\n" | sudo tee 
/etc/systemd/resolved.conf.d/no-dnssec.conf

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

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

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

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

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

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

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

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

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

[Touch-packages] [Bug 1665727] Re: Window stuck in fullscreen mode

** Branch linked: lp:~fboucault/webbrowser-app/fix_fullscreen

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

Title:
  Window stuck in fullscreen mode

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Tested in unity8 deb session on xenial + overlay

  - Launcher set to always show in system-settings
  1) open youtube.com
  2) F11 to fullscreen browser
  3) play a video
  4) click fullscreen button to fullscreen video
  5) press esc, F11 or click the fullscreen button in bottom right to exist 
fullscreen
  6) Expected result: browser window still fullscreen, but esc or F11 should 
exist fullscreen 

  Actual result: browser window stuck in fullscreen, no way to exit it

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

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

2017-02-23 Thread Andrzej

I am having the same problem on updated Ubunut Mate 16.10 in Guake
Terminal and Mate Terminal. The error is showing after hitting tab after
typing "sudo systemctl start " so when system is looking for names of
systemd processes. The error is showing also when partial name has been
put like "sudo systemctl start ngi[TAB][TAB]"

-- 
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 shows error

Status in systemd package in Ubuntu:
  Fix Released

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

2017-02-23 Thread monte

Please try network-manager-1.2.6 from xenial-proposed, if you have
16.04. For me it seems to fix this bug. But when you will test don't
forget to turn off all self-made scripts to see if it really does the
job.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

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

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

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

[Touch-packages] [Bug 1664947] Re: [unity8] alt drag a child window doesn't work

I don't get those crashes with gtk applications.

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

Title:
  [unity8] alt drag a child window doesn't work

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

Bug description:
  ubuntu 17.04 unity8

  open a random app, tiled or kate or whatever, open a child window
  (help/about or whatever) and then try to move the window with alt left
  click, press alt left click inside the window and drag (move the
  mouse). it doesn't work. it does work with the main window

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

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

[Touch-packages] [Bug 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

I meant the child windows of those apps.

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

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

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

[Touch-packages] [Bug 1623383] Re: Some restarts fail due to missing base devices

2017-02-23 Thread Frank Heimes

Looks like this can happen on VM guests and KVM vms, too.
(could be somehow related to zfs ...)

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

Title:
  Some restarts fail due to missing base devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Arch: s390x
  Release: Yakkety / 16.10

  This happens on some (but not all) system starts with Yakkety. In
  Xenial (which is using the same 4.4 kernel version the Yakkety systems
  were using when the problem was first observed) this did not happen.
  The system (LPAR) this was seen first was an upgrade from Xenial but
  since then has been freshly installed with Yakkety. The same behaviour
  is seen on a zVM guest running Yakkety.

  The attached syslog shows a failed boot, followed by one that did work. Note 
the "Found device .*(sclp|encc00).*" messages in the good boot. Those are 
missing in the bad attempt and as a result networking and console fail to be 
usable. Also note, those boots were 4.8 kernels but we saw this with 4.4 
kernels, too.
  This might be a systemd problem / race, I just filed it into udev for now as 
that better matches the not finding basic devices symptom.

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

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

[Touch-packages] [Bug 1667284] [NEW] [unity8] can't drag child window back into main GUI

Public bug reported:

ubuntu 17.04 unity8. see the screenshot first.

install tiled (qt app) "apt install tiled"
launch tiled
in tiled you can move the gui elements arround, drag one of the tabs out of
main window "Mini-map" "Objects" "Tilesets" "Terrains" or whatever. it will
pop out of main window into a child window. now move the tab at the previous
position in the main window by drag and droping it. you can't because there is
no way to move or close the child window.

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

** Affects: ubuntu-ux
Importance: Undecided
Status: New

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

** Attachment added: "screenshot20170223_132304018.png"

https://bugs.launchpad.net/bugs/1667284/+attachment/4825157/+files/screenshot20170223_132304018.png

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

** Also affects: ubuntu-ux
Importance: Undecided
Status: New

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

Title:
[unity8] can't drag child window back into main GUI

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

Bug description:
ubuntu 17.04 unity8. see the screenshot first.

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

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

[Touch-packages] [Bug 1667284] Re: [unity8] can't drag child window back into main GUI

in unity7 the child window is dragable and i can put the window back,
see attached screenshot on unity7

** Attachment added: "u7.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667284/+attachment/4825158/+files/u7.png

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

Title:
  [unity8] can't drag child window back into main GUI

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

Bug description:
  ubuntu 17.04 unity8. see the screenshot first.

  install tiled (qt app) "apt install tiled"
  launch tiled
  in tiled you can move the gui elements arround, drag one of the tabs out of 
main window "Mini-map" "Objects" "Tilesets"  "Terrains" or whatever. it will 
pop out of main window into a child window. now move the tab at the previous 
position in the main window by drag and droping it. you can't because there is 
no way to move or close the child window.

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

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

[Touch-packages] [Bug 1667284] Re: [unity8] can't drag child window back into main GUI

looks like in u8 it's missing the "custom?" title bar?

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

Title:
  [unity8] can't drag child window back into main GUI

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

Bug description:
  ubuntu 17.04 unity8. see the screenshot first.

  install tiled (qt app) "apt install tiled"
  launch tiled
  in tiled you can move the gui elements arround, drag one of the tabs out of 
main window "Mini-map" "Objects" "Tilesets"  "Terrains" or whatever. it will 
pop out of main window into a child window. now move the tab at the previous 
position in the main window by drag and droping it. you can't because there is 
no way to move or close the child window.

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

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

[Touch-packages] [Bug 1664151] Re: [performance] unity8.log flooded with debug messages about cursor position and appearance

** Branch linked: lp:~dandrader/qtmir/reduceLogVerbosity

** Summary changed:

- [performance] unity8.log flooded with debug messages about cursor position 
and appearance
+ [performance] unity8.log flooded with debug messages about window position 
and cursor shape

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

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  [performance] unity8.log flooded with debug messages about window
  position and cursor shape

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  [performance] qtmir.surfaces messages about cursor position and
  appearance flood unity8.log when dragging a window, or when moving the
  cursor over some apps:

  [2017-02-13:14:03:45.132] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(577,109))
  [2017-02-13:14:03:45.140] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(580,109))
  [2017-02-13:14:03:45.148] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(582,109))
  [2017-02-13:14:03:45.148] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(582,107))
  [2017-02-13:14:03:45.162] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(586,107))
  [2017-02-13:14:03:45.164] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(588,107))
  [2017-02-13:14:03:45.172] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(591,107))
  [2017-02-13:14:03:45.180] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(593,107))
  [2017-02-13:14:03:45.188] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(595,107))
  [2017-02-13:14:03:45.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(597,107))
  [2017-02-13:14:03:45.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(597,108))
  [2017-02-13:14:03:45.204] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(599,108))
  [2017-02-13:14:03:45.220] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(601,108))
  [2017-02-13:14:03:45.279] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setRequestedPosition(QPoint(602,108))
  [2017-02-13:14:03:53.564] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.572] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.604] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.612] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.620] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:53.628] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.916] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.972] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:54.988] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.012] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.044] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.100] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.156] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)
  [2017-02-13:14:03:55.196] qtmir.surfaces: 
MirSurface[0x5562bca913b0,"unity8-dash"]::setCursor(Arrow)

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

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

[Touch-packages] [Bug 1657215] Re: "Highlighting" submenu in Kate is shown empty

2017-02-23 Thread Albert Astals Cid

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

** This bug has been marked a duplicate of bug 1664578
   Menus that fill themselves on QMenu::aboutToShow don't work

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

Title:
  "Highlighting" submenu in Kate is shown empty

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch Kate
  - Click on "Tools" menu
  - Click on "Highlighting" menu item

  Expected outcome:
  - A submenu with around 11 items is shown

  Actual outcome:
  - An empty submenu is shown

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

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

[Touch-packages] [Bug 1657215] Re: "Highlighting" submenu in Kate is shown empty

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

** Changed in: unity8 (Ubuntu)
 Assignee: Nick Dedekind (nick-dedekind) => (unassigned)

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

Title:
  "Highlighting" submenu in Kate is shown empty

Status in unity8 package in Ubuntu:
  New

Bug description:
  - Launch Kate
  - Click on "Tools" menu
  - Click on "Highlighting" menu item

  Expected outcome:
  - A submenu with around 11 items is shown

  Actual outcome:
  - An empty submenu is shown

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

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

[Touch-packages] [Bug 1589975] Re: Ubuntu 16.04 has Networking problems

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

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

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1427663] Re: No padding on right side of Header

2017-02-23 Thread Adnane Belmadiaf

I guess this is has been fixed with the new redesign.

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

Title:
  No padding on right side of Header

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  When there's text at the right edge of the Header there's no padding/
  spacing/ margin at all, which is especially visible with a RTL locale
  such as Hebrew.

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

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

[Touch-packages] [Bug 1667311] [NEW] gdebi also tries to use debian/control file as debian archive

2017-02-23 Thread Fabian Niepelt

Public bug reported:

Hello,

we are using gdebi to install the build dependencies of packages we are 
building for internal use.
Parsing the debian/control file and installing the listed dependencies works 
fine. However, gdebi also tries to use the control file as a debian archive 
resulting in an error and non-zero exit status:

root@fabian-ubuntu-vm:/home/fabian/UbuntuPackages# LANG=C gdebi 
foobar/debian/control
Reading package lists... Done
Building dependency tree
Reading state information... Done
Requires the installation of the following packages: apache2 

Install Build-Dependencies for source package 'foobar' that builds

Do you want to install the software package? [y/N]:y
[Build Dependencies being successfully installed here]
dpkg-deb: error: 'foobar/debian/control' is not a debian format archive
dpkg: error processing archive foobar/debian/control (--install):
 subprocess dpkg-deb --control returned error exit status 2
Errors were encountered while processing:
 foobar/debian/control
root@fabian-ubuntu-vm:/home/fabian/UbuntuPackages# echo $?
1

Greetings,
Fabian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gdebi-core 0.9.5.7ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Feb 23 15:08:40 2017
InstallationDate: Installed on 2017-02-23 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  gdebi also tries to use debian/control file as debian archive

Status in gdebi package in Ubuntu:
  New

Bug description:
  Hello,

  we are using gdebi to install the build dependencies of packages we are 
building for internal use.
  Parsing the debian/control file and installing the listed dependencies works 
fine. However, gdebi also tries to use the control file as a debian archive 
resulting in an error and non-zero exit status:

  root@fabian-ubuntu-vm:/home/fabian/UbuntuPackages# LANG=C gdebi 
foobar/debian/control
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Requires the installation of the following packages: apache2 

  Install Build-Dependencies for source package 'foobar' that builds

  Do you want to install the software package? [y/N]:y
  [Build Dependencies being successfully installed here]
  dpkg-deb: error: 'foobar/debian/control' is not a debian format archive
  dpkg: error processing archive foobar/debian/control (--install):
   subprocess dpkg-deb --control returned error exit status 2
  Errors were encountered while processing:
   foobar/debian/control
  root@fabian-ubuntu-vm:/home/fabian/UbuntuPackages# echo $?
  1

  Greetings,
  Fabian

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdebi-core 0.9.5.7ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Feb 23 15:08:40 2017
  InstallationDate: Installed on 2017-02-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1263198] Re: Browser only shows on left part of screen

2017-02-23 Thread Florian Boucault

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

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

Title:
  Browser only shows on left part of screen

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The screen is approximately 217 mm wide. Between 146 mm and 150 mm
  there is a black bar. The browswer is only displayed to the left of
  the bar, the screen to the right of the bar is blank (white). Gestures
  on the right (blank) side can affect the left side: sweeping the page
  up or down, for example.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: webbrowser-app 0.22+14.04.20131107-0ubuntu1
  Uname: Linux 3.4.0-4-manta armv7l
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: armhf
  Date: Fri Dec 20 11:25:50 2013
  InstallationDate: Installed on 2013-12-20 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131220)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1665655] Re: Scrolling over addressbar shouldn't scroll webview

2017-02-23 Thread Florian Boucault

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

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

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

Title:
  Scrolling over addressbar shouldn't scroll webview

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Move mouse pointer to addressbar (over the text entry).
  2) Use the scroll wheel.

  What should happen:

  Nothing

  What happens:

  The webview content scrolls

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

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

[Touch-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

2017-02-23 Thread Thadeu Lima de Souza Cascardo

** No longer affects: tor (Ubuntu)

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in tor package in Ubuntu:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

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

[Touch-packages] [Bug 1648143] Missing required logs.

2017-02-23 Thread Brad Figg

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1648143

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in tor package in Ubuntu:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

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

[Touch-packages] [Bug 1661030] Re: regession tests failing after stackprofile test is run

2017-02-23 Thread Thadeu Lima de Souza Cascardo

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

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

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in apparmor source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  New

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running setattr

  running symlink

  run

[Touch-packages] [Bug 1421718] Re: [Ubuntu Phone Store] No message when no applications found

ame on M10 with rc-proposed r268.

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

Title:
  [Ubuntu Phone Store] No message when no applications found

Status in Ubuntu UX:
  Won't Fix
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Hi!

  Steps:
  1. Open Store.
  2. Search RRS (Not RSS).
  3. Bug: Nothing found, but you can't see a message for this.
  4. Search RSS.
  5. OK: You see 5 applications found message.

  Thanks in advance!

  --
  Desired resolution:

  This is part of a bigger redesign project (Scopes toolkit) and it
  can't be fixed as a single bug. The description and specs will be
  updated as soon as they are available.

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

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

[Touch-packages] [Bug 1667328] [NEW] Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

2017-02-23 Thread Till Kamppeter

Public bug reported:

I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
#42-Ubuntu

In the last days the microphone stopped working when I am on the Google
Hangouts video conference in the Chromium browser. I checked the sound
settings of the System Settings and on the "input" tab the slider for
the microphone volume is grayed out and cannot be moved away from the
zero position. The microphone level monitor bar does not move when
talking or touching the microphone.

Then I found the following on the internet

http://askubuntu.com/questions/508221/sound-input-device-microphone-not-
working

and tried to solve the problem following the hints:

- Reboot does not solve the problem.

- I could not do any tests with gstreamer-properties as it seems to have
been removed from gstreamer (what is the successor?).

- pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
Tab that the microphone of the laptop is OK and that the kernel works
with it. The Level monitor bar is moving according to environment noise
and touching of the microphone.

- "sudo alsa force-reload" does not solve the problem.

- "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does
not solve the problem.

- audacity is recording through the microphone correctly.

- Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d/alsa-
base.conf and rebooting does not solve the problem.

I hope that is a known problem. Please tell me if you need further
information.

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Summary changed:

- .
+ Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

** Description changed:

- .
+ I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
+ Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
+ #42-Ubuntu
+ 
+ In the last days the microphone stopped working when I am on the Google
+ Hangouts video conference in the Chromium browser. I checked the sound
+ settings of the System Settings and on the "input" tab the slider for
+ the microphone volume is grayed out and cannot be moved away from the
+ zero position. The microphone level monitor bar does not move when
+ talking or touching the microphone.
+ 
+ Then I found the following on the internet
+ 
+ http://askubuntu.com/questions/508221/sound-input-device-microphone-not-
+ working
+ 
+ and tried to solve the problem following the hints:
+ 
+ - Reboot does not solve the problem.
+ 
+ - I could not do any tests with gstreamer-properties as it seems to have
+ been removed from gstreamer (what is the successor?).
+ 
+ - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
+ Tab that the microphone of the laptop is OK and that the kernel works
+ with it. The Level monitor bar is moving according to environment noise
+ and touching of the microphone.
+ 
+ - "sudo alsa force-reload" does not solve the problem.
+ 
+ - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
+ install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does
+ not solve the problem.
+ 
+ - audacity is recording through the microphone correctly.
+ 
+ - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d/alsa-
+ base.conf and rebooting does not solve the problem.
+ 
+ I hope that is a known problem. Please tell me if you need further
+ information.

** Package changed: cups (Ubuntu) => gstreamer (Ubuntu)

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

[Touch-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-02-23 Thread FFab

Christopher M. Penalver, re backlight cycle.

Booting, grub config: no workaround, "quiet splash", reboot - I note
following cycle:

Grub menu - gray backlight (brightness same as grub menu background) -
then a flash (white), not covering the whole screen - black( 0%
brigthness, lasting 6 sec) - gray like before.

cold start:

grub-menu - gray - flash (white), not covering the whole screen -a cycle
of 16 times:   black  and  gray  - the last gray

note:
runnig Ubuntu, brightness cannot be changed
running Windows10, no brightness problem.

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

2017-02-23 Thread Scott Moser

This failure breaks automated installation and such, even when re-trying
because the caller that might retry does not know that this failed.

Our curtin vmtest hit this at
https://jenkins.ubuntu.com/server/view/Curtin/job/curtin-vmtest-devel-
amd64/781/consoleFull .

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

2017-02-23 Thread Thadeu Lima de Souza Cascardo

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

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in tor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in tor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Committed
Status in tor source package in Yakkety:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

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

[Touch-packages] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

2017-02-23 Thread Brad Figg

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

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

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

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

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

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in tor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in tor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Committed
Status in tor source package in Yakkety:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

To manage notifications about t

[Touch-packages] [Bug 1661030] Missing required logs.

2017-02-23 Thread Brad Figg

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1661030

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in apparmor source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file

[Touch-packages] [Bug 1666554] Re: webbrowser - when you drop back a tab it always places the tab at the last position, should be placed where the mouse pointer is, i think

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

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

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

Title:
  webbrowser - when you drop back a tab it always places the tab at the
  last position, should be placed where the mouse pointer is, i think

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

Bug description:
  webbrowser - when you drop back a tab it always places the tab at the
  last position, should be placed where the mouse pointer is, i think

  open the webbrowser app, open many tabs, drag a random tab out into a
  new window, drop the tab back into the tabs bar, it always places the
  tab at the last position on the tabs bar. this not like a bug bug,
  maybe i'm just to used to the google's chrome tab management way

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes

2017-02-23 Thread Gerry Boland

@alf:
http://pastebin.ubuntu.com/24053520/

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 5 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Incomplete
Status in repowerd:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-02-23 Thread spike speigel

I would like to share that I found this post referring to a similar
issue where sound settings weren't maintained, maintained being a better
word than saved because I believe alsamixer might properly save the
settings.

According to the post it is pulseaudio which is actually modifying the
settings:

http://askubuntu.com/a/549939

I tested as suggested, by modifying the "Headphone Mic Boost" within
alsamixer and exiting. I then ran:

pulseaudio -k

And pulseaudio reset the "Headphone Mic Boost" to dB gain 0.00, 0.00.
The hissing reappeared.

If I could get pulseaudio to stop resetting the "Headphone Mic Boost" in
alsamixer, then that would be an acceptable workaround.

But, I think the real issue still needs to be resolved. One would
expect a dB gain 0.00, 0.00 to be absolutely silent. The user should
not need to kick it up a notch to dB gain 10.00, 10.00.

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

Title:
XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
Pertaining to 16.04 on a dell XPS 13 9360

ii alsa-base 1.0.25+dfsg-0ubuntu5

Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

When headphones are plugged in, there is a clearly audible hiss (white
noise). This is present as soon as the headphones are plugged in, whether
'headphones' or 'headset' are selected from the pop-up box.

Using alsamixer to debug the issue reveals that it is related to
"Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
this is changed to:

10.00, 10.00 (one notch up) the hiss disappears.
20.00, 20.00 cause a louder hiss and
30.00, 30.00 causes an even louder hiss with high frequency audio artifacts.

When the headphones are removed and plugged back in the Headphone Mic
Boost setting returns to dB gain 0 and the problem also returns.

This (problem and workaround) has been reported in the wild:
https://news.ycombinator.com/item?id=13050843 and

https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
for example

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

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

[Touch-packages] [Bug 1667355] [NEW] Please merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable (main)

2017-02-23 Thread FanJun Kong - ( BH1SCW )

Public bug reported:


Please upload merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable
(main).

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Assignee: FanJun Kong - ( BH1SCW ) (fjkong)
 Status: In Progress

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+2.0 (Ubuntu)
 Assignee: (unassigned) => FanJun Kong - ( BH1SCW ) (fjkong)

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

Title:
  Please merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable
  (main)

Status in gtk+2.0 package in Ubuntu:
  In Progress

Bug description:

  Please upload merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian
  unstable (main).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1667355/+subscriptions

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

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

2017-02-23 Thread Michael Terry

Is this still happening?

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

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

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

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

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

  Expected result
  It starts successfully and the app works as expected

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

  They all report:

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

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

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

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

[Touch-packages] [Bug 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate

2017-02-23 Thread Albert Astals Cid

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => Invalid

** Branch linked: lp:~aacid/unity8/dontCreateUnusedMenus

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

Title:
  unity8 freezes for a second while opening a client-side submenu in
  kate

Status in QtMir:
  Invalid
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:

  - Launch kate
  - Right-click on its main, text editor, area. A pop-up menu should show up.
  - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with 
"Set Bookmark" and "Clear All Bookmarks" options will show up.

  Expected outcome:
  The sub menu opens immediately and the mouse pointer is responsive throughout

  Actual outcome:
  unity8 freezes for a bit, with mouse pointer becoming unresponsive, before 
finally resuming and showing up the submenu.

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

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

[Touch-packages] [Bug 1667358] [NEW] terminal screen black or blinking in latest unity8 snap

2017-02-23 Thread Victor gonzalez

Public bug reported:

STORY: with the latest version of unity8 snap I have a black screen when
opening terminal app and the screen blinks if you type something or
press mouse buttons

Environment: Zesty

STEPS:

1º Install latest unity8-snap-install(with unity8-session 448)
2º Enter unity8-session snap
3º Open terminal-app 

Current result: terminal app window is black
Expected result: should show the terminal app like if it is open in unity7

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

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

Title:
  terminal screen black or blinking in latest unity8 snap

Status in unity8 package in Ubuntu:
  New

Bug description:
  STORY: with the latest version of unity8 snap I have a black screen
  when opening terminal app and the screen blinks if you type something
  or press mouse buttons

  Environment: Zesty

  STEPS:

  1º Install latest unity8-snap-install(with unity8-session 448)
  2º Enter unity8-session snap
  3º Open terminal-app 

  Current result: terminal app window is black
  Expected result: should show the terminal app like if it is open in unity7

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

-- 
Mailing list: https://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 1662145] Re: [regression] Some apps fail to start with [QPA] UbuntuClientIntegration: connection to Mir server failed.

2017-02-23 Thread Andy Bleaden

Seemed to have been fixed with develop rc_proposed but then the wifi
broke!

On 23 February 2017 at 15:53, Michael Terry 
wrote:

> Is this still happening?
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> Touch Developer Preview.
> Matching subscriptions: andyblea...@gmail.com
> https://bugs.launchpad.net/bugs/1662145
>
> Title:
>   [regression] Some apps fail to start with [QPA]
>   UbuntuClientIntegration: connection to Mir server failed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1662145/+
> subscriptions
>


-- 
*Andy Bleaden*
07946481674
Skype/Twitter/Telegram *@andybleaden*

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

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

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

Bug description:
  Zesty
  unity8-session  16.04   396   canonical  
devmode

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

  Expected result
  It starts successfully and the app works as expected

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

  They all report:

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

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

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

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

[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2017-02-23 Thread Ricardo Rodrigues

I'm also suffering from this issue.

New wireless headset with mic, can't use the mic...

But I'm using Ubuntu 16.10 (Yakkety Yak). What can I do to help debug
this issue?

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

** Branch linked: lp:~smoser/software-properties/trunk.lp1532855

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

2017-02-23 Thread Scott Moser

Merge proposal at https://code.launchpad.net/~smoser/software-
properties/trunk.lp1532855/+merge/318132

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes

2017-02-23 Thread Gerry Boland

Ok, with Alexandros' help I've dug a bit more.

On my hardware, I tear everything down and just run 
sudo mir_demo_server_basic --arw-file
I can see clients ok.

I forked mir_demo_client_display_config to add extra bits:
https://code.launchpad.net/~gerboland/+git/display-configurator
which adds an "O" option to power off the display

When I run it, and hit "O", the display flickers 8 times and then stays
off (mir_power_mode_off)

If I hit "P" to turn it on again, nothing happens (mir_power_mode_on).
Applying the configuration appears to hang the client - I get no success
or fail response from Mir.

If I kill the client, Mir re-activates the display (flickering 8 times)

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

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

** Changed in: repowerd (Ubuntu)
   Status: Incomplete => Invalid

** Summary changed:

- [amd] screen-unblanking seems to flicker backlight on/off 5 times before 
display resumes
+ [amd] screen-unblanking seems to flicker backlight on/off 8 times before 
display resumes

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

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 8 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  New
Status in repowerd:
  Invalid
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1667358] Re: terminal screen black or blinking in latest unity8 snap

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

Title:
  terminal screen black or blinking in latest unity8 snap

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  STORY: with the latest version of unity8 snap I have a black screen
  when opening terminal app and the screen blinks if you type something
  or press mouse buttons

  Environment: Zesty

  STEPS:

  1º Install latest unity8-snap-install(with unity8-session 448)
  2º Enter unity8-session snap
  3º Open terminal-app 

  Current result: terminal app window is black
  Expected result: should show the terminal app like if it is open in unity7

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

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

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

2017-02-23 Thread Brian Murray

There are some apt-key error messages in the autopkgtest, could you take
a look at this?

** Changed in: software-properties (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

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

Bug description:
  Please add support for:

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

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

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

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

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1550983] Re: Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

2017-02-23 Thread Dariusz Gadomski

I have just verified it for Trusty and Yakkety on the same images that
were used earlier to reproduce it.

The issue is gone.

** 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983

Title:
  Fails to start with "Couldn't open libGL.so.1" (missing dependency?)

Status in One Hundred Papercuts:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Committed
Status in gtk+3.0 source package in Yakkety:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  [Impact]
  There are some unlinked calls to libGL.so.1 undetected in the build process 
because of using libepoxy. Running an application that does not depend on 
libgl1 (directly or indirectly) may lead to aborting the process with an 
undefined reference to libGL.so.1.

  [Test Case]
  1. Deploy a server / cloud image of Xenial or Yakkety.
  2. Use a Windows or a Mac client with Cygwin/X and ssh -XY to Ubuntu machine.
  3. sudo apt install firefox; firefox

  Expected result:
  firefox is launched on the client machine.

  Actual result:
  "Couldn't open libGL.so.1" message is printed.

  [Regression Potential]
  Minimal, it is an upstream change already released to zesty. It performs a 
runtime check for GL support and disables GLX function calls in case they're 
not available.

  [Other Info]
  Original bug description:

  virt-manager fails to start:

  $ virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (cli:256) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:143) 
virt-manager version: 1.3.2
  [Sun, 28 Feb 2016 19:18:22 virt-manager 7592] DEBUG (virt-manager:144) 
virtManager import: 
  Couldn't open libGL.so.1: libGL.so.1: cannot open shared object file: No such 
file or directory
  $

  Installing the 'libgl1-mesa-glx' package resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virt-manager 1:1.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 19:19:27 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1442941] Re: Bluetooth Built-in HP 650 does not work in Ubuntu 14.10.

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

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

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

Title:
   Bluetooth Built-in HP 650 does not work in Ubuntu 14.10.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When I purchased the HP 650 Laptop, 12.04LTS have installed Ubuntu,
  built-in Bluetooth function and F12 light was white. I made updates to
  12.10 to 14.10. Since then, bluetooth built fails, the F12 LED is
  orange. USB works.

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

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

[Touch-packages] [Bug 1667407] [NEW] improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug

2017-02-23 Thread Gustavo Serra Scalet

Public bug reported:

Dear Maintainer,

The sha256sum provided by coreutils (without openssl) is performing
poorly with gcc versions >= 4.9 until 7.0 (currently under development).
The reason for that is the -fschedule-insns optimization that is used
with -O2. By simply deactivating it, there is a performance improvement
of 2 to 3 times.

I'm using Ubuntu 16.10 and the coreutils package version 8.25-2ubuntu2.

Please check the following closed debian bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

Be aware of the following conditions that are required:
* If ppc64le
* If gcc being used is >= 4.9 and < 7.0

Notes:
1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
2) clang is not affected by this bug (verified on v3.8 and v3.9).
3) strangely the sha512 is not affected by this.

Below a demonstration of how it performs on my POWER8 machine:

===
$ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
configure: WARNING: libacl development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without ACL support.
configure: WARNING: libattr development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without xattr support.
configure: WARNING: libcap library was not found or not usable.
configure: WARNING: GNU coreutils will be built without capability support.
configure: WARNING: libgmp development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without GMP support.
src/who.c: In function 'print_user':
src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
 int   *a = utmp_ent->ut_addr_v6;
^~~~
d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

real0m18.670s
user0m16.566s
sys 0m0.745s

$ # now with the following patch: ## Check Michael Stone's patch for an 
improved version.
$ diff Makefile.in ../Makefile.in
8989c8989
< @am__fastdepCC_TRUE@  $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< 
&&\
---
> @am__fastdepCC_TRUE@  $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo 
> "-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\
$ cp ../Makefile.in Makefile.in
$ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
configure: WARNING: libacl development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without ACL support.
configure: WARNING: libattr development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without xattr support.
configure: WARNING: libcap library was not found or not usable.
configure: WARNING: GNU coreutils will be built without capability support.
configure: WARNING: libgmp development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without GMP support.
src/who.c: In function 'print_user':
src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
 int   *a = utmp_ent->ut_addr_v6;
^~~~
d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

real0m5.903s
user0m5.560s
sys 0m0.255s

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


** Tags: regression-release

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

Title:
   improve 2x-3x sha256sum performance on ppc64le due to current gcc
  optimization bug

Status in coreutils package in Ubuntu:
  New

Bug description:
  Dear Maintainer,

  The sha256sum provided by coreutils (without openssl) is performing
  poorly with gcc versions >= 4.9 until 7.0 (currently under development).
  The reason for that is the -fschedule-insns optimization that is used
  with -O2. By simply deactivating it, there is a performance improvement
  of 2 to 3 times.

  I'm using Ubuntu 16.10 and the coreutils package version
  8.25-2ubuntu2.

  Please check the following closed debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

  Be aware of the following conditions that are required:
  * If ppc64le
  * If gcc being used is >= 4.9 and < 7.0

  Notes:
  1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
  2) clang is not affected by this bug (verified on v3.8 and v3.9).
  3) strangely the sha512 is not affected by this.

  Below a demonstration of how it performs on my POWER8 machine:

  ===
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configu

[Touch-packages] [Bug 1643675] Re: hugepages for non-default pagesize need manual setup

2017-02-23 Thread James Page

** Changed in: charm-nova-compute
   Importance: Undecided => Medium

** Changed in: charm-nova-compute
   Status: New => Triaged

** Changed in: nova-compute (Juju Charms Collection)
   Status: Triaged => Invalid

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

Title:
  hugepages for non-default pagesize need manual setup

Status in OpenStack nova-compute charm:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in nova-compute package in Juju Charms Collection:
  Invalid

Bug description:
  This is a amd64 xenial/mitaka deploy using 1607 charms release
  where I need to have 1G hugepages available for openstack/kvm.

  nova-compute charm should provide ways to ease e.g.
  1G hugepages setup, currently only exposes a 
  "hugepages" setting that ends setting vm.nr_hugepages
  for the node, but even after settings kernel cmdline
  parameters for 1G hugepages (hugepagesz=1G hugepages=128),
  is not usable by libvirt-bin:

  #1 systemd:
  Installs /lib/systemd/system/dev-hugepages.mount with
  default pagesize
  => no hugetblfs mount with (e.g.) pagesize=1G

  #2 libvirt-bin:
  Installs apparmor profile ("libvirt-qemu") which only allows:
# for access to hugepages
owner "/run/hugepages/kvm/libvirt/qemu/**" rw,
owner "/dev/hugepages/libvirt/qemu/**" rw,
  => not possible to have other mount points for other pagesizes.

  I've workaround'd #1,#2 above by overriding systemd's
  by creating a /etc/systemd/system/dev-hugepages.mount
  with below extra line at [Mount] section:
  Options=pagesize=1G
  -> https://paste.ubuntu.com/23513048/

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1643675/+subscriptions

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

[Touch-packages] [Bug 1570511] Re: Select All shows up when replying to gmail message

2017-02-23 Thread Olivier Tilloy

** Changed in: webbrowser-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Select All shows up when replying to gmail message

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  open gmail webapp (or in browser), try to reply to a mail
  scroll to the top of the message and tap to begin typing

  expected result:
  - can start typing, no menu

  actual result:
  - can start typing but Select All menu is incorrectly displayed

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

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

[Touch-packages] [Bug 1667358] Re: terminal screen black or blinking in latest unity8 snap

the latest version is   edge:16.04 (450) 401MB devmode

:D

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

Title:
  terminal screen black or blinking in latest unity8 snap

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  STORY: with the latest version of unity8 snap I have a black screen
  when opening terminal app and the screen blinks if you type something
  or press mouse buttons

  Environment: Zesty

  STEPS:

  1º Install latest unity8-snap-install(with unity8-session 448)
  2º Enter unity8-session snap
  3º Open terminal-app 

  Current result: terminal app window is black
  Expected result: should show the terminal app like if it is open in unity7

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

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

[Touch-packages] [Bug 1667425] [NEW] ModemManager crashed with SIGSEGV in g_closure_invoke()

2017-02-23 Thread siucdude

Public bug reported:

This is on 17.04 Beta, just started after today updates.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: modemmanager 1.6.4-1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 22 21:43:41 2017
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2015-12-17 (433 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x55bf1fab2ab7:  repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x55bf1fab2ab7) ok
 source "%es:(%rdi)" (0x55bf1fb453fa) ok
 destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
UserGroups:

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


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

** Information type changed from Private to Public

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  This is on 17.04 Beta, just started after today updates.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: modemmanager 1.6.4-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 22 21:43:41 2017
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55bf1fab2ab7:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55bf1fab2ab7) ok
   source "%es:(%rdi)" (0x55bf1fb453fa) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1667358] Re: terminal screen black or blinking in latest unity8 snap

the terminal looks ok on 450.. ok in the sense that is how it always
been... it's ubuntu-terminal-app snaps running on Xmir (not sure why it
doesn't native o_O ). if the terminal app is black try resizing the
window, does the trick here.

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

Title:
  terminal screen black or blinking in latest unity8 snap

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  STORY: with the latest version of unity8 snap I have a black screen
  when opening terminal app and the screen blinks if you type something
  or press mouse buttons

  Environment: Zesty

  STEPS:

  1º Install latest unity8-snap-install(with unity8-session 448)
  2º Enter unity8-session snap
  3º Open terminal-app 

  Current result: terminal app window is black
  Expected result: should show the terminal app like if it is open in unity7

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

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

[Touch-packages] [Bug 1667358] Re: terminal screen black or blinking in latest unity8 snap

interesting, taking a screenshot locks unity (attached is the unity8 log
if anyone is interested, it's too spammy for me)

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1667358/+attachment/4825380/+files/unity8.log

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

Title:
  terminal screen black or blinking in latest unity8 snap

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  STORY: with the latest version of unity8 snap I have a black screen
  when opening terminal app and the screen blinks if you type something
  or press mouse buttons

  Environment: Zesty

  STEPS:

  1º Install latest unity8-snap-install(with unity8-session 448)
  2º Enter unity8-session snap
  3º Open terminal-app 

  Current result: terminal app window is black
  Expected result: should show the terminal app like if it is open in unity7

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

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

[Touch-packages] [Bug 1667425] Re: ModemManager crashed with SIGSEGV in g_closure_invoke()

2017-02-23 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1594799, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825373/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825375/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825376/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825377/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825378/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1667425/+attachment/4825379/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1594799

** Tags removed: need-amd64-retrace

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  This is on 17.04 Beta, just started after today updates.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: modemmanager 1.6.4-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 22 21:43:41 2017
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55bf1fab2ab7:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55bf1fab2ab7) ok
   source "%es:(%rdi)" (0x55bf1fb453fa) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 8 times before display resumes

2017-02-23 Thread Gerry Boland

One small warning message is printed during display on flicker:
http://pastebin.ubuntu.com/24053776/

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

Title:
  [amd] screen-unblanking seems to flicker backlight on/off 8 times
  before display resumes

Status in Canonical System Image:
  Incomplete
Status in Mir:
  New
Status in repowerd:
  Invalid
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free
  driver. I have unity8 installed.

  If I let the screen blank, and hit a key to unblank, it takes about 5
  seconds until screen turns on properly. During those 5 seconds, I see
  the display backlight turn on & off about 5 times, all the while with
  a black picture.

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

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

[Touch-packages] [Bug 1621654] Re: package click-apparmor 0.2ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 100

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

** Changed in: click-apparmor (Ubuntu)
   Status: New => Confirmed

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

Title:
  package click-apparmor 0.2ubuntu1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 100

Status in click-apparmor package in Ubuntu:
  Confirmed

Bug description:
  it started with broken-package issues re. bind9. i re-installed debian
  repositories but still have issues with apt update...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: click-apparmor 0.2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-95-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu Sep  8 18:22:58 2016
  DpkgTerminalLog:
   Removing click-apparmor (0.2ubuntu1) ...
   invoke-rc.d: unknown initscript, /etc/init.d/click-apparmor not found.
   /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
   dpkg: error processing package click-apparmor (--remove):
subprocess installed pre-removal script returned error exit status 100
  DuplicateSignature: package:click-apparmor:0.2ubuntu1:subprocess installed 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 100
  InstallationDate: Installed on 2016-08-21 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.2ubuntu1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661691] Re: TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

2017-02-23 Thread Scott Moser

Well, its not *anything*.  setting term to the following allow you to paste 
normally:
 TERM=ansi
 TERM=vt220
 TERM=vt100
 TERM=pcansi

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

Title:
  TERM=xterm enables mouse mode in vi, breaks pasting with middle mouse

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I quite often have the following work flow:

  a.) lxc launch ubuntu-daily:zesty z1
  b.) lxc exec z1 /bin/bash
  c.) % vi foo.txt
  d.) paste some thing from my X buffer (hit middle mouse button).

  Somewhere between yakkety (2:7.4.1829-1ubuntu2.1) and zesty
  (2:8.0.0095-1ubuntu2) this behavior changed.

  Previously this all worked fine.

  Now, in zesty, however an attempt to paste results in a vi error message:
   E353: Nothing in register "

  to fix this, you can first disable the mouse 'a' [1]

   : set mouse-=a

  
  I'm not sure what is enabling this, because /usr/share/vim/vimrc has the line
  set mouse=a commented out.

  --
  [1] 
http://www.varesano.net/blog/fabio/disable%20vim%20automatic%20visual%20mode%20using%20mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: vim-nox 2:8.0.0095-1ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 12:14:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (561 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1655324] Re: Display does not rotate

Affects me on M10 with staging (Ubuntu 16.04, r151).

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

Title:
  Display does not rotate

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

Bug description:
  current build number: 119
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  Test Case:
  1. Rotate the device in landscape then portrait

  Expected result 
  The display follows the orientation of the device

  Actual result
  The display does not follow the orientation of the device

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

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

[Touch-packages] [Bug 1641898] Re: error when adding U1 account

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

** This bug is no longer a duplicate of bug 1655951
   Cannot create Ubuntu One account
** This bug has been marked a duplicate of bug 1640662
   [xenial64]Cannot sign in U1 account with error 
"GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:The name 
io.snapcraft.SnapdLoginService was not provided by any .service files"

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

Title:
  error when adding U1 account

Status in ubuntuone-credentials package in Ubuntu:
  New

Bug description:
  Environment:

  current build number: 82
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-15 21:07:37
  version version: 82
  version ubuntu: 20161115
  version device: 20161014.0
  version custom: 20161115

  Steps to reproduce:

  1º Go to System settings>Accounts>U1 account
  2º Enter your credentials and continue

  Current result: error, screenshot attached

  Expected result: U1 account should be added

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

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

touch-packages@lists.launchpad.net

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

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

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

Title:
  Camera doesn't start on arm64 - crash in
  AalServicePlugin::devices(QByteArray const&)

Status in camera-app package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  Confirmed

Bug description:
  Camera crashes on startup on arm64

  It's possible the reason is the lack of media-hub (bug #1618416), but
  camera should probably not die because of that.

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * launch camera

  == Logfile =
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  Import path added 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654/lib/aarch64-linux-gnu"
  Camera app directory 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654"
  virtual QMediaService* AalServicePlugin::create(const QString&) 
"org.qt-project.qt.mediaplayer"
  [TT 2016-08-30 12:35:27.595951] [service.cpp:29@instance] 
  Failed to start a new media-hub player session:  
org.freedesktop.DBus.Error.ServiceUnknown: The name core.ubuntu.media.Service 
was not provided by any .service files
  Failed to create a new media player backend. Video playback will not 
function. 

  Could not finish contructing new AalMediaPlayerService instance since 
m_hubPlayerSession is NULL
  library "libcamera_compat_layer.so" not found

  
  == Stacktrace =
  #0  0x in  ()
  #1  0x007f6d20b7e4 in AalServicePlugin::devices(QByteArray const&) const 
(this=, service=...) at aalcameraserviceplugin.cpp:56
  deviceList = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin 
= 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  cameras = -293107960
  #2  0x007f74ff8d8c in QPluginServiceProvider::devices(QByteArray const&) 
const (this=, serviceType=...) at qmediaserviceprovider.cpp:593
  obj = 
  _container_ = {c = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x39e32080}, d = 
0x39e32080}}, i = {i = 0x39e32090}, e = {i = 0x39e320a0}, control = 1}
  res = {> = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = {> = 
{static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #3  0x007f75024a18 in QCameraInfo::availableCameras(QCamera::Position) 
(position=position@entry=QCamera::UnspecifiedPosition) at 
camera/qcamerainfo.cpp:242
  cameras = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 
}, d = 0x7f87cc9d60 }}
  provider = 0x7f7508eda0 <(anonymous 
namespace)::Q_QGS_pluginProvider::innerFunction()::holder>
  service = {static MaxSize = 1073741800, d = 0x39e0eed0}
  devices = {> = {}, {p 
= {static shared_null = {ref = {atomic = {_q_value = {> 
= {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #4  0x007f6d217d00 in AalVideoDeviceSelectorControl::deviceCount() const 
(this=) at aalvideodeviceselectorcontrol.cpp:45
  #5  0x007f75023e68 in QCameraInfo::QCameraInfo(QCamera const&) 
(this=0x7fee878938, camera=...) at camera/qcamerainfo.cpp:99
  deviceControl = 0x39e30110
  infoControl = 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: camera-app 3.0.0+16.04.20160824-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 12:48:50 2016
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

touch-packages@lists.launchpad.net

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

** Changed in: qtubuntu-camera (Ubuntu)
   Status: New => Confirmed

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

Title:
  Camera doesn't start on arm64 - crash in
  AalServicePlugin::devices(QByteArray const&)

Status in camera-app package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  Confirmed

Bug description:
  Camera crashes on startup on arm64

  It's possible the reason is the lack of media-hub (bug #1618416), but
  camera should probably not die because of that.

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * launch camera

  == Logfile =
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  Import path added 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654/lib/aarch64-linux-gnu"
  Camera app directory 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654"
  virtual QMediaService* AalServicePlugin::create(const QString&) 
"org.qt-project.qt.mediaplayer"
  [TT 2016-08-30 12:35:27.595951] [service.cpp:29@instance] 
  Failed to start a new media-hub player session:  
org.freedesktop.DBus.Error.ServiceUnknown: The name core.ubuntu.media.Service 
was not provided by any .service files
  Failed to create a new media player backend. Video playback will not 
function. 

  Could not finish contructing new AalMediaPlayerService instance since 
m_hubPlayerSession is NULL
  library "libcamera_compat_layer.so" not found

  
  == Stacktrace =
  #0  0x in  ()
  #1  0x007f6d20b7e4 in AalServicePlugin::devices(QByteArray const&) const 
(this=, service=...) at aalcameraserviceplugin.cpp:56
  deviceList = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin 
= 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  cameras = -293107960
  #2  0x007f74ff8d8c in QPluginServiceProvider::devices(QByteArray const&) 
const (this=, serviceType=...) at qmediaserviceprovider.cpp:593
  obj = 
  _container_ = {c = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x39e32080}, d = 
0x39e32080}}, i = {i = 0x39e32090}, e = {i = 0x39e320a0}, control = 1}
  res = {> = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = {> = 
{static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #3  0x007f75024a18 in QCameraInfo::availableCameras(QCamera::Position) 
(position=position@entry=QCamera::UnspecifiedPosition) at 
camera/qcamerainfo.cpp:242
  cameras = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 
}, d = 0x7f87cc9d60 }}
  provider = 0x7f7508eda0 <(anonymous 
namespace)::Q_QGS_pluginProvider::innerFunction()::holder>
  service = {static MaxSize = 1073741800, d = 0x39e0eed0}
  devices = {> = {}, {p 
= {static shared_null = {ref = {atomic = {_q_value = {> 
= {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #4  0x007f6d217d00 in AalVideoDeviceSelectorControl::deviceCount() const 
(this=) at aalvideodeviceselectorcontrol.cpp:45
  #5  0x007f75023e68 in QCameraInfo::QCameraInfo(QCamera const&) 
(this=0x7fee878938, camera=...) at camera/qcamerainfo.cpp:99
  deviceControl = 0x39e30110
  infoControl = 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: camera-app 3.0.0+16.04.20160824-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 12:48:50 2016
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

touch-packages@lists.launchpad.net

Affects me on M10 with staging (Ubuntu 16.04, r151).

** Tags added: bq m10 touch

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

Title:
  Camera doesn't start on arm64 - crash in
  AalServicePlugin::devices(QByteArray const&)

Status in camera-app package in Ubuntu:
  Confirmed
Status in qtubuntu-camera package in Ubuntu:
  Confirmed

Bug description:
  Camera crashes on startup on arm64

  It's possible the reason is the lack of media-hub (bug #1618416), but
  camera should probably not die because of that.

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * launch camera

  == Logfile =
  Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
  Import path added 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654/lib/aarch64-linux-gnu"
  Camera app directory 
"/usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.654"
  virtual QMediaService* AalServicePlugin::create(const QString&) 
"org.qt-project.qt.mediaplayer"
  [TT 2016-08-30 12:35:27.595951] [service.cpp:29@instance] 
  Failed to start a new media-hub player session:  
org.freedesktop.DBus.Error.ServiceUnknown: The name core.ubuntu.media.Service 
was not provided by any .service files
  Failed to create a new media player backend. Video playback will not 
function. 

  Could not finish contructing new AalMediaPlayerService instance since 
m_hubPlayerSession is NULL
  library "libcamera_compat_layer.so" not found

  
  == Stacktrace =
  #0  0x in  ()
  #1  0x007f6d20b7e4 in AalServicePlugin::devices(QByteArray const&) const 
(this=, service=...) at aalcameraserviceplugin.cpp:56
  deviceList = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin 
= 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  cameras = -293107960
  #2  0x007f74ff8d8c in QPluginServiceProvider::devices(QByteArray const&) 
const (this=, serviceType=...) at qmediaserviceprovider.cpp:593
  obj = 
  _container_ = {c = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x39e32080}, d = 
0x39e32080}}, i = {i = 0x39e32090}, e = {i = 0x39e320a0}, control = 1}
  res = {> = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = {> = 
{static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #3  0x007f75024a18 in QCameraInfo::availableCameras(QCamera::Position) 
(position=position@entry=QCamera::UnspecifiedPosition) at 
camera/qcamerainfo.cpp:242
  cameras = {> = {}, 
{p = {static shared_null = {ref = {atomic = {_q_value = 
{> = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 
}, d = 0x7f87cc9d60 }}
  provider = 0x7f7508eda0 <(anonymous 
namespace)::Q_QGS_pluginProvider::innerFunction()::holder>
  service = {static MaxSize = 1073741800, d = 0x39e0eed0}
  devices = {> = {}, {p 
= {static shared_null = {ref = {atomic = {_q_value = {> 
= {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 
0, end = 0, array = {0x0}}, d = 0x7f87cc9d60 }, d = 
0x7f87cc9d60 }}
  #4  0x007f6d217d00 in AalVideoDeviceSelectorControl::deviceCount() const 
(this=) at aalvideodeviceselectorcontrol.cpp:45
  #5  0x007f75023e68 in QCameraInfo::QCameraInfo(QCamera const&) 
(this=0x7fee878938, camera=...) at camera/qcamerainfo.cpp:99
  deviceControl = 0x39e30110
  infoControl = 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: camera-app 3.0.0+16.04.20160824-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 12:48:50 2016
  SourcePackage: camera-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621124] Re: Can't turn bluetooth off

https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640669

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

Title:
  Can't turn bluetooth off

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  /!\ ARM64 BUILD ONLY

  Enviroment:

  current build number: 33
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-09-07 11:29:04
  version version: 33
  version ubuntu: 20160906
  version device: 20160906.0
  version custom: 20160906

  Steps to reproduce:

  Preconditions_ bluetooth on
  1º Go to System settings>Battery or indicator-bluetooth
  2º Switch bluetooth off and wait around 30 secs
  3º Check bluetooth toggle slides off->on again

  Current result: Can't turn bluetooth off

  Expected result: Bluetooth toggles should turn off bt

  Add:video attached

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

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

[Touch-packages] [Bug 1667463] [NEW] Unity8 Greeter mock initializes sessionMode incorrectly

2017-02-23 Thread Josh Arenson

Public bug reported:

In the WideView mock, the "multipleSessions" checkbox is instantiated
unchecked. However, the mock behaves as if the box were checked. Cycling
through check/uncheck resolves the issue.

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

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

Title:
  Unity8 Greeter mock initializes sessionMode incorrectly

Status in unity8 package in Ubuntu:
  New

Bug description:
  In the WideView mock, the "multipleSessions" checkbox is instantiated
  unchecked. However, the mock behaves as if the box were checked.
  Cycling through check/uncheck resolves the issue.

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

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

[Touch-packages] [Bug 1667463] Re: Unity8 Greeter mock initializes sessionMode incorrectly

** Branch linked: lp:~josharenson/unity8/fix-wide-view-mock-sessions-
checkbox

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

Title:
  Unity8 Greeter mock initializes sessionMode incorrectly

Status in unity8 package in Ubuntu:
  New

Bug description:
  In the WideView mock, the "multipleSessions" checkbox is instantiated
  unchecked. However, the mock behaves as if the box were checked.
  Cycling through check/uncheck resolves the issue.

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

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

[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

** Description changed:

+ [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
- to always-added linker option "-as-needed". 
+ to always-added linker option "-as-needed".
+ 
+ [Test case]
+ 1. Pass -mmpx to gcc when building an arbitrary project on x86.
+ 2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
+ 3. Install binutils and gcc-5 from -proposed.
+ 4. Rebuild the target, again with -mmpx.
+ 5. Verify with ldd that the new executable is linked against libmpx.so.
+ 6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.
+ 
+ [Regression potential]
+ This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.
+ 
  
  Here is the GCC upstream bug & fix
  
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267
  
  https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057
  
  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  New
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  New
Status in gcc-5 source package in Xenial:
  New

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

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

[Touch-packages] [Bug 1656155] Re: System (keyboard & touchpad) freezes

2017-02-23 Thread Viacheslav

Hi, again. That I wrote above didn't help. Super sad...

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

Title:
  System (keyboard & touchpad) freezes

Status in libdrm package in Ubuntu:
  Confirmed

Bug description:
  I have a 1-month old Acer Aspire F5-573-58VX that came with Win-10
  installed. It relies on its Intel i5-7200u for its graphics (HD 620).
  It runs Win-10 with no problems (other than Win-10 itself), so I do
  not suspect the hardware.

  I succeeded in dual-booting Ubuntu 16.04 with EFI and secure-boot both
  enabled, but was suffering random freezes at 3-30 minutes of use, even
  after setting the c-state limit in grub. It hangs both with and
  without Intel microcode. So I upgraded to 16.10 hoping that a newer
  kernel would have a fix in it.

  It's still freezing at random (many apps, and sometimes using only the
  desktop controls). It still has the c-state parameter in grub.

  It appears that if I leave the system untouched with the cursor in an
  empty area, then no freeze will occur (I can see display changing) as
  long as I don't touch anything. Bittorrent runs reliably overnight,
  and then the machine can freeze within seconds of my moving the cursor
  to a control in the morning.

  Thunderbird is also suspicious: I can work most of an hour OK as long
  as I never move the cursor over the scroll slider in the folder pane.
  However, bringing the cursor close enough to change the slider's
  appearance will usually freeze the machine. Update: I've now
  experienced a freeze while the cursor was stationary and I was merely
  typing into an email message window.

  When it freezes, the machine goes quiet (it's not spinning). There's
  no message to the GUI, only a sudden halt. When frozen, soft restart
  and reboot (ctrl-alt-back & ctrl-alt-del) both fail. Only a forced
  power-off has had any effect. (I'll try your alt+sysreq combos in my
  next freeze).

  Synaptic says I have an intel driver update utility installed, but I
  don't know if it has run. When I try to sudo it, I am told that the
  command is not found. I have been unable to locate it in the file
  system. If anyone knows where that goes (or where to hunt), that might
  be helpful.

  I do not (yet) know how to ssh into the sick machine to get kernel
  logs or crash dumps. I'm a user-space programmer, not a sysadmin, so I
  have a learning curve to open the firewall enough to allow an
  intrusion, and more learning curves for the cryptic debugging tools.

  var/log/kern.log has this:
  Jan 14 10:43:26 prop6 kernel: [1.002400] [drm:parse_csr_fw [i915_bpo]] 
*ERROR* Unknown stepping info, firmware loading failed
  Jan 14 10:43:26 prop6 kernel: [1.002405] i915_bpo :00:02.0: Failed to 
load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.
  Jan 14 10:43:26 prop6 kernel: [1.006089] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  Jan 14 10:43:26 prop6 kernel: [1.018209] ACPI: Video Device [GFX0] 
(multi-head: yes  rom: no  post: no)
  Jan 14 10:43:26 prop6 kernel: [1.018522] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  Jan 14 10:43:26 prop6 kernel: [1.018601] [drm] Initialized i915_bpo 1.6.0 
20160229 for :00:02.0 on minor 0
  Jan 14 10:43:26 prop6 kernel: [1.064117] r8169 :03:00.1 enp3s0f1: 
renamed from eth0
  Jan 14 10:43:26 prop6 kernel: [1.142340] fbcon: inteldrmfb (fb0) is 
primary device
  Jan 14 10:43:26 prop6 kernel: [1.142437] Console: switching to colour 
frame buffer device 240x67
  Jan 14 10:43:26 prop6 kernel: [1.142466] i915_bpo :00:02.0: fb0: 
inteldrmfb frame buffer device

  My current work-around is to do as much work as possible in Win-10  :(

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

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

[Touch-packages] [Bug 1655181] Re: P9 support in binutils

Hello bugproxy, or anyone else affected,

Accepted binutils into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.4 in
a few hours, and then in the -proposed repository.

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

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

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

** Description changed:

- The upstream binutils (2.27 and trunk) is almost complete for POWER9,
- but unfortunately the changes expected to land in DD2 hardware have not
- yet been set in stone.  With that said, the remaining changes are fairly
- small and will only affect user space; there are no kernel dependencies
- on the unresolved architecture changes.
+ [SRU Justification]
+ Hardware enablement of new P9 architecture on 16.04 LTS
  
+ [Test case]
+ Verify that the binutils testsuite still passes.  This requires manual review 
of the build logs.
+ 
+ [Regression potential]
+ One of the patches changes the behavior around handling of undefined weak 
symbols on ppc64el as a whole.  This behavior change could cause regressions on 
code built for existing ppc64el targets.  This is unlikely because nothing 
should be relying on the current behavior, and this is an upstream patch driven 
by the architecture owner.
+ 
+ One of the patches changes the set of assembly mnemonics available for
+ POWER9 opcodes.  This should have no impact because nothing should be
+ relying on the not-yet-finalized P9 support in xenial.
+ 
+ 
+ The upstream binutils (2.27 and trunk) is almost complete for POWER9, but 
unfortunately the changes expected to land in DD2 hardware have not yet been 
set in stone.  With that said, the remaining changes are fairly small and will 
only affect user space; there are no kernel dependencies on the unresolved 
architecture changes.
  
  == Comment: #3 - Peter E. Bergner  - 2016-11-01 10:43:16 
==
  Complete POWER9 support is upstream and exists in trunk and the binutils 2.27 
and 2.26 release branches.
  
  == Comment: #4 - Breno Henrique Leitao  - 2016-11-21 
12:45:53 ==
  (In reply to comment #3)
  > Complete POWER9 support is upstream and exists in trunk and the binutils
  > 2.27 and 2.26 release branches.
  
  Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else
  required?
  
  == Comment: #5 - William J. Schmidt  - 2016-11-21 
13:32:50 ==
  (In reply to comment #4)
  > (In reply to comment #3)
  > > Complete POWER9 support is upstream and exists in trunk and the binutils
  > > 2.27 and 2.26 release branches.
- > 
+ >
  > Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else
  > required?
  
  Well, as long as they pick up the backported fixes, nothing else is
  required.  That's what this feature is there to ensure.
  
  == Comment: #6 - Breno Henrique Leitao  - 2016-11-24 
06:52:51 ==
  Hi,
  
  > Well, as long as they pick up the backported fixes, nothing else is
  > required.  That's what this feature is there to ensure.
  
  Do you know, at this time, which are the fixes that will be requested to
  be backported?
  
  == Comment: #7 - William J. Schmidt  - 2016-11-28 
09:17:01 ==
  (In reply to comment #6)
  > Hi,
- > 
+ >
  > > Well, as long as they pick up the backported fixes, nothing else is
  > > required.  That's what this feature is there to ensure.
- > 
+ >
  > Do you know, at this time, which are the fixes that will be requested to be
  > backported?
  
  Peter, can you please respond to Breno's question?
  
  == Comment: #8 - Peter E. Bergner  - 2016-11-29 12:08:11 
==
  CC'ing Alan in case he has an extra input.
  
  Looking through the binutils-2_27-branch log, I see the following
  commits we would want picked up:
  
  commit 799b679496c98eb1f31625b00bb5db67a6f608d7
  Author: Peter Bergner 
  Date:   Fri Sep 16 16:17:46 2016 -0500
  
- Backport lastest POWER9 support to match final ISA 3.0 documentation.
- 
- opcodes/
- Apply from master.
- 2016-09-14  Peter Bergner 
- 
- * ppc-opc.c (powerpc_opcodes) : New mnemonic.
- : Delete mnemonics.
- : Rename mnemonic from ...
- : ...to this.
- : Change to a X form instruction.
- : Change to 1 operand form.
- : Delete mnemonic.
- : Rename mnemonic from ...
-

[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

Hello Alexander, or anyone else affected,

Accepted binutils into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.4 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  New
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

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

[Touch-packages] [Bug 1665711] Re: /etc/os-release: Use https

This bug was fixed in the package base-files - 9.6ubuntu12

---
base-files (9.6ubuntu12) zesty; urgency=medium

  [ Jeremy Bicha ]
  * /etc/os-release : Use https in URLs (LP: #1665711)

 -- Steve Langasek   Tue, 21 Feb 2017
00:01:18 -0800

** Changed in: base-files (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  /etc/os-release: Use https

Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's main website is now accessible via https so let's update /etc
  /os-release for this.

  .debdiff attached for sponsoring.

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

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

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

This bug was fixed in the package gpgme1.0 - 1.8.0-3ubuntu2

---
gpgme1.0 (1.8.0-3ubuntu2) zesty; urgency=medium

  * Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
will fix the build failures of kf5-kdepim-apps-libs when built against this
gpgme package.
  * Set LDFLAGS=-Wl,-z,relro in debian/rules, this avoids passing
"-Bsymbolic-functions" which seems to be the cause of FTBFS'es for some
architectures.
  * Add 0005-tests-Reduce-iterations-threads.patch, this fixes another cause of
FTBFS'es on some architectures.
  * Previous two changes fix (LP: #1647204)
  * Thank you to Rik Mills for his help fixing the above problems.

 -- José Manuel Santamaría Lema   Sat, 18 Feb 2017
22:22:02 +0100

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

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Fix Released

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

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

  The packages builds without this issue in debian unstable.

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1590462] Re: City search “Hospitalet” doesn’t find L'Hospitalet de Llobregat

This bug was fixed in the package geonames - 0.2+17.04.20170220-0ubuntu1

---
geonames (0.2+17.04.20170220-0ubuntu1) zesty; urgency=medium

  * Be less strict on city search (LP: #1590462)

 -- Albert Astals Cid   Mon, 20 Feb 2017
11:07:52 +

** Changed in: geonames (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  City search “Hospitalet” doesn’t find  L'Hospitalet de Llobregat

Status in Ubuntu UX:
  Fix Released
Status in geonames package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The official name of my city is 
L'Hospitalet de Llobregat
  but it is often usually written as
Hospitalet de Llobregat

  On the wizard city/timezone selection window we only search from the 
beginning of the string so I could not find my city until i realized i may have 
to type the
L'
  at the beginning.

  : “As with any search
  field, any series of letters immediately followed by a space or
  punctuation character should match only complete words, while any
  series of letters at the end of the string should match both complete
  words and the beginnings of words. (In the terms being searched, a
  “word” is a series of letters that is immediately preceded by the
  start of the string or any non-letter character, and immediately
  followed by the end of the string or any non-letter character.)”

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

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

[Touch-packages] [Bug 1611188] Re: Bluetooth doesn't work after recovering computer from sleeping

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

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth doesn't work after recovering computer from sleeping

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure which package is not working properly. I know the easy
  way to solve the problem, which it doesn't make sense really but it
  works:

  1. When the PC recovers from sleeping, the bluetooth indicator is dark
  and bluetooth mouse doesn't work. First step is to click (with the
  built-in laptop mouse, of course) on "visible" to turn off visibility.
  Somehow the bluetooth is enabled, then.

  2. Then you have to click visible to switch it on again. Then you
  click on your bluetooth mouse and it connects in 0.0s.

  If you don't follow these two steps and try to do other, more logical
  things (like putting your laptop on airplane mode through the physical
  switch, or turn off and on bluetooth) you'll get in trouble. Sometimes
  you have to delete the mouse from bluetooth devices and pair it again.

  The solution is easy, I've got used to it and it's superfast, but
  people who don't find this procedure -which I found by luck- will get
  very frustrated unless this bug is fixed.

  Oh, I had this problem in previous Ubuntu versions (15.10, 15.04 and
  maybe before) but at some point it got solved. I don't remember if I
  had this problem after updating to 16.04, but I did a clean install
  recently and got it back.

  Dell Latitude E6410
  430-3659 : Dell Wireless 375 Bluetooth Module, Dell Latitude E
  Drivers should be whatever drivers Ubuntu assigns to this hardware. There are 
no proprietary bluetooth drivers in the system configuration.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-bluetooth 0.0.6+16.04.20160526-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug  8 21:03:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-27 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ca
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1667499] [NEW] the difference between 1.38 and 1.5 dpi in the displays settings is huge

2017-02-23 Thread graingert

Public bug reported:

1.38 is far too small, 1.5 is far too big.

I used to use 1.62 on ubuntu 16.10 and that was fine.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu Feb 23 22:25:26 2017
DistUpgraded: 2017-02-23 15:19:02,158 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
InstallationDate: Installed on 2017-02-13 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic.efi.signed 
root=/dev/mapper/lvm-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-02-23 (0 days ago)
dmi.bios.date: 12/23/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B21.1612230252
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B21.1612230252:bd12/23/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
xserver.bootTime: Thu Feb 23 22:23:05 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu9
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 reproducible single-occurrence ubuntu zesty

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

Title:
  the difference between 1.38 and 1.5 dpi in the displays settings is
  huge

Status in xorg package in Ubuntu:
  New

Bug description:
  1.38 is far too small, 1.5 is far too big.

  I used to use 1.62 on ubuntu 16.10 and that was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Thu Feb 23 22:25:26 2017
  DistUpgraded: 2017-02-23 15:19:02,158 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2017-02-13 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001:

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

As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?

Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track that problem separately?

** Also affects: network-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: systemd (Ubuntu Yakkety)
Milestone: None => yakkety-updates

** Changed in: systemd (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Triaged

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

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

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

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

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

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

[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

2017-02-23 Thread Cruz Fernandez

@mikhaildd have you tried to select Settings->Sound->Headphones ?

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

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