date:20161116

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2209

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

Title:
  Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-
  size array

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Mir FTBFS on zesty:

  In file included from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:27:0:
  
/home/dan/bzr/mir/trunk/tests/include/mir/test/doubles/mock_android_native_buffer.h:65:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::MockAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from /usr/include/android-23/hardware/gralloc.h:21,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/buffer.h:27,
   from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:20:
  /usr/include/android-23/cutils/native_handle.h:29:15: note: array member ‘int 
native_handle::data [0]’ declared here
   int data[0];/* numFds + numInts ints */
 ^

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

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

[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2209

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

Title:
  Clients cannot connect when MIR_SOCKET=""

Status in Mir:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Launch a Unity 8 desktop session, log out, then log into a Unity 7
  session. Launch a Mir-on-X shell like MirAL and then try to launch a
  Mir client like mir_demo_client_egltriangle. The client will refuse to
  connect.

  Unity 8's upstart script always sets MIR_SOCKET to its old value when
  the session ends. If MIR_SOCKET wasn't set, then the post-stop script
  will still set MIR_SOCKET, setting it to "". Mir should interpret this
  as if MIR_SOCKET were unset.

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

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

[Touch-packages] [Bug 1626866] Re: [regression] 'make abi-check' fails to build

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2209

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

Title:
  [regression] 'make abi-check' fails to build

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  make abi-check fails to build:

  The GCC parameters:
/usr/bin/c++ -fdump-translation-unit -fkeep-inline-functions -c -x 
c++-header -fpermissive -w  -pthread -g -std=c++14 -Werror -Wall 
-fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC 
"/tmp/rTU25VRtKM/dump1.h"  -I/home/dan/bzr/mir/unbreak/include/common 
-I/home/dan/bzr/mir/unbreak/include/cookie -I/usr/include 
-I/home/dan/bzr/mir/unbreak/src/include/common 
-I/home/dan/bzr/mir/unbreak/build/src/protobuf 
-I/home/dan/bzr/mir/unbreak/include/platform 
-I/home/dan/bzr/mir/unbreak/src/include/platform

  In file included from /tmp/rTU25VRtKM/dump1.h:22:0:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: redefinition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~
  In file included from 
/home/dan/bzr/mir/unbreak/include/platform/mir/graphics/display_configuration.h:26:0,
   from /tmp/rTU25VRtKM/dump1.h:4:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: previous definition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

What we see from your debug output is that gpgv is not returning any
sensible information:

Summary:
  Good: 
  Bad: 
  Worthless: 
  SoonWorthless: 
  NoPubKey: 


You could try running apt-key verify manually on a few InRelease files (like 
apt-key verify 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial_InRelease) and see if 
that gives us any clue - or at least look at the files (especially in 
partial/), maybe they are garbage.

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  New

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu

[Touch-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out

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

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

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

First thanks for the files. Unfortunately, I can't reproduce it with the
files either. It must be a fairly system-specific bug.

> HEAD is now at 235347e... Release 1.2.12
> $ make fast
> [... with errors]

Whoa, if it happens with the 1.2.12 checkout too, then something else
seems wrong. I picked that as the "good" commit, as it apparently worked
in your first log file. But with 1.2.12 failing in the checkout as well,
that seems really weird.  You could try older 1.2 versions if you want,
specifying bad as 1.2.12, and good as 1.2.10, for example (1.2.10 is
basically the version xenial shipped with).

So this does not really look like a regression because it apparently
happens with the previously installed version as well now (at least when
built via git).

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  New

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

All known issues in comment 8 addressed, so I think that's all we need
for lxd porting.

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

  [Steps to reproduce current setup]

  0. rebuild avila kernel with additional patches from
  https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
  , or just use the prebuilt one in the attachments.

  1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
  mode and disable current lxc-based android container.

  2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
  then reboot the device so that writable path may take effect.

  3. initialize lxd. This can take a while (2 minutes for me).

    $ sudo lxd init --auto

  4. run lxd image create script to create the android lxd image.

$ ./lxd-image-create.sh

  5. create an ephemeral container for debug:

    $ lxc init -e -p android android armhf
    $ lxc start armhf

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

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

[Touch-packages] [Bug 1638204] Re: install snapd in default ubuntu xenial image

Confirmed installed in ubuntu-touch version 1.264xenial19, or system-
image rev 84. Thanks!

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

Title:
  install snapd in default ubuntu xenial image

Status in Canonical System Image:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released

Bug description:
  currently m10 have arm64 branch. we want to run snapd on it !

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

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

[Touch-packages] [Bug 1554621] Re: Invalid use of palette apparent with new SDK

2016-11-16 Thread Nekhelesh Ramananthan

** Changed in: ubuntu-clock-app
   Status: Fix Committed => Fix Released

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

Title:
  Invalid use of palette apparent with new SDK

Status in address-book-app:
  Fix Released
Status in Canonical System Image:
  Fix Released
Status in Ubuntu Music App:
  Fix Released
Status in Tagger:
  Fix Released
Status in Telegram app:
  Fix Released
Status in Ubuntu Clock App:
  Fix Released
Status in Ubuntu File Manager App:
  Fix Committed
Status in camera-app package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Invalid
Status in messaging-app package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  The content hub uses the wrong palette values for text (which becomes
  apparent with new UITK), see screenshot.

  The new UITK is landing here: https://requests.ci-
  train.ubuntu.com/#/ticket/905

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: content-hub 0.1+15.04.20160129.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Mar  8 18:00:22 2016
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304)
  SourcePackage: content-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

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

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

  [Steps to reproduce current setup]

  0. rebuild avila kernel with additional patches from
  https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
  , or just use the prebuilt one in the attachments.

  1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
  mode and disable current lxc-based android container.

  2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
  then reboot the device so that writable path may take effect.

  3. initialize lxd. This can take a while (2 minutes for me).

    $ sudo lxd init --auto

  4. run lxd image create script to create the android lxd image.

$ ./lxd-image-create.sh

  5. create an ephemeral container for debug:

    $ lxc init -e -p android android armhf
    $ lxc start armhf

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

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

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

Update prebuilt boot.img with current kernel changes in
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849

** Attachment added: "boot.img"

https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4778450/+files/boot.img

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

Title:
migrate lxc android container to lxd

Status in Canonical System Image:
Confirmed
Status in lxc-android-config package in Ubuntu:
New

Bug description:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
* migrate systemd service definitions, etc.

[Steps to reproduce current setup]

0. rebuild avila kernel with additional patches from
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
, or just use the prebuilt one in the attachments.

1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
mode and disable current lxc-based android container.

2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
then reboot the device so that writable path may take effect.

3. initialize lxd. This can take a while (2 minutes for me).

$ sudo lxd init --auto

4. run lxd image create script to create the android lxd image.

$ ./lxd-image-create.sh

5. create an ephemeral container for debug:

$ lxc init -e -p android android armhf
$ lxc start armhf

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

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

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

audit namespace issue fixed in upstream
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9441639e6319f0c0e12bd63fa2f58990af0a9d2
and
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=33faba7fa7f2288d2f8aaea95958b2c97bf9ebfb
. Already included in my kernel merge proposal.

** Attachment removed: "boot.img"

https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777591/+files/boot.img

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

Title:
migrate lxc android container to lxd

Status in Canonical System Image:
Confirmed
Status in lxc-android-config package in Ubuntu:
New

[Steps to reproduce current setup]

0. rebuild avila kernel with additional patches from
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
, or just use the prebuilt one in the attachments.

1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
mode and disable current lxc-based android container.

2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
then reboot the device so that writable path may take effect.

3. initialize lxd. This can take a while (2 minutes for me).

$ sudo lxd init --auto

4. run lxd image create script to create the android lxd image.

$ ./lxd-image-create.sh

5. create an ephemeral container for debug:

$ lxc init -e -p android android armhf
$ lxc start armhf

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

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

[Touch-packages] [Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2

2016-11-16 Thread Yu Ning

Hi Martin,

I have backported the patch to 14.04 and verified by my own, could you
help to review it and push the SRU process? Here is my patch:

http://bazaar.launchpad.net/~yuningdodo/systemd/systemd.trusty.lp1562344/revision/2

Thanks

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

Title:
  Not working hotkeys for brightness in HP ProBook 640 G2

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Description
  =

  It seems like a new HP laptops are using new vendor string which brokes
  hotkeys.

  
  Workaround
  ==

  Just to put following lines to fix hotkeys for brithness.

  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
   KEYBOARD_KEY_92=brightnessdown
   KEYBOARD_KEY_97=brightnessup

  
  Proposed solution
  ===

  The issue was already solved by upstream systemd[1] developers 25 days
  ago, so resync of hwdb/60-keyboard.hwdb should be enough.

[1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 26 17:20:25 2016
  InstallationDate: Installed on 2016-02-25 (30 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 640 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic 
root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro 
cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30
 quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N76 Ver. 01.00
  dmi.board.name: 80FD
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 22.36
  dmi.chassis.asset.tag: 5CG605253R
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 640 G2
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd

** Branch linked: lp:~vicamo/lxc-android-config/lxd-migration

** Branch unlinked: lp:~vicamo/lxc-android-config/lxd-writable-path

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

  [Steps to reproduce current setup]

  0. rebuild avila kernel with additional patches from
  https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
  , or just use the prebuilt one in the attachments.

  1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
  mode and disable current lxc-based android container.

  2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
  then reboot the device so that writable path may take effect.

  3. initialize lxd. This can take a while (2 minutes for me).

    $ sudo lxd init --auto

  4. run lxd image create script to create the android lxd image.

$ ./lxd-image-create.sh

  5. create an ephemeral container for debug:

    $ lxc init -e -p android android armhf
    $ lxc start armhf

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

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

[Touch-packages] [Bug 1642465] [NEW] package lib32z1-dev (not installed) failed to install/upgrade: попытка перезаписать «/usr/include/i386-linux-gnu/zconf.h», который уже имеется в пакете zlib1g-dev:

2016-11-16 Thread Karen

Public bug reported:

Ставил для компиляции андроида.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: lib32z1-dev (not installed)
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov 16 18:52:05 2016
ErrorMessage: попытка перезаписать «/usr/include/i386-linux-gnu/zconf.h», 
который уже имеется в пакете zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5
InstallationDate: Installed on 2016-11-13 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: zlib
Title: package lib32z1-dev (not installed) failed to install/upgrade: попытка 
перезаписать «/usr/include/i386-linux-gnu/zconf.h», который уже имеется в 
пакете zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package lib32z1-dev (not installed) failed to install/upgrade: попытка
  перезаписать «/usr/include/i386-linux-gnu/zconf.h», который уже
  имеется в пакете zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5

Status in zlib package in Ubuntu:
  New

Bug description:
  Ставил для компиляции андроида.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: lib32z1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov 16 18:52:05 2016
  ErrorMessage: попытка перезаписать «/usr/include/i386-linux-gnu/zconf.h», 
который уже имеется в пакете zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5
  InstallationDate: Installed on 2016-11-13 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: zlib
  Title: package lib32z1-dev (not installed) failed to install/upgrade: попытка 
перезаписать «/usr/include/i386-linux-gnu/zconf.h», который уже имеется в 
пакете zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1610772] Re: [drm] stuck on render ring

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

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

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

Title:
  [drm] stuck on render ring

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The problem is similiar to the one discrabed in #1547800

  It was happen once in a while. Now it always happens when returning
  from sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sda6: clean, 278496/3727360 files, 2012554/14884352 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Aug  7 22:04:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:179b]
  InstallationDate: Installed on 2016-06-26 (42 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=1126bf38-027a-410d-a905-5dbbd05a6b4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.45
  dmi.board.name: 179B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.45:bd10/07/2013:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:rvnHewlett-Packard:rn179B:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8470p
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul 25 07:40:00 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5236 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1642447] [NEW] package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versã

2016-11-16 Thread Weiller

Public bug reported:

Description:Ubuntu Zesty Zapus (development branch)
Release:17.04

libgraphite2-3:
  Instalado: 1.3.9-1
  Candidato: 1.3.9-1
  Tabela de versão:
 *** 1.3.9-1 500
500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 Packages
500 http://mirror.ufscar.br/ubuntu zesty-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.3.8-1ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://cz.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty/main amd64 Packages
500 http://mirror.ufscar.br/ubuntu zesty/main amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgraphite2-3:amd64 1.3.9-1
ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
Uname: Linux 4.9.0-1-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Thu Nov 17 00:03:37 2016
Dependencies:
 gcc-6-base 6.2.0-13ubuntu1
 libc6 2.24-3ubuntu1
 libgcc1 1:6.2.0-13ubuntu1
ErrorMessage: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois 
libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1)
InstallationDate: Installed on 2016-02-11 (279 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: graphite2
Title: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote 
libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 
tem uma versão diferente (1.3.8-1ubuntu1)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed zesty

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

Title:
  package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote
  libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois
  libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1)

Status in graphite2 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  libgraphite2-3:
Instalado: 1.3.9-1
Candidato: 1.3.9-1
Tabela de versão:
   *** 1.3.9-1 500
  500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 
Packages
  500 http://mirror.ufscar.br/ubuntu zesty-proposed/main amd64 Packages
  100 /var/lib/dpkg/status
   1.3.8-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://cz.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty/main amd64 Packages
  500 http://mirror.ufscar.br/ubuntu zesty/main amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgraphite2-3:amd64 1.3.9-1
  ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
  Uname: Linux 4.9.0-1-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Nov 17 00:03:37 2016
  Dependencies:
   gcc-6-base 6.2.0-13ubuntu1
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-13ubuntu1
  ErrorMessage: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado 
pois libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1)
  InstallationDate: Installed on 2016-02-11 (279 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote 
libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 
tem uma versão diferente (1.3.8-1ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1642259] Re: ubuntu-terminal-app settings screen stretches too much with large window sizes

2016-11-16 Thread Daniel van Vugt

** Summary changed:

- [Design Suggestion] App Settings on desktop
+ ubuntu-terminal-app settings screen stretches too much with large window sizes

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

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

** Tags removed: app mir
** Tags added: unity8-desktop

** Changed in: ubuntu-terminal-app
   Status: New => Confirmed

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

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

** Changed in: canonical-devices-system-image
   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/1642259

Title:
  ubuntu-terminal-app settings screen stretches too much with large
  window sizes

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Confirmed
Status in Ubuntu UX:
  New
Status in ubuntu-terminal-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I think that Unity 8 app settings in look weird on desktop, especially
  when the window is larger.

  My suggestion is that at a certain size the menu stays where it is
  instead of stretching across the screen, so that it would look like in
  the attached image (made an example of the Terminal app).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

2016-11-16 Thread Daniel van Vugt

Please also attach these logs (the second one requires sudo to access):
   ~/.cache/upstart/unity8.log*
   /var/log/lightdm/unity-system-compositor.log

We need them to check that Mir is getting sane physical dimensions for
your screen and not reporting crazy information like "this is a 4-inch
tablet".

** Tags added: unity8-desktop

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

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

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

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

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

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

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

** Changed in: mir
   Importance: Undecided => High

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

Title:
  incorrect UI scale on high-resolution desktop

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

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2016-11-16 Thread Joe Giampaoli

I can confirm same results:

HP G240
Xubuntu 16.04 64bit

Uncommented and changed HandleLidSwitchDocked=ignore to
HandleLidSwitchDocked=suspend in /etc/systemd/logind.conf worked

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  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: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-11-16 Thread Dan Streetman

to clarify, tcpdump with klibc-utils 2.0.3-0ubuntu1.14.04.1 shows the
flag is 0x0800 (incorrect) while tcpdump with klibc-utils
2.0.3-0ubuntu1.14.04.2 (from -proposed) shows the flag is 0x8000
(correct).

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

Title:
  Wrong bit set in klibc PXE dhcp/bootp flags

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Committed
Status in klibc source package in Xenial:
  Fix Released
Status in klibc source package in Yakkety:
  Fix Released

Bug description:
  [Description]

  The patch for bug 1327412 set the wrong bit in the bootp flags field.
  It set flags to 0x800, but the correct value is 0x8000.  That sets the
  "broadcast" bit, and the spec requires all other bits to be 0.

  Setting one of the "must be zero" bits in the flags field causes some
  DHCP relay agents to drop the packets, causing PXE to fail.

  [Test Case]

  Get a DHCP relay agent that drops PXE packets with an invalid
  bootp.flags bit set, and try to PXE boot; it fails.

  [Regression]

  None, the previous patch introduced this regression.

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

I'm skeptical of the git bisect results:

$ git checkout cde5b485c9cdf0bfd5b6ea8e4973abe378270e60^
Previous HEAD position was cde5b48... fail instead of segfault on unreadable 
config files
HEAD is now at 235347e... Release 1.2.12
$ make fast
Compiling cachefile.cc to ../build/obj/apt-pkg/cachefile.opic
Compiling policy.cc to ../build/obj/apt-pkg/policy.opic
Building shared library ../build/bin/libapt-pkg.so.5.0.0
Compiling contrib/arfile.cc to ../build/obj/apt-inst/arfile.opic
Compiling contrib/extracttar.cc to ../build/obj/apt-inst/extracttar.opic
Compiling deb/debfile.cc to ../build/obj/apt-inst/debfile.opic
Compiling dirstream.cc to ../build/obj/apt-inst/dirstream.opic
Compiling extract.cc to ../build/obj/apt-inst/extract.opic
Compiling filelist.cc to ../build/obj/apt-inst/filelist.opic
Building shared library ../build/bin/libapt-inst.so.2.0.0
Compiling private-cacheset.cc to ../build/obj/apt-private/private-cacheset.opic
Compiling private-list.cc to ../build/obj/apt-private/private-list.opic
Compiling private-depends.cc to ../build/obj/apt-private/private-depends.opic
Compiling private-show.cc to ../build/obj/apt-private/private-show.opic
Building shared library ../build/bin/libapt-private.so.0.0.0
Compiling apt-mark.cc to ../build/obj/cmdline/apt-mark.o
Building program ../build/bin/apt-mark
Must have libdb to build apt-ftparchive
$ sudo rm -rf /var/lib/apt/lists
sarnold@hunt:~/trees/apt$ sudo LD_LIBRARY_PATH=$PWD/build/bin/ 
./build/bin/apt-get update -o Dir::Bin::Methods="$PWD/build/bin/methods/" 2>&1 
| tee update.log
Get:1 http://mirrors.kernel.org/ubuntu xenial InRelease [247 kB]
Get:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease [95.7 kB]
Get:3 http://security.debian.org jessie/updates InRelease [63.1 kB]
Get:4 http://mirrors.kernel.org/ubuntu xenial-security InRelease [94.5 kB]
Ign:5 http://mirrors.kernel.org/ubuntu precise InRelease
Get:6 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]
Get:7 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]
Get:8 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]
Ign:9 http://mirrors.kernel.org/ubuntu trusty InRelease
Get:10 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB]
Get:11 http://mirrors.kernel.org/ubuntu trusty-security InRelease [65.9 kB]
Get:12 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]
Get:13 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]
Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]
Get:15 http://security.debian.org wheezy/updates InRelease [40.6 kB]
Get:16 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease [94.5 kB]
Get:17 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]
Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]
Get:19 http://mirrors.kernel.org/ubuntu zesty InRelease [247 kB]
Ign:1 http://mirrors.kernel.org/ubuntu xenial InRelease
Get:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease [92.1 kB]
Get:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease [92.2 kB]
Get:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease [95.6 kB]
Get:23 http://mirrors.kernel.org/ubuntu precise Release [49.6 kB]
Get:24 http://mirrors.kernel.org/ubuntu trusty Release [58.5 kB]
Get:25 http://mirrors.kernel.org/ubuntu xenial/main Sources [868 kB]
Get:26 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Get:27 http://mirrors.kernel.org/ubuntu xenial/restricted Sources [4,808 B]
Get:28 http://mirrors.kernel.org/ubuntu xenial/universe Sources [7,728 kB]
Ign:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease
Ign:4 http://mirrors.kernel.org/ubuntu xenial-security InRelease
Ign:29 http://archive.canonical.com/ubuntu precise InRelease
Get:30 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease [20.9 kB]
Get:31 http://ftp.debian.org/debian unstable InRelease [219 kB]
Get:32 http://mirrors.kernel.org/ubuntu xenial/multiverse Sources [179 kB]
Get:33 http://mirrors.kernel.org/ubuntu xenial/main amd64 Packages [1,201 kB]
Ign:6 http://mirrors.kernel.org/ubuntu precise-updates InRelease
Get:34 http://mirrors.kernel.org/ubuntu xenial/main i386 Packages [1,196 kB]
Get:35 http://mirrors.kernel.org/ubuntu xenial/main Translation-en [568 kB]
Get:36 http://mirrors.kernel.org/ubuntu xenial/restricted amd64 Packages [8,344 
B]
Get:37 http://mirrors.kernel.org/ubuntu xenial/restricted i386 Packages [8,684 
B]
Get:38 http://mirrors.kernel.org/ubuntu xenial/restricted Translation-en [2,908 
B]
Get:39 http://mirrors.kernel.org/ubuntu xenial/universe amd64 Packages [7,532 
kB]
Ign:7 http://mirrors.kernel.org/ubuntu precise-security InRelease
Ign:40 http://archive.canonical.com/ubuntu trusty InRelease
Ign:8 http://mirrors.kernel.org/ubuntu precise-proposed InRelease
Get:41 http://mirrors.kernel.org/ubuntu xenial/universe i386 Packages [7,512 kB]
Ign:10 http://mirrors.kernel.org/ubuntu

[Touch-packages] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags

2016-11-16 Thread Dan Streetman

I confirmed the fix is correct in trusty by tcpdumping a run of
/usr/lib/klibc/bin/ipconfig

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

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

Title:
  Wrong bit set in klibc PXE dhcp/bootp flags

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Committed
Status in klibc source package in Xenial:
  Fix Released
Status in klibc source package in Yakkety:
  Fix Released

Bug description:
  [Description]

  The patch for bug 1327412 set the wrong bit in the bootp flags field.
  It set flags to 0x800, but the correct value is 0x8000.  That sets the
  "broadcast" bit, and the spec requires all other bits to be 0.

  Setting one of the "must be zero" bits in the flags field causes some
  DHCP relay agents to drop the packets, causing PXE to fail.

  [Test Case]

  Get a DHCP relay agent that drops PXE packets with an invalid
  bootp.flags bit set, and try to PXE boot; it fails.

  [Regression]

  None, the previous patch introduced this regression.

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

And the results of git bisect, thanks for the excellent instruction and
script!

cde5b485c9cdf0bfd5b6ea8e4973abe378270e60 is the first bad commit
commit cde5b485c9cdf0bfd5b6ea8e4973abe378270e60
Author: David Kalnischkies 
Date:   Fri May 20 09:37:24 2016 +0200

fail instead of segfault on unreadable config files

The report mentions "apt list --upgradable", but there are others which
have inconsistent behavior ranging from segfaulting to doing something
with the partial (and hence incomplete) data. We had a recent report
about sources.list (#818628), this one mentions prefences, the obvious
next step is conf files… so the testcase is adapted to check for all
three in file and directory versions and run a bunch of commands each
time which should all have more or less the same behavior in such a case
(aka error out).

Closes: 824503
(cherry picked from commit fdf9eef4d96a18d0167708499c993e1174251e88)

:04 04 04f4856e0a9313f9f51a5a6dc56c9af005ac54f4 
98d34296e4f9212a124515095f6ed9afd5739111 M  apt-pkg
:04 04 d48745d59ec9dd40087de492197c7a1060d1451d 
a5038f3b3730d8ba9e070f68a60af11fbe0e7ac3 M  apt-private
:04 04 cfb7d9b7f8130e98173cf09a56eea0c232cc75fa 
c2f0ed862e98021705643c42a1b549306b648c15 M  cmdline
:04 04 24d65ae746427999b728b85acb6969f509885cb1 
82f28b27a48c3a6cf5b9caaf6434512a4a5dd79f M  test
bisect run success

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

sarnold@hunt:/var/lib/apt$ sudo mv lists lists.old
sarnold@hunt:/var/lib/apt$ sudo apt-get update
Get:1 http://mirrors.kernel.org/ubuntu xenial InRelease [247 kB]
Get:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease [95.7 kB]   
  
Get:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease [94.5 kB]  
  
Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease
  
Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]  
  
Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB] 
  
Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB] 
  
Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease 
  
Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB]   
  
Get:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease [65.9 kB] 
  
Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB] 
  
Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]  
  
Get:13 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]  
  
Get:14 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease [94.5 kB] 
  
Get:15 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]
  
Get:16 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]
  
Get:17 http://mirrors.kernel.org/ubuntu zesty InRelease [247 kB]
  
Ign:1 http://mirrors.kernel.org/ubuntu xenial InRelease 
  
Get:18 http://security.debian.org jessie/updates InRelease [63.1 kB]
  
Get:19 http://mirrors.kernel.org/ubuntu zesty-updates InRelease [92.1 kB]   
  
Get:20 http://mirrors.kernel.org/ubuntu zesty-security InRelease [92.2 kB]  
  
Get:21 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease [95.6 kB]  
  
Get:22 http://mirrors.kernel.org/ubuntu precise Release [49.6 kB]   
  
Get:23 http://mirrors.kernel.org/ubuntu trusty Release [58.5 kB]
  
Get:24 http://mirrors.kernel.org/ubuntu xenial/main Sources [868 kB]
  
Ign:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease 
  
Get:25 http://mirrors.kernel.org/ubuntu xenial/restricted Sources [4,808 B] 
  
Get:26 http://mirrors.kernel.org/ubuntu xenial/universe Sources [7,728 kB]  
  
Ign:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
  
Get:27 http://security.debian.org wheezy/updates InRelease [40.6 kB]
  
Get:28 http://ftp.debian.org/debian unstable InRelease [219 kB] 
  
Get:29 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
  
Ign:30 http://archive.canonical.com/ubuntu precise InRelease
  
Get:31 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease [20.9 kB]
Ign:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease
  
Ign:6 http://mirrors.kernel.org/ubuntu precise-security InRelease   
  
Ign:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease   
  
Ign:32 http://archive.canonical.com/ubuntu trusty InRelease 
  
Ign:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease 
  
Ign:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease   
  
Get:33 http://mirrors.kernel.org/ubuntu xenial/multiverse Sources [179 kB]  
  
Get:34 http://mirrors.kernel.org/ubuntu xenial/main amd64 Packages [1,201 kB]   
  
Get:35 http://archive.canonical.com/ubuntu xenial InRelease [11.5 kB]

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

393c61b8e29bd1923a5fe8abf4690c24e7f498aa8a4f5954a6a87da7d05a0bef  apt-
etc-and-var.tar.xz

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was encountered.
  Err:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease   
 
At least one

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

Tarball of /etc/apt and /var/lib/apt

** Attachment added: "Tarball of /etc/apt and /var/lib/apt"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1642386/+attachment/4778362/+files/apt-etc-and-var.tar.xz

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was

[Touch-packages] [Bug 1590461] Re: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: shared-mime-info (Ubuntu)
   Status: New => Confirmed

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

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  when upgrade ,it hapenned!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-60.67~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-60-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Wed Jun  8 22:12:54 2016
  DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-27 (285 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-06-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1590461/+subscriptions

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

apt-get update -o Debug::Acquire::gpgv=1

** Attachment added: "apt-get update -o Debug::Acquire::gpgv=1"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1642386/+attachment/4778350/+files/debug-gpgv

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was encountered.

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

Oh, you may also want to try moving lists/ out of the way and running
apt update again.

And perhaps send me a tarball of /var/lib/apt and /etc/apt - then I
might have luck reproducing it.

If you want to, you could try bisecting this in the apt git repo,
starting with

git bisect start
git bisect good 1.2.12
git bisect bad 1.2.15
git bisect run sh ./script.sh

where script.sh is:

#!/bin/sh
make fast || exit 125
sudo LD_LIBRARY_PATH=$PWD/build/bin/ ./build/bin/apt-get update -o 
Dir::Bin::Methods="$PWD/build/bin/methods/" 2>&1 | tee update.log

if grep "was encountered" update.log; then
  exit 1
fi

exit 0

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27

[Touch-packages] [Bug 1639920] Re: NVMe detection failed during bootup

2016-11-16 Thread dexterb

** Information type changed from Private to Public

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

Title:
  NVMe detection failed during bootup

Status in apport package in Ubuntu:
  New

Bug description:
  I've been running an on-off test on a couple of Power8 systems and
  have been getting a failure of detection on the NVMe drives on Ubuntu
  16.04.1 only.  I've ran the same test on RHEL 7.2 and have not
  encountered this proble. Once the problem occurs the OS will stop to
  boot up and a message appears:

  Welcome to emergency mode! After logging in, type "journalctl -xb" to view 
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try 
again to boot into default mode.
  Give root password for maintenance (or press Control-D to continue):

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  CrashReports:
   640:0:116:12295:2016-11-07 11:11:27.995107650 -0800:2016-11-07 
11:31:31.733627559 -0800:/var/crash/_usr_bin_apport-bug.0.crash
   644:0:116:0:2016-11-07 11:11:28.931104586 -0800:2016-11-07 
11:11:28.931104586 -0800:/var/crash/_usr_bin_apport-cli.0.None.hanging
  Date: Mon Nov  7 11:11:28 2016
  ExecutablePath: /usr/bin/apport-bug
  InstallationDate: Installed on 2016-11-05 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.30 0.41 0.19 1/1132 2428
  ProcLocks:
   
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition157914048   0   
-1
  ProcVersion: Linux version 4.4.0-45-generic (buildd@bos01-ppc64el-030) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.2) ) #66-Ubuntu SMP Wed 
Oct 19 14:13:11 UTC 2016
  PythonArgs: ['/usr/bin/ubuntu-bug', '--hanging']
  SourcePackage: apport
  Title: apport-bug crashed with TypeError in run_hang(): int() argument must 
be a string, a bytes-like object or a number, not 'NoneType'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8
  mtime.conffile..etc.apport.crashdb.conf: 2016-11-07T10:38:18.528739

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

Your coworker seems to have caught a crash in appstream, BTW, not in
apt. Not sure why the files fail their hashes or have no sections in
them, though.

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

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

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was encountered.
  Err:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease   
 
At least one invalid signature was

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

It works perfectly fine for me. Can you re-run this with:

 -o Debug::Acquire::gpgv=1


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

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was encountered.
  Err:9 http://mirrors.kernel.org/ubuntu trusty-updates

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

This bug was fixed in the package policykit-unity8 -
0.1+17.04.20161116-0ubuntu1

---
policykit-unity8 (0.1+17.04.20161116-0ubuntu1) zesty; urgency=medium

  * Let policykit-unity8 work inside of a unity8 snap. (LP: #1629009)

 -- Michael Terry   Wed, 16 Nov 2016
19:22:13 +

** Changed in: policykit-unity8 (Ubuntu)
   Status: New => Fix Released

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

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

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Confirmed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1642360] Re: Display occasionally stays on forever after boot in rc-proposed

2016-11-16 Thread Pat McGowan

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

** Branch linked: lp:~afrantzis/ubuntu-touch-session/fix-1642360

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

Title:
  Display occasionally stays on forever after boot in rc-proposed

Status in Canonical System Image:
  Confirmed
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Occasionally the display stays on forever after boot in rc-proposed,
  due to a keep display on request.

  The problem seems to be that the keep-display-on-request introduced to
  fix bug 1623853, sometimes doesn't get released due to races in the
  upstart scripts. This happens if the lightdm job starts before the
  keep-display-on-during-boot job starts, in which case the keep-
  display-on-during-boot job never gets the signal it needs to stop
  ("stop on started lightdm").

  This issue can be reproduced easily by changing the related upstart
  script timings, for example, by inserting a "sleep 10" at the end of
  the repowerd.conf pre-start stanza.

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

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

[Touch-packages] [Bug 1035755] Re: [firefox] Extension causes context/drop down menus to disappear

2016-11-16 Thread Mathew Hodson

** Package changed: libdbusmenu-qt (Gentoo Linux) => ubuntu

** No longer affects: ubuntu

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

Title:
  [firefox] Extension causes context/drop down menus to disappear

Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  For anyone looking into fixing this: see comment#4

  Symptom:
  With the Global Menu Integration enabled, sometimes drop down and context 
menus inside Firefox will stop working. They show up for a moment and 
immediately disappear. This includes context menus of tab buttons and web 
pages, and drop down menus opened from toolbar buttons. The problem lasts until 
Firefox is restarted.

  To reproduce:
  With Global Menu Integration enabled, toggle the Navigation toolbar (View - 
Toolbars - Navigation Toolbar).
  This is one way I've found that always reproduces the problem. Whether the 
toolbar was toggled on or off, it triggers the problem for me. It happens even 
when this is the only enabled extension, and does not happen when it is 
disabled.

  Sometimes the problem also seems to be triggered by opening a new tab
  but I haven't found a pattern in that.

  Environment:
  Firefox 14.0.1
  Global Menu Integration 3.2.6 package at 
https://aur.archlinux.org/packages.php?ID=55724
  KDE 4.9.00
  Arch Linux

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

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

[Touch-packages] [Bug 1035755] Re: [firefox] Extension causes context/drop down menus to disappear

2016-11-16 Thread Mathew Hodson

** Project changed: libdbusmenu-qt => ubuntu

** No longer affects: ubuntu

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

Title:
  [firefox] Extension causes context/drop down menus to disappear

Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  For anyone looking into fixing this: see comment#4

  Symptom:
  With the Global Menu Integration enabled, sometimes drop down and context 
menus inside Firefox will stop working. They show up for a moment and 
immediately disappear. This includes context menus of tab buttons and web 
pages, and drop down menus opened from toolbar buttons. The problem lasts until 
Firefox is restarted.

  To reproduce:
  With Global Menu Integration enabled, toggle the Navigation toolbar (View - 
Toolbars - Navigation Toolbar).
  This is one way I've found that always reproduces the problem. Whether the 
toolbar was toggled on or off, it triggers the problem for me. It happens even 
when this is the only enabled extension, and does not happen when it is 
disabled.

  Sometimes the problem also seems to be triggered by opening a new tab
  but I haven't found a pattern in that.

  Environment:
  Firefox 14.0.1
  Global Menu Integration 3.2.6 package at 
https://aur.archlinux.org/packages.php?ID=55724
  KDE 4.9.00
  Arch Linux

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

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

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

--- Comment From ru...@us.ibm.com 2016-11-16 16:02 EDT---
Tested with 4.8.0-27 from proposed.  With this kernel, the vlan filtering init 
appears to have been successful, so br->vlgrp was not NULL on shutdown.

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

[Touch-packages] [Bug 1035755] Re: [firefox] Extension causes context/drop down menus to disappear

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

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  [firefox] Extension causes context/drop down menus to disappear

Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  For anyone looking into fixing this: see comment#4

  Symptom:
  With the Global Menu Integration enabled, sometimes drop down and context 
menus inside Firefox will stop working. They show up for a moment and 
immediately disappear. This includes context menus of tab buttons and web 
pages, and drop down menus opened from toolbar buttons. The problem lasts until 
Firefox is restarted.

  To reproduce:
  With Global Menu Integration enabled, toggle the Navigation toolbar (View - 
Toolbars - Navigation Toolbar).
  This is one way I've found that always reproduces the problem. Whether the 
toolbar was toggled on or off, it triggers the problem for me. It happens even 
when this is the only enabled extension, and does not happen when it is 
disabled.

  Sometimes the problem also seems to be triggered by opening a new tab
  but I haven't found a pattern in that.

  Environment:
  Firefox 14.0.1
  Global Menu Integration 3.2.6 package at 
https://aur.archlinux.org/packages.php?ID=55724
  KDE 4.9.00
  Arch Linux

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

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

[Touch-packages] [Bug 1641915] Re: GtkToolButtons clip and overlap

2016-11-16 Thread Mathew Hodson

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GtkToolButtons clip and overlap

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  [ Impact ]

  GtkToolButton styling causes buttons to clip and overlap each other. This
  can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 
16.04.1. See the attached screenshot:

    * https://bugs.launchpad.net/ubuntu-
  themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton-
  clipping.png

  [ Test Case ]

  Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live
  Desktop click the Ubuntu logo in the launcher, search for Disks and
  start it. Select the hard disk from the side panel, then look at and
  hover over, the buttons beneath the representation of the disk
  partitions. You'll notice the buttons clip/overlap as illustrated in
  the screenshot above.

  Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop.
  The Installer will start, click Continue, click Continue, check
  "Something else" and then the click Continue. Look at, and hover over,
  the buttons beneath the tree representing the disk partitions. You'll
  notice they clip/overlap as illustrated in the screenshot above.

  After the patched ubuntu-themes has been installed the buttons
  described in the steps above will no longer clip/overlap.

  [ Regression Potential ]

  None expected.

  [ Other Info ]

  This issue does not present in Yakkety or Zesty.

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

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

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

I was too hasty -- apt appears to still function (e.g. apt-get install
expat, apt-get purge expat, installed an expat from the -updates pocket
and removed it again). It's just insanely ugly warnings on the apt-get
update step, and maybe(?) new lists can't be downloaded.

Anyway it's more nuanced than "broken entirely". Sorry.

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  New

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7

[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.

The full run, showing apt working a few seconds before it fails, and no
errors in dmesg.

** Attachment added: "terminal-log"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1642386/+attachment/4778315/+files/terminal-log

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

Title:
  At least one invalid signature was encountered.

Status in apt package in Ubuntu:
  New

Bug description:
  Hello, a recent apt update appears to have broken apt entirely.

  A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

  To test, I upgraded my laptop then immediately re-ran apt-get update
  && apt-get -u dist-upgrade:

  sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
  Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
  Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

  Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

  Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease  

  Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]

  Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB]   

  Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB]   

  Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease   

  Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] 

  Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 

  Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB]   

  Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]

  Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease   

At least one invalid signature was encountered.
  Hit:13 http://security.debian.org jessie/updates InRelease

  Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease   

At least one invalid signature was encountered.
  Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]

  Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease  

At least one invalid signature was encountered.
  Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease 

  Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]  

  Hit:17 http://security.debian.org wheezy/updates InRelease

  Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]  

  Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease   

  Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease   

  Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease  

  Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease  

At least one invalid signature was encountered.
  Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease  

  Hit:23 http://mirrors.kernel.org/ubuntu precise Release   

  Hit:24 http://mirrors.kernel.org/ubuntu trusty Release

  Ign:25 http://archive.canonical.com/ubuntu precise InRelease  

  Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease

  Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
  Hit:28 http://ftp.debian.org/debian unstable InRelease
 
  Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
At least one invalid signature was encountered.
  Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease 
 
At least one invalid signature was

[Touch-packages] [Bug 1642386] [NEW] At least one invalid signature was encountered.

Public bug reported:

Hello, a recent apt update appears to have broken apt entirely.

A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/

To test, I upgraded my laptop then immediately re-ran apt-get update &&
apt-get -u dist-upgrade:

sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade
Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease
Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease 
  
Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
  
Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease
  
Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB]  
  
Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB] 
  
Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB] 
  
Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease 
  
Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB]   
  
Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease   
  
Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB] 
  
Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB]  
  
Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease 
  
  At least one invalid signature was encountered.
Hit:13 http://security.debian.org jessie/updates InRelease  
  
Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease 
  
  At least one invalid signature was encountered.
Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB]  
  
Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
  
  At least one invalid signature was encountered.
Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease   
  
Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB]
  
Hit:17 http://security.debian.org wheezy/updates InRelease  
  
Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB]
  
Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease 
  
Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease 
  
Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease
  
Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease
  
  At least one invalid signature was encountered.
Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease
  
Hit:23 http://mirrors.kernel.org/ubuntu precise Release 
  
Hit:24 http://mirrors.kernel.org/ubuntu trusty Release  
  
Ign:25 http://archive.canonical.com/ubuntu precise InRelease
  
Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease  
  
Hit:27 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid 
InRelease
Hit:28 http://ftp.debian.org/debian unstable InRelease  
   
Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease
  At least one invalid signature was encountered.
Err:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease   
   
  At least one invalid signature was encountered.
Err:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease 
   
  At least one invalid signature was encountered.
Ign:29 http://archive.canonical.com/ubuntu trusty InRelease 

Hit:30 http://ppa.launchpad.net/snappy-dev/image/ubuntu vivid InRelease 

Hit:31 http://ftp.debian.org/debian testing InRelease 
Err:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease 
  At least one invalid signature was encountered.
Err:11

[Touch-packages] [Bug 1594380] Re: package libva-x11-1 (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/x86_64-linux-gnu/libva-x11.so.1.3900.0 » v

2016-11-16 Thread Sebastian Ramacher

Please provide a log in English.

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

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

Title:
  package libva-x11-1 (not installed) failed to install/upgrade:
  impossible de copier les données extraites pour « ./usr/lib/x86_64
  -linux-gnu/libva-x11.so.1.3900.0 » vers « /usr/lib/x86_64-linux-
  gnu/libva-x11.so.1.3900.0.dpkg-new » : fin de fichier ou de flux
  inattendue

Status in libva package in Ubuntu:
  Incomplete

Bug description:
  I can't install this module

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libva-x11-1 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jun 20 15:28:27 2016
  ErrorMessage: impossible de copier les données extraites pour « 
./usr/lib/x86_64-linux-gnu/libva-x11.so.1.3900.0 » vers « 
/usr/lib/x86_64-linux-gnu/libva-x11.so.1.3900.0.dpkg-new » : fin de fichier ou 
de flux inattendue
  InstallationDate: Installed on 2016-06-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libva
  Title: package libva-x11-1 (not installed) failed to install/upgrade: 
impossible de copier les données extraites pour « 
./usr/lib/x86_64-linux-gnu/libva-x11.so.1.3900.0 » vers « 
/usr/lib/x86_64-linux-gnu/libva-x11.so.1.3900.0.dpkg-new » : fin de fichier ou 
de flux inattendue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1637271] Re: Desktop background is black after resume from suspend

2016-11-16 Thread Cliff Carson

Running 16.10 Gnome and regularly suspend the laptop.  The background
picture turns into random rectangles on a black ground.  No other
problems noticed.  Restoring the same picture via right-click on the
desktop work until the next suspend.

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

Title:
  Desktop background is black after resume from suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running a standard 16.10 system with Unity 7, Intel i965 graphics, and
  a secondary external display.  This behaviour has been observed under
  16.04 and possibly earlier releases as well.

  Often (though frustratingly not always), when I resume from suspend,
  my desktop background will be solid black, my wallpaper is not
  visible.  This is *not* the background colour I have selected in the
  Appearance settings.  The system is fully usable when this occurs:
  cursor, icons, windows, etc. all render fine.  If I change any
  Appearance setting (zoom/tile type, colour, image), it seems to
  refresh and my wallpaper is restored.  Sometimes this only happens on
  my secondary display, and the wallpaper is still visible on my primary
  display.

  Please move this bug as appropriate, I wasn't quite sure what to
  report this against.  Compiz?  GNOME?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  Uname: Linux 4.8.0-2.1-liquorix-amd64 x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Thu Oct 27 12:08:50 2016
  DistUpgraded: 2016-10-18 18:39:21,612 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:fa72]
  InstallationDate: Installed on 2014-08-03 (815 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite P75-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2.1-liquorix-amd64 
root=UUID=9b00c4ca-5dfe-4d81-89db-3404d87c8820 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (8 days ago)
  dmi.bios.date: 04/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd04/18/2014:svnTOSHIBA:pnSatelliteP75-A:pvrPSPLNU-04702KB:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P75-A
  dmi.product.version: PSPLNU-04702KB
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 12:28:06 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8349 
   vendor AUO
  xserver.version: 2:1.18.4-1ubuntu6

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

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

[Touch-packages] [Bug 1637271] Re: Desktop background is black after resume from suspend

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

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

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

Title:
  Desktop background is black after resume from suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running a standard 16.10 system with Unity 7, Intel i965 graphics, and
  a secondary external display.  This behaviour has been observed under
  16.04 and possibly earlier releases as well.

  Often (though frustratingly not always), when I resume from suspend,
  my desktop background will be solid black, my wallpaper is not
  visible.  This is *not* the background colour I have selected in the
  Appearance settings.  The system is fully usable when this occurs:
  cursor, icons, windows, etc. all render fine.  If I change any
  Appearance setting (zoom/tile type, colour, image), it seems to
  refresh and my wallpaper is restored.  Sometimes this only happens on
  my secondary display, and the wallpaper is still visible on my primary
  display.

  Please move this bug as appropriate, I wasn't quite sure what to
  report this against.  Compiz?  GNOME?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  Uname: Linux 4.8.0-2.1-liquorix-amd64 x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Thu Oct 27 12:08:50 2016
  DistUpgraded: 2016-10-18 18:39:21,612 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:fa72]
  InstallationDate: Installed on 2014-08-03 (815 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: TOSHIBA Satellite P75-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2.1-liquorix-amd64 
root=UUID=9b00c4ca-5dfe-4d81-89db-3404d87c8820 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (8 days ago)
  dmi.bios.date: 04/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.50:bd04/18/2014:svnTOSHIBA:pnSatelliteP75-A:pvrPSPLNU-04702KB:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P75-A
  dmi.product.version: PSPLNU-04702KB
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 12:28:06 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8349 
   vendor AUO
  xserver.version: 2:1.18.4-1ubuntu6

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

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

[Touch-packages] [Bug 1642353] Re: package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2016-11-16 Thread LocutusOfBorg

I'm trying to reassign to apt then :)

** Package changed: virtualbox-ext-pack (Ubuntu) => apt (Ubuntu)

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

Title:
  package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in apt package in Ubuntu:
  New

Bug description:
  VirtualBox and "extension pack" are working as a charm, this is not a
  but about package virtualbox-ext-pack.

  **This is a something to fix on the crash-reporter process**

  I have pressed CTRL+C or something like that when the installation of
  package virtualbox-ext-pack was displaying me the PUEL licence. And
  the crash-reporter thought I had a problem while installing this
  package. I just wanted to quit the installer (sudo apt install).

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: virtualbox-ext-pack 5.1.6-2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   virtualbox-ext-pack:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov 16 16:51:59 2016
  DpkgTerminalLog:
   Preparing to unpack .../virtualbox-ext-pack_5.1.6-2_all.deb ...
   User did not accept the license.
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/virtualbox-ext-pack_5.1.6-2_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-09-08 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: virtualbox-ext-pack
  Title: package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616107] shutdown-problem-power8

Default Comment by Bridge

** Attachment added: "shutdown-problem-power8"
   
https://bugs.launchpad.net/bugs/1616107/+attachment/4778285/+files/shutdown-problem-power8

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

[Touch-packages] [Bug 1616107] sosreport from the iaos1 host.

Default Comment by Bridge

** Attachment added: "sosreport from the iaos1 host."
   
https://bugs.launchpad.net/bugs/1616107/+attachment/4778284/+files/sosreport-iaos1-20161115131621.tar.xz

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

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

--- Comment From cdead...@us.ibm.com 2016-11-16 13:36 EDT---
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS06682471/JournalErrors.txt on 2016-11-16 12:33:12
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS06682471/shutdown-problem-power8 on 2016-11-16 12:33:12
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS06682471/ProcEnviron.txt on 2016-11-16 12:33:12

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

[Touch-packages] [Bug 1642353] [NEW] package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

You have been subscribed to a public bug:

VirtualBox and "extension pack" are working as a charm, this is not a
but about package virtualbox-ext-pack.

**This is a something to fix on the crash-reporter process**

I have pressed CTRL+C or something like that when the installation of
package virtualbox-ext-pack was displaying me the PUEL licence. And the
crash-reporter thought I had a problem while installing this package. I
just wanted to quit the installer (sudo apt install).

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: virtualbox-ext-pack 5.1.6-2
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 virtualbox-ext-pack:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Nov 16 16:51:59 2016
DpkgTerminalLog:
 Preparing to unpack .../virtualbox-ext-pack_5.1.6-2_all.deb ...
 User did not accept the license.
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/virtualbox-ext-pack_5.1.6-2_all.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2016-09-08 (69 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160907)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: virtualbox-ext-pack
Title: package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages yakkety
-- 
package virtualbox-ext-pack 5.1.6-2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1642353
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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

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

--- Comment From ru...@us.ibm.com 2016-11-16 13:27 EDT---
Reversed mirrored as we can still replicate this with 4.4.0-47.  I'll give the 
proposed 4.8 kernel a try later today.

Regardless of whether the bnx2x vlan filter init error is resolved, it
seems that the nbp_vlan_flush() routine needs to be hardened a bit to
hand a null vlan group (seems like simply posting a warning and
returning would be a better response than panicking since there isn't a
group to flush).

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

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

2016-11-16 Thread Heinrich Hartl

I hope my comment #35 answered the question raised in comment #32.
I do not fully understand the discussion and I am a newbe in that knowledge 
domain however I would like to have the problem solved.
Please let me know if you think the following attempt makes sense.

Grep'ing through /etc I found /etc/network/if-up.d/ntpdate
which is at least one place where ntpdate is used. However there I find also a 
suggestion that we could skip that action!
So I suggest:
#> mv /etc/network/if-up.d/ntpdate /etc/network/if-up.d/ntpdate_bak
#> cat - >/etc/network/if-up.d/ntpdate
#!/bin/sh
exit 0
^d
chmod 755 /etc/network/if-up.d/ntpdate

# now try a reboot and see if the problem (no ntpd running) persists.

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

Title:
  ntpd not started when using ntpdate

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

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

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

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


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

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

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

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

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

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

  What else can I do to debug this further?

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

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

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

2016-11-16 Thread Michael Terry

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

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

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

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Confirmed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

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

** Branch linked: lp:~mterry/policykit-unity8/snap-root

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

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

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Confirmed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

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

Default Comment by Bridge

** Tags added: architecture-ppc64le bugnameltc-148746 severity-high
targetmilestone-inin---

** Attachment added: "sosreport from the iaos1 host."
   
https://bugs.launchpad.net/bugs/1616107/+attachment/4778262/+files/sosreport-iaos1-20161115131621.tar.xz

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

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

2016-11-16 Thread Breno Leitão

Kernel 4.8 just make 16.04 proposed repository. Does it happen on Ubuntu
16.04 with kernel 4.8?

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

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

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

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

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

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

[Touch-packages] [Bug 1642002] Re: Can't install snaps inside unity8-session snap

2016-11-16 Thread Michael Terry

I think the error is in unity8-dash.log:
[2016-11-16:13:09:23.612] RequestAccess failed:
QDBusError("com.ubuntu.OnlineAccountsUi.InvalidApplication", "Invalid client
application")

Which would seem to place the problem in ubuntu-system-settings-online-
accounts. It's ApplicationManagerPrivate::applicationProfile() at the
least looks like it probably doesn't expect this scenario. I'll
reassign there.

** Package changed: unity-scope-snappy (Ubuntu) => ubuntu-system-
settings-online-accounts (Ubuntu)

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

Title:
Can't install snaps inside unity8-session snap

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
New

Bug description:
I'm not sure where the root cause is, but I'm reporting here for now.

I'm inside a unity8-session snap session. My user is logged into
snapd and can remove/install apps on the console.

But inside the snappy scope, pressing the Install button does nothing
visible. No output in logs that I could find, but maybe I wasn't
looking in the right place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1642002/+subscriptions

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

[Touch-packages] [Bug 1642002] [NEW] Can't install snaps inside unity8-session snap

You have been subscribed to a public bug:

I'm not sure where the root cause is, but I'm reporting here for now.

I'm inside a unity8-session snap session.  My user is logged into snapd
and can remove/install apps on the console.

But inside the snappy scope, pressing the Install button does nothing
visible.  No output in logs that I could find, but maybe I wasn't
looking in the right place.

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Can't install snaps inside unity8-session snap
https://bugs.launchpad.net/bugs/1642002
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.

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

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

2016-11-16 Thread Rodney Dawes

I don't know anything about how those staging images based on xenial are
being built exactly, but this sounds like snapd-login-service is missing
for some reason. The libsnapd-glib1 package Recommends it, but it's not
getting pulled into the image.

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

Title:
  error when adding U1 account

Status in ubuntuone-credentials package in Ubuntu:
  New

Bug description:
  Environment:

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

  Steps to reproduce:

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

  Current result: error, screenshot attached

  Expected result: U1 account should be added

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

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

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

2016-11-16 Thread Michael Terry

Unsetting address-book-app as fixed, since it still uses hardcoded
/usr/lib/XXX/unity8/qml path for qml plugin lookups.

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

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

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

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Confirmed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1556274] Re: MX4 bluetooth not pairing with Jaguar XKR 2007

2016-11-16 Thread Dave H

Hi, Just wondered if anyone was looking at the above. My Meizu MX4 is
now on OTA-13 and although the car can see the phone and identifies it
as an MX4 it will not pair with the phone. I can understand that it may
not be possible to use the high end feature of the Jaguar blue-tooth
connection but I would have though the car should at least pair with the
phone.

Any idea's would be welcome. Thanks for your continued great work.

Regards

Dave H

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

Title:
  MX4 bluetooth not pairing with Jaguar XKR 2007

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi I have an MX4 with OTA-9.1 update installed. The phone has never
  been able to pair with my Jaguar XKR 2007. The car finds the Meizu MX4
  and displays the phone type, but will not pair to it Any help to
  improve this would be appreciated.

  Just to say, really enjoying Ubuntu Touch, once miracast is added it
  will be the one to beat.

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1448179] Re: veth devices still appear in the applet

2016-11-16 Thread Christophe Meron

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

** This bug has been marked a duplicate of bug 1458322
   NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

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

Title:
  veth devices still appear in the applet

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  vethXYZ devices as created by LXC shouldn't be managed or even
  displayed by Network Manager.

  They currently don't appear to be managed (good), but running a few
  hundred containers, having each of them take two lines in the network
  menu makes NM almost unusable.

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

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

[Touch-packages] [Bug 1622002] Fix included in openstack/neutron 10.0.0.0b1

2016-11-16 Thread OpenStack Infra

This issue was fixed in the openstack/neutron 10.0.0.0b1 development
milestone.

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

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

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

[Touch-packages] [Bug 1642304] Re: [Ubuntu 17.04] Add GDB support to record Power ISA 3.0/POWER9 instructions

2016-11-16 Thread Steve Langasek

** Package changed: ubuntu => gdb (Ubuntu)

** Changed in: gdb (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Gerrie de Beer (gdb)

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

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

** Changed in: gdb (Ubuntu)
 Assignee: Gerrie de Beer (gdb) => Matthias Klose (doko)

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

Title:
  [Ubuntu 17.04] Add GDB support to record Power ISA 3.0/POWER9
  instructions

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  This feature aims to add support for GDB to record Power ISA 3.0
  instructions in order to enable reverse debugging on Power9.

  This enablement was already submitted and accepted on upstream GDB:
  
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6ec2b213de6962ceeb81bfa33354ea6e60c57049

  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=de6784544abc97d5e396cb1e83eda1ae09f63d40

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

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

[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

2016-11-16 Thread slash

Gents,

I'm currently in Rc-proposed, so my phone should have received by now
the fix, however the phone still experiencing this bug.

Regards

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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

[Touch-packages] [Bug 1642304] [NEW] [Ubuntu 17.04] Add GDB support to record Power ISA 3.0/POWER9 instructions

You have been subscribed to a public bug:

This feature aims to add support for GDB to record Power ISA 3.0
instructions in order to enable reverse debugging on Power9.

This enablement was already submitted and accepted on upstream GDB:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6ec2b213de6962ceeb81bfa33354ea6e60c57049

https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=de6784544abc97d5e396cb1e83eda1ae09f63d40

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Assignee: Gerrie de Beer (gdb)
 Status: New


** Tags: architecture-ppc64le bot-comment bugnameltc-148607 severity-medium 
targetmilestone-inin1704
-- 
[Ubuntu 17.04] Add GDB support to record Power ISA 3.0/POWER9 instructions
https://bugs.launchpad.net/bugs/1642304
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gdb in Ubuntu.

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

[Touch-packages] [Bug 1639050] Re: Wrong package section, should be in "introspection"

2016-11-16 Thread Michael Biebl

In Debian, the values in debian/control are only used when the package is 
uploaded intially to the archive. The override entry is created from that.
Changing the contents of the archive override is done by the ftp-masters. If 
you later change the contents of debian/control does not have an influence on 
the override file.

So, this needs to be assigned to your ftp masters, they need to fix the
overrides and should be able to do that in one go.

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

Title:
  Wrong package section, should be in "introspection"

Status in webapps-sprint:
  New
Status in libsignon-glib package in Ubuntu:
  Confirmed

Bug description:
  Packages shipping gobject introspection should be in the dedicated
  section "introspection". This archive section was added a while ago,
  see also the corresponding entry in the debian policy 3.9.3.0:

  2.6. Version 3.9.3.0
  

   Released February, 2012.

   2.4
New archive sections _education_, _introspection_, and
_metapackages_ added.

  
  Packages shipping gobject introspection should be named 
gir1.2-NAMESPACE-VERSION.

  Based on the output of apt-cache, the following packages are in the
  wrong section. I didn't file a separate bug for all of them. I would
  appreciate if you can adjust the archive section for all the following
  packages in one go.

  #!/bin/bash

  while read pkg ; do
 apt-cache show $pkg | grep Section | grep -v introspection -q && echo 
$pkg
  done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' )

  
  gir1.2-accounts-1.0
  gir1.2-accountsservice-1.0
  gir1.2-appindicator-0.1
  gir1.2-appindicator3-0.1
  gir1.2-atk-1.0
  gir1.2-atspi-2.0
  gir1.2-bamf-3
  gir1.2-cheese-3.0
  gir1.2-clutter-1.0
  gir1.2-cogl-1.0
  gir1.2-coglpango-1.0
  gir1.2-colord-1.0
  gir1.2-dbusmenu-glib-0.4
  gir1.2-dbusmenu-gtk-0.4
  gir1.2-dbusmenu-gtk3-0.4
  gir1.2-dee-1.0
  gir1.2-ebook-1.2
  gir1.2-edataserver-1.2
  gir1.2-fcitx-1.0
  gir1.2-freedesktop
  gir1.2-gconf-2.0
  gir1.2-gdata-0.0
  gir1.2-gdesktopenums-3.0
  gir1.2-gdkpixbuf-2.0
  gir1.2-gkbd-3.0
  gir1.2-glib-2.0
  gir1.2-gmenu-3.0
  gir1.2-gnomebluetooth-1.0
  gir1.2-gnomedesktop-3.0
  gir1.2-goa-1.0
  gir1.2-gtk-2.0
  gir1.2-gtk-3.0
  gir1.2-gtkclutter-1.0
  gir1.2-gtksource-3.0
  gir1.2-gtop-2.0
  gir1.2-gucharmap-2.90
  gir1.2-gudev-1.0
  gir1.2-gweather-3.0
  gir1.2-hud-2
  gir1.2-hud-client-2
  gir1.2-ido3-0.1
  gir1.2-json-1.0
  gir1.2-lightdm-1
  gir1.2-messagingmenu-1.0
  gir1.2-nautilus-3.0
  gir1.2-networkmanager-1.0
  gir1.2-notify-0.7
  gir1.2-packagekitglib-1.0
  gir1.2-pango-1.0
  gir1.2-peas-1.0
  gir1.2-polkit-1.0
  gir1.2-rb-3.0
  gir1.2-rest-0.7
  gir1.2-rest-extras-0.7
  gir1.2-rsvg-2.0
  gir1.2-signon-1.0
  gir1.2-soup-2.4
  gir1.2-telepathyglib-0.12
  gir1.2-timezonemap-1.0
  gir1.2-totem-1.0
  gir1.2-totem-plparser-1.0
  gir1.2-unity-5.0
  gir1.2-upowerglib-1.0
  gir1.2-wnck-3.0
  gir1.2-evince-3.0
  gir1.2-geocodeglib-1.0
  gir1.2-libertine
  gir1.2-nmgtk-1.0
  gir1.2-ubuntu-app-launch-2
  gir1.2-anjuta-3.0
  gir1.2-atril
  gir1.2-caja
  gir1.2-caribou-1.0
  gir1.2-champlain-0.12
  gir1.2-cryptui-0.0
  gir1.2-diodon-1.0
  gir1.2-eom
  gir1.2-evd-0.1
  gir1.2-folks-0.6
  gir1.2-gdl-3
  gir1.2-gssdp-1.0
  gir1.2-gtk-vnc-2.0
  gir1.2-gtkchamplain-0.12
  gir1.2-gupnp-1.0
  gir1.2-gupnp-av-1.0
  gir1.2-gupnpigd-1.0
  gir1.2-indicate-0.7
  gir1.2-itl-1.0
  gir1.2-keybinder-3.0
  gir1.2-maliit-1.0
  gir1.2-mate-menu
  gir1.2-mate-panel
  gir1.2-mate-polkit
  gir1.2-matekbd
  gir1.2-mutter-3.0
  gir1.2-spice-client-glib-2.0
  gir1.2-spice-client-gtk-3.0
  gir1.2-telepathylogger-0.2
  gir1.2-urfkill-glib0
  gir1.2-v-sim-1.0
  gir1.2-gladeui-2.0
  gir1.2-grip
  gir1.2-javascriptcoregtk-3.0
  gir1.2-libvirt-glib-1.0
  gir1.2-nemo-3.0
  gir1.2-snapd-1
  gir1.2-webkit-3.0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 22:02:42 2016
  InstallationDate: Installed on 2011-11-10 (1819 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libaccounts-glib
  UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1639050/+subscriptions

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

Could you also share hte output of

xargs -n 1 -0 < /proc/`pidof unity8`/enviro | grep QT_

in case there are Qt dynamic scaling env vars set in your environment
too. (e.g. QT_DEVICE_PIXEL_RATIO, QT_AUTO_SCREEN_SCALE_FACTOR,
QT_SCALE_FACTOR, QT_SCREEN_SCALE_FACTORS)

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

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

--- Comment From bren...@br.ibm.com 2016-11-16 10:41 EDT---
*** This bug has been marked as a duplicate of bug 148607 ***

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

Title:
  [Ubuntu 15.10] GDB improvements

Status in gdb package in Ubuntu:
  Invalid

Bug description:
  This is a feature to track the new features on GDB on Ubuntu 15.10.

  The request is to add TAR register support,  PPR, DSCR as
  miscellaneous registers. This request also covers a set of TM related
  ptrace requests covering related SPR and various check-pointed
  registers.

  Leader: Edjunior Barbosa

  Bugs:

  https://bugs.launchpad.net/tasty-taco/+bug/1278706 ( gdb not able to
  display TAR register )

  == Comment: #1 - Edjunior Barbosa Machado  - 2014-07-11 
10:27:00 ==
  It depends on kernel enablement, updating Power ptrace interface to have 
access to the new registers (bug #104280)

  == Comment: #2 - Breno Henrique Leitao  - 2014-07-14 
08:45:19 ==
  Ed,

  It seems that the patch was finally accepted in

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=96d016108640bc2b7fb0ee800737f80923847294

  Is it correct?

  == Comment: #3 - Edjunior Barbosa Machado  - 2014-07-14 
08:54:37 ==
  (In reply to comment #2)
  > Ed,
  >
  > It seems that the patch was finally accepted in
  >
  > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/
  > ?id=96d016108640bc2b7fb0ee800737f80923847294
  >
  > Is it correct?

  This is actually a fix for a issue related to DSCR value that were
  being discussed when the ptrace patch was submitted (as mentioned in
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=104280#c5). The
  patchset updating the ptrace interface to include the new registers is
  still waiting for review in the kernel mailing list.

  == Comment: #4 - Breno Henrique Leitao  - 2014-07-14 
15:49:53 ==
  > the patchset
  > updating the ptrace interface to include the new registers is still waiting
  > for review in the kernel mailing list.
  Right, what is the status on the GDB part? Is it already done, or, does it 
depend on those patches accepted before starting the development?

  == Comment: #5 - Edjunior Barbosa Machado  - 2014-07-14 
16:15:07 ==
  (In reply to comment #4)
  > > the patchset
  > > updating the ptrace interface to include the new registers is still 
waiting
  > > for review in the kernel mailing list.
  > Right, what is the status on the GDB part? Is it already done, or, does it
  > depend on those patches accepted before starting the development?

  GDB part is depending on the kernel side patches to start the
  development.

  == Comment: #6 - Breno Henrique Leitao  - 2014-08-25 
16:22:58 ==
  This is going to be deferred to Ubuntu 15.04.

  Si Yuan, let me know if it doesn't work for you.

  == Comment: #7 - Application Cdeadmin  - 2014-11-10 
12:01:35 ==
  default problem description

  == Comment: #11 - Breno Henrique Leitao  - 2015-01-27 
07:15:01 ==
  Deferring to 15.10.

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

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

[Touch-packages] [Bug 1522414] Re: [Ubuntu 15.10] GDB improvements

2016-11-16 Thread Breno Leitão

This feature will be split in minor other features. So, this one can be
kept closed.

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

Title:
  [Ubuntu 15.10] GDB improvements

Status in gdb package in Ubuntu:
  Invalid

Bug description:
  This is a feature to track the new features on GDB on Ubuntu 15.10.

  The request is to add TAR register support,  PPR, DSCR as
  miscellaneous registers. This request also covers a set of TM related
  ptrace requests covering related SPR and various check-pointed
  registers.

  Leader: Edjunior Barbosa

  Bugs:

  https://bugs.launchpad.net/tasty-taco/+bug/1278706 ( gdb not able to
  display TAR register )

  == Comment: #1 - Edjunior Barbosa Machado  - 2014-07-11 
10:27:00 ==
  It depends on kernel enablement, updating Power ptrace interface to have 
access to the new registers (bug #104280)

  == Comment: #2 - Breno Henrique Leitao  - 2014-07-14 
08:45:19 ==
  Ed,

  It seems that the patch was finally accepted in

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/?id=96d016108640bc2b7fb0ee800737f80923847294

  Is it correct?

  == Comment: #3 - Edjunior Barbosa Machado  - 2014-07-14 
08:54:37 ==
  (In reply to comment #2)
  > Ed,
  >
  > It seems that the patch was finally accepted in
  >
  > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/
  > ?id=96d016108640bc2b7fb0ee800737f80923847294
  >
  > Is it correct?

  This is actually a fix for a issue related to DSCR value that were
  being discussed when the ptrace patch was submitted (as mentioned in
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=104280#c5). The
  patchset updating the ptrace interface to include the new registers is
  still waiting for review in the kernel mailing list.

  == Comment: #4 - Breno Henrique Leitao  - 2014-07-14 
15:49:53 ==
  > the patchset
  > updating the ptrace interface to include the new registers is still waiting
  > for review in the kernel mailing list.
  Right, what is the status on the GDB part? Is it already done, or, does it 
depend on those patches accepted before starting the development?

  == Comment: #5 - Edjunior Barbosa Machado  - 2014-07-14 
16:15:07 ==
  (In reply to comment #4)
  > > the patchset
  > > updating the ptrace interface to include the new registers is still 
waiting
  > > for review in the kernel mailing list.
  > Right, what is the status on the GDB part? Is it already done, or, does it
  > depend on those patches accepted before starting the development?

  GDB part is depending on the kernel side patches to start the
  development.

  == Comment: #6 - Breno Henrique Leitao  - 2014-08-25 
16:22:58 ==
  This is going to be deferred to Ubuntu 15.04.

  Si Yuan, let me know if it doesn't work for you.

  == Comment: #7 - Application Cdeadmin  - 2014-11-10 
12:01:35 ==
  default problem description

  == Comment: #11 - Breno Henrique Leitao  - 2015-01-27 
07:15:01 ==
  Deferring to 15.10.

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

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

[Touch-packages] [Bug 1639737] Re: New Version of JasPer JPEG2000 Software Available

2016-11-16 Thread Michael Adams

Just an update:
The latest tarball release of JasPer (on the JasPer web site) is now version 
1.900.29:
http://www.ece.uvic.ca/~frodo/jasper/software/jasper-1.900.29.tar.gz

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

Title:
  New Version of JasPer JPEG2000 Software Available

Status in jasper package in Ubuntu:
  New

Bug description:
  I hope that this is not inappropriate to submit as a bug report.

  As best I can tell, it seems that Ubuntu Zesty (as well as other
  versions) is using JasPer version 1.900.1.  This version of the JasPer
  software is very old and numerous bug fixes have been made since the
  time that this old version was released. It is possible to adopt a
  newer version of JasPer the from upstream source?

  The most recent version of JasPer is 1.900.22.  See the JasPer web site for 
details:
  http://www.ece.uvic.ca/~mdadams/jasper

  A link to the 1.900.22 release tarball is as follows:
  http://www.ece.uvic.ca/~frodo/jasper/software/jasper-1.900.22.tar.gz

  Or alternatively you could just pull code from the master branch of the 
official JasPer Git repository on GitHub:
  https://github.com/mdadams/jasper

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

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

[Touch-packages] [Bug 1642289] [NEW] package cups-daemon 2.2.0-2 failed to install/upgrade: le sous-processus nouveau script pre-removal a retourné une erreur de sortie d'état 1

2016-11-16 Thread Aurélien MANCA

Public bug reported:

Occured on reboot after a fatal shutdown

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: cups-daemon 2.2.0-2
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CupsErrorLog:
 
Date: Wed Nov  2 09:01:57 2016
ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
InstallationDate: Installed on 2013-12-27 (1054 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
Lpstat:
 device for DCP9010CN: lpd://192.168.1.75/binary_p1
 device for PSDIMPVER17: smb://SD-PRINT2k8-01/PSDIMPVER17
MachineType: ASUSTeK COMPUTER INC. UX302LG
Papersize: a4
PpdFiles:
 DCP9010CN: Brother DCP-9010CN CUPS
 PSDIMPVER17: Xerox WorkCentre 7335 Foomatic/Postscript (recommended)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=0252779d-5d7d-4442-85cb-152a9bf5a2dd ro quiet splash acpi_osi= 
vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=0252779d-5d7d-4442-85cb-152a9bf5a2dd ro quiet splash acpi_osi= 
vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: cups
Title: package cups-daemon 2.2.0-2 failed to install/upgrade: le sous-processus 
nouveau script pre-removal a retourné une erreur de sortie d'état 1
UpgradeStatus: Upgraded to yakkety on 2016-10-31 (16 days ago)
dmi.bios.date: 10/30/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX302LG.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX302LG
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX302LG
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-03-12T09:17:22.851984

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


** Tags: amd64 apport-package yakkety

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

Title:
  package cups-daemon 2.2.0-2 failed to install/upgrade: le sous-
  processus nouveau script pre-removal a retourné une erreur de sortie
  d'état 1

Status in cups package in Ubuntu:
  New

Bug description:
  Occured on reboot after a fatal shutdown

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: cups-daemon 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Nov  2 09:01:57 2016
  ErrorMessage: le sous-processus nouveau script pre-removal a retourné une 
erreur de sortie d'état 1
  InstallationDate: Installed on 2013-12-27 (1054 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  Lpstat:
   device for DCP9010CN: lpd://192.168.1.75/binary_p1
   device for PSDIMPVER17: smb://SD-PRINT2k8-01/PSDIMPVER17
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  Papersize: a4
  PpdFiles:
   DCP9010CN: Brother DCP-9010CN CUPS
   PSDIMPVER17: Xerox WorkCentre 7335 Foomatic/Postscript (recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=0252779d-5d7d-4442-85cb-152a9bf5a2dd ro quiet splash acpi_osi= 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=0252779d-5d7d-4442-85cb-152a9bf5a2dd ro quiet splash acpi_osi= 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: cups
  Title: package cups-daemon 2.2.0-2 failed to install/upgrade: le 
sous-processus nouveau script pre-removal a retourné une erreur de sortie 
d'état 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (16 days ago)
  dmi.bios.date: 10/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor:

[Touch-packages] [Bug 1642286] [NEW] Package immune to --yes --force-yes when deployed with chef

2016-11-16 Thread Stoyan Ivanov

Public bug reported:

The sudo package exists in every server base in our infrastructure. For 
security reasons we want to keep it updated. By default the Chef resource that 
handles apt-get installs has -y. The sudo package still failed to install 
asking for a decision on the keeping or replacing of the /etc/sudoers file. It 
fails even if --force-yes is specified. I did not manage to find a way to 
automatically answer on this process, even though there is a default action - 
No, it still spits out the lovely:
Configuration file '/etc/sudoers'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** sudoers (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package sudo 
(--configure):
This caused massive issues in our infrastructure as all the deploys failed the 
first time when they hit the sudo package upgrade. A second deploy magically 
fixes the problem.

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

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

Title:
  Package immune to --yes --force-yes when deployed with chef

Status in sudo package in Ubuntu:
  New

Bug description:
  The sudo package exists in every server base in our infrastructure. For 
security reasons we want to keep it updated. By default the Chef resource that 
handles apt-get installs has -y. The sudo package still failed to install 
asking for a decision on the keeping or replacing of the /etc/sudoers file. It 
fails even if --force-yes is specified. I did not manage to find a way to 
automatically answer on this process, even though there is a default action - 
No, it still spits out the lovely:
  Configuration file '/etc/sudoers'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** sudoers (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package sudo 
(--configure):
  This caused massive issues in our infrastructure as all the deploys failed 
the first time when they hit the sudo package upgrade. A second deploy 
magically fixes the problem.

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

Oops, safer to use grep:

xargs -n 1 -0 < /proc/`pidof unity8`/environ | grep GRID_UNIT

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

Contents of $HOME/.cache/upstart/unity8.log might be handy 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/1642272

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

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

2016-11-16 Thread Bill Filler

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

** Changed in: messaging-app (Ubuntu)
 Assignee: Tiago Salem Herrmann (tiagosh) => Renato Araujo Oliveira Filho 
(renatofilho)

** Changed in: dialer-app (Ubuntu)
 Assignee: Gustavo Pichorim Boiko (boiko) => Renato Araujo Oliveira Filho 
(renatofilho)

** Changed in: dialer-app (Ubuntu)
   Status: Fix Committed => In Progress

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

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

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in address-book-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  New
Status in indicator-transfer package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1642259] Re: [Design Suggestion] App Settings on desktop

2016-11-16 Thread Michał Sawicz

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

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

** Also affects: ubuntu-terminal-app
   Importance: Undecided
   Status: New

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

Title:
  [Design Suggestion] App Settings on desktop

Status in Ubuntu Terminal App:
  New
Status in Ubuntu UX:
  New
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I think that Unity 8 app settings in look weird on desktop, especially
  when the window is larger.

  My suggestion is that at a certain size the menu stays where it is
  instead of stretching across the screen, so that it would look like in
  the attached image (made an example of the Terminal app).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

Hey,
this is weird. Would you be able to open a terminal and run the following 
command:

xargs -n 1 -0 < /proc/`pidof unity8`/environ | ag GRID_UNIT

(it prints all the environment variables that the unity8 process has, and just 
returns the GRID_UNIT_PX one)
Thanks
-G

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 661735] Re: Black screen on video playback

Unfortunately, X11 video output (XCB) is not a good solution. On my
Thinkpad it produces massive frame drops and color artifacts if I try to
use a zoom level other than 100% oder 200%. This means I cannot watch my
favorite YouTube videos on fullscreen on that computer.

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

2016-11-16 Thread crysman

Unfortunatelly, in my case, the workaround described works only for
first hibernation after fresh boot :/ Any next hibernation would fail
ending-up with a login screen like if I had just locked the desktop.

In dmesg I see some weird info regarding nouveau - see eg. log time time
"8109.997421" in the attachment dmesg.txt.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1641919/+attachment/4778174/+files/dmesg.txt

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

2016-11-16 Thread crysman

This is especially weird:

[ 8071.341105] Suspending console(s) (use no_console_suspend to debug)
[ 8071.341993] nouveau :01:00.0: DRM: suspending console...
[ 8071.342004] nouveau :01:00.0: DRM: suspending display...
[ 8071.342086] nouveau :01:00.0: DRM: evicting buffers...
[ 8071.342087] nouveau :01:00.0: DRM: waiting for kernel channels to go 
idle...
[ 8071.342164] nouveau :01:00.0: fifo: read fault at a7 engine 07 
[PFIFO] client 06 [PFIFO] reason 00 [PT_NOT_PRESENT] on channel 0 [003fe12000 
DRM]
[ 8071.342166] nouveau :01:00.0: fifo: fifo engine fault on channel 0, 
recovering...
[ 8086.338867] nouveau :01:00.0: DRM: failed to idle channel 0 [DRM]
[ 8086.338868] nouveau :01:00.0: DRM: resuming display...
[ 8086.339317] pci_pm_freeze(): nouveau_pmops_freeze+0x0/0x20 [nouveau] returns 
-16
[ 8086.339327] dpm_run_callback(): pci_pm_freeze+0x0/0xf0 returns -16
[ 8086.339336] PM: Device :01:00.0 failed to freeze async: error -16

** Also affects: nouveau-firmware (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  New

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1642259] Re: [Design Suggestion] App Settings on desktop

2016-11-16 Thread Michał Sawicz

This is not a unity8 issue, every app needs to do it for themselves. The
UI Toolkit might be able to help here, still.

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

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

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

Title:
  [Design Suggestion] App Settings on desktop

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  I think that Unity 8 app settings in look weird on desktop, especially
  when the window is larger.

  My suggestion is that at a certain size the menu stays where it is
  instead of stretching across the screen, so that it would look like in
  the attached image (made an example of the Terminal app).

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

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

[Touch-packages] [Bug 1642272] Re: incorrect UI scale on high-resolution desktop

2016-11-16 Thread Lukáš Tinkl

What Qt version do you have installed?

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

Title:
  incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  On a hidpi display, the unity8 desktop session in 16.10 has an
  oversized and inconsistent UI scale. The unity8 session is absolutely
  not usable for testing (because there is not even enough screen space
  to display the logout menu item).

  The shell+cursor is rendered with a UI scale of at least 2× the correct scale 
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus 
collapse immediately after clicking because they are larger than the screen 
height.
  The content of the scopes window is rendered with 4× the correct scale, 
giving space for only one icon.

  In unity 16.04, the correct scale could be achieved by setting "export
  GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
  remove or change it. The issue is also in the guest session.

  
  Ubuntu version: 16.10 (fresh install)

  unity8 version: 8.14+16.10.20160 amd64

  physical resolution: 3200×1800

  resolution used by unity8: 3200×1800 (at first sight I thought it
  selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 1642272] [NEW] incorrect UI scale on high-resolution desktop

2016-11-16 Thread Andreas E.

Public bug reported:

On a hidpi display, the unity8 desktop session in 16.10 has an oversized
and inconsistent UI scale. The unity8 session is absolutely not usable
for testing (because there is not even enough screen space to display
the logout menu item).

The shell+cursor is rendered with a UI scale of at least 2× the correct scale
(e.g. 4× the scale of a low-dpi display). Due to this the indicator menus
collapse immediately after clicking because they are larger than the screen
height.
The content of the scopes window is rendered with 4× the correct scale, giving
space for only one icon.

In unity 16.04, the correct scale could be achieved by setting "export
GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I
remove or change it. The issue is also in the guest session.

Ubuntu version: 16.10 (fresh install)

unity8 version: 8.14+16.10.20160 amd64

physical resolution: 3200×1800

resolution used by unity8: 3200×1800 (at first sight I thought it
selected a low resolution, but in fact fonts are very sharp).

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

** Attachment added: "photo showing the shell 2× too big and the scopes 4× too
big"

https://bugs.launchpad.net/bugs/1642272/+attachment/4778139/+files/IMG_20161116_141005.jpg

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

Title:
incorrect UI scale on high-resolution desktop

Status in unity8 package in Ubuntu:
New

Bug description:
On a hidpi display, the unity8 desktop session in 16.10 has an
oversized and inconsistent UI scale. The unity8 session is absolutely
not usable for testing (because there is not even enough screen space
to display the logout menu item).

Ubuntu version: 16.10 (fresh install)

unity8 version: 8.14+16.10.20160 amd64

physical resolution: 3200×1800

resolution used by unity8: 3200×1800 (at first sight I thought it
selected a low resolution, but in fact fonts are very sharp).

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

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

[Touch-packages] [Bug 661735] Re: Black screen on video playback

Possible dupe:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/108769

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 1641092] Re: Does not support patterns containing newline

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

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

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

Title:
  Does not support patterns containing newline

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  $ printf 'a
  b\0b' | grep --null-data "a
  b" |  hexdump -C
    61 0a 62 00 62 00 |a.b.b.|
  0006

  expect
    61 0a 62

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: grep 2.25-1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 11 12:58:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (355 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: grep
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (139 days ago)

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

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

[Touch-packages] [Bug 1551464] Re: apt-get sources should support TLS SNI (server name)

2016-11-16 Thread David Kalnischkies

That would be horrible… If you contact a server foo.example.org it
should respond with the cert for it, not with a cert for
bar.example.com. That is what SNI is all about after all (as your client
connects to an IP and SNI is telling the server which hostname it wanted
to connect to, so the server can respond with the right cert).

I somehow doubt a highlevel interface like libcurl even exposes such a
detail. The bugreport you reference is speculating about all sorts of
things, so one of them might be it. I would personally consider a bug in
libcurl-gnutls most likely (note that this is not always the library
behind curl. It seems to be in newer releases, older releases use
libcurl (the openssl variant)).

As an additional datapoint: On Debian stretch the command "/usr/lib/apt
/apt-helper download-file
'https://deb.nodesource.com/gpgkey/nodesource.gpg.key' 'nodesource.gpg'"
works just fine, so in newer versions that seems resolved.

Anyway, this report is a mixture between a feature request we will not
be implement and a bug we don't have – as such marked as invalid in apt
as you are better of finding the real culprit and report a new bug
against that.

P.S.: apt doesn't need https for integrity. Given the sorry state of CAs
(compare e.g. StartSSL/WoSign) that wouldn't really be secure… There are
other reasons you might want https even in case of apt, but blank
statements aren't making anyone more secure – they just make them feel
secure.

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

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

Title:
  apt-get sources should support TLS SNI (server name)

Status in apt package in Ubuntu:
  Invalid

Bug description:
  There needs to be an option in apt source.list entries to specify the
  server name to be used by TLS for the Server Name Indication (SNI).

  The openSSL equivalent is '-servername'.

  Currently, when accessing sources over https when multiple names are
  used on the same IP address, there is no way to specify which server
  name should be used and so the default name is always used.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.11
  ProcVersionSignature: Ubuntu 4.2.0-30.35~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Mon Feb 29 17:25:22 2016
  InstallationDate: Installed on 2016-02-26 (3 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1642259] [NEW] [Design Suggestion] App Settings on desktop

2016-11-16 Thread Kay

Public bug reported:

I think that Unity 8 app settings in look weird on desktop, especially
when the window is larger.

My suggestion is that at a certain size the menu stays where it is
instead of stretching across the screen, so that it would look like in
the attached image (made an example of the Terminal app).

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


** Tags: app apps mir settings unity8

** Attachment added: "Unity8MenuDesktop.png"
   
https://bugs.launchpad.net/bugs/1642259/+attachment/4778127/+files/Unity8MenuDesktop.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/1642259

Title:
  [Design Suggestion] App Settings on desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  I think that Unity 8 app settings in look weird on desktop, especially
  when the window is larger.

  My suggestion is that at a certain size the menu stays where it is
  instead of stretching across the screen, so that it would look like in
  the attached image (made an example of the Terminal app).

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

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

[Touch-packages] [Bug 661735] Re: Black screen on video playback

I tested some VLC output modules on the AOD255E:
VDPAU video output: no video
XVideo video output (XCB): black video
OpenGL GLX video output (XCB): degraded as with gnome-mplayer
X11 video output (XCB): "stairways" when diagonal objects move very fast, but 
acceptable in all other aspects, so I'll just use that for now.

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

2016-11-16 Thread Alan Robertson

Sorry I didn't update this, but somewhere along the line, the problem
went away - after another set of updates. I'm not sure which one(s). But
it is definitely working again.

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

Title:
  Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I just took some updates to a number of graphic libraries on 16.04,
  and now I can't login to kubuntu. The symptom is that it takes my
  password on the greeter screen, but never updates the screen after
  that.

  The messages include these possibly related kernel messages:
  kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] 
*ERROR* uncleared fifo underrun on pipe B
  kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] 
*ERROR* CPU pipe B FIFO underrun

  I'm currently running kernel 4.4.0-36.

  Here are my most recent updates. The problem started after I rebooted.
  Of course that was the next time I logged in too...

  Start-Date: 2016-09-07 08:46:04
  Commandline: /usr/bin/unattended-upgrade
  Remove: libcdaudio1:amd64 (0.99.12p2-14), 
linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), 
linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), 
gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 
(0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), 
linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 
(1.28+cvs20151130-1)
  End-Date: 2016-09-07 08:48:13

  Start-Date: 2016-09-07 16:42:27
  Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), 
libgnome-keyring0:amd64 (3.12.0-1build1, automatic)
  Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), 
libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 
(11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 
(1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2
 743.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), 
libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), 
libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 
(0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 
0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 
11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 
(51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), 
ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 
14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 
1.8.3-2ubuntu3.1)
  End-Date: 2016-09-07 16:44:34

  Start-Date: 2016-09-12 14:31:39
  Commandline: /usr/sbin/synaptic
  Requested-By: alanr (1000)
  Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 
(0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), 
accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), 
libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2)
  End-Date: 2016-09-12 14:32:17

  
  It was after rebooting after updates that this occurred. My workaround is "rm 
-fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can 
log in...

  If I try to log in again without doing this, the problem recurs. This
  happens even if I just log in and log back out, and try to log in
  again.

  However, I may just found a better workaround - press ALT-CTRL-F1 then
  ALT-CTRL-F7, and then the next chunk of the login sequence occurs.

  This makes it consistent with an issue reported in AskUbuntu
  http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen-
  hangs

  And it's possibly related to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779 - because
  of the CPU underrun being apparently related to

[Touch-packages] [Bug 661735] Re: Black screen on video playback

When I "watch" a black video in VLC on the AOD255E or the bug-affected
Thinkpad, take a screenshot of thath blackness and display the image
file in eog, I see what I'd expect to have seen in the video at that
position.

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails

2016-11-16 Thread Masoud Kazemi

I have exactly the same problem on Ubuntu 16.04. I have created a vpn
connection and it disconnects after almost 5 minutes. One weird thing is
that the laptop fan starts working with a high speed and exactly at the
same moment the vpn disconnects.

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

Title:
  VPN Connects Successfully & Then Shortly Thereafter Fails

Status in network-manager-pptp:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am able to successfully establish a PPTP VPN connection in Ubuntu
  12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to
  1.5 minutes it will fail.  During the connection time I am only able
  to load about 1-2 webpages and then they freeze and I cannot access
  resources on the VPN network.  I do not believe this is related to my
  VPN server as I am able to establish VPN connections with my Windows
  machines and Smartphones all day long with no problems.  Is there a
  solution to this problem?

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  network-manager: 0.9.4.0-0ubuntu3

  Here is the syslog:

  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  Starting VPN 
service 'pptp'...
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN service 'pptp' 
started (org.freedesktop.NetworkManager.pptp), PID 15069
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN service 'pptp' 
appeared; activating connections
  Apr 30 00:17:50 satellite-p755 NetworkManager[994]:  VPN plugin state 
changed: starting (3)
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:  VPN connection 
'Schaefer Law Group' (Connect) reply received.
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin 
/usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
  Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0
  Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 
log[main:pptp.c:314]: The synchronous pptp option is NOT activated
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
  Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 
'Outgoing-Call-Request'
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
  Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 
log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's 
call ID 0).
  Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded
  Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless 
compression enabled
  Apr 30 00:17:55 satellite-p755 pppd[15073]: local  IP address 192.168.1.20
  Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1
  Apr 30 00:17:55 satellite-p755 pppd[15073]: primary   DNS address 8.8.8.8
  Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  VPN connection 
'Schaefer Law Group' (IP Config Get) reply received.
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  VPN Gateway: 
75.75.79.330
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Tunnel Device: ppp0
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Internal IP4 
Address: 192.168.1.20
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Internal IP4 
Prefix: 32
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Internal IP4 
Point-to-Point Address: 192.168.1.1
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Maximum Segment 
Size (MSS): 0
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Forbid Default 
Route: no
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Internal IP4 DNS: 
8.8.8.8
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  Internal IP4 DNS: 
8.8.4.4
  Apr 30 00:17:55 satellite-p755 NetworkManager[994]:  DNS Domain: 
'(none)'
  Apr 30 00:17:56 satellite-p755 dnsmasq[14712]: exiting on receipt of SIGTERM
  Apr 30

[Touch-packages] [Bug 661735] Re: Black screen on video playback

In case it helps: On the AOD255E, lspci | grep VGA | cut -d : -sf 3-
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller
On the AOD360:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller
 (however, this one runs on Ubuntu precise, so maybe I should just try
  and downgrade the AOD255E.)
On the Thinkpad:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller (rev 09)
On another Thinkpad that can play video with no problems:
 Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 1642240] [NEW] package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de sal

2016-11-16 Thread Luis Herrera

Public bug reported:

package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
install/upgrade: el subproceso instalado el script post-installation
devolvió el código de salida de error 1

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Tue Nov 15 20:02:19 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2014-09-26 (781 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: url-dispatcher
Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 1
UpgradeStatus: Upgraded to yakkety on 2016-10-18 (29 days ago)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Nov 15 20:02:19 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2014-09-26 (781 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (29 days ago)

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

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

[Touch-packages] [Bug 661735] Re: Black screen on video playback

Same problem on xenial in an Acer Aspire One 255 (AOD255E), also in VLC.
gnome-mplayer shows the video but at a very slow frame rate, and in
cases where it has to scale the image up to make it fill the screen, the
image quality is worse than on an Acer Aspire One 360 with VLC (same
resolution, full screen, no frame skips). I guess that gnome-mplayer
used software rendering, most probably because hardware video
acceleration was unavailable. The latter would explain why other media
players failed.

Also a Thinkpad on precise started to have the all-black video problem
some time in spring or summer of 2016; I had thought this was just an
end-of-support thing precise is quite old now. On the Thinkpad, VLC and
gnome-mplayer also show the video as just black.

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

Title:
  Black screen on video playback

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  On a Lucid clean install, I cannot play any kind of video using Totem. I just 
get the audio and a black screen and after that I get the same black screen on 
any video player I try (mplayer, vlc, xine, etc.). If I don't open totem first, 
I can see the videos on the other players. I tried disabling compiz, but get 
the same behavior.
  I also tried gst-launch playbin uri=file:///path/to/vid and that works Ok.
  Please, tell me if you need any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libgstreamer0.10-0 0.10.28-1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Oct 16 10:38:09 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_AR.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/661735/+subscriptions

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

[Touch-packages] [Bug 661735] Re: Black screen on video playback