date:20160518

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

** Changed in: gconf (Ubuntu)
   Importance: High => Critical

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error occured during regular "do-release-upgrade". System remains in
  unstable condition. dpkg --configure -a / apt-get -f install continues
  the process (still running).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 22 17:05:44 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - 
Trigger bleiben unverarbeitet
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-03-17 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1574251] Re: Resuming from screen lock with a multimonitor setup causes all windows to migrate to the "primary screen"

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

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

Title:
  Resuming from screen lock with a multimonitor setup causes all windows
  to migrate to the "primary screen"

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hardware:

  * Dell M3800; builtin screen is a 15", 1920x1080 screen;
  * an external display connected via HDMI, brand ASUS, same resolution;
  * the configuration via settings is that the screen on the laptop is on the 
left and the ASUS screen on the right.

  The bug did not appear with 15.10; only starting with 16.04 did this
  start to happen. This is a laptop with a nVidia chipset, and it
  doesn't matter whether I use nouveau or the proprietary nVidia driver.

  When the screen locks after inactivity, or I lock it explicitly, and
  then some time later (for some definition of "later") log back in, all
  windows have migrated to the laptop screen. This is annoying since it
  means I have to move all the windows over again.

  I am not sure what details I should give. I only noticed that compared
  to 15.10 which did not exhibit the bug, the ASUS screen takes longer
  to "wake up" again... My hunch here is that the HDMI port was
  deactivated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 24 14:43:24 2016
  DistUpgraded: 2016-04-23 03:26:23,168 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
  InstallationDate: Installed on 2015-07-16 (282 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b8f6e64b-30d4-4621-8885-8079631fbd0e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: unable to create the OpenGL context
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/08/2015:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A09
  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: Sat Apr 23 19:16:20 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4589 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1572244] Re: Kubuntu 16.04 requires that the wifi password be entered twice before wifi can be used

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

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

Title:
  Kubuntu 16.04 requires that the wifi password be entered twice before
  wifi can be used

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  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
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  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/+bug/1572244/+subscriptions

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

[Touch-packages] [Bug 1570359] Re: pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()

** Changed in: pcsc-lite (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  pcscd crashed with SIGSEGV in
  __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  crashed when login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pcscd 1.8.14-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr  4 17:29:56 2016
  Disassembly: => 0x7f7da881b64c:   Cannot access memory at address 
0x7f7da881b64c
  ExecutablePath: /usr/sbin/pcscd
  InstallationDate: Installed on 2016-03-06 (39 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit
  SegvAnalysis:
   Segfault happened at: 0x7f7da881b64c:Cannot access memory at address 
0x7f7da881b64c
   PC (0x7f7da881b64c) not located in a known VMA region (needed executable 
region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: pcsc-lite
  StacktraceTop:
   ?? ()
   __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__ () from 
/lib/x86_64-linux-gnu/libc.so.6
   ?? ()
  Title: pcscd crashed with SIGSEGV in 
__elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1571158] Re: Crash in QXcbWindow::setParent() due to NULL xcbScreen()

2016-05-18 Thread Mahnu

Dear Martin,

I purged landing-016 ppa, re-compile my application, and it crashes as expected.
Then I enabled pre-released updates, updated the Qt packages to version 
5.5.1+dfsg-16ubuntu7.1 from proposed, re-compile again, and the crash 
disappeared.

So, yes, thank you: this package fixes the crash for me!

For the details, the application is camitk-imp (available in the package
"camitk" version 4.0.0, which did not make it to Ubuntu 16.04), a
medical image analysis and modeling software based on Qt and VTK. My
machine is a (rather old) Dell M6400 laptop.

Let me know if you want me to use the test case provided by Mitsuya as
welle or need more information about my testing or if you need me to do
further testing.

Thanks to everyone for this fix and to Martin for the detailed
instruction on how to test and report this package!

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

Title:
  Crash in QXcbWindow::setParent() due to NULL xcbScreen()

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Application crash in certain situation.

  [Test Case]

  See bug comments for test app.

  [Regression Potential]]

  The fixes are in the currently release upstream LTS release (Qt 5.6),
  but they do touch a core component of (X11) Qt so eg multi-monitor
  setups should be tested for no regressions.

  --

  Qt 5.5.1 has problem to "[QTBUG-50081] Crash in
  QXcbWindow::setParent() due to NULL xcbScreen()".

  This is already fixed in upstream.
  https://bugreports.qt.io/browse/QTBUG-50081

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1571158/+subscriptions

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

[Touch-packages] [Bug 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04

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

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

Title:
  MatchIsTouchscreen also matches touchpads in 16.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Previously in 15.10 I had the following rule in 
/usr/share/X11/xorg.conf.d/99-no-touchscreen.conf:
  Section "InputClass"
  Identifier "Touchscreen disable"
  MatchIsTouchscreen "on"

  Option "Ignore" "on"
  EndSection

  This worked in disabling the touchpad on my lenovo T440s

  After the upgrade to 16.04 I noticed that my touchpad would not work. And I 
found the following lines in the log:
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/event6)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"
  [  3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/mouse0)
  [  3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"Touchscreen disable"

  So I had to disable the rule in order to be able to use the touchpad,
  and now  I can't disable the touchscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-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
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Apr 29 09:39:23 2016
  InstallationDate: Installed on 2015-03-18 (407 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago)

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

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

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

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

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1579584] Re: package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

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

Title:
  package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  root@music:~/media/midi-files# sudo apt-get install ia32-libs
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package ia32-libs is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
lib32ncurses5 lib32z1

  E: Package 'ia32-libs' has no installation candidate
  root@music:~/media/midi-files# sudo apt-get install   lib32ncurses5 lib32z1
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  lib32ncurses5 is already the newest version (6.0+20160213-1ubuntu1).
  lib32z1 is already the newest version (1:1.2.8.dfsg-2ubuntu4).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   guitarpro6:i386 : Depends: gksu:i386 but it is not going to be installed
 Depends: libportaudio0:i386 but it is not installable
 Depends: libportaudio2:i386 but it is not going to be 
installed
 Depends: libssl0.9.8:i386 but it is not installable
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).
  root@music:~/media/midi-files# apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
extlinux gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 
libdatrie1:i386 libdbus-glib-1-2:i386
libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 
libgnome-keyring0:i386 libgraphite2-3:i386 libgtk2.0-0:i386
libgtop-2.0-10:i386 libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 
libpango-1.0-0:i386 libpangocairo-1.0-0:i386
libpangoft2-1.0-0:i386 libpixman-1-0:i386 libstartup-notification0:i386 
libthai0:i386 libxcb-render0:i386
libxcb-shm0:i386 libxcb-util1:i386 sudo:i386 syslinux syslinux-common 
unetbootin-translations
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 
libdbus-glib-1-2:i386 libgconf-2-4:i386
libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 libgnome-keyring0:i386 
libgraphite2-3:i386 libgtk2.0-0:i386 libgtop-2.0-10:i386
libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 libpango-1.0-0:i386 
libpangocairo-1.0-0:i386
libpangoft2-1.0-0:i386 libpixman-1-0:i386 libportaudio2:i386 
libstartup-notification0:i386 libthai0:i386
libxcb-render0:i386 libxcb-shm0:i386 libxcb-util1:i386 sudo:i386
  Suggested packages:
librsvg2-common:i386 gvfs:i386 libpam-doc:i386
  Recommended packages:
update-motd:i386
  The following packages will be REMOVED:
gksu guitarpro6:i386 libgksu2-0 pd-deken sudo ubuntu-minimal unetbootin
  The following NEW packages will be installed:
gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 
libdbus-glib-1-2:i386 libgconf-2-4:i386
libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 libgnome-keyring0:i386 
libgraphite2-3:i386 libgtk2.0-0:i386 libgtop-2.0-10:i386
libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 libpango-1.0-0:i386 
libpangocairo-1.0-0:i386
libpangoft2-1.0-0:i386 libpixman-1-0:i386 libportaudio2:i386 
libstartup-notification0:i386 libthai0:i386
libxcb-render0:i386 libxcb-shm0:i386 libxcb-util1:i386 sudo:i386
  0 upgraded, 27 newly installed, 7 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 4,702 kB of archives.
  After this operation, 215 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libaudit1 i386 
1:2.4.5-1ubuntu2 [37.6 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libpam0g i386 
1.1.8-3.2ubuntu2 [57.8 kB]
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libpam-modules 
i386 1.1.8-3.2ubuntu2 [256 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libgnome-keyring0 
i386 3.12.0-1build1 [59.5 kB]
  Get:5 http://us.archive.ubuntu.com/ubuntu xenial/main i386 sudo i386 
1.8.16-0ubuntu1 [395 kB]
  Get:6 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libdbus-glib-1-2 
i386 0.106-1 [73.6 kB]
  Get:7 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libpixman-1-0 i386 
0.33.6-1 [237 kB]
  Get:8

[Touch-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted

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

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   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/1573720/+subscriptions

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

[Touch-packages] [Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container

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

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

Title:
  Can't install kernel-nfs-server inside lxc container

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to virtualize a package that depends on NFS by installing
  it in an LXC container.

  The commands

  sudo apt-get install nfs-kernel-server
  sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64
  sudo lxc-start -n nfstest
  sudo lxc-attach -n nfstest apt-get update
  sudo lxc-attach -n nfstest apt-get install nfs-kernel-server

  should install NFS server software inside the container, but instead
  fail with

  ...
  Not creating home directory `/var/lib/nfs'.
  nfs-utils.service is a disabled or a static unit, not starting it.
  Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ...
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  nfs-server.service couldn't start.
  Creating config file /etc/exports with new version
  Creating config file /etc/default/nfs-kernel-server with new version
  A dependency job for nfs-server.service failed. See 'journalctl -xe' for 
details.
  invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
  dpkg: error processing package nfs-kernel-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu4) ...
  Errors were encountered while processing:
   nfs-kernel-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  sudo lxc-attach -n nfstest journalctl -xe reports:

  Apr 27 15:42:59 nfstest systemd[1]: Failed to mount NFSD configuration 
filesystem
  -- Subject: Unit proc-fs-nfsd.mount has failed
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- Unit proc-fs-nfsd.mount has failed.
  -- The result is failed.

  Presumably this is intended, and there is a way to configure lxc to allow
  running nfs servers inside it (there are rumors of success on the web), but 
  https://help.ubuntu.com/lts/serverguide/lxc.html  is silent on the issue,
  and doesn't even mention the word nfs.
  Likewise, https://help.ubuntu.com/lts/serverguide/network-file-system.html
  doesn't even mention lxc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 27 08:19:41 2016
  InstallationDate: Installed on 2016-03-26 (32 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1307883] Re: ca-certificates-java misses runtime dependency on initscripts

2016-05-18 Thread David Daynard

** Also affects: openjdk
   Importance: Undecided
   Status: New

** No longer affects: openjdk

** Also affects: openjdk-8 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ca-certificates-java misses runtime dependency on initscripts

Status in ca-certificates-java package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  Jitsi build-depends on openjdk-7-jre but the package fails to install
  in pbuilder and thus I currently cannot build the package.  Here is
  the output I get while I am logged in to the trusty chroot.

  # aptitude install default-jdk
  [...]
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up ca-certificates-java (20130815ubuntu1) ...
  /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: 
command not found
  the keytool command requires a mounted proc fs (/proc).
  dpkg: error processing package ca-certificates-java (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ...
  /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: 
/var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found
  the java command requires a mounted proc fs (/proc).
  dpkg: error processing package openjdk-7-jre-headless:i386 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up default-jre-headless (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jre:i386:
   openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 
7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre-headless:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jre:i386 (--configure):
   dependency problems - leaving unconfigured
  Setting up default-jre (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386:
   openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jdk:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of default-jdk:
   default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however:
    Package openjdk-7-jdk:i386 is not configured yet.

  dpkg: error processing package default-jdk (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for ca-certificates (20130906ubuntu2) ...
  Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d
  /etc/ca-certificates/update.d/jks-keystore: 33: 
/etc/ca-certificates/update.d/jks-keystore: mountpoint: not found
  the keytool command requires a mounted proc fs (/proc).
  E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
  done.
  Errors were encountered while processing:
   ca-certificates-java
   openjdk-7-jre-headless:i386
   openjdk-7-jre:i386
   openjdk-7-jdk:i386
   default-jdk

  # mount
  /proc on /proc type proc (rw,relatime)
  tmpfs on /run/shm type tmpfs (rw,relatime)
  /dev/pts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

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

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

[Touch-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2016-05-18 Thread Treviño

Updated the upower patch, as requested on upstream bug.
Attaching new debdiff here.

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in upower source package in Xenial:
  New

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Touch-packages] [Bug 1583399] Re: Unity8 screenshots don't capture Xmir/RGBX window contents correctly

Also visible in the above screenshot is:
  Corrupt titlebar text -> bug 1583088
  Blurry window contents of Web Browser -> bug 1510382

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

** Changed in: qtmir (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/1583399

Title:
  Unity8 screenshots don't capture Xmir/RGBX window contents correctly

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 screenshots don't capture Xmir/RGBX window contents correctly.

  Just press PrtScn... On my screen I can see the gedit app rendered
  correctly, but the Unity8 screenshotting feature saves a faulty image.

  It's probably the same issue as bug 1510386.

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

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

[Touch-packages] [Bug 1583399] [NEW] Unity8 screenshots don't capture Xmir/RGBX window contents correctly

Public bug reported:

Unity8 screenshots don't capture Xmir/RGBX window contents correctly.

Just press PrtScn... On my screen I can see the gedit app rendered
correctly, but the Unity8 screenshotting feature saves a faulty image.

It's probably the same issue as bug 1510386.

** Affects: qtmir (Ubuntu)
 Importance: Medium
 Status: New

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

** Attachment added: "screenshot20160519_095933390.png"
   
https://bugs.launchpad.net/bugs/1583399/+attachment/4665921/+files/screenshot20160519_095933390.png

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

Title:
  Unity8 screenshots don't capture Xmir/RGBX window contents correctly

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 screenshots don't capture Xmir/RGBX window contents correctly.

  Just press PrtScn... On my screen I can see the gedit app rendered
  correctly, but the Unity8 screenshotting feature saves a faulty image.

  It's probably the same issue as bug 1510386.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in text rendering, mainly in Unity8 window titlebars

Other bugs are visible in that screenshot:
  Blurry window contents after moving (Web Browser) -> bug 1510382
  White/translucent window contents for screenshots of Xmir -> bug 1583399
  All white QML window contents for Scopes -> bug 1577639
  Thin titlebar font -> bug 1583092

Sorry for the confusion. I didn't intend to capture so may bugs in one
picture.

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

Title:
  Randomly corrupt characters in text rendering, mainly in Unity8 window
  titlebars

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in text rendering, mainly in Unity8 window titlebars

Oh bug 1543467 is visible too.

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

Title:
  Randomly corrupt characters in text rendering, mainly in Unity8 window
  titlebars

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in text rendering, mainly in Unity8 window titlebars

Here's a screenshot of a couple of slightly corrupt titlebars.

Ignore the messed up window contents. That's just a screenshot bug I'll
log separately. The window contents look right on the real screen. But
the corrupt titlebar text is visible.

** Attachment added: "screenshot20160519_095933390.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1583088/+attachment/4665919/+files/screenshot20160519_095933390.png

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

Title:
  Randomly corrupt characters in text rendering, mainly in Unity8 window
  titlebars

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files

2016-05-18 Thread Tiago Stürmer Daitx

I was unable to reproduce it yesterday, but it was due to the jpeg files
I was using. I repeated it today with different jpeg files and
reproduced it.

Got a crash on OpenJDK 7u101 with both LCMS 2.5 (Trusty) and 2.6 (Wily),
also reproduced when using the LCMS lib that comes with OpenJDK (by
default Ubuntu uses the lib from lcms2-2 package). OpenJDK 8 on Wily
uses the same LCMS and does not crash.

I will report this upstream.

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

Title:
  ImageIO crashes (core dumped) while reading many image files

Status in OpenJDK:
  Fix Released
Status in lcms2 package in Ubuntu:
  Incomplete
Status in openjdk-7 package in Ubuntu:
  Incomplete

Bug description:
  Code that uses ImageIO.read() to read many image files (on my system:
  270 files, totalling 522.9 MiB) crashes the JVM.

  ~~~ My system information:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 11.10
  Release:  11.10
  Codename: oneiric

  $ uname -a
  Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  $ javac -version
  javac 1.7.0_147

  $ java -version
  java version "1.7.0_147-icedtea"

  ~~~ To reproduce the error:

  $ javac BugIIO.java

  $ ulimit -c unlimited # to enable core dump

  $ java BugIIO

  ~~~ Terminal output that signifies the error:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752
  #
  # JRE version: 7.0_147-b147
  # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea7 2.0
  # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1
  # Problematic frame:
  # C  [liblcms2.so.2+0x121f8]  cmsSaveProfileToIOhandler+0x38
  #
  # Core dump written. Default location: /home/joshua/core or core.4978
  #
  # An error report file with more information is saved as:
  # /home/joshua/hs_err_pid4978.log
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  #
  Dibatalkan (core didump)

  ~~~ PS
  When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the 
program finishes normally (no crash).

  To clarify:
  1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on 
oneiric).
  2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested 
on oneiric).

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

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

[Touch-packages] [Bug 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

It's probably Unity8 if not QtMir.

Mir (demo shells) don't have this bug. Unity8 just needs fixing to
ensure the vertices it emits are on integer pixel boundaries, so the
textures line up with the pixels of the display without blurring into
their neighbours.

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

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

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1547826] Re: Enable libappindicator support

** Changed in: ibus (Ubuntu Xenial)
   Importance: Undecided => Wishlist

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

Title:
  Enable libappindicator support

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Xenial:
  New
Status in ibus source package in Yakkety:
  Fix Released

Bug description:
  It appears an FFe is needed at this stage in Xenial cycle, thus
  changing the bug status.

  
  ---Original Report
  Please enable libappindicator support.
  This feature is good at KDE 5.
  https://desktopi18n.wordpress.com/2015/07/21/ibus-1-5-11-is-released/

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

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

[Touch-packages] [Bug 1543467] Re: Unity8 can't correctly display multi-surface apps (including menus and tooltips)

That's a reasonable argument, however this bug was also about menus and
tooltips right from the beginning on 9 February.

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

Title:
  Unity8 can't correctly display multi-surface apps (including menus and
  tooltips)

Status in QtMir:
  Triaged
Status in qtmir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Unity8 can't display multi-surface apps (including menus and
  tooltips).

  Fixing bug 1497085 was a great start. However instead of crashing
  Unity8 now just shows the most recently created window by the app in
  the apps /single window/, and stretches it too. When such a secondary
  window like a menu or tooltip closes, you never get back to the
  original app window. So existing apps still aren't quite usable yet.

  Test case:
  sudo apt-get install mir-demos
  mir_demo_client_multiwin -- --desktop_file_hint=unity8

  Expected: Three windows (red, green, blue)
  Observed: Only the blue window

  You can also experience the same bug with lots of apps via:  Xmir
  -rootless under Unity8.

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

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

[Touch-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

** Changed in: unity-settings-daemon (Ubuntu Xenial)
   Importance: Undecided => High

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

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

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in Upower:
  Unknown
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in upower source package in Xenial:
  New

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Touch-packages] [Bug 1575109] Re: Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init'

2016-05-18 Thread Bug Watch Updater

** Changed in: binutils (Debian)
   Status: Unknown => Fix Released

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

Title:
  Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation
  (0x2a) in section `.init'

Status in binutils:
  New
Status in binutils package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in binutils package in Debian:
  Fix Released

Bug description:
  Running sa-compile (may take a long time)
  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized 
relocation (0x2a) in section `.init'
  /usr/bin/ld: final link failed: Bad value
  collect2: error: ld returned 1 exit status
  make: *** [blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so] 
Error 1
  command 'make >>/tmp/.spamassassin6654c6JaRRtmp/log' failed: exit 2
  dpkg: error processing package sa-compile (--configure):
   subprocess installed post-installation script returned error exit status 25
  Errors were encountered while processing:
   libgmp-dev:amd64
   systemd
   sa-compile

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:15.10.14.4
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Apr 26 11:38:01 2016
  InstallationDate: Installed on 2012-02-04 (1542 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root

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

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

Upstream release of Mir 0.22.1 with this fix completed. The fix is also
in some PPAs but not yet Ubuntu distro.

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

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

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

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.22 series:
  Fix Released
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Committed
Status in qtmir package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

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

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

[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200 3.2.21-1ubuntu1

** Summary changed:

- network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
+ network-manager crashes when using libnl-3-200 3.2.21-1ubuntu1

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

Title:
network-manager crashes when using libnl-3-200 3.2.21-1ubuntu1

Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Trusty:
Fix Released

Bug description:
[Triage Notes]

This regression is caused by a libnl proposed update tracked in bug
1511735. It has not been released as an update, only proposed as an
update for early testing. If you volunteered to test proposed updates,
then thank you. Your care and attention will stop this regression from
hitting ordinary users, and we appreciate your contribution to Ubuntu.

If you are not aware that you volunteered to test proposed updates,
then please be aware that your system is configured to do so. In this
case, you probably should turn this off. I'd appreciate if someone
could explain how to do this in the comments.

[Impact]

* NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
libnl-route-3-200) and when libnl is updated to proposed
3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
validation packets.

This affects the 0.98 release of NetworkManager and has already
been fixed in newer releases.

* Backporting fixes from upstream release is required to prevent
NetworkManager from faulting which breaks networking on most
Desktop releases.

* All patches applied are already accepted upstream and newer Ubuntu
releases are not affected.

* Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

[Test Case]

* Reproduce crash test:
1. Download 14.04.03 Desktop iso, amd64
2. Launched in a VM, run from iso
3. In terminal, enable proposed
4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
5. sudo restart network-manager
# note the nm-applet disappears as NM has now crashed, no network
conn.
6. dmesg to confirm network-manager crash
7. sudo dpkg --install
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
8. sudo start network-manager
# nm-applet reappears, network connectivity restored

* Successful upgrade test:
1. Download 14.04.03 Desktop iso, amd64
2. Launched in a VM, run from iso
3. In a terminal, sudo dpkg --install
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
4. sudo restart network-manager # NM still runs, no crash, net up
5. enable trusty-proposed in /etc/apt/sources.list
6. sudo apt-get update
7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
8. sudo restart network-manager # NM still runs, no crash, net up.

[Regression Potential]

* NetworkManager is a highly visible package, so testing NetworkManager
functionality is critical. The patch does address the crash specificly
introduced by the updated libnl SRU.

* We need to ensure that users have installed this NetworkManager
update before installing libnl3 update (special phasing needed).

[Original Description]
Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

After installing updated libnl3 and restarting networkmanager, NM
crashes with:

/var/log/syslog shows:
init: network-manager main process (1057) killed by SEGV signal
init: network-manager main process ended, respawning
init: network-manager main process (1065) killed by SEGV signal
init: network-manager respawning too fast, stopped

The bug has been fixed in upstream 0.98 with these patches:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

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

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

[Touch-packages] [Bug 989819] Re: Make duplicate signature more specific for DBusException and OSError

** Changed in: apport (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
  Make duplicate signature more specific for DBusException and OSError

Status in Daisy:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released

Bug description:
  Looking through some db bug examples and saw some incorrect bug
  associations, one example

  "Traceback (most recent call last):
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1090, in on_combobox_locale_chooser_changed
  self.writeUserFormats()
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
  self.writeUserFormatsSetting(userFormats=code)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
  iface.SetFormatsLocale(macr['SYSLOCALE'])
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  DBusException: org.freedesktop.Accounts.Error.PermissionDenied: Not 
authorized"

  has been associated to
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/930785

  "Traceback (most recent call last):
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1081, in on_combobox_locale_chooser_changed
  self.writeUserFormats()
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
  self.writeUserFormatsSetting(userFormats=code)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
  iface.SetFormatsLocale(macr['SYSLOCALE'])
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  DBusException: org.freedesktop.Accounts.Error.Failed: 'bg_BG.UTF-8' is not a 
valid locale name"

  The "functions signature" is the same, the exceptions are different
  though, it should probably consider that as part of the signature

  SRU TEST CASE:
  --
   * Modify /usr/bin/pybuild to append these two lines right after "def 
main(cfg):"

  raise OSError(99, 'some OS error')

   * Now running "pybuild" will provoke an OSError, and you should get a
  /var/crash/_usr_share_dh-python_pybuild.1000.crash

   * With current apport, the crash signature looks like this, i. e. it
  does not include the errno (99):

$ python3 -c 'import apport; r = apport.Report(); 
r.load(open("/var/crash/_usr_share_dh-python_pybuild.1000.crash", "rb")); 
print(r.crash_signature())'
  /usr/share/dh-python/pybuild:OSError:/usr/share/dh-python/pybuild@449:main

   * With this apport update (you need to rm the .crash and re-generate
  it), it will look like this instead:

/usr/share/dh-python/pybuild:OSError(99):/usr/share/dh-
  python/pybuild@449:main

   i. e. the errno 99 will be used to disambiguate/duplicate the crash.

  This works similarly for DBusErrors, but this is much harder to test
  manually. The backported patch includes automatic test cases which
  cover the DBusError cases, though.

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

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

[Touch-packages] [Bug 1582414] Re: No HDMI audio on Lenovo pro dock with T440s

2016-05-18 Thread Martin D. Weinberg

Does this issue have to do with MST support in kernel 4.4?  The 3.13 in
14.04 did not have MST support.

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

Title:
  No HDMI audio on Lenovo pro dock with T440s

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
  be chosen as a sink.  This is only a problem with the dock; audio
  works when plugging HDMI through the laptop's DP input.

  The audio did work with the dock in Ubuntu 14.04.  Did something in
  jack detection change?  Anyway, my work around is to plug a 3.4mm
  audio cable into the dock and power the speakers that way, but it
  would be nice to use the HDMI audio again.

  I would love to have a work around.  I've attached the output from
  alsa-info.sh, just in case this is useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  weinberg   2221 F pulseaudio
   /dev/snd/controlC2:  weinberg   2221 F pulseaudio
   /dev/snd/controlC0:  weinberg   2221 F pulseaudio
   /dev/snd/controlC1:  weinberg   2221 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 17:18:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1583372] [NEW] 73-special-net-names.rules is renaming manually created wifi interface

2016-05-18 Thread Simon Arlott

Public bug reported:

The 73-special-net-names.rules file from 229-4ubuntu5 is renaming USB
wifi network interfaces that I create manually with "iw phy phy0
interface add wifi0 type managed":

# Use MAC based names for network interfaces which are directly or indirectly
# on USB and have an universally administered (stable) MAC address (second bit
# is 0).
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", 
ATTR{address}=="?[014589cd]:*", IMPORT{builtin}="net_id", 
NAME="$env{ID_NET_NAME_MAC}"


The device is being renamed by udev as soon as it is created:
KERNEL[3299.499637] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0 (net)
KERNEL[3299.500180] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
KERNEL[3299.500388] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
KERNEL[3299.500548] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
KERNEL[3299.500680] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
KERNEL[3299.500811] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
KERNEL[3299.502911] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
UDEV  [3299.546165] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
UDEV  [3299.547977] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
UDEV  [3299.549123] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
UDEV  [3299.550082] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
UDEV  [3299.550353] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
UDEV  [3299.550495] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
UDEV  [3299.552404] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)

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

** Package changed: systemd (Ubuntu) => udev (Ubuntu)

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

Title:
  73-special-net-names.rules is renaming manually created wifi interface

Status in udev package in Ubuntu:
  New

Bug description:
  The 73-special-net-names.rules file from 229-4ubuntu5 is renaming USB
  wifi network interfaces that I create manually with "iw phy phy0
  interface add wifi0 type managed":

  # Use MAC based names for network interfaces which are directly or indirectly
  # on USB and have an universally administered (stable) MAC address (second bit
  # is 0).
  ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", 
ATTR{address}=="?[014589cd]:*", IMPORT{builtin}="net_id", 
NAME="$env{ID_NET_NAME_MAC}"

  
  The device is being renamed by udev as soon as it is created:
  KERNEL[3299.499637] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0 (net)
  KERNEL[3299.500180] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  KERNEL[3299.500388] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  KERNEL[3299.500548] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  KERNEL[3299.500680] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  KERNEL[3299.500811] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  KERNEL[3299.502911] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.546165] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
  UDEV  [3299.547977] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
  UDEV  [3299.549123] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
  UDEV  [3299.550082] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
  UDEV  [3299.550353] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
  UDEV  [3299.550495] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
  UDEV  [3299.552404] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)

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

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

[Touch-packages] [Bug 1299610] Re: pulseaudio crashed in pa_thread_mq_get

2016-05-18 Thread harre

This bug is no longer relevant for me.

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

Title:
  pulseaudio crashed in pa_thread_mq_get

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  pulse audio crashed during play of a movie in mplayer and I'm
  outputting audio on coax.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  markus10576 F pulseaudio
markus10710 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar 29 22:35:43 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-01-29 (59 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20140128)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/18/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 5002
  dmi.board.name: M2N32-SLI DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N32-SLIDELUXEACPIBIOSRevision5002:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N32-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1583365] [NEW] Strange graphic artifacts.

2016-05-18 Thread P.Johnston

Public bug reported:

In window menus, scroll bars.  Strange and random colors shift and
spread through areas of the screen.  Usually the color is blue.

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
Architecture: amd64
BootLog:
 /dev/sdb1: recovering journal
 /dev/sdb1: clean, 287693/3662848 files, 1686817/14648437 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May 18 17:27:10 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
InstallationDate: Installed on 2016-05-18 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS 8700
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=9b3a2ee0-7743-43b2-b375-527cf9436dab ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0KWVT8
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd07/09/2015:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8700
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 May 18 17:21:11 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug 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/1583365

Title:
  Strange graphic artifacts.

Status in xorg package in Ubuntu:
  New

Bug description:
  In window menus, scroll bars.  Strange and random colors shift and
  spread through areas of the screen.  Usually the color is blue.

  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
  Architecture: amd64
  BootLog:
   /dev/sdb1: recovering journal
   /dev/sdb1: clean, 287693/3662848 files, 1686817/14648437 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 18 17:27:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  InstallationDate: Installed on 2016-05-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 8700
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=9b3a2ee0-7743-43b2-b375-527cf9436dab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd07/09/2015:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8700
  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:

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

2016-05-18 Thread Stunts

Sorry about the delay. I'll try this ASAP, which is likely before the weekend.
I'll report back with results soon.

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

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

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

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

  It was working fine just before the update.

  Any logs I should post to help debug?

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

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

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

[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-05-18 Thread Evan Broder

Thanks Martin. I've confirmed that the package solves the issue for me.

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

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

Title:
  Excessive CPU utilization

Status in ccid package in Ubuntu:
  Fix Released
Status in pcsc-lite package in Ubuntu:
  Invalid
Status in ccid source package in Xenial:
  Fix Committed
Status in pcsc-lite source package in Xenial:
  Invalid
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  [Impact]

  When hotplugging a composite USB device that expose multiple
  interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not
  correctly de-initialize the USB library when it skips over the non-
  CCID interface.

  This subsequently results in pcscd (or, presumably, anything that
  loads libccid, though I don't think anything else does) either using
  100% CPU or segfaulting when the device is unplugged.

  This seems worthy of an SRU as it is an easily reproducible bug with a
  simple, targeted fix.

  [Test Case]

  1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo 
systemctl restart pcscd if a potentially fixed package has just been installed)
  2. Plug and then unplug a composite USB device that includes a CCID interface 
(such as a Yubikey NEO)
  3. Observe that pcscd has crashed with a segfault (sudo systemctl status 
pcscd)

  [Regression Potential]

  The patch is quite narrow, and thus the potential for regression
  should be limited. The new code adds calls to close_libusb_if_needed,
  which is already written to be fairly conservative.

  The worst case here is likely an unexpected call to libusb_exit, which
  could cause libusb to get into an inconsistent state. However, in
  practice the call seems quite safe, and the likelihood of regression
  low.

  ==
  Original bug description:

  In xenial, pcscd CPU utilization occasionally goes haywire:

    PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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

[Touch-packages] [Bug 1583055] Re: Empty settings.ini created for every scope even if it doesn't have settings

** 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)

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

Title:
  Empty settings.ini created for every scope even if it doesn't have
  settings

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  After recent changes to scope settings handling in shell plugin (the
  switch from QSettings to glib-based settings) we now get empty
  settings.ini and settings dir created for absolutely every scope in
  the system, even if it doesn't offer any settings. This doesn't pose
  any issues as far as I can tell (other than polluting fs), but it
  would be nice not to do that if not needed.

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

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

[Touch-packages] [Bug 1582824] Re: Pointless access request prompt

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => David Barth (dbarth)

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

Title:
  Pointless access request prompt

Status in Canonical System Image:
  Confirmed
Status in webapps-sprint:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  In attempting to test for bug #1582804 on my mako with updated rc-
  proposed image 441, immediately after logging in to the U1 account
  after tapping on the '$2.99' button for 'Cut the Rope', I was
  presented with the screen shown in the attached screenshot (e-mail
  address removed in screenshot).

  There is no reason this dialog should ever appear for the U1 account,
  and choosing either option is irrelevant to whether the account can be
  used by the scope. Choosing to not allow simply acts as cancelling the
  current in-progress action, returning the user to the app preview.
  However, immediately tapping on the '$2.99' button again will work
  just fine, and the payment UI will be presented.

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

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

[Touch-packages] [Bug 1583067] Re: Lag when favoriting/unfavoriting scopes via Manage Dash

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Lag when favoriting/unfavoriting scopes via Manage Dash

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  There is a noticable lag (2-3 seconds) when unfavoriting and
  favoriting scopes via Manage Dash. This is probably caused by the
  fact, that favorites are first written to gsettings, then read back
  upon gsettings change signal and only then reflected in the display,
  so there is some I/O and processing of gsettings change when user taps
  the star. It would be nice to optimize this.

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

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

[Touch-packages] [Bug 1583155] Re: Camera view not displayed correctly in landscape + desktop mode

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

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

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

Title:
  Camera view not displayed correctly in landscape + desktop mode

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

Bug description:
  Test case.
  - Connect the Bluetooth mouse to switch to desktop mode.
  - Put the tablet in landscape mode.
  - Open camera app.
  - Click in button to set the window to full screen.

  Expected result.
  - Camera view is in landscape mode.

  Actual result.
  - Live feed is not shown correctly, it is rotated in portrait mode.

  current build number: 10
  device name: frieza
  channel: ubuntu-touch/rc/bq-aquaris-pd.en

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

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

[Touch-packages] [Bug 1583115] Re: Gallery app unresponsive when sharing images

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

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

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

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

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

Title:
  Gallery app unresponsive when sharing images

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

Bug description:
  arale/rc-proposed.

  gallery app /Photo sections becomes unresponsive for 30-40s when
  trying to select images to share in telegram.

  how to reproduce: open telegram, share a photo, choose "Gallery" from
  "Choose from" form, select Photos (in Gallery app) from the hamburger
  menu and then try to select what photos to share. At this stage
  Gallery app freezes for 30-40s, i can't select pictures nor scroll
  up/down

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

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

[Touch-packages] [Bug 1581351] Re: Improve deltas for click packages (puritine)

@kgunn,  not sure how to approach this

** 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) => kevin gunn (kgunn72)

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

Title:
  Improve deltas for click packages (puritine)

Status in Canonical System Image:
  Confirmed
Status in Developer registration portal:
  New
Status in Puritine:
  Invalid
Status in click package in Ubuntu:
  New
Status in system-image package in Ubuntu:
  New

Bug description:
  Currently if the version of a click package changes, the full click package 
is included in the delta, which may result in huge delta updates.
  It's minor for most of the click packages. But in the case of ubuntu-pd and 
the puritine click it means we are delivering all of puritine and the apps in 
the libertine container even for a single file change in the click package. 
It's an OTA of 350MB and 1.5GB to uncompress on disk on the tablet.

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

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

[Touch-packages] [Bug 1581070] Re: [touchmx4] Data connection drops after x time

If this is specific to the mobile network it sounds like a dupe of bug #1579098
Wifi should certainly reconnect

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

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

Title:
  [touchmx4] Data connection drops after x time

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

Bug description:
  Device: Meizu MX4 Ubuntu Edition (ARALE-MEIZU)
  OS: Ubuntu 15.04 (r323) 
  Ubuntu Image 20160512 armhf (20160512-020304)
  Device Image 20160331-e14fc2
  Adaptation Image 20160504-975-19-6

  (above Image descriptions may be wrong, i'm working from Dutch Locale)

  problem exists since estimated sunday, May 8 2016

  expected behavior:
  - Data connection remains up until manually specified otherwise
  - when connection is lost due to external causes (such as bad signal), data 
connection is automatically  restored when available
  - same for Wifi.

  encoutered behavior:
  - after x amount of time (x varies between 1 and 4 hours so far) data and 
wifi connection is lost, and neither data or wifi will reconnect until I 
manually switch to flight-mode and back.
  - may also affect SIM status

  see also
  https://plus.google.com/106203549473766388410/posts/GFJAcs32kKa

  I am willing to supply log files or enter terminal commands, but need
  to be instructed

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

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

[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-05-18 Thread Jamie Strandboge

In my first attempt I didn't use --devmode.

However, I can't seem to make the snap work in a xenial amd64 VM.

I tried the original snap with:
$ sudo snap install --devmode ./snappy-tests_0.1_amd64.snap
$ snappy-tests -check.f homeInterfaceSuite
...
... Error reading config: open integration-tests/data/output/testconfig.json: 
no such file or directory


I then created a new snap with:
$ sudo apt-get install snapcraft
$ sudo unsquashfs /var/lib/snapd/snaps/snappy-tests_11.snap
$ sudo vi ./squashfs-root/command-snappy-tests.wrapper
adjust to be:
export GOPATH=$SNAP_USER_DATA/go
mkdir "$GOPATH"
$ adjust ./squashfs-root/snap.yaml
adjust version to be: 0.1+jdstrand1
$ sudo snap install --devmode ./snappy-tests_0.1+jdstrand1_amd64.snap
sudo systemctl stop snappy-autopilot.timer
sudo: no tty present and no askpass program specified
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x53b74f]

goroutine 1 [running]:
panic(0x94a020, 0xc8200100e0)
/usr/lib/go-1.6/src/runtime/panic.go:464 +0x3e6
gopkg.in/check%2ev1.(*methodType).PC(0x0, 0x5544e6)

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/check.go:60
 +0x4f
gopkg.in/check%2ev1.(*C).logCaller(0xc8200e61e0, 0x3)

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/check.go:284
 +0xa1
gopkg.in/check%2ev1.(*C).internalCheck(0xc8200e61e0, 0x9f39b8, 0x6, 0x9cda80, 
0xc8201970c0, 0x7feac3fb2568, 0xc820026028, 0xc82004fd88, 0x0, 0x1, ...)

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/helpers.go:216
 +0xeaf
gopkg.in/check%2ev1.(*C).Assert(0xc8200e61e0, 0x9cda80, 0xc8201970c0, 
0x7feac3fb2568, 0xc820026028, 0xc82004fd88, 0x1, 0x1)

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/helpers.go:173
 +0x8c
github.com/ubuntu-core/snappy/integration-tests/testutils/cli.ExecCommand(0xc8200e61e0,
 0xc820013b40, 0x4, 0x4, 0x0, 0x0)

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/github.com/ubuntu-core/snappy/integration-tests/testutils/cli/cli.go:42
 +0x306
snappy/integration-tests/tests.init.1()

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/snappy/integration-tests/tests/base_test.go:55
 +0x16d
snappy/integration-tests/tests.init()

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/snappy/integration-tests/tests/writablePaths_test.go:107
 +0x10c4
main.init()
snappy/integration-tests/tests/_test/_testmain.go:56 +0x4a



I then tried to build it myself:
$ sudo apt-get install git snapcraft
$ export GOPATH=$HOME/work
$ mkdir $GOPATH
$ export PATH=$PATH:$GOPATH
$ git clone https://github.com/plars/snappy-tests.git
$ cd snappy-tests
$ snapcraft
(this may fail; if it does, keep trying until it succeeds per IRC)
...
$ sudo snap install --devmode ./snappy-tests_0.1_amd64.snap
$ snappy-tests -check.f homeInterfaceSuite
sudo systemctl stop snappy-autopilot.timer
sudo: no tty present and no askpass program specified
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x531c3f]

goroutine 1 [running]:
panic(0x928e60, 0xc8200100f0)
/usr/lib/go-1.6/src/runtime/panic.go:464 +0x3e6
gopkg.in/check%2ev1.(*methodType).PC(0x0, 0x52ab16)

/home/jamie/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/check.go:60
 +0x4f
gopkg.in/check%2ev1.(*C).logCaller(0xc8200da000, 0x3)

/home/jamie/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/check.go:284
 +0xa1
gopkg.in/check%2ev1.(*C).internalCheck(0xc8200da000, 0x9cf2e0, 0x6, 0x9a9800, 
0xc8201a0c00, 0x7f7be51ec590, 0xc820024028, 0xc82004dd70, 0x0, 0x1, ...)

/home/jamie/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/helpers.go:216
 +0xeaf
gopkg.in/check%2ev1.(*C).Assert(0xc8200da000, 0x9a9800, 0xc8201a0c00, 
0x7f7be51ec590, 0xc820024028, 0xc82004dd70, 0x1, 0x1)

/home/jamie/snappy-tests/parts/snappy-tests/go/src/gopkg.in/check.v1/helpers.go:173
 +0x8c
github.com/ubuntu-core/snappy/integration-tests/testutils/cli.ExecCommand(0xc8200da000,
 0xc820013840, 0x4, 0x4, 0x0, 0x0)

/home/jamie/snappy-tests/parts/snappy-tests/go/src/github.com/ubuntu-core/snappy/integration-tests/testutils/cli/cli.go:42
 +0x306
snappy/integration-tests/tests.init.1()

/home/jamie/snappy-tests/parts/snappy-tests/go/src/snappy/integration-tests/tests/base_test.go:56
 +0x16d
snappy/integration-tests/tests.init()

/home/jamie/snappy-tests/parts/snappy-tests/go/src/snappy/integration-tests/tests/writablePaths_test.go:107
 +0xce8
main.init()
snappy/integration-tests/tests/_test/_testmain.go:56 +0x4a


I'm not sure what to do at this point. It seems like adjusting the GOPATH and 
creating the dir in your snap will resolve the first issue, but then run into 
the next issues.

Paul, can you provide precise steps on how to reproduce?

**

[Touch-packages] [Bug 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

2016-05-18 Thread kevin gunn

wait..so is this mir or qmtir?


** Changed in: canonical-devices-system-image
 Assignee: Stephen M. Webb (bregma) => Michał Sawicz (saviq)

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

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

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1579549] Re: Music stops playing from main speaker when a call comes in

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

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

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

Title:
  Music stops playing from main speaker when a call comes in

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Music App:
  New
Status in media-hub package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in media-hub package in Ubuntu RTM:
  New
Status in pulseaudio package in Ubuntu RTM:
  New

Bug description:
  1. Music is playing
  2. It is ok with sms notification and sound but whenever a call comes or even 
missed call the music stops playing during call but after the call is 
disconnected music resumes playing in low volume and i turned the volume to 
full and still the sound is low and then i noticed that music stopped playing 
from the phone's loud speaker instead it is playing from top talking speaker 
(my nexus 4).
  3. to resolve this issue i've to close and re open music app which is very 
frustrating.
  4. And lastly When can i receive and disconnect calls from ear phone's call 
disconnect button it would be very handy while driving.

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

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

[Touch-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

Is bug #1270189 related

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

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

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

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

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Touch-packages] [Bug 1579031] Re: High CPU usage (~10%) on Pro 5 when idle (with screen on)

** Also affects: turbo
   Importance: Undecided
   Status: New

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

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

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

Title:
  High CPU usage (~10%) on Pro 5 when idle (with screen on)

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

Bug description:
  It was reported that the Pro 5 is draining battery and I can confirm
  we're seeing unusually high CPU usage when the device is idle (with
  screen on).

  Steps:
  * turn the screen on
  * monitor top output

  Expected:
  * unity8 under/around 1% CPU usage

  Current:
  * unity8 around 10% CPU usage

  I've confirmed it's not rendering, will be looking at a perf report
  when I get it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.12+15.04.20160504.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.100-user-01767-gf5aa556 aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Fri May  6 13:46:56 2016
  InstallationDate: Installed on 2016-05-05 (1 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160505-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect

** 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) => John McAleely (john.mcaleely)

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

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

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

Title:
  [touch] Mobile data connection drops, and doesn't automatically
  reconnect

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

Bug description:
  Krillin, rc-proposed, r325

  In the last couple of weeks it often happened that the mobile data
  connection dropped without reconnecting afterwards. I often find my
  device without mobile data connection without apparent reason.

  Switching mobile data connection Off and back On from settings
  restores the connection.

  I don't have any useful additional info to provide, unfortunately.
  Please let me know if you need log/cmd output in particular.

  phablet@ubuntu-phablet:~$ nmcli d status
  DEVICE   TYPE  STATE CONNECTION 
  ril_1gsm   disconnected  -- 
  wlan0wifi  disconnected  -- 
  ril_0gsm   unavailable   -- 
  ifb0 ifb   unmanaged -- 
  ifb1 ifb   unmanaged -- 
  ip6tnl0  ip6tnlunmanaged -- 
  sit0 iptunnel  unmanaged -- 
  lo   loopback  unmanaged -- 
  tunl0unknown   unmanaged --

  Syslog since last time mobile data was connected:
  http://pastebin.ubuntu.com/16259803/

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

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

[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling

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

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

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

Title:
  Upstart log files are not reopened after rolling

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

Bug description:
  Seen on stable and proposed vivid based touch images
  I noticed on two of my devices that after a scheduled rolling of the files in 
/var/log/upstart that there were no active *.log files at all.
  The config for upstart includes nocreate but this has always been this way.
  Is this intended or did something change in logrotate?
  A similar bug report states that the files will be opened on a subsequent 
write from the upstart process, but this is clearly not happening.

  See 
http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation
  and perhaps bug #1350782

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

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

[Touch-packages] [Bug 1583355] [NEW] Add support for vti/vti6 interfaces

2016-05-18 Thread Halvor Lyche Strandvoll

Public bug reported:

Add support for vti/vti6 interfaces

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

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

Title:
  Add support for vti/vti6 interfaces

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Add support for vti/vti6 interfaces

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

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

[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD

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

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

Title:
  tablet connected to monitor shows black screen - Idek Iiyama PL2409HD

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When connecting my M10 device to my monitor (Idek Iiyama PL2409HD),
  the monitor shows that there is a signal on hdmi, but the screen stays
  black.

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

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

[Touch-packages] [Bug 1572576] Re: Taking a photo not working with Qt 5.6

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

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

Title:
  Taking a photo not working with Qt 5.6

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

Bug description:
  It seems taking a photo (or video) buttons are dimmed for some reason
  on Qt 5.6.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1510382] Re: Window contents (and mouse cursors) become randomly blurry (or clear) after moving around

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  Window contents (and mouse cursors) become randomly blurry (or clear)
  after moving around

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

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1581206] Re: Cannot read the time and SIM information on a message

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

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

Title:
  Cannot read the time and SIM information on a message

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

Bug description:
  Light gray on a white background with miniscule font size is illegible
  for many people

  See bug #1579704

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

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

[Touch-packages] [Bug 1580099] Re: telephony-service-indicator causing constant dbus traffic

What dbus-monitor command are you using? curious as I could not  see
such traffic

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

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

Title:
  telephony-service-indicator causing constant dbus traffic

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Today I noticed that telephony-service-indicator causes repeated
  method calls on dbus. It seems to call Get Postion on the media hub
  every second. The message below is repeated every second:

  
  method call sender=:1.61 -> dest=core.ubuntu.media.Service serial=2795 
path=/core/ubuntu/media/Service/sessions/0; 
interface=org.freedesktop.DBus.Properties; member=Get
 string "org.mpris.MediaPlayer2.Player"
 string "Position"

  
  phablet@ubuntu-phablet:~$ busctl status :1.61
  [...]
  Exe=/usr/bin/telephony-service-indicator
  [...]

  
  Instead of polling every second, this method should be called only once and 
then it should listed to the PropertyChanged coming from media hub.

  FWIW, I am not playing any media or have phone calls ongoing.

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

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

[Touch-packages] [Bug 1581892] Re: Download fails on already authenticated site

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

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

Title:
  Download fails on already authenticated site

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

Bug description:
  I have a personal website that I use Apache's AuthType Basic to authenticate.
  From my phone ( Nexas 4 Mako OTA10 ) I can access the page and login OK. When 
I download a file I get a HttpError: 401-Unathorized.

  More in depth:
  When I press the "GetFile" link Apache logs (in access.log):

  192.168.0.67 - barry [14/May/2016:17:47:11 -0500] "GET
  /briefcase/getfile.php?id=45 HTTP/1.1" 200 154936
  "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0
  (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36
  Chromium/35.0.1870.2 Mobile Safari/537.36"

  On my phone the the Download Dialog pops up and I press download
  apache logs

  192.168.0.67 - - [14/May/2016:17:47:33 -0500] "GET
  /briefcase/getfile.php?id=45 HTTP/1.1" 401 728
  "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0
  (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36
  Chromium/35.0.1870.2 Mobile Safari/537.36"

  The difference is the first has my user name "barry" in it and the
  second doesn't.

  In comparison when doing the same thing from my desktop (14.04) and
  FireFox Apache logs

  192.168.0.2 - barry [14/May/2016:18:04:49 -0500] "GET
  /briefcase/getfile.php?id=45 HTTP/1.1" 200 492086
  "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0
  (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0"

  and displays the "What should FireFox do with this file" dialog and
  Apache logs nothing further.

  On my phone this behavior is the same whether I press "Download" or
  "Choose an application" from the Download dialog. Also if I long press
  the link and choose "Save link" the download fails also.

  When I tried to download a file from a commercial site I have to log
  into, the download succeeded. I suspect the difference is the
  commercial site probably uses something beside "AuthType Basic".

  I'm happy to provide any logs or to do more testing.

  Thanks

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in text rendering, mainly in Unity8 window titlebars

2016-05-18 Thread kevin gunn

comparison screenshot even better

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

Title:
  Randomly corrupt characters in text rendering, mainly in Unity8 window
  titlebars

Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

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

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

[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-18 Thread Dave Chiluk

@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm.  This issue very likely unrelated.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr

[Touch-packages] [Bug 1582642] Re: Current platform-api FTBFS on xenial due to unit test failure

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

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

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

Title:
  Current platform-api FTBFS on xenial due to unit test failure

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  Current package in xenial FTBFS due to failures in the
  test_ua_sensors_mock test-case. Example logs can be found in the
  recent no-change rebuild:

  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
  phone-overlay/+sourcepub/6391641/+listing-archive-extra

  It is critical to get this fixed as we need all arm64 binaries built
  for ubuntu-touch xenial.

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

Sounds like bug #1528668 but that fix released in late Jan when this was
first reported

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1578007] Update Released

2016-05-18 Thread Chris J Arges

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

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

Title:
  python-apt in yakkety no longer creates partial

Status in Snapcraft:
  In Progress
Status in python-apt package in Ubuntu:
  In Progress
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released

Bug description:
  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/

  If 'partial' is created in `downloaddir` then it works again

  [Impact]

   * Users of yakkety won't be able to build snaps with stage packages.

   * Users of xenial are not affected.

  [Test Case]

  Build a snap with stage packages:
   * apt get install snapcraft snapcraft-examples
   * mkdir /tmp/mosquitto
   * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
   * cd /tmp/mosquitto
   * snapcraft

  A snap must be generated.

  [Regression Potential]

   * The fix in yakkety could affect the version in xenial.

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

@tenleftfingers can you provide the output of system-image-cli --info

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1578007] Re: python-apt in yakkety no longer creates partial

This bug was fixed in the package snapcraft - 2.8.8b

---
snapcraft (2.8.8b) xenial; urgency=medium

  [ Sergio Schvezov ]
  * Remove missing replacement for unittest.mock (#494) (LP: #1576998)
  * Create the 'partial' directory for apt. (#499) (LP: #1578007)
  * Don't fail if there is no system library list (#496) (LP: #1577750)
  * Don't clean target before extracting npm (#489) (LP: #1575876)
  * Don't delete the nodejs download on build. (#490) (LP: #1575882)

  [ Leo Arias ]
  * Import mock from unittest. (#492) (LP: #1576998)
  * autopkgtests: run the tests using the installed package (#464)
(LP: #1570992)
  * Remove --allow-unauthenticated from examples tests (#482) (LP: #1573211)
  * Update the assertion of the example install (#483) (LP: #1573243)
  * Examples tests: Update the path to the snaps binaries (#484) (LP: #1573349)
  * Examples tests: use systemctl instead of the removed snap service (#485)
(LP: #1573697)
  * Update the mosquitto example SNAP_USER_DATA path. (#486) (LP: #1574857)
  * Update the busybox test to use the snap data path. (LP: #1574901)
  * Remove the integration tests coverage. (#488) (LP: #1575383)

  [ Vincent Ladeuil ]
  * Make upload more robust by ignoring spurious errors while polling the
scan status. (#480) (LP: #1572963)

  [ Kyle Fazzari ]
  * docs/get-started.md: Stop discussing snappy-tools. (#454) (LP: #1568113)

 -- Sergio Schvezov   Fri, 29 Apr 2016
14:59:47 -0300

** Changed in: snapcraft (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  python-apt in yakkety no longer creates partial

Status in Snapcraft:
  In Progress
Status in python-apt package in Ubuntu:
  In Progress
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released

Bug description:
  This now fails: http://paste.ubuntu.com/16208927/
  With an error that looks like http://paste.ubuntu.com/16208917/

  If 'partial' is created in `downloaddir` then it works again

  [Impact]

   * Users of yakkety won't be able to build snaps with stage packages.

   * Users of xenial are not affected.

  [Test Case]

  Build a snap with stage packages:
   * apt get install snapcraft snapcraft-examples
   * mkdir /tmp/mosquitto
   * cp /usr/share/doc/snapcraft-examples/examples/mosquitto/* /tmp/mosquitto
   * cd /tmp/mosquitto
   * snapcraft

  A snap must be generated.

  [Regression Potential]

   * The fix in yakkety could affect the version in xenial.

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

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

[Touch-packages] [Bug 1581559] Re: Some apps don't start (guitar tools, tuner beta)

2016-05-18 Thread Daniel d'Andrada

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

** 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/1581559

Title:
  Some apps don't start (guitar tools, tuner beta)

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  Fix Released
Status in trust-store package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  current build number: 105
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

  but same problem on krillin

  Some apps don't start on frieza (guitar tools, tuner beta). There is
  only a splash screen and a spinner.

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

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

[Touch-packages] [Bug 1377996] Re: dialer is freezing on active call screen

@saviq any ideas from these logs?

** Changed in: unity-mir (Ubuntu)
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in unity-mir package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

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

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

[Touch-packages] [Bug 1583232] Re: Wowza Streaming Engine out of memory on Ubuntu 16.04

2016-05-18 Thread Martin Pitt

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

** This bug has been marked a duplicate of bug 1578080
   percona cluster hits resource limits in HA Openstack cloud with xenial

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

Title:
  Wowza Streaming Engine out of memory on Ubuntu 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  Wowza Streaming Engine using systemd runs out of memory within a few
  minutes on Ubuntu 16.04. Specific Java error is: Failed to get the
  session[java.lang.OutOfMemoryError: unable to create new native thread

  This appears to be related to systemd, and specific to 16.04, since
  the software functions properly in previous versions of Ubuntu
  (verified with 15.04 and 15.10) and also works in 16.04 when the
  system is reverted to upstart init.

  I have also verified that a working 15.10 installation (systemd) fails
  after upgrading to 16.04.

  Currently, we are recommending that users don't upgrade to 16.04.

  Thanks you for your assistance and I can provide additional
  information as needed.

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

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

[Touch-packages] [Bug 1581559] Re: Some apps don't start (guitar tools, tuner beta)

2016-05-18 Thread Jean-Baptiste Lallement

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

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

Title:
  Some apps don't start (guitar tools, tuner beta)

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  In Progress
Status in trust-store package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  current build number: 105
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

  but same problem on krillin

  Some apps don't start on frieza (guitar tools, tuner beta). There is
  only a splash screen and a spinner.

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

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

[Touch-packages] [Bug 1583237] Re: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file

2016-05-18 Thread Martin Pitt

** No longer affects: autopkgtest (Ubuntu)

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

Title:
  lxc-attach strange tty behavior (kills command) when stderr is
  redirected to a file

Status in lxc package in Ubuntu:
  New

Bug description:
  On a fresh Ubuntu 16 release, commands started by lxc-attach such as
  dd are being killed WHEN REDIRECTING stderr (to a file), and lxc-
  attach return a zero status. Command works fine without the
  redirection.

  This scenario is working on Ubuntu 15 with previous lxc release, but
  not on new LXC 2.0.0 (same issue on 2.0.1 too)

  sudo apt-get -y install lxc
  sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER
  sudo lxc-start -d --name utest

  sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 
2>/tmp/bar
  sudo lxc-attach -n utest -- ls -lh /tmp/foo
  -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo

  Might be related to bug 1553097 (and/or
  https://github.com/lxc/lxc/pull/873)

  NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh
  /tmp/foo" ALSO does not return anything (no output)

  I'm available for any additional info.

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

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

[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap

2016-05-18 Thread Jamie Strandboge

@Paul, I tried to test this in a snappy VM with:
$ snappy-tests -check.f homeInterfaceSuite
Bad system call

--
FAIL: :46: homeInterfaceSuite.SetUpSuite

/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/github.com/ubuntu-core/snappy/integration-tests/testutils/common/common.go:65:
...open 
/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/github.com/ubuntu-core/snappy/integration-tests/testutils/common/common.go:
 no such file or directory
... value *os.PathError = {Op:"open", 
Path:"integration-tests/data/output/testconfig.json", Err:0x2} ("open 
integration-tests/data/output/testconfig.json: no such file or directory")
... Error reading config: open integration-tests/data/output/testconfig.json: 
no such file or directory

OOPS: 0 passed, 1 FAILED, 7 MISSED
--- FAIL: Test (0.01s)
FAIL

Let me try to checkout the branch in a desktop VM to reproduce.

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

Title:
  kernel BUG on snap disconnect from within a snap

Status in apparmor package in Ubuntu:
  New

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

To manage notifications about this

[Touch-packages] [Bug 1583331] [NEW] Change to lsb package in 16.04+ breaks backwards compatibility

2016-05-18 Thread Patrick Then

Public bug reported:

Since Ubuntu 16.04 Xenial Xerus, lsb has been changed (removed?
numbering scheme altered?) in such a way that installation of various
software becomes impossible due to missing dependencies.

Most prominently it has become impossible to install the Linux driver packages 
for Epson printers (available from Epson).
While the repositories contain a package (escpr) for epson printer drivers, 
this package provides only limited functionality (indicated by the r suffix in 
the package), which in some cases prevents any reasonable work with Epson 
printers (e.g. no support for duplex printing, additional paper cartridges, 
etc.).
In my case, a Stylus Office BX925 (compatible to Workforce 840) can't be used 
with Ubuntu anymore, except for the most simple printing tasks.

This issue affects the drivers and utilities for other printer brands as
well.

Further affected software seems to be e.g. Google Earth.

While it's reasonable to assume that Google Earth will be eventually
updated, there's no such guarantee for affected printer
drivers/utilities, given the notoriously bad official Linux support of
some hardware.

lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04

lsb version 9.20160110

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

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

Title:
  Change to lsb package in 16.04+ breaks backwards compatibility

Status in lsb package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.04 Xenial Xerus, lsb has been changed (removed?
  numbering scheme altered?) in such a way that installation of various
  software becomes impossible due to missing dependencies.

  Most prominently it has become impossible to install the Linux driver 
packages for Epson printers (available from Epson).
  While the repositories contain a package (escpr) for epson printer drivers, 
this package provides only limited functionality (indicated by the r suffix in 
the package), which in some cases prevents any reasonable work with Epson 
printers (e.g. no support for duplex printing, additional paper cartridges, 
etc.).
  In my case, a Stylus Office BX925 (compatible to Workforce 840) can't be used 
with Ubuntu anymore, except for the most simple printing tasks.

  This issue affects the drivers and utilities for other printer brands
  as well.

  Further affected software seems to be e.g. Google Earth.

  While it's reasonable to assume that Google Earth will be eventually
  updated, there's no such guarantee for affected printer
  drivers/utilities, given the notoriously bad official Linux support of
  some hardware.

  lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lsb version 9.20160110

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

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

[Touch-packages] [Bug 1579922] Re: dh_systemd_enable fails due to 'preset' when service file is renamed

2016-05-18 Thread Serge Hallyn

I can reproduce it with the package excerpts at

https://code.launchpad.net/~serge-hallyn/+git/pkg1
and
https://code.launchpad.net/~serge-hallyn/+git/pkg2

First

dpkg -i pkg1_1-1_amd64.deb

then

dpkg -i pkg1_1-2_amd64.deb pkg2_1-2_amd64.deb

On yakkety, this gives me:

(Reading database ... 27385 files and directories currently installed.)
Preparing to unpack /pkg1_1-2_amd64.deb ...
enabled
Unpacking pkg1 (1-2) over (1-1) ...
Selecting previously unselected package pkg2.
Preparing to unpack /pkg2_1-2_amd64.deb ...
Unpacking pkg2 (1-2) ...
Setting up pkg2 (1-2) ...
Failed to execute operation: No such file or directory
/usr/bin/deb-systemd-helper: error: systemctl preset failed on pkg2.service: No 
such file or directory
Failed to get unit file state for pkg2.service: No such file or directory
pkg2.service is a disabled or a static unit, not starting it.

I trust I'm doing something wrong in pkg1.preinst (in version 1-2).

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

Title:
  dh_systemd_enable fails due to 'preset' when service file is renamed

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  This is a bit of a special case and may be being done wrong by the
  package...  libvirt is moving the libvirt-bin.service from libvirt-bin
  package to libvirtd.service in libvirt-daemon-system package.  The
  packaging source can be seen at https://git.launchpad.net/~libvirt-
  maintainers/ubuntu/+source/libvirt/tree/?h=2016-05-07/yakkety, and it
  is packaged at ppa:serge-hallyn/virt.

  When using the init-system-helpers package from xenial, this all
  works. However with the init-system-helpers package in yakkety, and
  when upgrading the current libvirt-bin package to this proposed
  package, it fails during deb-systemd-helper with a message from:

  system("/bin/systemctl", "--preset-mode=enable-only",
  "preset", $scriptname) == 0 or
  error("systemctl preset failed on $scriptname: $!");

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

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

[Touch-packages] [Bug 1578391] Re: Initial Wi-Fi connection (from wizard) not reflected in indicator

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Initial Wi-Fi connection (from wizard) not reflected in indicator

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

Bug description:
  Able to connect to Wi-Fi during initial wizard, but indicator never
  reflects connected state.  Reboot remedies.

  TEST CASE
  Fresh flash, navigate through wizard to network setup
  1. Connect to access point, input password, tap 'ok'
  2. "Connected" appears below selected access point
  EXPECTED
  Network indicator reflects Wi-Fi connected
  ACTUAL
  Network indicator dark

  Data evidently connected (although possibly via edge).  Note that
  navigating to settings and disabling cellular data "kicks" network
  indicator, indicator reflects Wi-Fi connected state.  Some signal not
  being received by or expressed to i-n?

  awe instructed in adding some debugging infos to n-m but I see no
  syslog.

  current build number: 324
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-04 14:18:22
  version version: 324
  version ubuntu: 20160503
  version device: 20160329-a9bacdb
  version custom: 20160324--36-54-vivid

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

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

[Touch-packages] [Bug 1580700] Re: wget in 12.04 does not support SNI

2016-05-18 Thread Marc Deslauriers

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

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

Title:
  wget in 12.04 does not support SNI

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Precise:
  Fix Committed

Bug description:
  [Impact]
  wget in Ubuntu 12.04 doesn't have support for TLS Server Name Indication, 
which makes it incompatible with certain sites, includes sites that use the 
Let's Encrypt Authority.

  The updated package fixes the issue with a backported patch from wget
  1.14.

  [Test Case]
  1- wget https://www.x.org
  2- Connection should succeed, instead of getting an error (ERROR: no 
certificate subject alternative name matches)

  [Regression Potential]
  Commit is simple. If broken, could possibly break SSL support in wget.

  
  Original report:

  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1580700] Re: wget in 12.04 does not support SNI

2016-05-18 Thread Al T

I've just tested the package from -proposed and it fixed a problem with
a GitHub https download for me.

It was failing before with SSL connection establishment error and after
finding a hint for lack of SNI support in a standard 12.04's wget
version by googling, I've found this very bug record and I'm glad to
confirm it works [for me].

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

Title:
  wget in 12.04 does not support SNI

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Precise:
  Fix Committed

Bug description:
  [Impact]
  wget in Ubuntu 12.04 doesn't have support for TLS Server Name Indication, 
which makes it incompatible with certain sites, includes sites that use the 
Let's Encrypt Authority.

  The updated package fixes the issue with a backported patch from wget
  1.14.

  [Test Case]
  1- wget https://www.x.org
  2- Connection should succeed, instead of getting an error (ERROR: no 
certificate subject alternative name matches)

  [Regression Potential]
  Commit is simple. If broken, could possibly break SSL support in wget.

  
  Original report:

  Let's Encrypt Authority should be added to CA-certificates.
  https://www.X.org is now using a cert from this CA, wget fails when
  connecting to X.org.

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

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

[Touch-packages] [Bug 1531270] Re: Shell always switches to Windowed mode when mouse is connected

** Changed in: canonical-developer-experience
   Status: New => Fix Released

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

Title:
  Shell always switches to Windowed mode when mouse is connected

Status in Client Developer Experience:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in android package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  When the emulator starts it presents the login screen for the phablet user, 
presumably because it detects a mouse.
  I expect it to emulate the phone and provide the passcode screen as 
approproate

  (see also bug #1531268)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1531270/+subscriptions

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

[Touch-packages] [Bug 1535583] Re: Unity8 is crashing in the emulator

** No longer affects: canonical-developer-experience

** No longer affects: canonical-devices-system-image

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

Title:
  Unity8 is crashing in the emulator

Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu RTM:
  Incomplete

Bug description:
  Creating an emulator from the rc-proposed channel on 15.04 desktop.

  The welcome screen appears and then the unity8 restarts. Logging in to
  the emulator with adb shows that the unity8 process is crashing and
  restarting.

  The emulator and the phablet tools ->
  http://pastebin.ubuntu.com/14574309/

   /var/crash/_usr_bin_unity8.32011.crash ->
  http://paste.ubuntu.com/14574296/

  
  /home/phablet/.cache/upstart/unity8.log -> http://paste.ubuntu.com/14574315/

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

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

[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken

** Changed in: canonical-developer-experience
   Status: New => Fix Released

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

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Fix Released
Status in android package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions

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

[Touch-packages] [Bug 1572943] Re: Token::isValid() returns true on invalid tokens

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => David Barth (dbarth)

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

Title:
  Token::isValid() returns true on invalid tokens

Status in Canonical System Image:
  Fix Committed
Status in ubuntuone-credentials package in Ubuntu:
  In Progress

Bug description:
  Token token(QString(), QString(), QString(), QString());
  token.isValid(); // prints true

  This is something which can obviously being worked around in the
  client code, but I think it would be nicer if Token would consider
  empty strings as missing data.

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

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

[Touch-packages] [Bug 1575510] Re: [feature] Option to take photos in 16:9 format with the mx4

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

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

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

Title:
  [feature] Option to take photos in 16:9 format with the mx4

Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  In the first OTA's was no option to change the picture resolution/format and 
all pictures where taken with 5120x2880  (16:9), which was nearer the full 
resolution of the chip than the new 5:3 format (4480x2688). 
  An option for the mx4 to take photos in 16:9 again would be great.

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

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

[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-18 Thread Aeaeaeaeaeae

is it possible that there is a link to the mysterious "vribr0"?
...it occurs both in the initial bug desription here, and on my laptop too (I 
did not configure virbr0 anywhere, but its there since the installation of 
16.04, when the wifi problem started)

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

2016-05-18 Thread Benjamin Morgan

I've confirmed this issue on multiple dell platforms including xps 9343,
9350, & 5510 laptops, both broadcom & intel wireless radios, & multiple
types of LE devices.

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

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

** Changed in: gnome-keyring (Ubuntu)
   Status: New => Confirmed

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

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

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

[Touch-packages] [Bug 1576711] Re: [xenial] Enable arm64 build

2016-05-18 Thread Rodney Dawes

** Changed in: unity-scope-click (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-scope-click (Ubuntu)
   Status: New => In Progress

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Rodney Dawes (dobey)

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

Title:
  [xenial] Enable arm64 build

Status in aethercast:
  New
Status in Canonical System Image:
  Confirmed
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  New
Status in libhybris package in Ubuntu:
  Fix Released
Status in qtmir-gles package in Ubuntu:
  New
Status in qtubuntu-camera package in Ubuntu:
  New
Status in qtubuntu-gles package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in qtubuntu-sensors package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Tracking bug for touch packages without arm64 enabled on xenial

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

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

[Touch-packages] [Bug 1576711] Re: [xenial] Enable arm64 build

** Branch linked: lp:~dobey/unity-scope-click/build-all

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

Title:
  [xenial] Enable arm64 build

Status in aethercast:
  New
Status in Canonical System Image:
  Confirmed
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  New
Status in libhybris package in Ubuntu:
  Fix Released
Status in qtmir-gles package in Ubuntu:
  New
Status in qtubuntu-camera package in Ubuntu:
  New
Status in qtubuntu-gles package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in qtubuntu-sensors package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  Tracking bug for touch packages without arm64 enabled on xenial

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

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

[Touch-packages] [Bug 890784] Re: Gnome-terminal continues to show outline cursor after getting focus

2016-05-18 Thread Sven Mueller

Is there a chance to have this fgix backported to Trusty? It affects
some of our users.

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

Title:
  Gnome-terminal continues to show outline cursor after getting focus

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Normall, it works like this: When a terminal is focused its cursor is
  solid (and blinking).  When a terminal is not focused, its cursor is
  an outline (and doesn't blink).

  Sometimes (but increasingly more often in Oneiric than with older
  versions) I get the outline cursor even when my GNOME Terminal is
  focused.

  Steps to reproduce:
  1. Open two windows on different workspaces: say, a browser on workspace 1, 
and a terminal on workspace 2
  2. Focus the browser window
  3. Trigger the Scale plugin for windows on all workspaces (W is the 
default keybinding for this, I believe)
  4. Click on the terminal to focus it (and switch to workspace 2)

  Expected behavior: cursor in terminal is filled solid and blinking

  Actual behaviour: cursor in terminal is an empty, non-blinking
  outline.

  This does not appear to happen when the terminal is on the same
  workspace as the window I'm switching from.

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

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

[Touch-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working

2016-05-18 Thread Huck-bernhard

I have install the fix and make a Test

1. Button "Browse File.." is removed in unity-control-center. But in Top Right 
Menu is it still visible. See on Image.
2. Send File is working now with LG L40

** Attachment added: "Bluetoth Browse file.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1562822/+attachment/4665710/+files/Bluetoth%20Browse%20file.png

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

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth source package in Xenial:
  New
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

2016-05-18 Thread Jean-Baptiste Lallement

** 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 unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1580774

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.22 series:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

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

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

[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work

2016-05-18 Thread Nicolas

Works fine for me too (Elitebook 830 G3 with ultra slim docking station). 
As for Rémi, pin line-out was 0x1b.
Thxs !

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

Title:
  [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line
  in/Line out on docking station doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When I plug in external speakers to line in/line out combo on the
  laptop the internal speakers are turned off but when I plug the
  speakers into the docking station (HP UltraSlim Dock 2013 EURO,
  D9Y32AA) music keeps playing in the internal speakers. Similar
  behaviour (nothing happens) is experienced with microphone connected
  to line in on docking station.

  ### Expected behaviour
  Plugging in external speakers to docking station should turn off sound from 
laptop internal speakers.

  Plugging in microphone to line in on docking station should switch
  from "internal microphone" to "microphone" in Ubuntu sound settings.

  ### Current behaviour
  Sound keeps playing in internal speakers when plugging in external speakers 
to docking station.

  Plugging in microphone to line in on docking station, nothing happens.

  ### Hardware
  Laptop: HP EliteBook 840 G2
  Product number: H9W19EA#AK8

  Docking station: HP UltraSlim Dock 2013 EURO
  Product number: D9Y32AA

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chol   2001 F pulseaudio
   /dev/snd/controlC0:  chol   2001 F pulseaudio
   /dev/snd/controlC1:  chol   2001 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  2 08:16:15 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-05 (26 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.04
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.54
  dmi.chassis.asset.tag: 5CG5093YZ7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G2
  dmi.product.version: A3009D410303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

2016-05-18 Thread bs

This solved the issue:
Append to /etc/sysctl.conf the following:
net.ipv4.tcp_mtu_probing = 1

after restart you should see at /proc/sys/net/ipv4/tcp_mtu_probing the
value "1"

A temporary solution is:
echo 1 > /proc/sys/net/ipv4/tcp_mtu_probing
caveat: this will be reset at boot.

You can try also with value "2" if still not working.

(see explanation at:https://thesimplecomputer.info/pages/adventures-in-
linux-tcp-tuning-page2)

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

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

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

[Touch-packages] [Bug 1583269] [NEW] Bash dies with a SIGABRT sporadically when doing 'read -N INTEGER'.

2016-05-18 Thread David Hunt

Public bug reported:

Bash sometimes dies with a SIGABRT on the command
read -N $N < /dev/urandom
where $N represent an integer >=1.

It occurs frequently for high values of N (>2**20).
It occurs rarely for low values of N (<2**20).
It has occurred more than once with a value of N as low as 128!

With N=2**21, this command aborts approximately 5 out of 10 tries.
( read -N 2097152 < /dev/urandom )

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1
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: Unity
Date: Wed May 18 12:24:28 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-formosa-beigang-precise-amd64-20130801-1
InstallationDate: Installed on 2016-01-23 (116 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130801-07:00
SourcePackage: bash
UpgradeStatus: Upgraded to xenial on 2016-04-22 (26 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bash dies with a SIGABRT sporadically when doing  'read -N INTEGER'.

Status in bash package in Ubuntu:
  New

Bug description:
  Bash sometimes dies with a SIGABRT on the command
  read -N $N < /dev/urandom
  where $N represent an integer >=1.

  It occurs frequently for high values of N (>2**20).
  It occurs rarely for low values of N (<2**20).
  It has occurred more than once with a value of N as low as 128!

  With N=2**21, this command aborts approximately 5 out of 10 tries.
  ( read -N 2097152 < /dev/urandom )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1
  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: Unity
  Date: Wed May 18 12:24:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-formosa-beigang-precise-amd64-20130801-1
  InstallationDate: Installed on 2016-01-23 (116 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130801-07:00
  SourcePackage: bash
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (26 days ago)

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

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

[Touch-packages] [Bug 1566373] Re: GMail webapp keyboard hide and seek

2016-05-18 Thread Chris Coulson

And the same behaviour happens with GMail in Chrome/Desktop

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

Title:
  GMail webapp keyboard hide and seek

Status in Canonical System Image:
  Confirmed
Status in webapps-sprint:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This is possibly a keyboard problem instead, please feel free to
  reassign as necessary.  Testing with Frieza r75.

  TEST CASE
  GMail account connected, GMail app open, landscape mode
  1.  Compose e-mail, compose screen appears
  2.  Tap in address header
  EXPECTED
  Keyboard appears
  ACTUAL
  Keyboard appears, keyboard immediately hides

  Possibly this is a layout issue; also the delay in opening the
  keyboard (blank white space left open during delay) may explain?
  Here's a link to a video (note upside-down :/ ):
  http://people.canonical.com/~alesage/video20160404_164751052.mp4 .

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

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

[Touch-packages] [Bug 1495120] Re: No function to explicitly enable Caller ID

2016-05-18 Thread Stuart McQuade

I used that solution for months, but eventually became sick of it and
stopped using my Ubuntu phone because of this bug. It may be operator
dependant, but I required an activate code each time I turned on my
phone or turned off flight mode. It seems that (at least with my
operator, Sonera Finland) that the phone sends a deactivate callerID by
default when initially connecting to the GSM network.

A temporary fix for this could be to update the OS so that callerID is
activated and sent by default. I've read, though, that some people claim
that CallerID is apparently activated by default, but this doesn't seem
to be the case when used with my local operator.

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

Title:
  No function to explicitly enable Caller ID

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  My phone network uses a secret Caller ID by default. There should bean
  option in Ubuntu Touch to explicitly enable a public caller ID.

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

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

[Touch-packages] [Bug 1566373] Re: GMail webapp keyboard hide and seek

2016-05-18 Thread Chris Coulson

With the GMail desktop UI, resizing the window causes it to remove focus
from the input elements in the compose UI - you can reproduce this with
the GMail webapp on a desktop.

I suspect this is relevant, given that the webapp is resized on the
tablet when the OSK is displayed

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

Title:
  GMail webapp keyboard hide and seek

Status in Canonical System Image:
  Confirmed
Status in webapps-sprint:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This is possibly a keyboard problem instead, please feel free to
  reassign as necessary.  Testing with Frieza r75.

  TEST CASE
  GMail account connected, GMail app open, landscape mode
  1.  Compose e-mail, compose screen appears
  2.  Tap in address header
  EXPECTED
  Keyboard appears
  ACTUAL
  Keyboard appears, keyboard immediately hides

  Possibly this is a layout issue; also the delay in opening the
  keyboard (blank white space left open during delay) may explain?
  Here's a link to a video (note upside-down :/ ):
  http://people.canonical.com/~alesage/video20160404_164751052.mp4 .

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

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

[Touch-packages] [Bug 762349] Re: [SRU] Difficult to distinguish which tab is selected

2016-05-18 Thread Will Cooke

** Changed in: ayatana-design
   Status: New => Fix Committed

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a dark grey 
background

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions

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

[Touch-packages] [Bug 1583256] Re: Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist

2016-05-18 Thread dino99

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

** This bug has been marked a duplicate of bug 1583255
   Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if 
~/.config/pulse/default.pa does not exist

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

Title:
  Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if
  ~/.config/pulse/default.pa does not exist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System is Ubuntu 16.04

  According to Ubuntu Pulseaudio MAN page:

  http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html

  it says...

 The  PulseAudio  sound  server  interprets  a  configuration  script on
 startup, which is mainly used to define the set  of  modules  to  load.
 When PulseAudio runs in the per-usermodeand
 ~/.config/pulse/default.pa exists, that file is used.  When  PulseAudio
 runs   in   the   per-user   mode   and   that   file   doesn't  exist,
 /etc/pulse/default.pa  is  used. 

  On my system I have put the following into - /etc/pulse/default.pa

  load-module module-native-protocol-tcp auth-ip-
  acl=127.0.0.1;10.204.151.0/24

  The contents of my ~/.config/pulse/ directory contains NO default.pa
  file only the cookie file:

  $ ls ~/.config/pulse
  cookie

  After a reload I issue the command patcl list modules and the "module-
  native-protocol-tcp" is NOT listed ?

  $ pactl list modules
  Module #0
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "8.0"

  Module #1
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Always keeps at least one sink loaded 
even if it's a null one"
module.version = "8.0"

  Module #3
Name: module-xrdp-sink
Argument: 
Usage counter: 0
Properties:
module.author = "Jay Sorg"
module.description = "xrdp sink"
module.version = "8.0"

  Module #4
Name: module-xrdp-source
Argument: 
Usage counter: n/a
Properties:
module.author = "Laxmikant Rashinkar"
module.description = "xrdp source"
module.version = "8.0"

  Module #5
Name: module-native-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "8.0"

  Module #6
Name: module-cli-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Command line interface protocol (UNIX 
sockets)"
module.version = "8.0"

  I am filing this bug because according to the MAN page (see above)...
  since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio
  should be executing the /etc/pulse/default.pa configuration instead...
  which should be loading:

  load-module module-native-protocol-tcp auth-ip-
  acl=127.0.0.1;10.204.151.0/24

  but it not.

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

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

[Touch-packages] [Bug 1583256] [NEW] Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist

2016-05-18 Thread brian mullan

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

Public bug reported:

System is Ubuntu 16.04

According to Ubuntu Pulseaudio MAN page:

http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html

it says...

   The  PulseAudio  sound  server  interprets  a  configuration  script on
   startup, which is mainly used to define the set  of  modules  to  load.
   When PulseAudio runs in the per-usermodeand
   ~/.config/pulse/default.pa exists, that file is used.  When  PulseAudio
   runs   in   the   per-user   mode   and   that   file   doesn't  exist,
   /etc/pulse/default.pa  is  used. 

On my system I have put the following into - /etc/pulse/default.pa

load-module module-native-protocol-tcp auth-ip-
acl=127.0.0.1;10.204.151.0/24

The contents of my ~/.config/pulse/ directory contains NO default.pa
file only the cookie file:

$ ls ~/.config/pulse
cookie

After a reload I issue the command patcl list modules and the "module-
native-protocol-tcp" is NOT listed ?

$ pactl list modules
Module #0
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "8.0"

Module #1
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Always keeps at least one sink loaded 
even if it's a null one"
module.version = "8.0"

Module #3
Name: module-xrdp-sink
Argument: 
Usage counter: 0
Properties:
module.author = "Jay Sorg"
module.description = "xrdp sink"
module.version = "8.0"

Module #4
Name: module-xrdp-source
Argument: 
Usage counter: n/a
Properties:
module.author = "Laxmikant Rashinkar"
module.description = "xrdp source"
module.version = "8.0"

Module #5
Name: module-native-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "8.0"

Module #6
Name: module-cli-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Command line interface protocol (UNIX 
sockets)"
module.version = "8.0"

I am filing this bug because according to the MAN page (see above)...
since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio
should be executing the /etc/pulse/default.pa configuration instead...
which should be loading:

load-module module-native-protocol-tcp auth-ip-
acl=127.0.0.1;10.204.151.0/24

but it not.

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


** Tags: pulseaudio

** Tags added: pulseaudio

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

Title:
  Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if
  ~/.config/pulse/default.pa does not exist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System is Ubuntu 16.04

  According to Ubuntu Pulseaudio MAN page:

  http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html

  it says...

 The  PulseAudio  sound  server  interprets  a  configuration  script on
 startup, which is mainly used to define the set  of  modules  to  load.
 When PulseAudio runs in the per-usermodeand
 ~/.config/pulse/default.pa exists, that file is used.  When  PulseAudio
 runs   in   the   per-user   mode   and   that   file   doesn't  exist,
 /etc/pulse/default.pa  is  used. 

  On my system I have put the following into - /etc/pulse/default.pa

  load-module module-native-protocol-tcp auth-ip-
  acl=127.0.0.1;10.204.151.0/24

  The contents of my ~/.config/pulse/ directory contains NO default.pa
  file only the cookie file:

  $ ls ~/.config/pulse
  cookie

  After a reload I issue the command patcl list modules and the "module-
  native-protocol-tcp" is NOT listed ?

  $ pactl list modules
  Module #0
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "8.0"

  Module #1

[Touch-packages] [Bug 1583255] [NEW] Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist

2016-05-18 Thread brian mullan

Public bug reported:

System is Ubuntu 16.04

According to Ubuntu Pulseaudio MAN page:

http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html

it says...

   The  PulseAudio  sound  server  interprets  a  configuration  script on
   startup, which is mainly used to define the set  of  modules  to  load.
   When PulseAudio runs in the per-usermodeand
   ~/.config/pulse/default.pa exists, that file is used.  When  PulseAudio
   runs   in   the   per-user   mode   and   that   file   doesn't  exist,
   /etc/pulse/default.pa  is  used. 

On my system I have put the following into - /etc/pulse/default.pa

load-module module-native-protocol-tcp auth-ip-
acl=127.0.0.1;10.204.151.0/24

The contents of my ~/.config/pulse/ directory contains NO default.pa
file only the cookie file:

$ ls ~/.config/pulse
cookie

After a reload I issue the command patcl list modules and the "module-
native-protocol-tcp" is NOT listed ?

$ pactl list modules
Module #0
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "8.0"

Module #1
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Always keeps at least one sink loaded 
even if it's a null one"
module.version = "8.0"

Module #3
Name: module-xrdp-sink
Argument: 
Usage counter: 0
Properties:
module.author = "Jay Sorg"
module.description = "xrdp sink"
module.version = "8.0"

Module #4
Name: module-xrdp-source
Argument: 
Usage counter: n/a
Properties:
module.author = "Laxmikant Rashinkar"
module.description = "xrdp source"
module.version = "8.0"

Module #5
Name: module-native-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "8.0"

Module #6
Name: module-cli-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Command line interface protocol (UNIX 
sockets)"
module.version = "8.0"

I am filing this bug because according to the MAN page (see above)...
since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio
should be executing the /etc/pulse/default.pa configuration instead...
which should be loading:

load-module module-native-protocol-tcp auth-ip-
acl=127.0.0.1;10.204.151.0/24

but it not.

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

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

Title:
  Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if
  ~/.config/pulse/default.pa does not exist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System is Ubuntu 16.04

  According to Ubuntu Pulseaudio MAN page:

  http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html

  it says...

 The  PulseAudio  sound  server  interprets  a  configuration  script on
 startup, which is mainly used to define the set  of  modules  to  load.
 When PulseAudio runs in the per-usermodeand
 ~/.config/pulse/default.pa exists, that file is used.  When  PulseAudio
 runs   in   the   per-user   mode   and   that   file   doesn't  exist,
 /etc/pulse/default.pa  is  used. 

  On my system I have put the following into - /etc/pulse/default.pa

  load-module module-native-protocol-tcp auth-ip-
  acl=127.0.0.1;10.204.151.0/24

  The contents of my ~/.config/pulse/ directory contains NO default.pa
  file only the cookie file:

  $ ls ~/.config/pulse
  cookie

  After a reload I issue the command patcl list modules and the "module-
  native-protocol-tcp" is NOT listed ?

  $ pactl list modules
  Module #0
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "8.0"

  Module #1
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin

[Touch-packages] [Bug 1583232] Re: Wowza Streaming Engine out of memory on Ubuntu 16.04

2016-05-18 Thread Brad Haakenson

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

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

Title:
  Wowza Streaming Engine out of memory on Ubuntu 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  Wowza Streaming Engine using systemd runs out of memory within a few
  minutes on Ubuntu 16.04. Specific Java error is: Failed to get the
  session[java.lang.OutOfMemoryError: unable to create new native thread

  This appears to be related to systemd, and specific to 16.04, since
  the software functions properly in previous versions of Ubuntu
  (verified with 15.04 and 15.10) and also works in 16.04 when the
  system is reverted to upstart init.

  I have also verified that a working 15.10 installation (systemd) fails
  after upgrading to 16.04.

  Currently, we are recommending that users don't upgrade to 16.04.

  Thanks you for your assistance and I can provide additional
  information as needed.

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

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

[Touch-packages] [Bug 1583232] [NEW] Wowza Streaming Engine out of memory on Ubuntu 16.04