Re: [Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

[mash]

Thank you and that's correct. This issue arrived for the first time with
the upgrade to 16.04.

Michael

On Wednesday, July 6, 2016, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> mash, to clarify, did this issue not occur in a Ubuntu release prior to
> 16.04?
>
> ** Changed in: xorg (Ubuntu)
>Importance: Low => Medium
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> ** Tags removed: bios-outdated-a07
> ** Tags added: latest-bios-a07
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1576844
>
> Title:
>   Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+subscriptions
>


-- 
Michael Ash, Chair, Economics
Professor of Economics & Public Policy
University of Massachusetts Amherst
Amherst, MA 01003
Email m...@econs.umass.edu
Tel +1-413-545-4815

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1596536] Re: fatal error: TimeSource: No such file or directory

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit-
ubuntu-yakkety-landing-019

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

Title:
  fatal error: TimeSource: No such file or directory

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  fatal error: TimeSource: No such file or directory

  The C++ API bits from the UI Toolkit lost their uppercase aliases.
  Unsurprisingly anyone using those can't build anymore even though the
  headers still exist.

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

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

[Touch-packages] [Bug 1590672] ProcEnviron.txt

[Ansar K A]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1590672/+attachment/4696173/+files/ProcEnviron.txt

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

Title:
   Mouse pointer disappear after suspend in Xubuntu 16.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   Mouse pointer disappear after suspend in Xubuntu 16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-28 (251 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (35 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1590672] JournalErrors.txt

[Ansar K A]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1590672/+attachment/4696172/+files/JournalErrors.txt

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

Title:
   Mouse pointer disappear after suspend in Xubuntu 16.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   Mouse pointer disappear after suspend in Xubuntu 16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-28 (251 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (35 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1590672] Re: Mouse pointer disappear after suspend in Xubuntu 16.04

[Ansar K A]

apport information

** Tags added: apport-collected xenial

** Description changed:

   Mouse pointer disappear after suspend in Xubuntu 16.04
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2015-10-28 (251 days ago)
+ InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
+ Package: xorg 1:7.7+13ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
+ Tags:  xenial
+ Uname: Linux 4.4.0-28-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-05-31 (35 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1590672/+attachment/4696171/+files/Dependencies.txt

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

Title:
   Mouse pointer disappear after suspend in Xubuntu 16.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   Mouse pointer disappear after suspend in Xubuntu 16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-10-28 (251 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (35 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1599360] Re: wireless device is detected as wired on boot

[Luiz Angelo Daros de Luca]

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

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

Title:
  wireless device is detected as wired on boot

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  On every boot since install, my wireless card is listed on network
  manager as a wired one. If I switch it on and off, it is correctly
  detected.

  It is a vintage asus eeepc 701 with a atheros wireless.

  This is an example of rfkill after switch wireless off and on using
  keyboard shortcut:

  luizluca@brinquedinho:~$ rfkill list
  0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  luizluca@brinquedinho:~$ rfkill list
  0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  4: phy3: Wireless LAN
Soft blocked: yes
Hard blocked: no

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Jul  6 01:08:59 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.3.1 dev wlp1s0  proto static  metric 600 
   169.254.0.0/16 dev wlp1s0  scope link  metric 1000 
   192.168.3.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.3.11  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp1s0  wifi  connected/org/freedesktop/NetworkManager/Devices/5  
PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1468020] Re: Two GPS compatible apps conflict and loose GPS

[Launchpad Bug Tracker]

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

** Changed in: location-service (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Two GPS compatible apps conflict and loose GPS

Status in Canonical System Image:
  Incomplete
Status in location-service package in Ubuntu:
  Expired

Bug description:
  Meizu MX4 with Ubuntu 15.04 r2

  1. run OSMscout (for example)
  2. drive/cycle a distance to confirm that GPS tracking is working fine
  3. run the camera app (for example)
  4. take a few photos (they'll be tagged with GPS info)
  5. switch to OSMscout
  6. drive/cycle and OSM will now not update from GPS

  Haven't tested this with other apps as yet, but it seems that one app
  will take control of the GPS and not hand it back. (For want of a
  better explanation.)

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

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

[Touch-packages] [Bug 1599360] [NEW] wireless device is detected as wired on boot

[Luiz Angelo Daros de Luca]

Public bug reported:

Hello,

On every boot since install, my wireless card is listed on network
manager as a wired one. If I switch it on and off, it is correctly
detected.

It is a vintage asus eeepc 701 with a atheros wireless.

This is an example of rfkill after switch wireless off and on using
keyboard shortcut:

luizluca@brinquedinho:~$ rfkill list
0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
luizluca@brinquedinho:~$ rfkill list
0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
4: phy3: Wireless LAN
Soft blocked: yes
Hard blocked: no

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: Unity
Date: Wed Jul  6 01:08:59 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.3.1 dev wlp1s0  proto static  metric 600 
 169.254.0.0/16 dev wlp1s0  scope link  metric 1000 
 192.168.3.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.3.11  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp1s0  wifi  connected/org/freedesktop/NetworkManager/Devices/5  
PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: apport-bug i386 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/1599360

Title:
  wireless device is detected as wired on boot

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,

  On every boot since install, my wireless card is listed on network
  manager as a wired one. If I switch it on and off, it is correctly
  detected.

  It is a vintage asus eeepc 701 with a atheros wireless.

  This is an example of rfkill after switch wireless off and on using
  keyboard shortcut:

  luizluca@brinquedinho:~$ rfkill list
  0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  luizluca@brinquedinho:~$ rfkill list
  0: eeepc-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
  4: phy3: Wireless LAN
Soft blocked: yes
Hard blocked: no

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Jul  6 01:08:59 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.3.1 dev wlp1s0  proto static  metric 600 
   169.254.0.0/16 dev wlp1s0  scope link  metric 1000 
   192.168.3.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.3.11  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp1s0  wifi  connected/org/freedesktop/NetworkManager/Devices/5  
PB1202 2267e91b4-d9c8-4670-92ce-c966b289cb52  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1599357] [NEW] WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04

[Luiz Angelo Daros de Luca]

Public bug reported:

Hello,

I installed ubuntu 16.04 on the vintage asus eeepc 701.
However, i915 is giving me warnings on dmesg and it is unstable, specially on 
vt-switch (I cannot go back to X).

I'll attach what dmesg shows me.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jul  6 00:52:20 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics 
Controller [1043:82d9]
   Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics 
Controller [1043:82d9]
MachineType: ASUSTeK Computer INC. 701
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet 
splash forcepae vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0910
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jul  6 00:20:43 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

** Attachment added: "dmesg "cut here" messages"
   https://bugs.launchpad.net/bugs/1599357/+attachment/4696130/+files/dmesg.txt

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

Title:
  WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I installed ubuntu 16.04 on the vintage asus eeepc 701.
  However, i915 is giving me warnings on dmesg and it is unstable, specially on 
vt-switch (I cannot go back to X).

  I'll attach what dmesg shows me.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jul  6 00:52:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics 
Controller [1043:82d9]
 Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics 
Controller [1043:82d9]
  MachineType: ASUSTeK Computer INC. 701
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet 
splash forcepae vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably 

[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

I can confirm this behavior recurred in a fresh install of Ubuntu 16.04
on this same machine.

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set 
default route.
  Mar 30 16:13:41 [my_hostname] 

[Touch-packages] [Bug 1580500] Re: No way to share calendar invites/events with calendar-app

[Bill Filler]

I think a few things would need to happen on the content-hub and calendar side 
first
1) content-hub would need to add a new type ContentHub.Calendar (until proper 
mime-type support lands in content-hub). See 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Content.ContentType/
2) Calendar app would register as content-hub destination for this content-type
3) Calendar app needs implement a content-hub importer for text/calendar files 
that would be invoked by content-hub operation. For first cut imported calendar 
events would be saved to the default calendar as specified in calendar settings.

** Changed in: ubuntu-calendar-app
   Status: New => Triaged

** Also affects: content-hub (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-calendar-app
   Importance: Undecided => Medium

** Changed in: content-hub (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  No way to share calendar invites/events with calendar-app

Status in Dekko:
  Triaged
Status in Ubuntu Calendar App:
  Triaged
Status in Ubuntu UX:
  New
Status in content-hub package in Ubuntu:
  New

Bug description:
  It would be great to be able to add calendar invites/events to the
  calendar-app via content-hub for all text/calendar file type
  extensions. (.ics, .ical, .icalendar ...)

  Additionally it would be nice to show some kind of indication in Dekko
  (maybe an icon in the message list?) that an invite has already been
  added to the calendar-app and the users attendance status of Yes, No,
  Maybe. Ideally the user should be able to determine if they have
  already addressed the invite without having to open calendar-app or
  try adding an already added invite/event. This will be especially
  helpful in Dekko's new header section filter for calendar invites.

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

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

[Paul Pianta]

I messed around with this for ages with no luck on my Dell XPS 13 9350.
It seemed to even screw up the bluetooth when I rebooted back into
windows where I wasn't able to remove and re-pair my Microsoft Sculpt
Comfort Mouse.

Then through freak chance I plugged in an older microsoft usb mouse
(with the nano transceiver) and started using that. Not sure why but
later on I retried connecting my Sculpt bluetooth mouse and boom - it
worked straight away.

Was having the same trouble with bluetooth on my other laptop ASUS
Zenbook 305CA but did a full reinstall (Linux Mint 18) with only the usb
mouse plugged in. After install - tried to connect the bluetooth mouse
and it connected first time.

I'm aware that the usb mouse thing could be a total red herring but for
me it is the only thing I can think of out of everything I was trying
that actually made a difference - and on 2 different laptops so I'm
thinking there might be something there for other people to at least try
:/

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[ChenYunChih]

This works!!

https://github.com/Ultimaker/Cura/pull/131

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

-- 
Mailing list: https://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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

[Fritz Hudnut]

@CP:

I took a screenshot, I think that should be pretty clear now.

F

On Mon, Jul 4, 2016 at 5:03 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Fritz Hudnut, my eyes must not be refined enough to see the problem.
>
> ** Changed in: xorg (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1541082
>
> Title:
>   [PowerMac3,1] Blotchy GUI graphics for images
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   The background image and other image files are blotchy.
>
>   ---
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: powerpc
>   BootLog:
>fsck from util-linux 2.27.1
>/dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroRelease: Ubuntu 16.04
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x
> TMDS [1002:5046] (prog-if 00 [VGA controller])
>   InstallationDate: Installed on 2016-01-31 (154 days ago)
>   InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc
> (20160123)
>   Lsusb:
>Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
>Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
>Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
>Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Package: xorg 1:7.7+13ubuntu3
>   PackageArchitecture: powerpc
>   ProcEnviron:
>LANGUAGE=en_US
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro
> quiet splash
>   ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
>   Renderer: Software
>   Tags:  xenial ubuntu
>   Uname: Linux 4.4.0-24-powerpc-smp ppc
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
>   version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+subscriptions
>


** Attachment added: "Screenshot at 2016-07-05 18:27:09.png"
   
https://bugs.launchpad.net/bugs/1541082/+attachment/4696102/+files/Screenshot%20at%202016-07-05%2018%3A27%3A09.png

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1392018] Re: apparmor stops /var/run/ldapi from being read causing ldap to fail

[Seth Arnold]

David, please file a new bug report and be sure to include any AppArmor
DENIED messages from your logs.

Thanks

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

Title:
  apparmor stops /var/run/ldapi from being read causing ldap to fail

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Utopic:
  Won't Fix
Status in openldap source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  * Changes to AppArmor's unix socket mediation in utopic and later
  require servers to have 'rw' file permissions on socket paths,
  compared to just 'w' previously.

  * This bug breaks any application that tries to communicate with slapd
  via the ldapi:// scheme, for example heimdal-kdc.

  * The recommended way to configure slapd in Ubuntu is to authenticate
  via SASL EXTERNAL over the ldapi socket. This bug prevents online
  configuration of slapd (via ldapmodify) in the default setup.

  [Test Case]

  apt-get install slapd
  ldapwhoami -H ldapi:// -QY EXTERNAL

  Expected result:
  dn:gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth

  Actual result:
  ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)

  [Regression Potential]

  * Extremely low potential for regression. No code changes, only
  granting an additional permission on contents of two directories. The
  worst possible regression is that slapd might be permitted to read
  some files it shouldn't, but having such files in /run/{slapd,nslcd}
  seems unlikely.

  [Other Info]

  Test packages can be found in ppa:rtandy/lp1392018

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

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

[Touch-packages] [Bug 1582455] Re: Update to 1.2.2

[Jeremy Bicha]

https://launchpad.net/ubuntu/+source/network-manager-
applet/1.2.2-0ubuntu1

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

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

Title:
  Update to 1.2.2

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  Update to 1.2.2

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

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

[Touch-packages] [Bug 1392018] Re: apparmor stops /var/run/ldapi from being read causing ldap to fail

[David Bonner]

This bug seems to still be be present in Ubuntu 16.04. How do i fix it
so & can use ldap?

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

Title:
  apparmor stops /var/run/ldapi from being read causing ldap to fail

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Utopic:
  Won't Fix
Status in openldap source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  * Changes to AppArmor's unix socket mediation in utopic and later
  require servers to have 'rw' file permissions on socket paths,
  compared to just 'w' previously.

  * This bug breaks any application that tries to communicate with slapd
  via the ldapi:// scheme, for example heimdal-kdc.

  * The recommended way to configure slapd in Ubuntu is to authenticate
  via SASL EXTERNAL over the ldapi socket. This bug prevents online
  configuration of slapd (via ldapmodify) in the default setup.

  [Test Case]

  apt-get install slapd
  ldapwhoami -H ldapi:// -QY EXTERNAL

  Expected result:
  dn:gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth

  Actual result:
  ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)

  [Regression Potential]

  * Extremely low potential for regression. No code changes, only
  granting an additional permission on contents of two directories. The
  worst possible regression is that slapd might be permitted to read
  some files it shouldn't, but having such files in /run/{slapd,nslcd}
  seems unlikely.

  [Other Info]

  Test packages can be found in ppa:rtandy/lp1392018

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

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

[Touch-packages] [Bug 1589703] Re: Alarm clock icon doesn't disappear (appears randomly) when alarm inactive

[Cerberus]

I noticed it appeared sometimes, not always, after midnight, but I
occasionally observed it appearing during the day too. It doesnt happen
often but still it does happen here and there, it seems random to me.

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

Title:
  Alarm clock icon doesn't disappear (appears randomly) when alarm
  inactive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  As in description. In my bq i see sometimes an alarm clock icon even
  if the alarm time passed and the alarm clock is no longer active.

  Set the alarm clock
  Let it ring and turn it off. The icon stays visible for some time which i can 
not exactly specify.

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

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

[Touch-packages] [Bug 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[Ubuntu Foundations Team Bug Bot]

The attachment "mii-tool interface-name searching" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Confirmed

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

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

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

[Touch-packages] [Bug 1598917] Re: windows on external display are displaced when OSK appears on phone

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 - 8.12+16.10.20160705-0ubuntu1

---
unity8 (8.12+16.10.20160705-0ubuntu1) yakkety; urgency=medium

  [ Michael Zanetti ]
  * don't displace windows if the OSK is on another screen (LP:
#1598917)

 -- Michał Sawicz   Tue, 05 Jul 2016
10:00:57 +

** Changed in: unity8 (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/1598917

Title:
  windows on external display are displaced when OSK appears on phone

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  - Connect phone to external display
  - Move dash to the bottom of the screen
  - Tap on the search field

  Expected outcome:
  - Window doesn't move

  Actual outcome:
  - Window is moved up, as if the OSK were being displayed on the external 
screen.

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

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

[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Leonid]

So, right now i am working with new (native ubuntu, 5.37) libbluetooth
and with bluez 5.27 downloaded from bluez.org, and there are no lags at
all, only disconnects. So i guess the reason for lags is in bluez
itself.

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

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
 

[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

[Christopher M. Penalver]

mash, to clarify, did this issue not occur in a Ubuntu release prior to
16.04?

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

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

** Tags removed: bios-outdated-a07
** Tags added: latest-bios-a07

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1584496] Re: Nouveau randomly freezes system

[Christopher M. Penalver]

Jason Yundt, could you please capture the crash following
https://wiki.ubuntu.com/DebuggingSystemCrash ?

** Tags added: latest-bios-f11

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1584496/+attachment/4668137/+files/JournalErrors.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1584496/+attachment/4668136/+files/Dependencies.txt

** Description changed:

- I'm running kubuntu 16.04.
  If I'm running Nouveau, my system randomly lockups.
- I have a MSI Geforce 660 Ti
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
- ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
- Uname: Linux 4.4.0-22-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2
- Architecture: amd64
- CurrentDesktop: KDE
- Date: Sun May 22 12:38:07 2016
- InstallationDate: Installed on 2016-05-22 (0 days ago)
- InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
- ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: xserver-xorg-video-nouveau
- UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ WORKAROUND: Use the nvidia proprietary drivers.
+ 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sdb2: clean, 287853/15499264 files, 3497348/61988608 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1000]
+  NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1000]
  InstallationDate: Installed on 2016-06-16 (18 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=780df466-9725-4142-92c6-bb2bd6ce8291 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial kubuntu
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

Title:
  Nouveau randomly freezes system

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I'm running Nouveau, my system randomly lockups.

  WORKAROUND: Use the nvidia proprietary drivers.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sdb2: clean, 287853/15499264 files, 3497348/61988608 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: NVIDIA Corporation GK104 [GeForce 

[Touch-packages] [Bug 1573229] Re: Greeter does not rotate

[Phil UK]

I did raise this under
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1576962 Is there
any update on this it is confirmed, but no update has been added since
the 7-5?

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

Title:
  Greeter does not rotate

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

Bug description:
  The Ubuntu Touch start/welcome screen (with the big wheel) does not
  rotate following the tablet orientation.

  Device: Aquaris M10
  Ubuntu version: Ubuntu touch OTA 10.1

  This bug can be very tedious for convergence, when you are in desktop
  mode, with the tablet on the table upside-down and using a bluetooth
  mouse tryng to start the desktop (with no security configuration)
  because the cursor movements follow an opposite direction to mouse
  movements.

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

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

[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property

[Launchpad Bug Tracker]

** Branch linked: lp:~dubstar-04/ubuntu-ui-toolkit/MainViewMouseFocus

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

Title:
  MainView intercepts MouseArea's cursorShape property

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The MouseArea CursorShape doesnt have any effect.

  Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html

  Expected Behavour:
  Mouse image shows selected Qt cursor

  Experienced Behavour:
  The regular arrow is displayed.

  Example Code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  objectName: "mainView"
  applicationName: "mouseTest"

  width: units.gu(100)
  height: units.gu(75)

  Rectangle{
  anchors.fill: parent
  color: UbuntuColors.coolGrey

  MouseArea{
  anchors.fill: parent
  cursorShape: Qt.CrossCursor
  hoverEnabled: true
  onClicked: console.log("In MouseArea")
  }
  }
  }

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

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

[Touch-packages] [Bug 1590432] Re: elan touchpad freezes randomly on ubuntu 16.04

[lillo82]

im a semi newbie , and im afraid to make a mess... plus i cant do a backup at 
the moment, maybe in the future when i have more time and an external hd.
anyway, i have tried to do

sudo modprobe -r elan_i2c
sudo modprobe elan_i2c

and then my  dmesg | grep -i elan is this:

lillo@lillo-X540SA:~$ dmesg | grep -i elan 
[   14.290318] i2c-ELAN1000:00 supply vcc not found, using dummy regulator
[   14.418179] input: Elan Touchpad as 
/devices/pci:00/808622C1:03/i2c-9/i2c-ELAN1000:00/input/input5
[  906.455349] elan_i2c i2c-ELAN1000:00: failed to read report data: -110
[ 1069.681827] i2c-ELAN1000:00 supply vcc not found, using dummy regulator
[ 1070.713682] elan_i2c i2c-ELAN1000:00: writing cmd (0x0005) failed: -110
[ 1070.713692] elan_i2c i2c-ELAN1000:00: device reset failed: -110
[ 1070.713702] elan_i2c i2c-ELAN1000:00: device initialize failed: -110
[ 1071.773741] elan_i2c i2c-ELAN1000:00: writing cmd (0x0005) failed: -110
[ 1071.773761] elan_i2c i2c-ELAN1000:00: device reset failed: -110
[ 1071.773778] elan_i2c i2c-ELAN1000:00: device initialize failed: -110
[ 1072.833816] elan_i2c i2c-ELAN1000:00: writing cmd (0x0005) failed: -110
[ 1072.833834] elan_i2c i2c-ELAN1000:00: device reset failed: -110
[ 1072.833852] elan_i2c i2c-ELAN1000:00: device initialize failed: -110
[ 1072.881767] elan_i2c: probe of i2c-ELAN1000:00 failed with error -110



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

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

Title:
  elan touchpad freezes randomly on ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  when i visit some websites, with a lot of videos or animations, my
  touchpad freezes, and the only thing to do is ctrl alt print REISUB,
  because if I open a terminal and write sudo shutdown -r now, the
  computer freezes and i have to click the power button...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  8 15:12:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10c0]
  InstallationDate: Installed on 2016-05-10 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SA
  ProcEnviron:
   LANGUAGE=it_IT
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=3d82a398-6d04-4ebd-9047-72877a62c81e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SA.207:bd11/25/2015:svnASUSTeKCOMPUTERINC.:pnX540SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X540SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jun  8 15:04:33 2016
  

Re: [Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Jyoti]

there is not Portuguese layout

2016-05-20 4:19 GMT+01:00 kevin gunn :

> ** Changed in: canonical-devices-system-image
>  Assignee: (unassigned) => Stephen M. Webb (bregma)
>
> ** Changed in: canonical-devices-system-image
> Milestone: None => 12
>
> ** Changed in: canonical-devices-system-image
>Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1576161).
> https://bugs.launchpad.net/bugs/1565236
>
> Title:
>   AltGr not working on external keyboards
>
> Status in Canonical System Image:
>   Confirmed
> Status in Mir:
>   In Progress
> Status in Mir 0.23 series:
>   Triaged
> Status in mir package in Ubuntu:
>   Confirmed
> Status in ubuntu-system-settings package in Ubuntu:
>   Incomplete
> Status in unity8 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Using my keyboard with Spanish layout:
>
>- PC: Everything works perfect.
>- Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).
>
>   Extra info:
>
>   - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (
> http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
>   - Ubuntu Desktop: 12.04
>   - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions
>

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

-- 
Mailing list: https://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 1565236] Re: AltGr not working on external keyboards

[Jyoti]

AltGr not working on external keyboards. There is not Portuguese layout
with '`^~ etc


2016-05-20 4:19 GMT+01:00 kevin gunn :

> ** Changed in: canonical-devices-system-image
>  Assignee: (unassigned) => Stephen M. Webb (bregma)
>
> ** Changed in: canonical-devices-system-image
> Milestone: None => 12
>
> ** Changed in: canonical-devices-system-image
>Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1576161).
> https://bugs.launchpad.net/bugs/1565236
>
> Title:
>   AltGr not working on external keyboards
>
> Status in Canonical System Image:
>   Confirmed
> Status in Mir:
>   In Progress
> Status in Mir 0.23 series:
>   Triaged
> Status in mir package in Ubuntu:
>   Confirmed
> Status in ubuntu-system-settings package in Ubuntu:
>   Incomplete
> Status in unity8 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Using my keyboard with Spanish layout:
>
>- PC: Everything works perfect.
>- Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).
>
>   Extra info:
>
>   - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (
> http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
>   - Ubuntu Desktop: 12.04
>   - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions
>

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property

[Dubstar_04]

** Branch linked: lp:~dubstar-04/ubuntu-ui-toolkit/MainViewMouseFocus

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

Title:
  MainView intercepts MouseArea's cursorShape property

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The MouseArea CursorShape doesnt have any effect.

  Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html

  Expected Behavour:
  Mouse image shows selected Qt cursor

  Experienced Behavour:
  The regular arrow is displayed.

  Example Code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  objectName: "mainView"
  applicationName: "mouseTest"

  width: units.gu(100)
  height: units.gu(75)

  Rectangle{
  anchors.fill: parent
  color: UbuntuColors.coolGrey

  MouseArea{
  anchors.fill: parent
  cursorShape: Qt.CrossCursor
  hoverEnabled: true
  onClicked: console.log("In MouseArea")
  }
  }
  }

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

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

[Touch-packages] [Bug 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[Nathan Stratton Treadway]

I'm not at all familiar with the net-tools source, but here's a quick
proof-of-concept patch to pull the list of interface names out of
/proc/net/dev (silently skipping any that don't support the SIOCGMIIPHY
ioctl [lo, lxcbr0, etc.]).

= first example =
./mii-tool_lp962616 
enp4s0: negotiated 100baseTx-FD, link ok
enp9s0: no link
enp8s0: negotiated 1000baseT-FD flow-control, link ok
enp6s0: negotiated 1000baseT-FD flow-control, link ok

= second example =
./mii-tool_lp962616 
eno1: negotiated 1000baseT-FD flow-control, link ok
SIOCGMIIPHY on 'eno2' failed: Resource temporarily unavailable


(Obviously one downside of /proc/net/dev is that it isn't always in 
alphabetical order...)

** Patch added: "mii-tool interface-name searching"
   
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+attachment/4696078/+files/mii-tool.c_lp962616.patch

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Confirmed

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

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

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

[Touch-packages] [Bug 1599295] Re: Apport should not just silently fail when it detects the specific crash report has already been uploaded

[Jeremy Bicha]

** No longer affects: ubuntu-gnome

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

Title:
  Apport should not just silently fail when it detects the specific
  crash report has already been uploaded

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  I have recently been having some trouble with Apport, I asked it to
  submit a crash report however there was a problem and it never
  launched the browser page. Now every time I try to manually submit the
  .crash file I get an error saying that the crash report has been
  already submitted (this is logged in syslog and not anywhere obvious).

  When I use the GUI, and when I use the apport-cli program and ask it
  to submit a report now on the matter it just silently exists without
  telling me anything. So how am I even meant to know what the URL is
  that it has been submitted to?

  So I think that Apport should really not just silently fail and should
  instead tell the user that the crash has already been submitted and
  then actually give them the URL to get to it because otherwise I don't
  know how one is expected to find it unless they get the Apport's
  signature generator working manually or something.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1599297] Re: One should be able to request the URL for a specific crash report

[Jeremy Bicha]

Your crash may have been reported to https://errors.ubuntu.com/ instead
of to Launchpad directly.

https://wiki.ubuntu.com/ErrorTracker

** No longer affects: ubuntu-gnome

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

Title:
  One should be able to request the URL for a specific crash report

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  As I said in Bug #1599295, when one submits a crash report and it for
  some reason fails to open a browser tab/window with the reporting bit
  one is unable to find the URL to go to as Apport just silently fails
  (though does log something to syslog).

  So I think that as well as the other bug being fixed, it would be
  really good if one could specify a crash signature or a .crash file
  and then ask Apport to provide the URL to the uploaded contents where
  one can then properly report the crash in question (perhaps this could
  be done by a command-line option or something).

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1599301] [NEW] GenericScopeView test getting stuck

[Michał Sawicz]

Public bug reported:

Every once in a while britney comes back with a failed run that is, in
fact, a timed out run. Every time it gets stuck on GenericScopeView -
but on different tests.

Here's an example log.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160705_203355@/log.gz

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity8 8.12+16.04.20160705-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul  5 23:25:40 2016
InstallationDate: Installed on 2016-05-06 (60 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Status: Triaged


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

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

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  GenericScopeView test getting stuck

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Every once in a while britney comes back with a failed run that is, in
  fact, a timed out run. Every time it gets stuck on GenericScopeView -
  but on different tests.

  Here's an example log.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/u/unity8/20160705_203355@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160705-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  5 23:25:40 2016
  InstallationDate: Installed on 2016-05-06 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1599190] Re: Data switch disabled until System Settings is opened

[Anupam]

possible duplicate of bug #1598010

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

Title:
  Data switch disabled until System Settings is opened

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

Bug description:
  Test case.
  - Flash rc image.
  - Insert a SIM card.
  - Complete the wizard.
  - Dismiss the welcome screen.
  - Introduce the SIM pin.
  - Open network indicator.

  Expected result.
  - Mobile data switch is enabled.

  Actual result.
  - No data connection active by default and mobile data switch disabled in the 
indicator.
  - Rebooting doesn't activate it.
  - Opening System Settings > Mobile data activates the switch in the indicator.

  current build number: 59
  device name: krillin
  channel: ubuntu-touch/rc/bq-aquaris.en

  Also checked with silo 25.

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

** Description changed:

- [Impact] 
+ [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.
  
  [Test Case]
+ First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.
+ 
  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
- 9. click can play audio (eg, SnapRecorder)
- 10. click can record audio if trust-store allows
+ 9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
+ 10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)
  
  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until phase
- 2 is implemented).
+ 2 is implemented which will be in a different bug).
  
  The attached script tests 1-7. 9 and 10 require testing on a device and
  using
  
- [Regression Potential] 
- The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected. 
- 
+ [Regression Potential]
+ The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected.
  
  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.
  
  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on connection
  if the apparmor security label of the connecting peer starts with
  "snap." which will identify it as a snap application.
  
  Pulseaudio with the patch is available as part of the landing request at
  https://requests.ci-train.ubuntu.com/#/ticket/1428

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.

  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
  10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented which will be in a different bug).

  The attached 

[Touch-packages] [Bug 1599295] Re: Apport should not just silently fail when it detects the specific crash report has already been uploaded

[Launching Dumplings]

Related: Bug #1599297

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

Title:
  Apport should not just silently fail when it detects the specific
  crash report has already been uploaded

Status in Apport:
  New
Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  I have recently been having some trouble with Apport, I asked it to
  submit a crash report however there was a problem and it never
  launched the browser page. Now every time I try to manually submit the
  .crash file I get an error saying that the crash report has been
  already submitted (this is logged in syslog and not anywhere obvious).

  When I use the GUI, and when I use the apport-cli program and ask it
  to submit a report now on the matter it just silently exists without
  telling me anything. So how am I even meant to know what the URL is
  that it has been submitted to?

  So I think that Apport should really not just silently fail and should
  instead tell the user that the crash has already been submitted and
  then actually give them the URL to get to it because otherwise I don't
  know how one is expected to find it unless they get the Apport's
  signature generator working manually or something.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1598010] Re: cellular data switch disabled on nexus 4

[Anupam]

Is this not an intended behaviour?
https://bugs.launchpad.net/ubuntu-ux/+bug/1373463/comments/39

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

Title:
  cellular data switch disabled on nexus 4

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

Bug description:
  
  Cellular data switch is disabled on nexus 4. 

  rc_proposed: r476
  Ubuntu Image Part: 20160701

  Mobile data cannot be activated on this device (possibly others) as
  the cellular data switch in settings and in the indicator are
  disabled.

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

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

[Touch-packages] [Bug 1599297] [NEW] One should be able to request the URL for a specific crash report

[Launching Dumplings]

Public bug reported:

As I said in Bug #1599295, when one submits a crash report and it for
some reason fails to open a browser tab/window with the reporting bit
one is unable to find the URL to go to as Apport just silently fails
(though does log something to syslog).

So I think that as well as the other bug being fixed, it would be really
good if one could specify a crash signature or a .crash file and then
ask Apport to provide the URL to the uploaded contents where one can
then properly report the crash in question (perhaps this could be done
by a command-line option or something).

I am running Ubuntu GNOME 16.04 with GNOME 3.20.

** Affects: apport
 Importance: Undecided
 Status: New

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

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


** Tags: xenial

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

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

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

Title:
  One should be able to request the URL for a specific crash report

Status in Apport:
  New
Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  As I said in Bug #1599295, when one submits a crash report and it for
  some reason fails to open a browser tab/window with the reporting bit
  one is unable to find the URL to go to as Apport just silently fails
  (though does log something to syslog).

  So I think that as well as the other bug being fixed, it would be
  really good if one could specify a crash signature or a .crash file
  and then ask Apport to provide the URL to the uploaded contents where
  one can then properly report the crash in question (perhaps this could
  be done by a command-line option or something).

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1599295] [NEW] Apport should not just silently fail when it detects the specific crash report has already been uploaded

[Launching Dumplings]

Public bug reported:

I have recently been having some trouble with Apport, I asked it to
submit a crash report however there was a problem and it never launched
the browser page. Now every time I try to manually submit the .crash
file I get an error saying that the crash report has been already
submitted (this is logged in syslog and not anywhere obvious).

When I use the GUI, and when I use the apport-cli program and ask it to
submit a report now on the matter it just silently exists without
telling me anything. So how am I even meant to know what the URL is that
it has been submitted to?

So I think that Apport should really not just silently fail and should
instead tell the user that the crash has already been submitted and then
actually give them the URL to get to it because otherwise I don't know
how one is expected to find it unless they get the Apport's signature
generator working manually or something.

I am running Ubuntu GNOME 16.04 with GNOME 3.20.

** Affects: apport
 Importance: Undecided
 Status: New

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

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


** Tags: xenial

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

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

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

Title:
  Apport should not just silently fail when it detects the specific
  crash report has already been uploaded

Status in Apport:
  New
Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  I have recently been having some trouble with Apport, I asked it to
  submit a crash report however there was a problem and it never
  launched the browser page. Now every time I try to manually submit the
  .crash file I get an error saying that the crash report has been
  already submitted (this is logged in syslog and not anywhere obvious).

  When I use the GUI, and when I use the apport-cli program and ask it
  to submit a report now on the matter it just silently exists without
  telling me anything. So how am I even meant to know what the URL is
  that it has been submitted to?

  So I think that Apport should really not just silently fail and should
  instead tell the user that the crash has already been submitted and
  then actually give them the URL to get to it because otherwise I don't
  know how one is expected to find it unless they get the Apport's
  signature generator working manually or something.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

@Simon, per the SRU process, I've done the paperwork to pursue the SRU
but leaving this as 'In Progress' due to my comments. Please attach an
updated debdiff and I'll review and adjust the bug as appropriate.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can play audio (eg, SnapRecorder)
  10. click can record audio if trust-store allows

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential] 
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected. 

  
  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

@Simon, finally, in reading the patch this will affect both strict and
devmode and so the patch should "if startswith 'snap.' and process is in
enforce mode ; then block recording".

This will be needed for the phase 2 implementation as well, so it is not
wasted effort. I've asked the apparmor devs to comment in the trello
card if there is an apparmor API for this. Be cognizant of TOUCTOU here
but also understand that a snap is not able to change its enforcement
mode so a TOCTOU is not security relevant for this particular change.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can play audio (eg, SnapRecorder)
  10. click can record audio if trust-store allows

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential] 
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected. 

  
  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1597683] Re: Cellular data switch visible on M10 tablet

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-network -
0.8.0+16.10.20160705.1-0ubuntu1

---
indicator-network (0.8.0+16.10.20160705.1-0ubuntu1) yakkety; urgency=medium

  [ Pete Woods ]
  * Only include the mobile data switch when we have modems (LP:
#1597683)

  [ Antti Kaijanmäki, Pete Woods ]
  * Mobile Data Switch should also track the presence of the
SimForMobileData. (LP: #1597615)

 -- Pete Woods   Tue, 05 Jul 2016 10:51:08
+

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Cellular data switch visible on M10 tablet

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  M10 FHD with rc-proposed (r130)

  When I pull down the indicators panel I can see greyed out 'Cellular data' 
and a switch next to it.
  Screenshot attached.

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

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

[Touch-packages] [Bug 1598978] Re: No Notification For Repeat Google Authenticator Attempts

[Robert Ancell]

Can you attach /var/log/lightdm/lightdm.log after this problem occurs?

** Package changed: lightdm (Ubuntu) => lightdm

** Also affects: lightdm-gtk-greeter
   Importance: Undecided
   Status: New

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

Title:
  No Notification For Repeat Google Authenticator Attempts

Status in Light Display Manager:
  Incomplete
Status in LightDM GTK+ Greeter:
  New

Bug description:
  Not using Ubuntu, but Arch Linux. Lightdm version 1.18.2. I have
  enabled 2fa using google authentication (pam_google_authenticator.so
  enabled in pam). The first time works great; I enter my password and
  then a small banner pops up saying "Authentication Code". But say I
  enter my password incorrectly (which doesn't get checked until the
  authentication code is good) the second time I have to enter the
  authentication code there is no banner. Obviously not critical, but it
  does make it sometimes tough to remember if this is an authentication
  code entry or a regular password entry.

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

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

[Touch-packages] [Bug 1597615] Re: The cellular data option in network indicator is disabled after turning on and turning off the flight mode.

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-network -
0.8.0+16.10.20160705.1-0ubuntu1

---
indicator-network (0.8.0+16.10.20160705.1-0ubuntu1) yakkety; urgency=medium

  [ Pete Woods ]
  * Only include the mobile data switch when we have modems (LP:
#1597683)

  [ Antti Kaijanmäki, Pete Woods ]
  * Mobile Data Switch should also track the presence of the
SimForMobileData. (LP: #1597615)

 -- Pete Woods   Tue, 05 Jul 2016 10:51:08
+

** Changed in: indicator-network (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 indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1597615

Title:
  The cellular data option in network indicator is disabled after
  turning on and turning off the flight mode.

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2

  Precondition:
  SIM card is inserted and Cellular data is open.

  Steps:
  1.Pull down the network indicator,and turn on flight mode toggle.
  2.After a few seconds turn  off the flight mode and check the cellular data 
option.

  Actual result:
  The state is on but option bar is disable and cannot be tapping. Go to 
cellular settings page, it works fine there.

  Expected result:
  The cellular data option should be still enabled after turn on and turning 
off the flight mode.

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

** Description changed:

- Until we have a proper trust-store implementation with snappy and on the
- desktop/ubuntu core we want pulseaudio to simply deny any audio
- recording request coming from an app shipped as part of a snap.
+ [Impact] 
+ Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.
+ 
+ [Test Case]
+ 1. unconfined can play audio
+ 2. unconfined can record audio
+ 3. non-snap confined can play audio
+ 4. non-snap confined can record audio
+ 5. snap confined can play audio
+ 6. snap confined cannot record audio
+ 7. snap confined devmode can record audio
+ 8. indicator-sound and 'Sound Settings... works'
+ 9. click can play audio (eg, SnapRecorder)
+ 10. click can record audio if trust-store allows
+ 
+ Currently '6' is not implemented and all snaps may record audio. When
+ this bug is fixed, no snaps should be able to record audio (until phase
+ 2 is implemented).
+ 
+ The attached script tests 1-7. 9 and 10 require testing on a device and
+ using
+ 
+ [Regression Potential] 
+ The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected. 
+ 
+ 
+ Original description:
+ Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.
  
  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on connection
  if the apparmor security label of the connecting peer starts with
  "snap." which will identify it as a snap application.
  
  Pulseaudio with the patch is available as part of the landing request at
  https://requests.ci-train.ubuntu.com/#/ticket/1428

** Attachment removed: "1583057-test.sh"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696048/+files/1583057-test.sh

** Attachment added: "1583057-test.sh"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696049/+files/1583057-test.sh

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can play audio (eg, SnapRecorder)
  10. click can record audio if trust-store allows

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential] 
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected. 

  
  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and 

[Touch-packages] [Bug 1597683] Re: Cellular data switch visible on M10 tablet

[Pat McGowan]

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

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

Title:
  Cellular data switch visible on M10 tablet

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  M10 FHD with rc-proposed (r130)

  When I pull down the indicators panel I can see greyed out 'Cellular data' 
and a switch next to it.
  Screenshot attached.

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

@barry any more steps we can do to debug

** Changed in: system-image (Ubuntu)
 Assignee: (unassigned) => Barry Warsaw (barry)

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

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

Title:
  Checking for updates never finishes on 3G

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

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

Set auto download to never (which is how I usually set it) rebooted and it 
worked fine on 3G
Set back to on wifi and it hung.

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

Title:
  Checking for updates never finishes on 3G

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

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

I should mention that when testing this installed test packages then
logged out of my session, killed my user's pulseaudio then logged back
in. I suppose I could have also done 'killall pulseaudio' and have it
restart automatically instead.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

The functionality does not work as expected and I am able to record when
running parecord under an apparmor profile that starts with 'snap.' (see
attached).

** Attachment added: "1583057-test.sh"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696048/+files/1583057-test.sh

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

The functionality does not work as expected and I am able to record when
running parecord under an apparmor profile that starts with 'snap.' (see
attached).

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1599290] [NEW] Hashsum error installing 101+ packages in 16.04 Docker image

[Matt Bearup]

Public bug reported:

When using the official Ubuntu 16.04 Docker image on a 16.04 Dockerhost (Docker 
version 1.11.2), if we run an apt-get command that installs > 100 packages, the 
101st package will fail as a hashsum mismatch. E.g.
Get:101 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 libldap-2.4-2 
amd64 2.4.42+dfsg-2ubuntu3 [160 kB]
Err:101 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 libldap-2.4-2 
amd64 2.4.42+dfsg-2ubuntu3
  Hash Sum mismatch

If the packages are installed via apt, or package installs are divided
so we never exceed 100 packages in a single command, the error never
occurs. But if we install 101 packages, the 101st is always a hashsum
mismatch. In testing thus far it only repros in the 16.04 Docker image
on a 16.04 Dockerhost. It doesn't repro if the 16.04 container is
running on a 14.04 host, nor in VM's hosted in the cloud (e.g. Azure) or
locally. Have not tried a bare metal server. Error occurs with latest
apt package (1.2.12~ubuntu16.04.1).

See below for a simplified example Dockerfile which will exceed 100
packages and trigger the error during build.

FROM ubuntu:16.04

RUN apt-get update -qq && apt-get install -y cifs-utils cmake clang llvm 
libc++1 libc++-dev \
libunwind-dev uuid-dev libxml2-dev libssl-dev libssh2-1-dev curl \
lttng-tools lttng-modules-dkms liblttng-ust-dev chrpath members sshpass \
nodejs nodejs-legacy npm

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

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

Title:
  Hashsum error installing 101+ packages in 16.04 Docker image

Status in apt package in Ubuntu:
  New

Bug description:
  When using the official Ubuntu 16.04 Docker image on a 16.04 Dockerhost 
(Docker version 1.11.2), if we run an apt-get command that installs > 100 
packages, the 101st package will fail as a hashsum mismatch. E.g.
  Get:101 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 
libldap-2.4-2 amd64 2.4.42+dfsg-2ubuntu3 [160 kB]
  Err:101 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 
libldap-2.4-2 amd64 2.4.42+dfsg-2ubuntu3
Hash Sum mismatch

  If the packages are installed via apt, or package installs are divided
  so we never exceed 100 packages in a single command, the error never
  occurs. But if we install 101 packages, the 101st is always a hashsum
  mismatch. In testing thus far it only repros in the 16.04 Docker image
  on a 16.04 Dockerhost. It doesn't repro if the 16.04 container is
  running on a 14.04 host, nor in VM's hosted in the cloud (e.g. Azure)
  or locally. Have not tried a bare metal server. Error occurs with
  latest apt package (1.2.12~ubuntu16.04.1).

  See below for a simplified example Dockerfile which will exceed 100
  packages and trigger the error during build.

  FROM ubuntu:16.04

  RUN apt-get update -qq && apt-get install -y cifs-utils cmake clang llvm 
libc++1 libc++-dev \
  libunwind-dev uuid-dev libxml2-dev libssl-dev libssh2-1-dev curl \
  lttng-tools lttng-modules-dkms liblttng-ust-dev chrpath members sshpass \
  nodejs nodejs-legacy npm

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

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

[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend

[Launching Dumplings]

It should also be noted that this issue does not seem to affect gnome-
shell areas, that is it is not seemingly present in the Activities
Overview nor the Top Bar.

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

Title:
  Strange font issue after awakening from suspend

Status in GTK+:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I awoke my computer from suspend last week on Thursday
  (23/06/2016) I found that all the text from all the title bars was
  missing, so I restarted gnome-shell as this normally fixes such
  problems, doing so seemed to make some text appear, but most not, as
  you can see from these images until I restarted my machine it was
  almost impossible to use:

  System_Monitor_No_Text.png
  Shutter_Main_Window_Font_Issue.png
  File_Chooser_Font_Issue.png
  Title_Bar_Partly_Missing.png
  Settings_Text_Issue.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 27 21:23:02 2016
  InstallationDate: Installed on 2016-05-15 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

I managed to repro it at 16:09 and 16:19 in the following log from
system-image. I got it both with download anytime and download wifi only
so that seems to not be related.

After 10 mins system-image reported a timeout error which resulted in
"Software is up to date" while a timeout error should really be reported
in the UI.


** Attachment added: "client.log"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588349/+attachment/4696044/+files/client.log

** Also affects: system-image (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: qtbase-opensource-src (Ubuntu)

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in system-image package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend

[Launching Dumplings]

Upstream said it's likely to be a driver problem, where should I report
this issue then? And is there any way to reload the driver or something
to fix this issue without having to completely restart the machine as it
is a bit annoying?

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

Title:
  Strange font issue after awakening from suspend

Status in GTK+:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I awoke my computer from suspend last week on Thursday
  (23/06/2016) I found that all the text from all the title bars was
  missing, so I restarted gnome-shell as this normally fixes such
  problems, doing so seemed to make some text appear, but most not, as
  you can see from these images until I restarted my machine it was
  almost impossible to use:

  System_Monitor_No_Text.png
  Shutter_Main_Window_Font_Issue.png
  File_Chooser_Font_Issue.png
  Title_Bar_Partly_Missing.png
  Settings_Text_Issue.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 27 21:23:02 2016
  InstallationDate: Installed on 2016-05-15 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1586955] User can swipe the incoming call notificationdialog

[Mike]

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

What do you mean with “voice mail”?
Sorry I didn't understand 

Su martedì 5 luglio 2016 21:03:34 CEST, Pat McGowan 
 ha scritto:
> *** This bug is a duplicate of bug 1512430 ***
> https://bugs.launchpad.net/bugs/1512430
> 
> Yes its a dupe
> @jibel I find I can swipe away the dialog at any time, without 
> changing volume, just by grabbing above or below the slider. For 
> me it results in the call going to voice mail, not continuing to 
> ring.On another bug we theorized perhaps if voice mail isn't 
> enabled the behavior is incorrect.
> 
> ** This bug has been marked a duplicate of bug 1512430
>[phone] Shouldn't be able to swipe away incoming call notification
> 


-- 
Inviato dal mio dispositivo Ubuntu

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

Title:
  User can swipe the incoming call notification dialog

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

Bug description:
  current build number: 338
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  
  Test Case:
  1. With DUT locked and display turned off, send a call to the DUT
  2. On DUT, when the incoming call notification is displayed, change the 
volume with the hardware buttons
  3. Wait until the answer dialog is displayed again and do a left edge swipe

  Aktual result
  User can swipe the incoming call notification dialog, leaving no way to take 
or reject the call.

  Expected result
  The dialog cannot be dismissed.

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

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

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Martin Pitt]

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: landscape-client (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: Won't Fix

** Changed in: systemd (Ubuntu Yakkety)
   Status: Won't Fix => Fix Released

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  In Progress
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debian 

Re: [Touch-packages] [Bug 1586955] User can swipe the incoming call notificationdialog

[Mike]

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

Yeah.
I didn't see this bug

Su martedì 5 luglio 2016 18:13:16 CEST, Michal Predotka 
 ha scritto:
> Isn't this bug a duplicate of bug #1512430 ?
> 


-- 
Inviato dal mio dispositivo Ubuntu

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

Title:
  User can swipe the incoming call notification dialog

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

Bug description:
  current build number: 338
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  
  Test Case:
  1. With DUT locked and display turned off, send a call to the DUT
  2. On DUT, when the incoming call notification is displayed, change the 
volume with the hardware buttons
  3. Wait until the answer dialog is displayed again and do a left edge swipe

  Aktual result
  User can swipe the incoming call notification dialog, leaving no way to take 
or reject the call.

  Expected result
  The dialog cannot be dismissed.

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

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

[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend

[Launching Dumplings]

This issue has now occurred again after awakening from a suspend.

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

Title:
  Strange font issue after awakening from suspend

Status in GTK+:
  Unknown
Status in Ubuntu GNOME:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I awoke my computer from suspend last week on Thursday
  (23/06/2016) I found that all the text from all the title bars was
  missing, so I restarted gnome-shell as this normally fixes such
  problems, doing so seemed to make some text appear, but most not, as
  you can see from these images until I restarted my machine it was
  almost impossible to use:

  System_Monitor_No_Text.png
  Shutter_Main_Window_Font_Issue.png
  File_Chooser_Font_Issue.png
  Title_Bar_Partly_Missing.png
  Settings_Text_Issue.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 27 21:23:02 2016
  InstallationDate: Installed on 2016-05-15 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

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

** Changed in: pulseaudio (Ubuntu Xenial)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Anupam]

@Pat wi-fi only

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

@anupam what is your auto download setting?

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1588349] Re: Checking for updates never finishes on 3G

[Pat McGowan]

I reproduced one case where there was an update available but something
may have failed during the download so the UI got into a confused state
with several different symptoms, the first was to get stuck on the
spinner indefinitely. Renetering the panel showed an already downloaded
system update.

So perhaps just generally racy logic. There is a rewrite of this panel
in progress to address similar symptoms.

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Jonas G. Drange (jonas-drange)

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Bill Filler (bfiller)

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

Title:
  Checking for updates never finishes on 3G

Status in Canonical System Image:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If I'm using wi-fi and go to settings and then select updates, "Checking for 
updates..." screen appears with a spinner for a few seconds; if there is any 
update available it shows, otherwise informs about the unavailability of 
updates.
  But while using mobile data (3G/H) *if there is no update available*, it gets 
stuck on the "Checking for updates..." screen and the spinner keeps spinning. I 
waited as long as 10-15 minutes.
  Note: If there is an update available then the behaviour is normal, i.e. 
shows the available update(s) after a few seconds.
  I'm seeing this behaviour from the very beginning (OTA-6 days).

  Related to bug #1528886

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

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

[Touch-packages] [Bug 1598902] Re: 16.04: network manager inconsistency in WIFI state

[Aron Xu]

** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)

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

Title:
  16.04: network manager inconsistency in WIFI state

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Please see:

  http://askubuntu.com/questions/794769/16-04-networking-ux-
  inconsistent-with-wifi-state

  Reposted here:

  HW: Bus 003 Device 002: ID 13b1:003f Linksys WUSB6300 802.11a/b/g/n/ac 
Wireless Adapter [Realtek RTL8812AU]
  Net:   *-network
 description: Wireless interface
 physical id: 3
 bus info: usb@3:2
 logical name: enxc8d719c1088a
 serial: c8:d7:19:c1:08:8a
 capabilities: ethernet physical wireless
 configuration: broadcast=yes driver=rtl8812au ip=192.168.1.171
 multicast=yes wireless=IEEE 802.11AC

  This is from 16.04LTS. A few points:

  The WIFI USB card driver install was flawless.

  Connecting to my WIFI works as expected.

  When the system enters into suspend mode, and returns the network
  interface continues to function as expected.

  However, the UX on the desktop has a LAN connection Icon, and as you
  can see from the screenshot, it doesn't show it as connected to a
  SSID.

  enter image description here I'm more concerned about the UX here, and
  inconsistency, and I don't know where the UX gets the information to
  update the state. Where should I start looking, and is this a known
  issue if not we can forward it to the team to look at it.

  Again this is a usability issue, I'm looking at things that may
  confuse the average non-techie person. And aside from there, there's a
  security concern that the user should be made aware of what SSID they
  are connected on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul  4 10:15:00 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev enxc8d719c1088a  proto static  metric 600 
   169.254.0.0/16 dev enxc8d719c1088a  scope link  metric 1000 
   192.168.1.0/24 dev enxc8d719c1088a  proto kernel  scope link  src 
192.168.1.171  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH
   OASIS_5GHz  e19433e4-ed9e-48bb-a374-b785593ae43e  802-11-wireless  
1467652452  Mon 04 Jul 2016 10:14:12 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/0  yes enxc8d719c1088a  
activated  /org/freedesktop/NetworkManager/ActiveConnection/6 
   Wired connection 1  51f761ab-b68d-44c0-9a79-d96dbe055452  802-3-ethernet   
1467608763  Sun 03 Jul 2016 10:06:03 PM PDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   
-- --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enxc8d719c1088a  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  OASIS_5GHz  
e19433e4-ed9e-48bb-a374-b785593ae43e  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1587965] Re: [OTA11][m10] long swipe or home button doesn't "mazimize" dash

[Pat McGowan]

** Description changed:

  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)
  
  PS: All in all good work, OTA 11 feels really faster!
+ 
+ The key point is that the M10 works differently from the phones, so
+ something is different with the staged mode.

** Changed in: canonical-devices-system-image
   Status: Incomplete => 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/1587965

Title:
  [OTA11][m10] long swipe or home button doesn't "mazimize" dash

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

Bug description:
  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)

  PS: All in all good work, OTA 11 feels really faster!

  The key point is that the M10 works differently from the phones, so
  something is different with the staged mode.

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

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

[Touch-packages] [Bug 1589703] Re: Alarm clock icon doesn't disappear (appears randomly) when alarm inactive

[Michal Predotka]

bq e4.5 OTA-11
I disabled all alarms, manually changed time to 23:58 and looked at the screen 
until 00:02 but nothing happened. The icon didn't show up. Tested 2 times.

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

Title:
  Alarm clock icon doesn't disappear (appears randomly) when alarm
  inactive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  As in description. In my bq i see sometimes an alarm clock icon even
  if the alarm time passed and the alarm clock is no longer active.

  Set the alarm clock
  Let it ring and turn it off. The icon stays visible for some time which i can 
not exactly specify.

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

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

[Touch-packages] [Bug 1587965] Re: [OTA11][m10] long swipe or home button doesn't "mazimize" dash

[Joan CiberSheep]

*Home button also works differnet

in app spread view, pressing home button behaves as long swipe:
 - in tablet moves Today Scope to the left and keeps the spread view
 - in phone shows Today Scope in full view

in full view always shows Today Scope no matter if in a scope or app,
phone or tablet.

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

Title:
  [OTA11][m10] long swipe or home button doesn't "mazimize" dash

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

Bug description:
  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)

  PS: All in all good work, OTA 11 feels really faster!

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

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

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Andreas Hasenack]

** Changed in: landscape-client
   Status: New => In Progress

** Changed in: landscape-client
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Branch linked: lp:~ahasenack/landscape-client/libpam-systemd-depends-
xenial-onwards

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  In Progress
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default 

[Touch-packages] [Bug 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [SRU]Network Manager sets powersave off by default in xenial

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  NetworkManager consumes more power than previous releases because powersave 
support is not updated.

  [Test Case]
  With the patch applied, network device power management should be on when 
supported, for example:

  $ sudo iwconfig wlan0 | grep "Power Management"
Power Management:on

  [Regression Potential]
  Regression may happen when the power management feature of certain device 
isn't implemented properly in kernel, but since we are quite conservative on 
enabling power management in kernel development such case should be rare.

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

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

[Touch-packages] [Bug 1582803] Re: [SRU]bug report script uses invalid nm options

[Aron Xu]

** Changed in: network-manager (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

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

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

[Touch-packages] [Bug 1587965] Re: [OTA11][m10] long swipe or home button doesn't "mazimize" dash

[Joan CiberSheep]

Sorry for my confusing explanations ;)

I am not sure if that behavior is the intended as the phone works in a
different way (also tablet until OTA10).

If it is then I might have to merge this bug with:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598957.


In resume: the behavior on OTA11 is confusing for me because:
 long swipe from the left in App Spread
  -in tablet moves the app to the left (keeps app spread) and shows Today Scope.
  -in phone opens full size Today Scope

 long swipe from the left in full view
   -in tablet and phone does nothing if in any scope (except if in an Today 
Scope "section", ie: if tap on Weather from Today Scope or Scope has been 
opened from bottom swipe)
   -in tablet and phone shows full size Today Scope if in an app

I hope is a bit clear.

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

Title:
  [OTA11][m10] long swipe or home button doesn't "mazimize" dash

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

Bug description:
  1) swipe from outside of the screen from the right to get the apps that are 
opened
  2) outside long swipe from the left, moves the most left app to move to the 
right but it doesn't "maximize" main scope.
  3) outside short swipe from the left shows dash but tapping on home button 
has no effect (before it was "maximizing" main scope)

  PS: All in all good work, OTA 11 feels really faster!

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

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

[Touch-packages] [Bug 1594532] Re: Portrait mode is missing top

[Sander Smit]

Since the last reboot of my tablet this bug seems gone.
Strange because previous reboots did not help.

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

Title:
  Portrait mode is missing top

Status in unity-scope-click package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When I open the apps scope in portrait mode on my m10 tablet. The top of the 
scope is missing.
  Contacts, camera etc + top 2 or 3 lines with apps

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

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

[Touch-packages] [Bug 1597205] Re: Not sending relative mouse events to clients

[Daniel d'Andrada]

** Changed in: qtmir
   Status: Triaged => In Progress

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

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

Title:
  Not sending relative mouse events to clients

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

Bug description:
  QtMir is not sending relative mouse movements in mouse events.

  Relevant code from mirsurface.cpp:

  
  mir::EventUPtr makeMirEvent(QMouseEvent *qtEvent, MirPointerAction action)
  {
  auto timestamp = 
uncompressTimestamp(qtmir::Timestamp(qtEvent->timestamp()));
  auto modifiers = getMirModifiersFromQt(qtEvent->modifiers());
  auto buttons = getMirButtonsFromQt(qtEvent->buttons());

  return mir::events::make_event(0 /*DeviceID */, timestamp, 
std::vector{} /* cookie */, modifiers, action,
 buttons, qtEvent->x(), qtEvent->y(), 0, 0, 
0, 0);

  
  The last 2 parameters in the make_event call should be the relative x & y 
motion.

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

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

[Touch-packages] [Bug 1597615] Re: The cellular data option in network indicator is disabled after turning on and turning off the flight mode.

[Pat McGowan]

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

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

Title:
  The cellular data option in network indicator is disabled after
  turning on and turning off the flight mode.

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2

  Precondition:
  SIM card is inserted and Cellular data is open.

  Steps:
  1.Pull down the network indicator,and turn on flight mode toggle.
  2.After a few seconds turn  off the flight mode and check the cellular data 
option.

  Actual result:
  The state is on but option bar is disable and cannot be tapping. Go to 
cellular settings page, it works fine there.

  Expected result:
  The cellular data option should be still enabled after turn on and turning 
off the flight mode.

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

@Simon, couple of small things:
* you should use 8.0-0ubuntu3.1 as the version instead of 8.0-0ubuntu4
* the changelog has a date of 'Tue, 17 May 2016 17:59:58 +0200' which is quite 
old, yet the diff was only recently uploaded. You can use 'dch -r' to update 
the date

More importantly:
 * the patch introduces compiler warnings. These should be cleaned up:
+modules/module-snappy-policy.c: In function ‘connect_record_hook’:
+modules/module-snappy-policy.c:57:5: warning: ISO C90 forbids mixed 
declarations and code [-Wdeclaration-after-statement]
+ char *label = NULL;
+ ^
+modules/module-snappy-policy.c:65:5: warning: ISO C90 forbids mixed 
declarations and code [-Wdeclaration-after-statement]
+ pa_hook_result_t decision = PA_HOOK_OK;
+ ^


* configure shows:
+Enable Snappy support: no
+Enable Apparmor:   yes

Can you comment on why snappy support was added to configure in this
patch if you aren't going to use it? It seems that snappy support is
compiled though, cause I see '-DHAVE_SNAPPY=1' in the build logs and see
usr/lib/pulse-8.0/modules/module-snappy-policy.so is now shipped.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1589703] Re: Alarm clock icon doesn't disappear (appears randomly) when alarm inactive

[Anupam]

I observed the same behaviour (i.e. false alarm clock icon appearing at
midnight, as in #8) each and every day for last 7-8 days. So probably
it's not a random behaviour. Can anyone else confirm?

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

Title:
  Alarm clock icon doesn't disappear (appears randomly) when alarm
  inactive

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  As in description. In my bq i see sometimes an alarm clock icon even
  if the alarm time passed and the alarm clock is no longer active.

  Set the alarm clock
  Let it ring and turn it off. The icon stays visible for some time which i can 
not exactly specify.

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

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

[Touch-packages] [Bug 1549733] Re: SystemSettings Language view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

[Pat McGowan]

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

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

Title:
  SystemSettings Language view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373
  Ubuntu UI Toolkit version r1795

  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen
  This is confusing for the user as he can never be sure about which item will 
be actioned by the keyboard keys

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

  : “To avoid errors from unintended focus and
  distraction from irrelevant focus rings, there should be three classes
  of control: … • Non-pointer-focusable: Focusable with Tab … Yes …
  Focusable with pointing device … No”

  : “To avoid distraction from irrelevant
  selection, there should be three classes of list: … • Non-pointer-
  selectable: Selectable with arrow keys … Yes … Selectable with
  pointing device … No … Any list that is non-pointer-selectable should
  be non-pointer-focusable.”

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

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

[Touch-packages] [Bug 1589594] Re: incoming call box can be closed without hanging up

[Pat McGowan]

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

** This bug is no longer a duplicate of bug 1586955
   User can swipe the incoming call notification dialog
** This bug has been marked a duplicate of bug 1512430
   [phone] Shouldn't be able to swipe away incoming call notification

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

Title:
  incoming call box can be closed without hanging up

Status in ofono package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When I have an incoming call, a box saying who's calling and the buttons to 
hang up and to answer appears.
  You can swipe the whole box (not the little one to hang up and answer) to 
left or to right, like all notifications, and the big box disappear. The 
problem is: the phone continue ringing but you can't do nothing.
  this swipe can hang up the call or the box shouldn't swipe like all 
notifications

  Description: Ubuntu 15.04
  Release: 15.04

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

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

[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

Title:
  MainView intercepts MouseArea's cursorShape property

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The MouseArea CursorShape doesnt have any effect.

  Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html

  Expected Behavour:
  Mouse image shows selected Qt cursor

  Experienced Behavour:
  The regular arrow is displayed.

  Example Code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  objectName: "mainView"
  applicationName: "mouseTest"

  width: units.gu(100)
  height: units.gu(75)

  Rectangle{
  anchors.fill: parent
  color: UbuntuColors.coolGrey

  MouseArea{
  anchors.fill: parent
  cursorShape: Qt.CrossCursor
  hoverEnabled: true
  onClicked: console.log("In MouseArea")
  }
  }
  }

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

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

[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

[Einar Mostad]

Same her on a Norwegian layout with M10 on OTA 11.

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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

[Touch-packages] [Bug 1586955] Re: User can swipe the incoming call notification dialog

[Pat McGowan]

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

Yes its a dupe
@jibel I find I can swipe away the dialog at any time, without changing volume, 
just by grabbing above or below the slider. For me it results in the call going 
to voice mail, not continuing to ring.On another bug we theorized perhaps if 
voice mail isn't enabled the behavior is incorrect.

** This bug has been marked a duplicate of bug 1512430
   [phone] Shouldn't be able to swipe away incoming call notification

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

Title:
  User can swipe the incoming call notification dialog

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

Bug description:
  current build number: 338
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  
  Test Case:
  1. With DUT locked and display turned off, send a call to the DUT
  2. On DUT, when the incoming call notification is displayed, change the 
volume with the hardware buttons
  3. Wait until the answer dialog is displayed again and do a left edge swipe

  Aktual result
  User can swipe the incoming call notification dialog, leaving no way to take 
or reject the call.

  Expected result
  The dialog cannot be dismissed.

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

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

[Touch-packages] [Bug 1494889] Re: Play movies directly from Scope

[Krzysztof Tataradziński]

Does that fix mean that now we can watch YouTube videos directly from
YouTube Scope?

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

Title:
  Play movies directly from Scope

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Hello,
  I think that instead of launching web browser, scopes should have possibility 
to play movies (local and from web (like YouTube)) directly from them. Example 
- I want to see some trailer of new movie from Film scope. I click and it 
launch web browser - and that's the part that makes me sad. Better would be to 
see movie from scope; if I need more information - I will click to open web 
browser and  get info about it.

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

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

[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

[mash]

No, the problem is not resolved. It seems as if the lock-ups are
shorter, but it is still happening.

** Changed in: xorg (Ubuntu)
   Status: Invalid => New

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

[mash]

>From /var/log/Xorg.0.log

(EE) SynPS/2 Synaptics TouchPad: Read error 19
[ 12554.829] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
[ 12554.844] (II) UnloadModule: "synaptics"

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1595113] Re: Icons in scope filters look pixelated

[Andrea Cimitan]

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

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

Title:
  Icons in scope filters look pixelated

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  bq M10 FHD rc-proposed with Libertine/X-Apps scope installed.

  Steps to reproduce:
  1. Open XApps scope
  2. Click "search" icon
  3. Click "filters" icon
  4. Click "down" icon to expand the list
  5. Click any list item to see "tick" icon

  Expected result:
  All icons are nice and smooth 

  What happens instead:
  Icons: "down", "up" and "tick" look pixelated

  Screenshot attached.

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

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

[Touch-packages] [Bug 1586673] Re: Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

[Matthias Klose]

wcsaxes is now fixed, see LP: #1598152.

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

Title:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS

Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Committed
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  Fix Committed

Bug description:
  Backport GCC 5.4.0 and binutils 2.26.1 to 16.04 LTS.  16.04 LTS ships
  binutils and gcc-5 versions taken from the release branches, which saw
  more regression fixes and support for new hardware until the 5.4.0 and
  2.26.1 point releases. The idea is to include these final point
  releases into 16.04.1 LTS, with test rebuilds done for all packages,
  and regression checks for seeded packages.

  Acceptance criteria should be no regressions for the seeded packages,
  plus a best effort for unseeded packages.  During the analysis of the
  build failures, one gcc regression (libstdc++ header reorg) was found
  and reverted, and validated, that these build failures are fixed (plus
  affected seeded packages were uploaded to xenial-proposed anyway).

  reference test rebuild:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-baseline-xenial.html

  test rebuild (xenial-release):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-xenial.html

  test rebuild (xenial-updates):
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160614-updates-xenial.html

  The test rebuild was done using packages from the ubuntu-
  toolchain-r/ppa.

  Attached is an analysis of the build failures, and whether they are
  regressions, or already are present in the xenial release.

  main component
  ==

  bzr
LP: #1592731, fixed in -proposed
  ecj
LP: #1592801, fixed in -updates
  freerdp
not a regression
  gcc-5-cross
needs update after gcc-5 acceptance
  gnutls28
LP: #1592693, fixed in -updates
  kmod
unrelated, tracked in LP: #1592722
  libnih
not a regression
  llvm-toolchain-3.6
not a regression
  migrate
unrelated (mysql-5.7), tracked in LP: #1592663
  neon27 (s390x)
unrelated, traked in LP: #1592698
  openvswitch
not a regression, tracked in LP: #1592793
  python-pymysql
unrelated (mysql-5.7), tracked in LP: #1592664
  python-tooz
unrelated, tracked in LP: #1592660
  sbsigntool
not a regression
  shim
not a regression
  strongswan
racy test, unrelated, tracked in LP: #1592706
  ubuntu-defaults-builder
unrelated, LP: #1597370, waiting for approval
  upstart
not a regression
  whoopsie
LP: #1592649, fixed in -updates
  yaboot
not a regression

  bzr package set
  ===

  bzr-builder
  bzr-upload
no regressions

  cli-mono package set
  

  gbrainy
  ikvm
  monodevelop
  tangerine
no regressions

  desktop-extra package set
  =

  java-gnome
not a regressions

  edubuntu package set
  

  atomix
  gbrainy
no regressions

  input-methods package set
  =

  fcitx-table-other
  libkkc
no regressions

  kubuntu package set (minus packages from main)
  ==

  avogadro
not a regression
  eigen2
not a regression
  fam
not a regression
  farstream-0.2
not a regression
  gst-plugins-base0.10
not a regression
  gst-plugins-good0.10
not a regression
  gstreamer0.10
not a regression
  kqoauth
not a regression
  kubuntu-web-shortcuts
not a regression
  libmpc
not a regression
  libmygpo-qt
not a regression
  libspe2
not a regression
  networkmanager-qt
obsoleted by version in -updates
  plotutils
not a regression
  qtcurve
not a regression
  tbb
not a regression
  telepathy-haze
not a regression
  telepathy-qt
not a regression

  
  lubuntu package set
  

  hardinfo
not a regression
  libguess
not a regression

  mozilla package set
  

  eclipse
  xiphos
no regressions

  mythbuntu package set
  =

  piston-mini-client
not a regression

  schooltool package set
  ==

  schooltool-book
not a regression

  ubuntu-cloud package set
  

  virtualbox
needs fix for bad GCC version check, in progress (LocutusOfBorg)

  ubuntu-qt-packages package set
  ==

  ciborium
not a regression

  ubuntukylin package set
  ===

  libguess
  piston-mini-client
  

[Touch-packages] [Bug 1494889] Re: Play movies directly from Scope

[Pat McGowan]

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

** Changed in: canonical-devices-system-image
Milestone: backlog => 12

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

Title:
  Play movies directly from Scope

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Hello,
  I think that instead of launching web browser, scopes should have possibility 
to play movies (local and from web (like YouTube)) directly from them. Example 
- I want to see some trailer of new movie from Film scope. I click and it 
launch web browser - and that's the part that makes me sad. Better would be to 
see movie from scope; if I need more information - I will click to open web 
browser and  get info about it.

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

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

[Touch-packages] [Bug 1598680] Re: Share icon isn't discoverable by first glance since bottom bar is hidden

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Also affects: unity-scope-mediascanner (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Share icon isn't discoverable by first glance since bottom bar is
  hidden

Status in Canonical System Image:
  Confirmed
Status in unity-scope-mediascanner package in Ubuntu:
  New

Bug description:
  current build number: 375
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-07-04 10:27:43
  version version: 375
  version ubuntu: 20160702
  version device: 20160606-ab415b2
  version custom: 20160701-981-38-14

  steps:
  1.Go to Video scope
  2.Select a local video and open to preview page
  3.Check the thumbnal of the video

  actual:
  Bottom bar only appears until user tapping on thumbnail, that user cannot 
find the share icon by first glance.

  expected:
  Display the bottom bar by default, like my photo scope did

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

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

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

@Simon, thanks, I'll work on sponsoring this.

@Zygmunt, I'm not sure this is the patch to upstream-- it is the phase 1
approach and the phase 2 approach is pulseaudion/trust-store/snappy
interfaces which we will be discussing this week.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Andreas Hasenack]

** Also affects: landscape-client
   Importance: Undecided
   Status: New

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  New
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default 20160609_11:40
  oracle6   i386default 20160609_11:40
  oracle7   amd64   default 20160609_11:40
  plamo 5.x amd64   default 20160608_21:36
  plamo 5.x 

[Touch-packages] [Bug 1599251] [NEW] Sites with many off site scripts tend to crash the Ubuntu browser

[uaneme]

Public bug reported:

Sites that use a large amount of offsite loaded scripts have a tendency
to crash the Ubuntu browswer (on a BQ M10 tablet)

I cannot pinpoint what scripts actually cause the issue. 
But if i load a site on another PC with firefox, then i always see heaps of 
off-site loaded scripts (no-script then gives a big list of url's)  This is 
what stood out when loading a few sites that crashed the Ubuntu browser in 
Firefox on another PC.

Mainly news-sites / magazine style sites.

optimizily, sharetrough, demdex, clicktale, 6cs, rubicon, adobe,
scorecard, jldbt, amazon, typekit, chartbeat, indexww, disqus,
mediavoice, etc. The craplist goes on and on and on.

In a way i'm hoping for no-script as an option in Ubuntu browser as a
way to block sites that waste ever more time, energy and mobile
bandwidth. And now also waste time due to crashing ubuntu browser.

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


** Tags: browser chrash ubuntu

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

Title:
  Sites with many off site scripts tend to crash the Ubuntu browser

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Sites that use a large amount of offsite loaded scripts have a
  tendency to crash the Ubuntu browswer (on a BQ M10 tablet)

  I cannot pinpoint what scripts actually cause the issue. 
  But if i load a site on another PC with firefox, then i always see heaps of 
off-site loaded scripts (no-script then gives a big list of url's)  This is 
what stood out when loading a few sites that crashed the Ubuntu browser in 
Firefox on another PC.

  Mainly news-sites / magazine style sites.

  optimizily, sharetrough, demdex, clicktale, 6cs, rubicon, adobe,
  scorecard, jldbt, amazon, typekit, chartbeat, indexww, disqus,
  mediavoice, etc. The craplist goes on and on and on.

  In a way i'm hoping for no-script as an option in Ubuntu browser as a
  way to block sites that waste ever more time, energy and mobile
  bandwidth. And now also waste time due to crashing ubuntu browser.

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

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

[Touch-packages] [Bug 1598726] Re: Unity crash when minimising Scopes App.

[kevin gunn]

curious, when you say crash...what symptom are you trying to describe?
reboot? restart of shell? freeze of shell/no input response?

also, what device did you experience this on? m10? laptop? something
else?

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

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

Title:
  Unity crash when minimising Scopes App.

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  
  On a few occasions unity has crashed when minimising the Apps Scope. 

  Logs will be provided at a later date if possible.

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

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

[Touch-packages] [Bug 1598805] Re: implement zoom in/zoom out [desktop]

[kevin gunn]

** Tags added: unity8-desktop

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

** Also affects: mir (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/1598805

Title:
  implement zoom in/zoom out [desktop]

Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  implement zoom in/zoom out [desktop]

  i need to zoom in/out when recording videos and since compiz is gone i
  can't do that anymore in unity8.

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

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

[Touch-packages] [Bug 1599229] Re: desktop mode tag not persitent if user set

[kevin gunn]

it would seem that a bt mouse pairing going missing/sleeping is a fairly common 
occurrence.
barring a formal design team answer, can we not do something "better" for this 
in the interim like you hint at? e.g. keyboard presence retaining the mode?

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

Title:
  desktop mode tag not persitent if user set

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  In an M10. If I set desktop mode on manually and then pair a bt mouse,
  when the bt mouse is switch off desktop mode resets to tablet mode.
  The problem is that if the mouse goes to sleep or loses the
  connection, tablet mode kicks in and I am told to switch off my xapps.
  This seems to happen very often.

  How to reproduce with M10:
  * pair a keyboard to the m10 and turn manually desktop mode from the indicator
  * pair a mouse to the m10
  * turn off the mouse after pairing

  expected result:device stays in desktop mode
  actual result: device resets to tablet mode

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

-- 
Mailing list: https://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 1599190] Re: Data switch disabled until System Settings is opened

[Víctor R . Ruiz]

That's *very* confusing.

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

Title:
  Data switch disabled until System Settings is opened

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

Bug description:
  Test case.
  - Flash rc image.
  - Insert a SIM card.
  - Complete the wizard.
  - Dismiss the welcome screen.
  - Introduce the SIM pin.
  - Open network indicator.

  Expected result.
  - Mobile data switch is enabled.

  Actual result.
  - No data connection active by default and mobile data switch disabled in the 
indicator.
  - Rebooting doesn't activate it.
  - Opening System Settings > Mobile data activates the switch in the indicator.

  current build number: 59
  device name: krillin
  channel: ubuntu-touch/rc/bq-aquaris.en

  Also checked with silo 25.

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

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

[Touch-packages] [Bug 1599242] [NEW] Going from portrait to landscape while in crop mode doesn't center the photo

[Pat McGowan]

Public bug reported:

The behavior is different that when first going to landscape then edit >
crop.

[Procedures]
1.open gallery-open one picture
2.click the edit
3.choose the Crop
4.landscape screen

[Expect result]
the picture display usual
[Actual results]
the picture not centered

[Reproduce]
Always

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

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

Title:
  Going from portrait to landscape while in crop mode doesn't center the
  photo

Status in gallery-app package in Ubuntu:
  New

Bug description:
  The behavior is different that when first going to landscape then edit
  > crop.

  [Procedures]
  1.open gallery-open one picture
  2.click the edit
  3.choose the Crop
  4.landscape screen

  [Expect result]
  the picture display usual
  [Actual results]
  the picture not centered

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1599243] [NEW] Left mouse click does not work

[furiousstyles74]

Public bug reported:

Unable to use mouse to open applications. Keyboard works.

$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 PST 
2015
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Jul  5 13:04:29 2016
DistUpgraded: 2016-06-23 14:32:51,855 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.2.0-38-generic, i686: installed
 bbswitch, 0.8, 4.4.0-24-generic, i686: installed
 nvidia-304, 304.131, 4.2.0-38-generic, i686: installed
 nvidia-304, 304.131, 4.4.0-24-generic, i686: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation GF100GL [Quadro 4000] [10de:06dd] (rev a3) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GF100GL [Quadro 4000] [10de:0780]
MachineType: Dell Inc. Precision WorkStation T7500
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=UUID=fe7866ba-f513-4068-8738-8ff7fdd3a1b1 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-06-23 (11 days ago)
Xrandr: Screen 0: minimum 0 x 0, current 3840 x 1200, maximum 4096 x 4096
dmi.bios.date: 10/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 06FW8P
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jul  5 11:36:57 2016
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: apport-bug i386 possible-manual-nvidia-install ubuntu xenial

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

Title:
  Left mouse click does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  Unable to use mouse to open applications. Keyboard works.

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul  5 13:04:29 2016
  DistUpgraded: 2016-06-23 14:32:51,855 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-38-generic, i686: installed
   bbswitch, 0.8, 4.4.0-24-generic, i686: installed
   nvidia-304, 304.131, 4.2.0-38-generic, i686: installed
   nvidia-304, 304.131, 4.4.0-24-generic, i686: installed
  

[Touch-packages] [Bug 1067386] Re: dm thin facility incomplete - thin-provisioning-tools not packaged

[elatllat]

On CentOS 7.2/Linux 3.10 lmv2 depends on device-mapper-persistent-data
which is what they call thin-provisioning-tools

repoquery --requires lvm2
yum info device-mapper-persistent-data.x86_64

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

Title:
  dm thin facility incomplete - thin-provisioning-tools not packaged

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  The lvm2 package is built with --with-thin=internal option activated,
  but the supporting userspace activation tools are neither packaged nor
  depended upon correctly.

  The errors reported in Debian at http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=673000#17 also occur on Ubuntu Quantal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lvm2 2.02.95-4ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 16 14:57:35 2012
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1598850] Re: [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian unstable (main)

[Mathew Hodson]

** Changed in: ncurses (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [merge request] Please merge ncurses 6.0+20160319-2 (main) from Debian
  unstable (main)

Status in ncurses package in Ubuntu:
  New

Bug description:
  Old Ubuntu version: 6.0+20160319-1ubuntu1

  Details: https://merges.ubuntu.com/n/ncurses/REPORT (from
  https://merges.ubuntu.com/main.html)

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

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